From mboxrd@z Thu Jan 1 00:00:00 1970 From: "pelzflorian (Florian Pelz)" Subject: bug#35996: User account password got locked when booting old generation Date: Tue, 4 Jun 2019 16:12:17 +0200 Message-ID: <20190604141217.7tq33idseebne5v2@pelzflorian.localdomain> References: <87r28dc7gw.fsf@gnu.org> <20190602070545.xp2pqlnzsthpjtbw@pelzflorian.localdomain> <87sgss9vj7.fsf@gnu.org> <20190602102122.bzapwt36vg32nmwq@pelzflorian.localdomain> <87o93g9dv5.fsf@gnu.org> <20190603060301.2nu2zqi5j3v3j5ki@pelzflorian.localdomain> <87tvd6erbo.fsf@gnu.org> <20190603145209.ub7663zp7yh7n7i4@pelzflorian.localdomain> <87d0jtemca.fsf@gnu.org> <20190604121710.uqni7cwp5jo4pwmq@pelzflorian.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([209.51.188.92]:35075) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hYABU-0001Ok-4J for bug-guix@gnu.org; Tue, 04 Jun 2019 10:13:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hYABT-000815-2c for bug-guix@gnu.org; Tue, 04 Jun 2019 10:13:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:60204) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hYABS-0007z9-9n for bug-guix@gnu.org; Tue, 04 Jun 2019 10:13:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hYABS-00018p-2t for bug-guix@gnu.org; Tue, 04 Jun 2019 10:13:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <20190604121710.uqni7cwp5jo4pwmq@pelzflorian.localdomain> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 35996@debbugs.gnu.org On Tue, Jun 04, 2019 at 02:17:11PM +0200, pelzflorian (Florian Pelz) wrote: > On Tue, Jun 04, 2019 at 11:22:45AM +0200, Ludovic Courtès wrote: > > What’s the effect of this brokenness concretely? Is the wrong root file > > system mounted, or something like that? > > > When removing quiet from the linux command line, shepherd complains incessantly that it is trying to load udev. All seems irrelevant, but: > I have multiple broken generation. On one that now for a third time > (on old generations without Ludo’s patches) led to a locked > /etc/shadow after booting I changed the line > (let ((pid (fork+exec-command (list udevd)))) > in gnu/services/base.scm to, I believe, this: > (let ((pid (fork+exec-command (list udevd "--debug-trace")))) > > (I am unsure if this is the same broken generation as on my first > report of the issue. I may have gotten confused.) > > This is unbootable, correct would have been --debug and not > --debug-trace. > The line in /gnu/store/kdql26k1pxgm74d94ryzk8fb4lg5q0ra-shepherd-udev.scm referenced from /gnu/store/b7mrb5pzsbbvhjmi8lbm9xa4wgvqbc7g-shepherd.conf referenced from the broken /var/guix/profiles/system-35-link/boot is (let ((pid (fork+exec-command (list udevd "--debug-trace" "--verbose")))) with an unneeded --verbose. > I may also have changed my syslog configuration to the incorrect > No, the syslog.conf in /gnu/store/y5nrfbj52vlnj77iyki9hbji8qjwk86d-syslog.conf referenced from /gnu/store/5bp6c0p357gaqikxkmvs0idrmvdrzf7h-shepherd-syslogd.scm referenced from /gnu/store/b7mrb5pzsbbvhjmi8lbm9xa4wgvqbc7g-shepherd.conf referenced from the broken /var/guix/profiles/system-35-link/boot appears to be the default syslog.conf. Booting this old generation and then an older working generation sometimes leads to a broken /etc/shadow. I do not yet know if a broken /etc/shadow can result when booting this old generation and then a new patched generation. I will reconfigure some more and try getting a bad /etc/shadow even with Ludo’s patches. Regards, Florian