Description of problem: systemd breaks SysV startup scripts; deamons don't start anymore after upgrading to Fedora 15. Version-Release number of selected component (if applicable): systemd-26-2.fc15.x86_64 How reproducible: Have nicely running Fedora 14 box with mysql and mythTV. Upgrade to Fedora 15. After booting into upgraded box notice no mysql and no mythTV. Steps to Reproduce: 1. See above 2. 3. Actual results: Failure of mysql to start due to removed pid directory. After correcting this manually: Failure of mythbackend to start even though systemctl shows 'ok'. Expected results: Started mysql, mythbackend Additional info: [root@recorder user]# service mysqld start Starting mysqld (via systemctl): [ OK ] [root@recorder user]# service mythbackend start Starting mythbackend (via systemctl): [ OK ] [root@recorder user]# ps -ef|grep myth root 4075 2913 0 09:41 pts/0 00:00:00 grep --color=auto myth [root@recorder user]# ps -ef|grep back root 4079 2913 0 09:41 pts/0 00:00:00 grep --color=auto back
Here's the script that now fails: # cat /etc/rc.d/init.d/mythbackend #!/bin/bash - # # Startup script for mythbackend # # chkconfig: - 86 14 # description: mythbackend. # processname: mythbackend # pidfile: /var/run/mythbackend.pid # config: # Source function library. . /etc/rc.d/init.d/functions if [ -f /etc/sysconfig/mythbackend ]; then . /etc/sysconfig/mythbackend fi export HOME ## Defaults, override them in /etc/sysconfig/mythbackend : ${MYTHTV_HOME=/var/lib/mythtv} binary=/usr/bin/mythbackend prog=mythbackend RETVAL=0 OPTIONS="$OPTIONS --daemon --logfile /var/log/mythtv/$prog.log --pidfile /var/run/$prog.pid" start() { echo -n $"Starting $prog: " touch /var/run/mythbackend.pid; chown mythtv:mythtv /var/run/mythbackend.pid # Does not work on Red Hat, do to to missing audio/video groups. cd $MYTHTV_HOME && daemon $binary $OPTIONS RETVAL=$? echo [ $RETVAL = 0 ] && touch /var/lock/subsys/$prog return $RETVAL } stop() { echo -n $"Stopping $prog: " killproc $binary RETVAL=$? echo [ $RETVAL = 0 ] && rm -f /var/lock/subsys/$prog /var/run/$prog.pid } # See how we were called. case "$1" in start) start ;; stop) stop ;; restart) stop start ;; status) status $prog ;; *) echo $"Usage: $prog {start|stop|status|restart}" exit 1 esac exit $RETVAL
(In reply to comment #0) > Failure of mysql to start due to removed pid directory. > After correcting this manually: I'm not seeing any problems with mysql starting on my system. Could you elaborate which directory you was removed and how did you correct it? As for the mythbackend, what does "systemctl status mythbackend.service" show?
Before: nicely running F14. Do the upgrade. Boot into F15. See: 110605 5:45:52 [Note] /usr/libexec/mysqld: Normal shutdown 110605 5:45:52 [Note] Event Scheduler: Purging the queue. 0 events 110605 5:45:53 [Note] /usr/libexec/mysqld: Shutdown complete 110605 05:45:53 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 110605 06:38:59 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 110605 6:38:59 [Warning] '--log_slow_queries' is deprecated and will be removed in a future release. Please use ''--slow_query_log'/'--slow_query_log_file'' instead. 110605 6:38:59 [Note] Plugin 'InnoDB' is disabled. ^G/usr/libexec/mysqld: File '/var/run/mysqld/mysqld-slow.log' not found (Errcode: 2) 110605 6:38:59 [ERROR] Could not use /var/run/mysqld/mysqld-slow.log for logging (error 2). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdo wn the MySQL server and restart it. 110605 6:39:00 [ERROR] /usr/libexec/mysqld: Can't create/write to file '/var/run/mysqld/mysqld.pid' (Errcode: 2) 110605 6:39:00 [ERROR] Can't start server: can't create PID file: No such file or directory 110605 06:39:00 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 110605 07:25:46 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 110605 7:25:46 [Warning] '--log_slow_queries' is deprecated and will be removed in a future release. Please use ''--slow_query_log'/'--slow_query_log_file'' instead. 110605 7:25:46 [Note] Plugin 'InnoDB' is disabled. ^G/usr/libexec/mysqld: File '/var/run/mysqld/mysqld-slow.log' not found (Errcode: 2) 110605 7:25:46 [ERROR] Could not use /var/run/mysqld/mysqld-slow.log for logging (error 2). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdo wn the MySQL server and restart it. 110605 7:25:46 [ERROR] /usr/libexec/mysqld: Can't create/write to file '/var/run/mysqld/mysqld.pid' (Errcode: 2) 110605 7:25:46 [ERROR] Can't start server: can't create PID file: No such file or directory 110605 07:25:46 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 110605 07:27:14 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 110605 7:27:14 [Warning] '--log_slow_queries' is deprecated and will be removed in a future release. Please use ''--slow_query_log'/'--slow_query_log_file'' instead. 110605 7:27:14 [Note] Plugin 'InnoDB' is disabled. 110605 7:27:14 [Note] Event Scheduler: Loaded 0 events 110605 7:27:14 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.50-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 110605 8:47:41 [Note] /usr/libexec/mysqld: Normal shutdown 110605 8:47:41 [Note] Event Scheduler: Purging the queue. 0 events 110605 8:47:41 [Note] /usr/libexec/mysqld: Shutdown complete So why was /var/run/mysqld removed and by what?
w.r.t Comment #2: It showed that the backend had exited.
/var/run is a tmpfs mount. /var/run/mysqld gets created on boot by systemd-tmpfiles-setup.service as requested by /etc/tmpfiles.d/mysql.conf shipped in the mysql-server package. Do you have the /etc/tmpfiles.d/mysql.conf file? What is the version of the mysql-server package?
(In reply to comment #4) > w.r.t Comment #2: It showed that the backend had exited. I'd really prefer the see the output literally. If it exited with an error, it may have produced an error message to stderr, which is unfortunately lost by default. Try booting with: systemd.default_standard_output=syslog And after failing to start mythbackend, see /var/log/messages.
Comment #5: mysql-server-5.5.12-1.fc15.x86_64 We have /etc/tmpfiles.d/mysql.conf Comment #4: I wrote a service file and removed the SysV startup script. Output as it was is in the beginning of the report: [root@recorder user]# service mythbackend start Starting mythbackend (via systemctl): [ OK ] [root@recorder user]# ps -ef|grep myth root 4075 2913 0 09:41 pts/0 00:00:00 grep --color=auto myth [root@recorder user]# ps -ef|grep back root 4079 2913 0 09:41 pts/0 00:00:00 grep --color=auto back No error was show. Nothing additional was written to /var/log/mythtv/mythbackend.log. I don't think that the default of losing errors is very unix-like since in that case we have no information to troubleshoot on as we have right now. So, to reproduce I have to reboot the box?! Another flaw. I'd liek to learn first how to properly (systemd dependencies...) got from my service file back to the SysV script. (just remove service file, put SysV file in place, chkconfig mythbackend on, reboot?) It also means the box is unavailable for what it is supposed to be doing.
[root@recorder linux]# grep systemd /var/log/messages Jun 5 06:38:53 recorder kernel: <30>systemd[1]: systemd 26 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; fedora) Jun 5 06:38:53 recorder kernel: <28>systemd[1]: /sbin/modprobe failed with error code 1. Jun 5 06:38:53 recorder kernel: <30>systemd[1]: Set hostname to <recorder.hierzo>. Jun 5 06:38:53 recorder kernel: <28>systemd[1]: /usr appears to be on a different file system than /. This is not supported anymore. Some things will probably break (sometimes even silently) in mysterious ways. Consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for more information. Jun 5 06:38:53 recorder kernel: <28>systemd[1]: CONFIG_CGROUPS was not set when your kernel was compiled. Systems without control groups are not supported. We will now sleep for 10s, and then continue boot-up. Expect breakage and please do not file bugs. Instead fix your kernel and enable CONFIG_CGROUPS. Jun 5 06:38:53 recorder kernel: <28>systemd[1]: No control group support available, not creating root group. Jun 5 06:38:53 recorder kernel: <27>systemd[1]: Failed to connect to audit log: Protocol not supported Jun 5 06:38:53 recorder kernel: <28>systemd[1]: Found ordering cycle on local-fs.target/start Jun 5 06:38:53 recorder kernel: <30>systemd[1]: Walked on cycle path to fedora-storage-init-late.service/start Jun 5 06:38:53 recorder kernel: <30>systemd[1]: Walked on cycle path to cryptsetup.target/start Jun 5 06:38:53 recorder kernel: <30>systemd[1]: Walked on cycle path to cryptsetup/start Jun 5 06:38:53 recorder kernel: <30>systemd[1]: Walked on cycle path to systemd-random-seed-load.service/start Jun 5 06:38:53 recorder kernel: <30>systemd[1]: Walked on cycle path to local-fs.target/start Jun 5 06:38:53 recorder kernel: <28>systemd[1]: Breaking ordering cycle by deleting job fedora-storage-init-late.service/start Jun 5 06:38:53 recorder kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory Jun 5 06:38:53 recorder kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory Jun 5 06:38:53 recorder kernel: <29>systemd[1]: Unit dev-hugepages.automount entered failed state. Jun 5 06:38:53 recorder kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory Jun 5 06:38:53 recorder kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory Jun 5 06:38:53 recorder kernel: <29>systemd[1]: Unit dev-mqueue.automount entered failed state. Jun 5 06:38:53 recorder kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory Jun 5 06:38:53 recorder kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory Jun 5 06:38:53 recorder kernel: <29>systemd[1]: Unit sys-kernel-security.automount entered failed state. Jun 5 06:38:53 recorder kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory Jun 5 06:38:53 recorder kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory Jun 5 06:38:53 recorder kernel: <29>systemd[1]: Unit proc-sys-fs-binfmt_misc.automount entered failed state. Jun 5 06:38:53 recorder kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory Jun 5 06:38:53 recorder kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory Jun 5 06:38:53 recorder kernel: <29>systemd[1]: Unit sys-kernel-debug.automount entered failed state. Jun 5 06:38:53 recorder kernel: <30>systemd-fsck[1369]: /dev/mapper/my_vg-rootlv: clean, 7263/320000 files, 203981/1280000 blocks Jun 5 06:38:53 recorder kernel: <30>systemd-fsck[2046]: /dev/mapper/my_vg-usrlv: clean, 185689/425984 files, 1308472/1703936 blocks Jun 5 06:38:53 recorder kernel: <30>systemd-fsck[2085]: /dev/mapper/my_vg-srclv: clean, 162714/393216 files, 1367025/1572864 blocks Jun 5 06:38:53 recorder kernel: <30>systemd-fsck[2078]: /dev/mapper/my_vg-homelv: clean, 1347/262144 files, 505333/1048576 blocks Jun 5 06:38:53 recorder kernel: <30>systemd-fsck[2080]: fsck.jfs version 1.1.13, 17-Jul-2008 Jun 5 06:38:53 recorder kernel: <30>systemd-fsck[2080]: processing started: 6/5/2011 6.37.24 Jun 5 06:38:53 recorder kernel: <30>systemd-fsck[1369]: The current device is: /dev/mapper/my_vg-mythlv Jun 5 06:38:53 recorder kernel: <30>systemd-fsck[1369]: Block size in bytes: 4096 Jun 5 06:38:53 recorder kernel: <30>systemd-fsck[1369]: Filesystem size in blocks: 303038464 Jun 5 06:38:53 recorder kernel: <30>systemd-fsck[1369]: **Phase 0 - Replay Journal Log Jun 5 06:38:53 recorder kernel: <30>systemd-fsck[1369]: Filesystem is clean. Jun 5 06:38:53 recorder kernel: <30>systemd-fsck[2082]: /dev/mapper/my_vg-varlv: clean, 27331/262144 files, 326703/1048576 blocks Jun 5 06:38:53 recorder kernel: <30>systemd-fsck[2106]: /dev/sda1: clean, 53/51200 files, 68055/204800 blocks Jun 5 06:38:53 recorder kernel: <30>systemd-cryptsetup[2172]: Set cipher aes, mode cbc-essiv:sha256, key size 256 bits for device /dev/sda2. Jun 5 06:38:53 recorder kernel: <28>systemd[1]: Job dev-mapper-swap.device/start timed out. Jun 5 06:38:53 recorder kernel: <29>systemd[1]: Job dev-mapper-swap.swap/start failed with result 'dependency'. Jun 5 06:38:53 recorder kernel: <29>systemd[1]: Job dev-mapper-swap.device/start failed with result 'timeout'. Jun 5 06:38:57 recorder dbus-daemon: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Jun 5 06:38:57 recorder dbus-daemon: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status' for details. Jun 5 06:39:01 recorder systemd[1]: mysqld.service: control process exited, code=exited status=1 Jun 5 06:39:01 recorder systemd[1]: Unit mysqld.service entered failed state. Jun 5 06:39:03 recorder systemd-update-utmp[2725]: Failed to connect to audit log: Protocol not supported Jun 5 06:39:03 recorder systemd[1]: Startup finished in 14s 855ms 464us (kernel) + 1min 43s 46ms 413us (userspace) = 1min 57s 901ms 877us. Jun 5 07:21:32 recorder dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service' Jun 5 07:21:56 recorder systemd[1]: getty holdoff time over, scheduling restart. Jun 5 08:51:43 recorder kernel: <30>systemd[1]: systemd 26 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; fedora) Jun 5 08:51:43 recorder kernel: <28>systemd[1]: /sbin/modprobe failed with error code 1. Jun 5 08:51:43 recorder kernel: <30>systemd[1]: Set hostname to <recorder.hierzo>. Jun 5 08:51:43 recorder kernel: <28>systemd[1]: /usr appears to be on a different file system than /. This is not supported anymore. Some things will probably break (sometimes even silently) in mysterious ways. Consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for more information. Jun 5 08:51:43 recorder kernel: <27>systemd[1]: Failed to connect to audit log: Protocol not supported Jun 5 08:51:43 recorder kernel: <28>systemd[1]: Found ordering cycle on local-fs.target/start Jun 5 08:51:43 recorder kernel: <30>systemd[1]: Walked on cycle path to fedora-storage-init-late.service/start Jun 5 08:51:43 recorder kernel: <30>systemd[1]: Walked on cycle path to cryptsetup.target/start Jun 5 08:51:43 recorder kernel: <30>systemd[1]: Walked on cycle path to cryptsetup/start Jun 5 08:51:43 recorder kernel: <30>systemd[1]: Walked on cycle path to systemd-random-seed-load.service/start Jun 5 08:51:43 recorder kernel: <30>systemd[1]: Walked on cycle path to local-fs.target/start Jun 5 08:51:43 recorder kernel: <28>systemd[1]: Breaking ordering cycle by deleting job fedora-storage-init-late.service/start Jun 5 08:51:43 recorder kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory Jun 5 08:51:43 recorder kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory Jun 5 08:51:43 recorder kernel: <29>systemd[1]: Unit dev-hugepages.automount entered failed state. Jun 5 08:51:43 recorder kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory Jun 5 08:51:43 recorder kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory Jun 5 08:51:43 recorder kernel: <29>systemd[1]: Unit dev-mqueue.automount entered failed state. Jun 5 08:51:43 recorder kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory Jun 5 08:51:43 recorder kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory Jun 5 08:51:43 recorder kernel: <29>systemd[1]: Unit sys-kernel-security.automount entered failed state. Jun 5 08:51:43 recorder kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory Jun 5 08:51:43 recorder kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory Jun 5 08:51:43 recorder kernel: <29>systemd[1]: Unit proc-sys-fs-binfmt_misc.automount entered failed state. Jun 5 08:51:43 recorder kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory Jun 5 08:51:43 recorder kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory Jun 5 08:51:43 recorder kernel: <29>systemd[1]: Unit sys-kernel-debug.automount entered failed state. Jun 5 08:51:43 recorder kernel: <30>systemd-fsck[2170]: /dev/mapper/my_vg-varlv: clean, 27259/262144 files, 344904/1048576 blocks Jun 5 08:51:43 recorder kernel: <30>systemd-fsck[2177]: /dev/mapper/my_vg-homelv: clean, 1347/262144 files, 505333/1048576 blocks Jun 5 08:51:43 recorder kernel: <30>systemd-fsck[2191]: /dev/mapper/my_vg-usrlv: clean, 185672/425984 files, 1306320/1703936 blocks Jun 5 08:51:43 recorder kernel: <30>systemd-fsck[2195]: fsck.jfs version 1.1.13, 17-Jul-2008 Jun 5 08:51:43 recorder kernel: <30>systemd-fsck[2195]: processing started: 6/5/2011 8.50.12 Jun 5 08:51:43 recorder kernel: <30>systemd-fsck[2195]: The current device is: /dev/mapper/my_vg-mythlv Jun 5 08:51:43 recorder kernel: <30>systemd-fsck[2195]: Block size in bytes: 4096 Jun 5 08:51:43 recorder kernel: <30>systemd-fsck[2195]: Filesystem size in blocks: 303038464 Jun 5 08:51:43 recorder kernel: <30>systemd-fsck[2195]: **Phase 0 - Replay Journal Log Jun 5 08:51:43 recorder kernel: <30>systemd-fsck[2195]: Filesystem is clean. Jun 5 08:51:43 recorder kernel: <30>systemd-fsck[2206]: /dev/mapper/my_vg-srclv: clean, 162706/393216 files, 1367565/1572864 blocks Jun 5 08:51:43 recorder kernel: <30>systemd-fsck[2235]: /dev/sda1: clean, 55/51200 files, 72288/204800 blocks Jun 5 08:51:43 recorder kernel: <30>systemd-cryptsetup[2279]: Set cipher aes, mode cbc-essiv:sha256, key size 256 bits for device /dev/sda2. Jun 5 08:51:43 recorder kernel: <28>systemd[1]: Job dev-mapper-swap.device/start timed out. Jun 5 08:51:43 recorder kernel: <29>systemd[1]: Job dev-mapper-swap.swap/start failed with result 'dependency'. Jun 5 08:51:43 recorder kernel: <29>systemd[1]: Job dev-mapper-swap.device/start failed with result 'timeout'. Jun 5 08:51:43 recorder dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service' Jun 5 08:51:44 recorder dbus-daemon: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Jun 5 08:51:44 recorder dbus-daemon: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status' for details. Jun 5 08:51:47 recorder systemd[1]: mysqld.service: control process exited, code=exited status=1 Jun 5 08:51:47 recorder systemd[1]: Unit mysqld.service entered failed state. Jun 5 08:51:51 recorder systemd-update-utmp[2862]: Failed to connect to audit log: Protocol not supported Jun 5 08:51:51 recorder systemd[1]: Startup finished in 1s 981ms 339us (kernel) + 3s 54ms 74us (initrd) + 1min 43s 365ms 292us (userspace) = 1min 48s 400ms 705us. Jun 5 08:54:19 recorder systemd[1]: mysqld.service: Supervising process 3160 which is not our child. We'll most likely not notice when it exits. Jun 5 08:55:37 recorder systemd[1]: mythbackend.service: main process exited, code=exited, status=254 Jun 5 09:30:30 recorder systemd[1]: Reloading. Jun 5 09:30:31 recorder systemd[1]: mysqld.service: Supervising process 3160 which is not our child. We'll most likely not notice when it exits. Jun 5 09:40:47 recorder systemd[1]: mysqld.service: Supervising process 4046 which is not our child. We'll most likely not notice when it exits. Jun 5 09:44:24 recorder systemd[1]: mysqld.service: control process exited, code=exited status=1 Jun 5 09:44:24 recorder systemd[1]: Unit mysqld.service entered failed state. Jun 5 09:45:58 recorder systemd[1]: mysqld.service: control process exited, code=exited status=1 Jun 5 09:45:58 recorder systemd[1]: Unit mysqld.service entered failed state. Jun 5 09:48:19 recorder systemd[1]: mysqld.service: control process exited, code=exited status=1 Jun 5 09:48:19 recorder systemd[1]: Unit mysqld.service entered failed state. Jun 5 09:49:05 recorder systemd[1]: mysqld.service: control process exited, code=exited status=1 Jun 5 09:49:06 recorder systemd[1]: Unit mysqld.service entered failed state. Jun 5 09:49:45 recorder systemd[1]: mysqld.service: Supervising process 7485 which is not our child. We'll most likely not notice when it exits. Jun 5 10:14:57 recorder systemd[1]: Reloading. Jun 5 10:14:58 recorder systemd[1]: mysqld.service: Supervising process 7485 which is not our child. We'll most likely not notice when it exits. Jun 5 10:29:05 recorder systemd[1]: Reloading. Jun 5 10:29:06 recorder systemd[1]: mysqld.service: Supervising process 7485 which is not our child. We'll most likely not notice when it exits. Jun 5 10:57:27 recorder kernel: <30>systemd[1]: systemd 26 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; fedora) Jun 5 10:57:27 recorder kernel: <28>systemd[1]: /sbin/modprobe failed with error code 1. Jun 5 10:57:27 recorder kernel: <30>systemd[1]: Set hostname to <recorder.hierzo>. Jun 5 10:57:27 recorder kernel: <28>systemd[1]: /usr appears to be on a different file system than /. This is not supported anymore. Some things will probably break (sometimes even silently) in mysterious ways. Consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for more information. Jun 5 10:57:27 recorder kernel: <27>systemd[1]: Failed to connect to audit log: Protocol not supported Jun 5 10:57:27 recorder kernel: <28>systemd[1]: Found ordering cycle on local-fs.target/start Jun 5 10:57:27 recorder kernel: <30>systemd[1]: Walked on cycle path to fedora-storage-init-late.service/start Jun 5 10:57:27 recorder kernel: <30>systemd[1]: Walked on cycle path to cryptsetup.target/start Jun 5 10:57:27 recorder kernel: <30>systemd[1]: Walked on cycle path to cryptsetup/start Jun 5 10:57:27 recorder kernel: <30>systemd[1]: Walked on cycle path to systemd-random-seed-load.service/start Jun 5 10:57:27 recorder kernel: <30>systemd[1]: Walked on cycle path to local-fs.target/start Jun 5 10:57:27 recorder kernel: <28>systemd[1]: Breaking ordering cycle by deleting job fedora-storage-init-late.service/start Jun 5 10:57:27 recorder kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory Jun 5 10:57:27 recorder kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory Jun 5 10:57:27 recorder kernel: <29>systemd[1]: Unit dev-hugepages.automount entered failed state. Jun 5 10:57:27 recorder kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory Jun 5 10:57:27 recorder kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory Jun 5 10:57:27 recorder kernel: <29>systemd[1]: Unit dev-mqueue.automount entered failed state. Jun 5 10:57:27 recorder kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory Jun 5 10:57:27 recorder kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory Jun 5 10:57:27 recorder kernel: <29>systemd[1]: Unit sys-kernel-security.automount entered failed state. Jun 5 10:57:27 recorder kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory Jun 5 10:57:27 recorder kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory Jun 5 10:57:27 recorder kernel: <29>systemd[1]: Unit proc-sys-fs-binfmt_misc.automount entered failed state. Jun 5 10:57:27 recorder kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory Jun 5 10:57:27 recorder kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory Jun 5 10:57:27 recorder kernel: <29>systemd[1]: Unit sys-kernel-debug.automount entered failed state. Jun 5 10:57:27 recorder kernel: <30>systemd-fsck[2196]: fsck.jfs version 1.1.13, 17-Jul-2008 Jun 5 10:57:27 recorder kernel: <30>systemd-fsck[1420]: processing started: 6/5/2011 10.55.56 Jun 5 10:57:27 recorder kernel: <30>systemd-fsck[1420]: The current device is: /dev/mapper/my_vg-mythlv Jun 5 10:57:27 recorder kernel: <30>systemd-fsck[1420]: Block size in bytes: 4096 Jun 5 10:57:27 recorder kernel: <30>systemd-fsck[1420]: Filesystem size in blocks: 303038464 Jun 5 10:57:27 recorder kernel: <30>systemd-fsck[1420]: **Phase 0 - Replay Journal Log Jun 5 10:57:27 recorder kernel: <30>systemd-fsck[1420]: Filesystem is clean. Jun 5 10:57:27 recorder kernel: <30>systemd-fsck[2192]: /dev/mapper/my_vg-homelv: clean, 1347/262144 files, 505333/1048576 blocks Jun 5 10:57:27 recorder kernel: <30>systemd-fsck[2194]: /dev/mapper/my_vg-varlv: clean, 27269/262144 files, 365131/1048576 blocks Jun 5 10:57:27 recorder kernel: <30>systemd-fsck[2199]: /dev/mapper/my_vg-usrlv: clean, 184401/425984 files, 1313654/1703936 blocks Jun 5 10:57:27 recorder kernel: <30>systemd-fsck[2209]: /dev/mapper/my_vg-srclv: clean, 162726/393216 files, 1367614/1572864 blocks Jun 5 10:57:27 recorder kernel: <30>systemd-fsck[2239]: /dev/sda1: clean, 55/51200 files, 72288/204800 blocks Jun 5 10:57:27 recorder kernel: <30>systemd-cryptsetup[2287]: Set cipher aes, mode cbc-essiv:sha256, key size 256 bits for device /dev/sda2. Jun 5 10:57:27 recorder kernel: <28>systemd[1]: Job dev-mapper-swap.device/start timed out. Jun 5 10:57:27 recorder kernel: <29>systemd[1]: Job dev-mapper-swap.swap/start failed with result 'dependency'. Jun 5 10:57:27 recorder kernel: <29>systemd[1]: Job dev-mapper-swap.device/start failed with result 'timeout'. Jun 5 10:57:28 recorder dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service' Jun 5 10:57:29 recorder dbus-daemon: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Jun 5 10:57:29 recorder dbus-daemon: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status' for details. Jun 5 10:57:38 recorder systemd[1]: mysqld.service: Supervising process 3008 which is not our child. We'll most likely not notice when it exits. Jun 5 10:57:39 recorder systemd-update-utmp[3181]: Failed to connect to audit log: Protocol not supported Jun 5 10:57:39 recorder systemd[1]: Startup finished in 1s 985ms 401us (kernel) + 3s 186ms 634us (initrd) + 1min 47s 284ms 536us (userspace) = 1min 52s 456ms 571us. Jun 5 10:58:44 recorder systemd[1]: [/etc/systemd/system/mythbackend.service:6] Invalid executable path in command line, ignoring: "/usr/bin/mythbackend --daemon --user mythtv --logfile /var/log/mythtv/mythbackend.log --pidfile /var/run/mythbackend.pid" Jun 5 10:58:44 recorder systemd[1]: [/etc/systemd/system/mythbackend.service:7] Unknown lvalue 'After' in section 'Service'. Ignoring. Jun 5 10:58:44 recorder systemd[1]: mythbackend.service lacks ExecStart setting. Refusing. Jun 5 11:07:10 recorder systemd[1]: Reloading. Jun 5 11:07:10 recorder systemd[1]: mysqld.service: Supervising process 3008 which is not our child. We'll most likely not notice when it exits. Jun 5 11:07:10 recorder systemd[1]: [/lib/systemd/system/mythbackend.service:7] Invalid executable path in command line, ignoring: "/usr/bin/mythbackend --daemon --user mythtv --logfile /var/log/mythtv/mythbackend.log --pidfile /var/run/mythbackend.pid" Jun 5 11:07:10 recorder systemd[1]: mythbackend.service lacks ExecStart setting. Refusing. Jun 5 12:57:36 recorder systemd[1]: Reloading. Jun 5 12:57:38 recorder systemd[1]: mysqld.service: Supervising process 3008 which is not our child. We'll most likely not notice when it exits. Jun 5 12:58:02 recorder systemd[1]: mythbackend.service: main process exited, code=killed, status=9 Jun 5 12:58:02 recorder systemd[1]: Unit mythbackend.service entered failed state. Jun 5 13:06:21 recorder systemd[1]: Reloading. Jun 5 13:06:21 recorder systemd[1]: mysqld.service: Supervising process 3008 which is not our child. We'll most likely not notice when it exits. Jun 5 13:20:03 recorder systemd[1]: Reloading. Jun 5 13:20:03 recorder systemd[1]: mysqld.service: Supervising process 3008 which is not our child. We'll most likely not notice when it exits. Jun 5 13:41:43 recorder systemd[1]: Reloading. Jun 5 13:41:44 recorder systemd[1]: mysqld.service: Supervising process 3008 which is not our child. We'll most likely not notice when it exits. Jun 5 13:41:44 recorder systemd[1]: [/lib/systemd/system/mythbackend.service:10] Invalid executable path in command line, ignoring: chown ${MYTHBACKEND_USER}:${MYTHBACKEND_USER} /var/run/mythbackend.pid Jun 5 13:43:11 recorder systemd[1]: Reloading. Jun 5 13:43:12 recorder systemd[1]: [/lib/systemd/system/mythbackend.service:10] Invalid executable path in command line, ignoring: chown ${MYTHBACKEND_USER}:${MYTHBACKEND_USER} /var/run/mythbackend.pid Jun 5 13:43:12 recorder systemd[1]: mysqld.service: Supervising process 3008 which is not our child. We'll most likely not notice when it exits. Jun 6 03:18:14 recorder systemd[1]: Reexecuting. Jun 6 03:18:15 recorder systemd[1]: systemd 26 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; fedora) Jun 6 03:18:15 recorder systemd[1]: Failed to connect to audit log: Protocol not supported Jun 6 03:18:15 recorder systemd[1]: [/lib/systemd/system/mythbackend.service:10] Invalid executable path in command line, ignoring: chown ${MYTHBACKEND_USER}:${MYTHBACKEND_USER} /var/run/mythbackend.pid Jun 6 03:18:16 recorder systemd[1]: mysqld.service: Supervising process 3008 which is not our child. We'll most likely not notice when it exits. Jun 6 03:18:16 recorder systemd[1]: Reexecuting. Jun 6 03:18:16 recorder systemd[1]: systemd 26 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; fedora) Jun 6 03:18:16 recorder systemd[1]: Failed to connect to audit log: Protocol not supported Jun 6 03:18:16 recorder systemd[1]: [/lib/systemd/system/mythbackend.service:10] Invalid executable path in command line, ignoring: chown ${MYTHBACKEND_USER}:${MYTHBACKEND_USER} /var/run/mythbackend.pid Jun 6 03:18:16 recorder systemd[1]: mysqld.service: Supervising process 3008 which is not our child. We'll most likely not notice when it exits. [root@recorder linux]# The error 254 from the backend has to do with being unable to connect to the database. But it was also unable to write to mythbackend.log. So it appears the environment was not successfully set up at all using the SysV script which worked well in F14.
/dev/autofs is present, btw. so why isn't it found by systemd?
Also /proc/sys/fs/binfmt_misc is a valid path on the box.
Where is my /proc/config.gz? See: CONFIG_IKCONFIG_PROC=y
And AUTOFS as a module or in the kernel does not matter for the /dev/autofs messages.
[root@recorder linux]# mount /proc on /proc type proc (rw,relatime) /sys on /sys type sysfs (rw,relatime) udev on /dev type tmpfs (rw,nosuid,relatime,mode=755) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw,relatime) tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755) /dev/mapper/my_vg-rootlv on / type ext4 (rw,noatime,barrier=1,data=ordered) tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) cgroup on /sys/fs/cgroup/ns type cgroup (rw,nosuid,nodev,noexec,relatime,ns) cgroup on /sys/fs/cgroup/cpu type cgroup (rw,nosuid,nodev,noexec,relatime,cpu) cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) tmpfs on /media type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755) /dev/mapper/my_vg-usrlv on /usr type ext4 (rw,nodev,noatime,barrier=1,data=ordered) /dev/mapper/my_vg-mythlv on /Myth type jfs (rw,relatime) /dev/mapper/my_vg-homelv on /home type ext4 (rw,nodev,noatime,barrier=1,data=ordered) /dev/mapper/my_vg-srclv on /usr/src type ext4 (rw,nodev,noatime,barrier=1,data=ordered) /dev/mapper/my_vg-varlv on /var type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered) tmpfs on /var/run type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755) tmpfs on /var/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755) /dev/sda1 on /boot type ext3 (rw,nosuid,nodev,noatime,errors=continue,user_xattr,acl,barrier=0,data=writeback) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime) Why is stuff that belongs under /var/run mounted on /run?!
[root@recorder linux]# fuser -v /run USER PID ACCESS COMMAND /run: root kernel mount /run [root@recorder linux]# umount /run umount: /run: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) So why is the system changed in the ways it is?
(In reply to comment #7) > Comment #5: mysql-server-5.5.12-1.fc15.x86_64 The log in comment #3 shows mysql is a different version: Version: '5.1.50-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution You may have a mixup between the distribution package and a self-compiled version. Check with: rpm -Va mysql\* > Comment #4: I wrote a service file and removed the SysV startup script. > Output as it was is in the beginning of the report: You have not pasted the new service file, so I don't know what's wrong about it. But I'd suggest forgetting about a native unit file for now, and let's focus on the SysV initscripts the bug report is about. They are supposed to work. > I don't think that the default of losing errors is very unix-like since > in that case we have no information to troubleshoot on as we have right now. The default will change. > I'd liek to learn first how to properly (systemd dependencies...) got from my > service file back to the SysV script. (just remove service file, put SysV file > in place, chkconfig mythbackend on, reboot?) That should be enough, yes. (In reply to comment #9) > /dev/autofs is present, btw. so why isn't it found by systemd? The log in comment #8 shows you're running a custom kernel with some required options and/or modules missing. Please use a Fedora kernel, at least while we're debugging this systemd-related issue.
For information about /run see: http://fedoraproject.org/wiki/Packaging:Guidelines#.2Frun https://lwn.net/Articles/436012/
It's a terrible duplicate: [root@recorder linux]# ls -l /run total 64 drwxr-xr-x 2 root root 80 Jun 6 17:13 abrt -rw-r--r-- 1 root root 5 Jun 6 17:13 abrtd.pid -rw-r--r-- 1 root root 5 Jun 6 17:13 atd.pid drwxr-xr-x 2 avahi avahi 80 Jun 6 17:13 avahi-daemon drwxr-xr-x 2 root root 40 Jun 6 17:12 console -rw-r--r-- 1 root root 5 Jun 6 17:13 crond.pid ---------- 1 root root 0 Jun 6 17:13 cron.reboot drwxr-xr-x 3 root lp 80 Jun 6 17:13 cups -rw-r--r-- 1 root root 5 Jun 6 17:13 cupsd.pid drwxr-xr-x 2 root root 60 Jun 6 17:13 dbus drwxr-xr-x 2 root root 40 Jun 6 17:12 dirmngr drwxr-xr-x 2 root root 40 Jun 6 17:12 faillock -rw-rw-r-- 1 root root 5 Jun 6 17:13 gpm.pid drwx--x--- 2 root apache 60 Jun 6 17:14 httpd drwxr-xr-x 2 root root 60 Jun 6 17:12 initramfs drwxr-xr-x 2 root root 40 Jun 6 17:12 lirc drwxr-xr-x 5 root root 100 Jun 6 17:12 lock drwx------ 2 root root 40 Jun 6 17:12 lvm srwxrwxr-x 1 root root 0 Jun 6 17:13 mcelog-client -rw-r--r-- 1 root root 5 Jun 6 17:13 messagebus.pid -rw-r--r-- 1 root root 5 Jun 6 17:15 monit.pid drwxr-xr-x 2 root root 60 Jun 6 17:12 mount drwxr-xr-x 2 mysql mysql 60 Jun 6 17:14 mysqld -rw-rw-r-- 1 root root 5 Jun 6 17:14 mythbackend.pid drwxrwxr-x 2 root root 40 Jun 6 17:12 netreport drwxr-xr-x 2 root root 40 Jun 6 17:12 net-snmp drwxr-xr-x 2 root root 40 Jun 6 17:14 plymouth drwxr-xr-x 2 root root 60 Jun 6 17:13 portreserve drwxr-xr-x 2 root root 40 Jun 6 17:12 ppp drwxr-x--- 2 root root 40 Jun 6 17:12 pptp -r--r--r-- 1 root root 0 Jun 6 17:13 rpcbind.lock srw-rw-rw- 1 root root 0 Jun 6 17:13 rpcbind.sock -rw-r--r-- 1 rpcuser rpcuser 5 Jun 6 17:13 rpc.statd.pid drwxr-xr-x 2 root root 40 Jun 6 17:12 saslauthd drwxrwxr-x 2 root screen 40 Jun 6 17:12 screen -rw------- 1 root smmsp 33 Jun 6 17:14 sendmail.pid drwxr-xr-x 2 root root 40 Jun 6 17:12 sepermit drwxr-xr-x 2 root root 40 Jun 6 17:12 setrans -rw-r--r-- 1 smmsp smmsp 49 Jun 6 17:14 sm-client.pid -rw------- 1 root root 5 Jun 6 17:13 sm-notify.pid -rw-r--r-- 1 root root 5 Jun 6 17:13 sshd.pid -rw-r--r-- 1 root root 5 Jun 6 17:13 syslogd.pid drwxr-xr-x 6 root root 200 Jun 6 17:15 systemd drwxr-xr-x 7 root root 160 Jun 6 17:12 udev -rw-r--r-- 1 root root 4 Jun 6 17:14 uptimed drwxr-xr-x 3 root root 100 Jun 6 17:14 user -rw-rw-r-- 1 root utmp 3456 Jun 6 17:14 utmp So why is the system malformed like it is? There was no stuff in /dev that didn't belong there. /run is ugly needs to go. How to do that?
(In reply to comment #17) > It's a terrible duplicate: There's no duplication. /var/run is either a symlink to /run, or a bind mount of the same. > So why is the system malformed like it is? > There was no stuff in /dev that didn't belong there. > /run is ugly needs to go. > How to do that? Can we stay on topic?
It shows twice the same info so it is a duplication. systemd messed up the system and my pleasant experience of the system. That is why we're here. If even the most basic stuff stops (like the swap) or the starting of services that is severe enough for it not to be stuffed in a distro and pushed onto users. Let's see when RHEL adopts systemd. Within a year? To get back to the bugs: I really do not need /run and want it to go. Please say it is a configurable option or it will be like that shortly. What other info do you need about the mythbackend issue? Please specify so I can help. Can you say something about the mysqld issue? The /dev/autofs messages? If CONFIG_AUTOFS4_FS=y or CONFIG_AUTOFS4_FS=m is not enough for autofs, please explain why and/or what is so specific about a fedora kernel except the politics. Yes, i'd like to learn about the technicalities. /proc/config.gz issue?
[root@recorder ~]# dmesg|grep -i auto <28>systemd[1]: Cannot add dependency job for unit autofs.target, ignoring: Unit autofs.target failed to load: No such file or directory. See system logs and 'systemctl status' for details. <27>systemd[1]: Failed to open /dev/autofs: No such file or directory <27>systemd[1]: Failed to initialize automounter: No such file or directory <29>systemd[1]: Unit dev-hugepages.automount entered failed state. <27>systemd[1]: Failed to open /dev/autofs: No such file or directory <27>systemd[1]: Failed to initialize automounter: No such file or directory (etc) [root@recorder ~]# find /lib -name autofs.target [root@recorder ~]# find /etc -name autofs.target [root@recorder ~]#
(In reply to comment #19) > systemd messed up the system and my pleasant experience of the system. That may be a premature conclusion. We don't know what causes the failure yet. > Let's see when RHEL adopts systemd. Within a year? We don't provide this kind of information. > To get back to the bugs: I really do not need /run and want it to go. Please > say it is a configurable option or it will be like that shortly. It's not configurable and it's going to stay. Have you read the rationale for introducing it? > What other info do you need about the mythbackend issue? Please specify so I > can help. In one of the previous comments you wrote: % The error 254 from the backend has to do with being unable to connect to % the database. So I'm assuming the problem is secondary to the mysqld issue. > Can you say something about the mysqld issue? I already have, in comment #15: % The log in comment #3 shows mysql is a different version: % Version: '5.1.50-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 % Source distribution % % You may have a mixup between the distribution package and a self-compiled % version. Check with: % rpm -Va mysql\* > The /dev/autofs messages? > If CONFIG_AUTOFS4_FS=y or CONFIG_AUTOFS4_FS=m is not enough for autofs, please > explain why and/or what is so specific about a fedora kernel except the > politics. I don't know and I don't care. It's not about politics. It's about reasonable use of my time.
(In reply to comment #20) > [root@recorder ~]# dmesg|grep -i auto > <28>systemd[1]: Cannot add dependency job for unit autofs.target, ignoring: > Unit autofs.target failed to load: No such file or directory. See system logs > and 'systemctl status' for details. This warning can be safely ignored. It is caused by an incorrect LSB header in the autofs initscript.
The tool is technically great, yet the delivery is flawed at my place. That is the main issue that we are trying to fix. w.r.t. autofs: [root@recorder linux]# rpm -qa|grep autofs [root@recorder linux]# So no LSB header? Or waht am I missing? W.r.t. /run: I said I didn't need it after reading. W.r.t. mysql: yes mysql was blocked in the yum.conf. That could have been the trigger to make it work after the next reboot. Right? (with then unknown the tmpfile thing) Then is the mythbackend issue that as far as I recall remained all the time. Currently I have the future-safe splution of a .service file. So what remains essentially is the autofs noise that I cannot yet explain. We have a kernel with autofs, no autofs rpm, and the log messages saying the kernel lacks autofs....
<31>systemd[1]: Successfully opened /dev/kmsg for logging. <30>systemd[1]: systemd 26 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; fedora) <31>systemd[1]: Your kernel apparently lacks built-in autofs4 support. Might be a good idea to compile it in. We'll now try to work around this by calling '/sbin/modprobe autofs4'... <31>systemd[1]: Your kernel apparently lacks built-in ipv6 support. Might be a good idea to compile it in. We'll now try to work around this by calling '/sbin/modprobe ipv6'... <31>systemd[1]: About to execute: /sbin/modprobe -qab -- autofs4 ipv6 <31>systemd[1]: Forked /sbin/modprobe as 1409 <28>systemd[1]: /sbin/modprobe failed with error code 1. <30>systemd[1]: Set hostname to <recorder.hierzo>. [root@recorder linux]# grep AUTOFS .config CONFIG_AUTOFS4_FS=y And yes wel rebuilt the kernel, rebooted, etc.
(In reply to comment #23) > w.r.t. autofs: > > [root@recorder linux]# rpm -qa|grep autofs > [root@recorder linux]# > > So no LSB header? Or waht am I missing? It may be some other initscript referring to the non-existent $autofs facility in its LSB header. > W.r.t. mysql: yes mysql was blocked in the yum.conf. That could have been the > trigger to make it work after the next reboot. Right? (with then unknown the > tmpfile thing) Having the old package installed could explain it, yes. You're not being entirely clear... Does mysqld work now? > Then is the mythbackend issue that as far as I recall remained all the time. > Currently I have the future-safe splution of a .service file. IF mysqld now works and mythbackend still does not, do a boot with: log_buf_len=2M systemd.log_level=debug systemd.log_target=kmsg systemd.default_standard_output=kmsg ... and attach the output of the 'dmesg' command this bug.
(In reply to comment #24) > <31>systemd[1]: Your kernel apparently lacks built-in autofs4 support. Might be > a good idea to compile it in. We'll now try to work around this by calling > '/sbin/modprobe autofs4'... systemd detects whether autofs4 is in the kernel by testing for the presence of /sys/class/misc/autofs That's all I know about this.
mysqld does now start reliably, but still via SysV: [root@recorder ~]# systemctl|grep sql mysqld.service loaded active running LSB: start and stop MySQL server Compiled the kernel again, installed modules etc and now (dunno why because I did some kernel compiles during the past years) the autofs module _is_ loaded, fixing most of the messages. I did boot with the debug stuff of which I posted a bit in Comment #24. So now the only real issue remaining is the encrypted swap as `modprobe configs` gives me the /proc/config.gz.
(In reply to comment #27) > mysqld does now start reliably, but still via SysV: Excellent. Only a few services have been ported to native systemd units so far, so it is perfectly alright that mysqld is still a SysV service. > Compiled the kernel again, installed modules etc and now (dunno why because I > did some kernel compiles during the past years) the autofs module _is_ loaded, > fixing most of the messages. Great. > So now the only real issue remaining is the encrypted swap as `modprobe > configs` gives me the /proc/config.gz. The encrypted swap is bug 710839. We'll solve that. Closing this one.