Univention Bugzilla – Bug 42204
Installed UCS 4.2 does not boot
Last modified: 2017-04-04 18:29:44 CEST
Created attachment 7954 [details] UCS-4.2-preview-boot.mp4 An installed UCS 4.2 system (ucs_4.2-0-20160831-170750-dvd-amd64.iso) does not boot. The system is not accessible via network. The console output gets resized at one point after that nothing more happens. I've captured a boot, see the attached video.
For me booting failed with the message when having network configured via DHCP: "A start job is running for LSB: Raise Network interfaces" I started a rescue CD and removed the content of /etc/network/interfaces and rebooted - which solved the problem.
In the meanwhile a new installed system boots but a login problem is missing. I see only: Loading, please wait... The system is accessible via SSH: root@master211:~# ps -ef UID PID PPID C STIME TTY TIME CMD root 1 0 0 14:23 ? 00:00:01 /sbin/init splash root 2 0 0 14:23 ? 00:00:00 [kthreadd] root 3 2 0 14:23 ? 00:00:00 [ksoftirqd/0] root 5 2 0 14:23 ? 00:00:00 [kworker/0:0H] root 6 2 0 14:23 ? 00:00:00 [kworker/u2:0] root 7 2 0 14:23 ? 00:00:00 [rcu_sched] root 8 2 0 14:23 ? 00:00:00 [rcu_bh] root 9 2 0 14:23 ? 00:00:00 [migration/0] root 10 2 0 14:23 ? 00:00:00 [watchdog/0] root 11 2 0 14:23 ? 00:00:00 [khelper] root 12 2 0 14:23 ? 00:00:00 [kdevtmpfs] root 13 2 0 14:23 ? 00:00:00 [netns] root 14 2 0 14:23 ? 00:00:00 [perf] root 15 2 0 14:23 ? 00:00:00 [khungtaskd] root 16 2 0 14:23 ? 00:00:00 [writeback] root 17 2 0 14:23 ? 00:00:00 [ksmd] root 18 2 0 14:23 ? 00:00:00 [kworker/0:1] root 19 2 0 14:23 ? 00:00:00 [khugepaged] root 20 2 0 14:23 ? 00:00:00 [crypto] root 21 2 0 14:23 ? 00:00:00 [kintegrityd] root 22 2 0 14:23 ? 00:00:00 [bioset] root 23 2 0 14:23 ? 00:00:00 [kblockd] root 24 2 0 14:23 ? 00:00:00 [devfreq_wq] root 25 2 0 14:23 ? 00:00:00 [kswapd0] root 26 2 0 14:23 ? 00:00:00 [fsnotify_mark] root 35 2 0 14:23 ? 00:00:00 [kthrotld] root 36 2 0 14:23 ? 00:00:00 [ipv6_addrconf] root 37 2 0 14:23 ? 00:00:00 [deferwq] root 38 2 0 14:23 ? 00:00:00 [kworker/u2:1] root 70 2 0 14:23 ? 00:00:00 [kpsmoused] root 72 2 0 14:23 ? 00:00:00 [ata_sff] root 73 2 0 14:23 ? 00:00:00 [scsi_eh_0] root 74 2 0 14:23 ? 00:00:00 [scsi_tmf_0] root 75 2 0 14:23 ? 00:00:00 [scsi_eh_1] root 76 2 0 14:23 ? 00:00:00 [scsi_tmf_1] root 79 2 0 14:23 ? 00:00:00 [kworker/0:1H] root 100 2 0 14:23 ? 00:00:00 [dm_bufio_cache] root 114 2 0 14:23 ? 00:00:00 [kdmflush] root 115 2 0 14:23 ? 00:00:00 [bioset] root 121 2 0 14:23 ? 00:00:00 [kdmflush] root 122 2 0 14:23 ? 00:00:00 [bioset] root 143 2 0 14:23 ? 00:00:00 [jbd2/dm-0-8] root 144 2 0 14:23 ? 00:00:00 [ext4-rsv-conver] root 178 2 0 14:23 ? 00:00:00 [kauditd] root 190 1 0 14:23 ? 00:00:00 /lib/systemd/systemd-journald root 192 1 0 14:23 ? 00:00:00 /lib/systemd/systemd-udevd root 229 2 0 14:23 ? 00:00:00 [vballoon] root 236 2 0 14:23 ? 00:00:00 [kvm-irqfd-clean] root 296 2 0 14:23 ? 00:00:00 [ext4-rsv-conver] root 643 1 0 14:23 ? 00:00:00 /sbin/rpcbind -w statd 653 1 0 14:23 ? 00:00:00 /sbin/rpc.statd --port 32765 --outgoing-port 32766 root 659 2 0 14:23 ? 00:00:00 [rpciod] root 661 2 0 14:23 ? 00:00:00 [nfsiod] root 668 1 0 14:23 ? 00:00:00 /usr/sbin/rpc.idmapd root 672 1 0 14:23 ? 00:00:00 /usr/sbin/rpc.gssd root 674 1 0 14:23 ? 00:00:00 /usr/sbin/inetd -i root 675 1 0 14:23 ? 00:00:00 runsvdir -P /etc/service log: ............................................................................................................. daemon 677 1 0 14:23 ? 00:00:00 /usr/sbin/atd -f bind 678 1 0 14:23 ? 00:00:00 /usr/sbin/named -f -u bind root 679 1 0 14:23 ? 00:00:00 /usr/sbin/sshd -D root 680 1 0 14:23 ? 00:00:00 /usr/sbin/cron -f root 682 1 0 14:23 ? 00:00:00 /lib/systemd/systemd-logind root 689 675 0 14:23 ? 00:00:00 runsv univention-directory-listener root 690 675 0 14:23 ? 00:00:00 runsv univention-bind-proxy root 691 675 0 14:23 ? 00:00:00 runsv univention-directory-notifier root 692 675 0 14:23 ? 00:00:00 runsv univention-bind root 693 675 0 14:23 ? 00:00:00 runsv univention-bind-samba4 memcache 719 1 0 14:23 ? 00:00:00 /usr/bin/memcached -m 64 -p 11211 -u memcache -l 127.0.0.1 root 735 1 0 14:23 ? 00:00:02 runsvdir -P /etc/service log: le to lock supervise/lock: temporary failure runsv univention-directory-notifier: fatal: unable to lock super message+ 738 1 0 14:23 ? 00:00:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation root 804 1 0 14:23 ? 00:00:00 /usr/sbin/rsyslogd -n root 807 1 0 14:23 ? 00:00:00 /usr/sbin/acpid root 812 1 0 14:23 ? 00:00:00 /usr/bin/docker -d -H fd:// --bip=172.17.42.1/16 --storage-driver=overlay root 821 1 0 14:23 ? 00:00:00 /usr/lib/heimdal-servers/kdc --config-file=/etc/heimdal-kdc/kdc.conf root 826 1 0 14:23 ? 00:00:00 /usr/lib/heimdal-servers/kpasswdd root 830 1 0 14:23 ? 00:00:00 /usr/sbin/nscd ntp 882 1 0 14:23 ? 00:00:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 115:123 root 884 1 0 14:23 tty1 00:00:00 /sbin/agetty --noclear tty1 linux nagios 899 1 0 14:23 ? 00:00:00 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d samlcgi 928 1 0 14:23 ? 00:00:00 /usr/bin/memcached -m 64 -s /var/run/univention-saml/memcached.socket -u samlcgi samlcgi 973 1 0 14:23 ? 00:00:00 /usr/bin/stunnel4 /etc/stunnel/univention_saml.conf root 1107 1 0 14:23 ? 00:00:00 /usr/sbin/slapd -h ldapi:/// ldap://:7389/ ldap://:389/ ldaps://:7636/ ldaps://:636/ root 1230 1 0 14:23 ? 00:00:00 /usr/lib/postfix/master postfix 1231 1230 0 14:23 ? 00:00:00 pickup -l -t fifo -u postfix 1232 1230 0 14:23 ? 00:00:00 qmgr -l -t fifo -u root 1259 679 0 14:23 ? 00:00:00 sshd: root@pts/0 root 1300 691 0 14:23 ? 00:00:00 /usr/sbin/univention-directory-notifier -o -d 1 -F root 1305 1 0 14:23 ? 00:00:01 /usr/bin/python2.7 /usr/sbin/univention-management-console-server start listener 1324 689 0 14:23 ? 00:00:01 /usr/sbin/univention-directory-listener -F -b dc=deadlock21,dc=intranet -m /usr/lib/univention-directory-listener/system -c /var/lib/univen root 1359 1259 0 14:24 pts/0 00:00:00 -bash root 1412 1 0 14:24 ? 00:00:02 /usr/bin/python2.7 /usr/sbin/univention-management-console-web-server start root 1479 1 0 14:24 ? 00:00:00 /usr/sbin/apache2 -k start www-data 1487 1479 0 14:24 ? 00:00:00 /usr/sbin/apache2 -k start www-data 1488 1479 0 14:24 ? 00:00:00 /usr/sbin/apache2 -k start www-data 1489 1479 0 14:24 ? 00:00:00 /usr/sbin/apache2 -k start www-data 1490 1479 0 14:24 ? 00:00:00 /usr/sbin/apache2 -k start www-data 1491 1479 0 14:24 ? 00:00:00 /usr/sbin/apache2 -k start root 2663 2 0 14:28 ? 00:00:00 [kworker/0:0] root 4037 2 0 14:34 ? 00:00:00 [kworker/0:2] root 4979 1 0 14:37 tty2 00:00:00 /sbin/agetty --noclear tty2 linux root 5042 735 0 14:38 ? 00:00:00 [runsv] <defunct> root 5043 735 0 14:38 ? 00:00:00 [runsv] <defunct> root 5047 1359 0 14:38 pts/0 00:00:00 ps -ef root@master211:~# I've simply installed in KVM with the latest UCS 4.2-0 DVD from today: ucs_4.2-0-20170105-192712-dvd-amd64.iso
(In reply to Stefan Gohmann from comment #2) > In the meanwhile a new installed system boots but a login problem is > missing. I see only: 'problem' -> 'prompt'? > Loading, please wait... ... > root@master211:~# ps -ef > UID PID PPID C STIME TTY TIME CMD ... > root 884 1 0 14:23 tty1 00:00:00 /sbin/agetty --noclear tty1 > linux The getty is there and you automatically get new gettys by switching to console 2-6. You don't see the console because of Bug #42754 comment 1 > I've simply installed in KVM with the latest UCS 4.2-0 DVD from today: > ucs_4.2-0-20170105-192712-dvd-amd64.iso Until we have a linux-4.10 kernel, I'll re-use the un-QA-ed kernel from UCS-4.1-4+errata: ssh -t omar cd /var/univention/buildsystem2/apt/ucs_4.1-0-errata4.1-4 && find \( -name linux_4.1.6.orig.tar.xz -o -name \*_4.1.6-\*.217.\* -o -name univention-kernel-image\* -o -name \*-signed_\* \) -exec ln -f {} ../ucs_4.2-0/{} \; -name \*.dsc -exec readlink -f ../ucs_4.2-0/{} \; | tee -a ../ucs_4.2-0/already_build-amd64.txt repo-apt-ftparchive --release ucs_4.2-0 build-cd-ucs4.2-0 -A amd64 --debug-failures
OK, looks good now.
UCS 4.2 has been released: https://docs.software-univention.de/release-notes-4.2-0-en.html https://docs.software-univention.de/release-notes-4.2-0-de.html If this error occurs again, please use "Clone This Bug".