Re: [gentoo-user] problems getting systemd to work

[covici@ccs.covici.com]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Fri, May 16, 2014 at 12:17 PM,  <covici@ccs.covici.com> wrote:
> [snip]
> >> I don't understand the current situation .So now you get ALL your
> >> volumes activated, or not?
> >
> > Yep, they are all activated and they all get mounted.
> 
> Cool, one problem less.
> 
> >> > Now for some systemd problems.  The root file system was read only when
> >> > I logged in, but I could remount it rw -- not sure why this was
> >> > happening.
> >>
> >> Set systemd.log_level=debug in your command line, and post the exit
> >> from journalctl -b.
> >
> > I had debug in the command line by itself, would that make the correct
> > log_level?  The file is quite large, should I send it to you privately?
> 
> I don't think is necessary, I may have found the real problem (see below).
> 
> >> >  Some units did start, but most did not.  Whenever I tried to
> >> > start one manually, I got a message like the following:
> [snip]
> >> > No matter what unit I tried to start I would get such a  message about
> >> > the service.mount.
> >>
> >> That sounds like a problem with the cgroups hierarchy (which uses a
> >> virtual filesystem). I don't remember seeing a problem like that
> >> before.
> >>
> >> > Also, even though my network names were correct, they did not come up,
> >> > but I will try to look in the logs to see why not.
> > I wrote a service file to start my network adaptors, here it is:
> > network@.service
> >
> >
> > [Unit]
> > Description=Network Connectivity for %i
> > Wants=network.target
> > Before=network.target
> > BindsTo=sys-subsystem-net-devices-%i.device
> > After=sys-subsystem-net-devices-%i.device
> > [Service]
> > Type=oneshot
> > RemainAfterExit=yes
> > EnvironmentFile=/etc/conf.d/network@%i
> > ExecStart=/usr/bin/ip link set dev %i up
> > ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev %i
> > ExecStart=/bin/bash -c 'test -n ${gateway} && /usr/bin/ip route add default via
> > ${gateway}'
> > ExecStart=/bin/bash -c 'test -f /etc/conf.d/postup@%i.sh&&/bin/bash  /etc/conf.d/postup@%i.sh
> > ExecStop=/usr/bin/ip addr flush dev %i
> > ExecStop=/usr/bin/ip link set dev %i down
> > [Install]
> > WantedBy=network.target
> 
> Did you enabled network@ifaca.service? Also, WantedBy=network.target
> doesn't do what you probably think it does (check [1]... and BTW, I
> forgot my last footnote, is now on [2]).
> 
> I would use WantedBy=multi-user.target.
> 
> >> systemd will not (AFAIK) start your network, and before the 209 or 210
> >> version it needed helper program (NetwokrManager, connman, ip,
> >> ifconfig, etc.) to do it. Now it includes networkd, but you need to
> >> set up .network files (like .service files) to configure it. See [1].
> >>
> >> > So we have made some progress, but still a long way to go yet.  Note
> >> > also, that I am not booting into a display manager, just a regular
> >> > console.
> >> >
> >> >
> >> > What a lot of work just to get the system booted!
> >>
> >> Well, you have a setup that is not, by any means, simple. Also, in my
> >> experience old LVM configurations seem to cause a lot of troubles to
> >> bring to what systemd expects.
> >>
> >> John, could you also post here your kernel config? Those cgroups
> >> errors *may* be related to some missing functionality from the kernel.
> 
> [snip kernel config]
> 
> John, your kernel is incorrectly configured to be used by systemd.
> When you installed systemd, a warning should have appeared about some
> missing configure options; you either didn't saw or ignored those
> warnings. Install systemd again so you can see them.
> 
> From what I can tell, you are missing *AT LEAST* the following options:
> 
> CONFIG_AUTOFS4_FS
configured as a module.

> CONFIG_DMIID

set to Y

> CONFIG_FANOTIFY
set to y

> CONFIG_INOTIFY_USER
set to y


> CONFIG_PROC_FS
set to y

> CONFIG_SYSFS
set to y

> 
> John, if you don't set them, systemd *CANNOT WORK PROPERLY*. They are
> mandatory. I'm surprised you are able to boot to a semi-working state.
> 
> Yes, migrating to systemd is a lot of work. But if you don't see (or
> ignore) your system messages, that work gets multiplied several times.
> 
> Reconfigure, recompile, and reinstall your kernel (don't forget to
> reinstall the modules!), regenerate your initramfs, update lilo (if I
> remember correctly, you need to run lilo -something-or-another every
> time you change kernel and/or initramfs), and try again.
> 
> Regards
> 
> [1] http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
> [2] http://www.freedesktop.org/software/systemd/man/systemd.network.html
> -- 
> Canek Peláez Valdés
> Profesor de asignatura, Facultad de Ciencias
> Universidad Nacional Autónoma de México
> 

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com