Re: core-updates call for testing

[Marius Bakke <mbakke@fastmail.com>]

[-- Attachment #1: Type: text/plain, Size: 3289 bytes --]

Leo Famulari <leo@famulari.name> writes:

> On Tue, Apr 28, 2020 at 03:17:06PM +0200, Marius Bakke wrote:
>> Leo Famulari <leo@famulari.name> writes:
>> 
>> > I reconfigured my Guix System based on core-updates, and afterwards I
>> > was unable to login, either remotely over SSH, or on the Linux console.
>> 
>> Do you still have the logs from this attempt?  Curious what caused login
>> to fail.
>
> Yes, they are excerpted below. First you'll see the remote login
> attempts, and then the attempts at the Linux console:

Thanks!

> Apr 25 13:57:16 localhost sshd[2731]: Accepted publickey for leo from 192.168.1.101 port 55512 ssh2: ED25519 SHA256:my-key
> Apr 25 13:57:16 localhost sshd[2731]: error: PAM: pam_open_session(): Module is unknown

strace on the ssh server process after reconfiguring on core-updates
shows:

966   sendto(8, "<83>Apr 29 14:38:19 sshd[966]: PAM unable to dlopen(/gnu/store/44il8dnl5qc6ryb3v0lp5374hg3h7vx5-elogind-243.4/lib/security/pam_elogind.so): /gnu/store/ahqgl4h89xqj695lgqvsaf6zh2nhy4pj-glibc-2.29/lib/libc.so.6: version `GLIBC_2.30' not found (required by /gnu/store/44il8dnl5qc6ryb3v0lp5374hg3h7vx5-elogind-243.4/lib/security/pam_elogind.so)", 340, MSG_NOSIGNAL, NULL, 0) = 340
966   getpid()                          = 966
966   sendto(8, "<83>Apr 29 14:38:19 sshd[966]: PAM adding faulty module: /gnu/store/44il8dnl5qc6ryb3v0lp5374hg3h7vx5-elogind-243.4/lib/security/pam_elogind.so", 142, MSG_NOSIGNAL, NULL, 0) = 142

Restarting 'ssh-daemon' allows login to succeed.

[...]

> Apr 25 13:58:17 localhost shepherd[1]: Respawning term-tty1.
> Apr 25 13:58:17 localhost shepherd[1]: Service host-name has been started.   
> Apr 25 13:58:17 localhost shepherd[1]: Service term-tty1 has been started.
> Apr 25 13:58:20 localhost vmunix: [433720.062263] login[2745]: segfault at 0 ip 00007f8fc66d0934 sp 00007fffcf163610 error 4 in libpthread-2.31.so[7f8fc66d0000+f000]
> Apr 25 13:58:20 localhost vmunix: [433720.062271] Code: 82 e8 02 00 00 e0 ff ff ff be 18 00 00 00 b8 11 01 00 00 48 89 ba d8 02 00 00 48 89 ba e0 02 00 00 0f 05 48 8b 05 84 56 01 00 <48> 8b 00 64 48 89 04 25 98 06 00 00 48 8d 05 09 9a 01 00 48 8d 8a

I see a similar failure when tracing the associated mingetty process:

1003  sendto(4, "<83>Apr 29 14:49:20 login[1003]: PAM unable to dlopen(/gnu/store/44il8dnl5qc6ryb3v0lp5374hg3h7vx5-elogind-243.4/lib/security/pam_elogind.so): /gnu/store/ahqgl4h89xqj695lgqvsaf6zh2nhy
4pj-glibc-2.29/lib/libc.so.6: version `GLIBC_2.30' not found (required by /gnu/store/44il8dnl5qc6ryb3v0lp5374hg3h7vx5-elogind-243.4/lib/security/pam_elogind.so)", 342, MSG_NOSIGNAL, NULL, 0) = 342
1003  getpid()                          = 1003
1003  sendto(4, "<83>Apr 29 14:49:20 login[1003]: PAM adding faulty module: /gnu/store/44il8dnl5qc6ryb3v0lp5374hg3h7vx5-elogind-243.4/lib/security/pam_elogind.so", 144, MSG_NOSIGNAL, NULL, 0) = 144

Again running 'herd restart term-tty1' lets me log in successfully.

I'm not sure what to do about this.  Can we get the Shepherd to
automatically restart select services on reconfigure?

For the term-tty services that are started on demand, one fix would be
to have Shepherd start the new service without the explicit 'herd
restart term-tty1' call.

Thoughts?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]