From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (unknown [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 5B5F71381FA for ; Fri, 16 May 2014 18:11:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C6509E0AF9; Fri, 16 May 2014 18:11:32 +0000 (UTC) Received: from mail0131.smtp25.com (mail0131.smtp25.com [75.126.84.131]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B5F20E07A0 for ; Fri, 16 May 2014 18:11:31 +0000 (UTC) Received: from ccs.covici.com (s-out-001.smtp25.com [67.228.91.90]) by d-out-001.smtp25.com (8.14.2/8.14.2) with ESMTP id s4GIBTXg002921 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 16 May 2014 14:11:30 -0400 Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.8/8.14.8) with ESMTP id s4GIBTO7016456 for ; Fri, 16 May 2014 14:11:29 -0400 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] problems getting systemd to work In-reply-to: References: <23736.1399879340@ccs.covici.com> <13680.1399912266@ccs.covici.com> <17066.1399913526@ccs.covici.com> <8704.1400060591@ccs.covici.com> <26238.1400079937@ccs.covici.com> <31967.1400082129@ccs.covici.com> <15515.1400106362@ccs.covici.com> <26096.1400186293@ccs.covici.com> <53753922.201@xunil.at> <13544.1400237631@ccs.covici.com> <8683.1400260656@ccs.covici.com> Comments: In-reply-to =?us-ascii?Q?=3D=3FUTF-8=3FB=3FQ2FuZWsgUGVsw6FleiBWY?= =?us-ascii?Q?Wxkw6lz=3F=3D?= message dated "Fri, 16 May 2014 12:41:56 -0500." X-Mailer: MH-E 8.2; nmh 1.3; GNU Emacs 23.4.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Date: Fri, 16 May 2014 14:11:29 -0400 Message-ID: <16453.1400263889@ccs.covici.com> From: covici@ccs.covici.com X-SpamH-OriginatingIP: 70.109.53.110 X-SpamH-Filter: d-out-001.smtp25.com-s4GIBTXg002921 X-Archives-Salt: de4fa92b-3bce-4277-acc9-799e4877eae0 X-Archives-Hash: a545817bd318e0a07ac825840710fbd9 Canek Pel=C3=A1ez Vald=C3=A9s wrote: > On Fri, May 16, 2014 at 12:17 PM, 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. >=20 > Cool, one problem less. >=20 > >> > Now for some systemd problems. The root file system was read only w= hen > >> > I logged in, but I could remount it rw -- not sure why this was > >> > happening. > >> > >> Set systemd.log_level=3Ddebug 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? >=20 > I don't think is necessary, I may have found the real problem (see below). >=20 > >> > 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 abo= ut > >> > 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 u= p, > >> > 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=3DNetwork Connectivity for %i > > Wants=3Dnetwork.target > > Before=3Dnetwork.target > > BindsTo=3Dsys-subsystem-net-devices-%i.device > > After=3Dsys-subsystem-net-devices-%i.device > > [Service] > > Type=3Doneshot > > RemainAfterExit=3Dyes > > EnvironmentFile=3D/etc/conf.d/network@%i > > ExecStart=3D/usr/bin/ip link set dev %i up > > ExecStart=3D/usr/bin/ip addr add ${address}/${netmask} broadcast ${broa= dcast} dev %i > > ExecStart=3D/bin/bash -c 'test -n ${gateway} && /usr/bin/ip route add d= efault via > > ${gateway}' > > ExecStart=3D/bin/bash -c 'test -f /etc/conf.d/postup@%i.sh&&/bin/bash = /etc/conf.d/postup@%i.sh > > ExecStop=3D/usr/bin/ip addr flush dev %i > > ExecStop=3D/usr/bin/ip link set dev %i down > > [Install] > > WantedBy=3Dnetwork.target >=20 > Did you enabled network@ifaca.service? Also, WantedBy=3Dnetwork.target > doesn't do what you probably think it does (check [1]... and BTW, I > forgot my last footnote, is now on [2]). >=20 > I would use WantedBy=3Dmulti-user.target. >=20 > >> 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. >=20 > [snip kernel config] >=20 > 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. >=20 > From what I can tell, you are missing *AT LEAST* the following options: >=20 > 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 >=20 > 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. >=20 > 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. >=20 > 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. >=20 > Regards >=20 > [1] http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ > [2] http://www.freedesktop.org/software/systemd/man/systemd.network.html > --=20 > Canek Pel=C3=A1ez Vald=C3=A9s > Profesor de asignatura, Facultad de Ciencias > Universidad Nacional Aut=C3=B3noma de M=C3=A9xico >=20 --=20 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