systemd 213.9 related issues (presumably)

This forum is for discussion about general software issues.

systemd 213.9 related issues (presumably)

Postby sleepymonad » Mon Jun 16, 2014 7:46 am

Subject

Hello

I had the same issue that many of us experienced: the system would not reboot after the recent systemd upgrade. I followed the method described elsewhere (cf. viewtopic.php?f=47&t=7330&p=40153&hilit=systemd#p40153 i.e. reverting back to systemd 212-3) to get my system working again, and soon after that upgraded to systemd 213-9.1.

$this->bbcode_second_pass_code('', ' [root@archy2 ~]# pacman -Q | grep systemd
libsystemd 213-9.1
systemd 213-9.1
systemd-sysvcompat 213-9.1
')

This system was before the upgrade a freshly installed system (utilite hardware), with dovecot and nfsd working. But both with the downgrade to 212-3 and after the re-upgrade to 213-9.1 I have the following services failing:

$this->bbcode_second_pass_code('', ' dovecot.service loaded failed failed Dovecot IMAP/POP3 email ser
nfsd.service loaded failed failed NFS Server Daemon
systemd-modules-load.service loaded failed failed Load Kernel Modules')

with details:

$this->bbcode_second_pass_code('', ' dovecot.service - Dovecot IMAP/POP3 email serversd.service systemd-modules-loa
Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled)
Active: failed (Result: exit-code) since Mon 2014-06-16 09:18:52 CEST; 12s ago
Process: 492 ExecStart=/usr/bin/dovecot -F (code=exited, status=89)
Main PID: 492 (code=exited, status=89)

Jun 16 09:18:51 archy2 systemd[1]: Started Dovecot IMAP/POP3 email server.
Jun 16 09:18:52 archy2 systemd[1]: dovecot.service: main process exited, code=exited, status=89/n/a
Jun 16 09:18:52 archy2 systemd[1]: Unit dovecot.service entered failed state.
Jun 16 09:18:52 archy2 dovecot[492]: Error: socket() failed: Address family not supported by protocol
Jun 16 09:18:52 archy2 dovecot[492]: Error: service(imap-login): listen(::, 143) failed: Address family not supported by protocol
Jun 16 09:18:52 archy2 dovecot[492]: Error: socket() failed: Address family not supported by protocol
Jun 16 09:18:52 archy2 dovecot[492]: Error: service(imap-login): listen(::, 993) failed: Address family not supported by protocol
Jun 16 09:18:52 archy2 dovecot[492]: Fatal: Failed to start listeners

nfsd.service - NFS Server Daemon
Loaded: loaded (/usr/lib/systemd/system/nfsd.service; enabled)
Active: failed (Result: exit-code) since Mon 2014-06-16 09:18:52 CEST; 12s ago
Docs: man:rpc.nfsd(8)
Process: 499 ExecStart=/usr/bin/rpc.nfsd $NFSD_OPTS $NFSD_COUNT (code=exited, status=1/FAILURE)
Main PID: 499 (code=exited, status=1/FAILURE)

Jun 16 09:18:52 archy2 systemd[1]: Starting NFS Server Daemon...
Jun 16 09:18:52 archy2 systemd[1]: nfsd.service: main process exited, code=exited, status=1/FAILURE
Jun 16 09:18:52 archy2 rpc.nfsd[499]: rpc.nfsd: Unable to access /proc/fs/nfsd errno 2 (No such file or directory).
Jun 16 09:18:52 archy2 rpc.nfsd[499]: Please try, as root, 'mount -t nfsd nfsd /proc/fs/nfsd' and then restart rpc.nfsd to correct the problem
Jun 16 09:18:52 archy2 systemd[1]: Failed to start NFS Server Daemon.
Jun 16 09:18:52 archy2 systemd[1]: Unit nfsd.service entered failed state.

systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
Active: failed (Result: exit-code) since Mon 2014-06-16 09:18:52 CEST; 12s ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 493 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 493 (code=exited, status=1/FAILURE)

Jun 16 09:18:52 archy2 systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
Jun 16 09:18:53 archy2 systemd[1]: Failed to start Load Kernel Modules.
Jun 16 09:18:53 archy2 systemd[1]: Unit systemd-modules-load.service entered failed state.
')
Also (trying the suggestion in the log above)

$this->bbcode_second_pass_code('', ' [root@archy2 ~]# mount -t nfsd nfsd /proc/fs/nfsd
mount: unknown filesystem type 'nfsd'
[root@archy2 ~]# ')

I guess these are all somehow related to the systemd upgrade. Any suggestions about how to proceed?

Thank you for your attention
sleepymonad
 
Posts: 6
Joined: Sat Jun 23, 2012 8:07 am

Re: systemd 213.9 related issues (presumably)

Postby WarheadsSE » Mon Jun 16, 2014 11:54 am

Systemd 213-9.1 has cgroups xattr disabled, so this in particular is not the case. Have a look at /etc/passwd.pacnew

viewtopic.php?f=58&t=7396&p=40536#p40536
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: systemd 213.9 related issues (presumably)

Postby sleepymonad » Tue Jun 17, 2014 7:01 am

Thank you for the suggestion.

I checked /etc/passwd and /etc/group and found only some minor differences such as /bin/false instead of /usr/bin/nologin, which I fixed; but no missing entries.

So, the problem persists.
sleepymonad
 
Posts: 6
Joined: Sat Jun 23, 2012 8:07 am

Re: systemd 213.9 related issues (presumably)

Postby sleepymonad » Tue Jun 17, 2014 7:50 am

I have been digging a little deeper, starting with the first failing service (systemd-modules-load.service). The only module needed is

$this->bbcode_second_pass_code('', '[root@archy2 systemd]# cat /usr/lib/modules-load.d/nfs-utils.conf
nfs
[root@archy2 systemd]# lsmod
Module Size Used by
[root@archy2 systemd]# modprobe nfs
[root@archy2 systemd]# lsmod
Module Size Used by
[root@archy2 systemd]# ')

Now I get suspicious: no modules loaded at all? Is this supported in the utilite provided kernel? How can I check?

I also didn't find any nfs module, only nfsd

$this->bbcode_second_pass_code('', '[root@archy2 modules]# find /usr/lib/modules -type f -name \*nfs\* -print
/usr/lib/modules/3.0.35-16-ARCH/kernel/fs/nfsd/nfsd.ko.gz
[root@archy2 modules]# modprobe nfsd
[root@archy2 modules]# lsmod
Module Size Used by
[root@archy2 modules]# ')

Yet I had nfs working before the systemd upgrade...
sleepymonad
 
Posts: 6
Joined: Sat Jun 23, 2012 8:07 am

Re: systemd 213.9 related issues (presumably)

Postby hydro » Tue Jun 17, 2014 7:54 am

Use uname -r to check which kernel is currently running, I guess it's not 3.0.35-16-ARCH.
VDR on DockStar / Pogoplug E02: http://linux.bplaced.net/
hydro
 
Posts: 210
Joined: Wed Jun 15, 2011 2:03 pm
Location: Germany

Re: systemd 213.9 related issues (presumably)

Postby sleepymonad » Tue Jun 17, 2014 11:21 am

That was spot on!

While trying to troubleshoot the issue, I had replaced the kernel with the one from the install media : 3.0.35-15-ARCH. And then, I kind of forgot.. .the joys of multitasking.

Thank you very much
sleepymonad
 
Posts: 6
Joined: Sat Jun 23, 2012 8:07 am


Return to General

Who is online

Users browsing this forum: No registered users and 13 guests