Nach dem ich hier neu bin und noch nie Probleme mit systemd hatte, jedenfalls in debian sid nicht, habe ich nachdem ich heute siduction december aktualisiert hatte, das Problem, das systemd sich wie sysvinit verhält. Nach der normalen Ausgabe wird jeder Dienst nacheinander gestartet, was kann ich dagegen tun?
Hi MartinF99,
erst mal Herzlich Willkommen hier im siduction-Forum. Du musst uns ein wenig mehr Informationen liefern, sonst können wir hier nur Rätselraten und das Problem nicht beheben.
Kannst du bitte die Ausgabe der folgenden Kommandos hier posten (bitte Codetags nutzen):
# systemd-analyze blame --no-pager
# systemctl --type=service --no-pager
# journalctl -b -p err --no-pager
Hier sind die Ausgaben
35.011s systemd-udev-settle.service
5.889s NetworkManager.service
5.733s ModemManager.service
4.103s alsa-restore.service
4.102s console-kit-log-system-start.service
3.931s systemd-logind.service
3.847s lm-sensors.service
3.824s pppd-dns.service
3.767s rc-local.service
3.764s kexec.service
3.760s systemd-user-sessions.service
3.595s avahi-daemon.service
2.501s preload.service
1.995s loadcpufreq.service
1.943s keyboard-setup.service
1.793s systemd-fsck-root.service
1.608s wpa_supplicant.service
1.527s lightdm.service
1.279s packagekit.service
1.001s mdadm-raid.service
980ms udisks2.service
969ms polkitd.service
949ms dev-hugepages.mount
925ms dev-mqueue.mount
923ms sys-kernel-debug.mount
904ms ntp.service
849ms systemd-modules-load.service
764ms dirmngr.service
744ms glances.service
733ms networking.service
660ms systemd-tmpfiles-setup-dev.service
525ms systemd-udevd.service
408ms nfs-common.service
381ms kbd.service
362ms systemd-sysctl.service
317ms lvm2-activation-early.service
295ms irqbalance.service
268ms home.mount
265ms systemd-fsck@dev-disk-by\x2duuid-57dcc5ce\x2d7831\x2d47e2\x2d9d40\x2dfceb71009354.service
260ms gpm.service
235ms rpcbind.service
230ms acpi-support.service
223ms hdparm.service
210ms console-setup.service
162ms upower.service
156ms hddtemp.service
138ms console-kit-daemon.service
135ms kdm.service
126ms systemd-udev-trigger.service
124ms user@102.service
114ms systemd-tmpfiles-setup.service
109ms dns-clean.service
98ms systemd-update-utmp.service
91ms udev-finish.service
90ms kmod-static-nodes.service
76ms kexec-load.service
76ms ifplugd.service
69ms systemd-rfkill@rfkill0.service
68ms user@1000.service
63ms dev-disk-by\x2duuid-9332cb80\x2d5ca2\x2d4598\x2d9e20\x2d85986038b4c6.swap
62ms systemd-random-seed.service
59ms bluetooth.service
57ms resolvconf.service
55ms systemd-remount-fs.service
31ms keymap.service
29ms sys-fs-fuse-connections.mount
23ms lvm2-activation.service
22ms lvm2-monitor.service
17ms systemd-update-utmp-runlevel.service
14ms cpufrequtils.service
10ms systemd-journal-flush.service
2
UNIT LOAD ACTIVE SUB DESCRIPTION
acpi-support.service loaded active exited LSB: Start some power managem
acpid.service loaded active running ACPI event daemon
avahi-daemon.service loaded active running Avahi mDNS/DNS-SD Stack
bluetooth.service loaded active running Bluetooth service
console-kit-daemon.service loaded active running Console Manager
console-kit-log-system-start.service loaded active exited Console System Startup Loggin
console-setup.service loaded active exited LSB: Set console font and key
cpufrequtils.service loaded active exited LSB: set CPUFreq kernel param
cron.service loaded active running Regular background program pr
cups-browsed.service loaded active running Make remote CUPS printers ava
cups.service loaded active running CUPS Printing Service
dbus.service loaded active running D-Bus System Message Bus
dirmngr.service loaded active running LSB: start DirMngr daemon
getty@tty1.service loaded active running Getty on tty1
glances.service loaded active exited LSB: Starts and daemonize Gla
gpm.service loaded active running LSB: gpm sysv init script
hddtemp.service loaded active exited LSB: disk temperature monitor
hdparm.service loaded active exited LSB: Tune IDE hard disks
ifplugd.service loaded active exited LSB: Brings up/down network a
irqbalance.service loaded active exited LSB: daemon to balance interr
kbd.service loaded active exited LSB: Prepare console
kdm.service loaded active exited LSB: X display manager for KD
kexec-load.service loaded active exited LSB: Load kernel image with k
kexec.service loaded active exited LSB: Execute the kexec -e com
keyboard-setup.service loaded active exited LSB: Set preliminary keymap
keymap.service loaded active exited LSB: Set keymap
kmod-static-nodes.service loaded active exited Create list of required stati
lightdm.service loaded active running Light Display Manager
lm-sensors.service loaded active exited Initialize hardware monitorin
loadcpufreq.service loaded active exited LSB: Load kernel modules need
lvm2-monitor.service loaded active exited Monitoring of LVM2 mirrors, s
mdadm-raid.service loaded active exited LSB: MD array assembly
ModemManager.service loaded active running Modem Manager
networking.service loaded active exited LSB: Raise network interfaces
NetworkManager.service loaded active running Network Manager
nfs-common.service loaded active running LSB: NFS support files common
ntp.service loaded active running LSB: Start NTP daemon
packagekit.service loaded active running PackageKit Daemon
polkitd.service loaded active running Authenticate and Authorize Us
preload.service loaded active running LSB: Adaptive readahead daemo
rc-local.service loaded active exited /etc/rc.local Compatibility
resolvconf.service loaded active exited Nameserver information manage
rpcbind.service loaded active running LSB: RPC portmapper replaceme
sidu-base.service loaded active running siduction base: shellserver d
smartd.service loaded active running Self Monitoring and Reporting
ssh.service loaded active running OpenBSD Secure Shell server
systemd-fsck-root.service loaded active exited File System Check on Root Dev
systemd-fsck@dev-disk-by\x2duuid-57dcc5ce\x2d7831\x2d47e2\x2d9d40\x2dfceb71009354.service loaded active exited File System Check on /dev/dis
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-modules-load.service loaded active exited Load Kernel Modules
systemd-random-seed.service loaded active exited Load/Save Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File
systemd-rfkill@rfkill0.service loaded active exited Load/Save RF Kill Switch Stat
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in
systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Dir
systemd-udev-settle.service loaded active exited udev Wait for Complete Device
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-update-utmp.service loaded active exited Update UTMP about System Boot
systemd-user-sessions.service loaded active exited Permit User Sessions
udev-finish.service loaded active exited Copy rules generated while th
udisks2.service loaded active running Disk Manager
upower.service loaded active running Daemon for power management
user@1000.service loaded active running User Manager for UID 1000
user@102.service loaded active running User Manager for UID 102
vnstat.service loaded active running vnStat network traffic monito
wpa_supplicant.service loaded active running WPA supplicant
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
69 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
3:
-- Logs begin at Di 2014-11-11 14:07:39 CET, end at Di 2014-11-11 22:13:37 CET. --
Nov 11 22:05:42 siductionbox kernel: tsc: Fast TSC calibration failed
Nov 11 22:05:43 siductionbox kernel: end_request: I/O error, dev fd0, sector 0
Nov 11 22:05:43 siductionbox kernel: end_request: I/O error, dev fd0, sector 0
Nov 11 22:05:44 siductionbox kernel: end_request: I/O error, dev fd0, sector 0
Nov 11 22:05:47 siductionbox systemd-udevd[242]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc0183, key code 226): Invalid argument
Nov 11 22:05:47 siductionbox systemd-udevd[242]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc1005, key code 212): Invalid argument
Nov 11 22:05:47 siductionbox systemd-udevd[242]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc101f, key code 419): Invalid argument
Nov 11 22:05:47 siductionbox systemd-udevd[242]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc1020, key code 418): Invalid argument
Nov 11 22:05:47 siductionbox systemd-udevd[242]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc1041, key code 421): Invalid argument
Nov 11 22:05:47 siductionbox systemd-udevd[242]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc1042, key code 423): Invalid argument
Nov 11 22:05:47 siductionbox systemd-udevd[242]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc1043, key code 397): Invalid argument
Nov 11 22:05:47 siductionbox systemd-udevd[242]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc1044, key code 149): Invalid argument
Nov 11 22:05:47 siductionbox systemd-udevd[242]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc1045, key code 202): Invalid argument
Nov 11 22:05:47 siductionbox systemd-udevd[242]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc1046, key code 203): Invalid argument
Nov 11 22:05:47 siductionbox systemd-udevd[242]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc1048, key code 430): Invalid argument
Nov 11 22:05:47 siductionbox systemd-udevd[242]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc104a, key code 136): Invalid argument
Nov 11 22:05:47 siductionbox systemd-udevd[242]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc104c, key code 162): Invalid argument
Nov 11 22:06:26 siductionbox NetworkManager[733]: <error> [1415739986.247698] [platform/nm-linux-platform.c:2250] link_change(): Netlink error changing link 2: <UP> mtu 0 (1) driver 'skge' udi '/sys/devices/pci0000:00/0000:00:1e.0/0000:01:04.0/net/eth0': Invalid address for specified address family
Nov 11 22:06:27 siductionbox ntpd_intres[866]: host name not found: 0.debian.pool.ntp.org
Nov 11 22:06:27 siductionbox ntpd_intres[866]: host name not found: 1.debian.pool.ntp.org
Nov 11 22:06:27 siductionbox ntpd_intres[866]: host name not found: 2.debian.pool.ntp.org
Nov 11 22:06:27 siductionbox ntpd_intres[866]: host name not found: 3.debian.pool.ntp.org
Nov 11 22:07:11 siductionbox pulseaudio[2025]: [pulseaudio] pid.c: Daemon already running.
Nov 11 22:07:23 siductionbox ntpd_intres[866]: host name not found: 0.debian.pool.ntp.org
Nov 11 22:07:23 siductionbox ntpd_intres[866]: host name not found: 1.debian.pool.ntp.org
Nov 11 22:07:23 siductionbox ntpd_intres[866]: host name not found: 2.debian.pool.ntp.org
Nov 11 22:07:23 siductionbox ntpd_intres[866]: host name not found: 3.debian.pool.ntp.org
Nach einem Neustart funktionierte alles wieder einwandfrei
Nochmal neugestartet, funktionierte es wieder als wäre sysvinit am werk
Ich nutze systemd seit ~ 18 monaten unter siduction und sowas hab ich bisher weder gehört noch selbswt erlebt. Ich wüsste auch garnicht, wo ansetzen. Sind Dir sonst Unregelmässigkeiten aufgefallen, die auf eine fehlerhafte Installation hinweisen würden?
greetz,
devil
Quote from: MartinF99 on 2014/11/11, 22:29:47
Nach einem Neustart funktionierte alles wieder einwandfrei
Nochmal neugestartet, funktionierte es wieder als wäre sysvinit am werk
Brauchst du LVM? wenn nicht, bitte deinstallieren. Google "systemd udev settle lvm".
Geht es um die Meldungen des Startvorgangs die Aussehen wie bei sysvinit? Also die Anzeige von [OK] DIENST beim Starten? Dann guck mal ob in der /etc/default/grub in der Zeile GRUB_CMDLINE_LINUX_DEFAULT= evtl systemd.show_status=true eingetragen ist.
Scheint tatsächlich lvm gewesen zu sein, nach dem Entfernen werden zwar noch einige Fehlermeldungen angezeigt, der Start ist aber wie ich es gewohnt bin.