Page 1 sur 1
[systemd-modules-load.service] loaded failed failed(resolu)
Publié : dim. 30 sept. 2012, 12:22
par Kainny
Bonjour,j'ai installé systemd complètement,c'est à dire que j'ai supprimé sysvinit et initscripts,et installé systemd-sysvcompat.
J'ai chargé 2 modules (loop et fuse) comme indiqué dans le wiki, et activé mes services au démarrage.
J'ai voulu regarder ma liste des unités et voilà ce que ça me donne:
Code : Tout sélectionner
yannick@yannick ~ % systemctl list-units -t service
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
accounts-daemon.service loaded active running Accounts Service
avahi-daemon.service loaded active running Avahi mDNS/DNS-SD Stack
colord-sane.service loaded active running Daemon for monitoring attached scanners and registering them with colord
colord.service loaded active running Manage, Install and Generate Color Profiles
console-kit-daemon.service loaded active running Console Manager
console-kit-log-system-start.service loaded active exited Console System Startup Logging
cronie.service loaded active running Periodic Command Scheduler
cups.service loaded active running CUPS Printing Service
dbus.service loaded active running D-Bus System Message Bus
dhcpcd@eth0.service loaded active running dhcpcd on eth0
gdm.service loaded active running Gnome Display Manager
getty@tty1.service loaded active running Getty on tty1
rtkit-daemon.service loaded active running RealtimeKit Scheduling Policy Service
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-modules-load.service loaded failed failed Load Kernel Modules
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-tmpfiles-setup.service loaded active exited Recreate Volatile Files and Directories
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-user-sessions.service loaded active exited Permit User Sessions
systemd-vconsole-setup.service loaded active exited Setup Virtual Console
udisks2.service loaded active running Storage Daemon
upower.service loaded active running Daemon for power management
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.
JOB = Pending job for the unit.
25 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Je ne comprends pas trop.
Voici mon /var/log/messages.log au cas ou:
Code : Tout sélectionner
yannick@yannick ~ % sudo tail /var/log/messages.log
[sudo] password for yannick:
Sep 29 14:58:10 yannick dbus[356]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service'
Sep 29 14:58:10 yannick dbus[356]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
Sep 29 14:58:11 yannick dbus[356]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Sep 29 14:58:11 yannick dbus[356]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
Sep 29 14:58:19 yannick dbus[356]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Sep 29 14:58:19 yannick dbus[356]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
Sep 29 14:58:34 yannick dbus[356]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service'
Sep 29 14:58:34 yannick dbus[356]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
Sep 29 15:06:57 yannick gnome-session[484]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.
Sep 29 15:06:57 yannick dhcpcd[978]: sending commands to master dhcpcd process
J'espère être sur le bon forum.
Merci de votre aide.
Re: [systemd-modules-load.service] loaded failed failed
Publié : dim. 30 sept. 2012, 12:38
par FoolEcho
Salut,
(journalctl aussi, éventuellement).
Et voir le contenu de tes modifications dans /etc/modules-load.d/.
Re: [systemd-modules-load.service] loaded failed failed
Publié : dim. 30 sept. 2012, 12:53
par Kainny
Salut,
voici:
Code : Tout sélectionner
yannick@yannick ~ % systemctl status systemd-modules-load.service
systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
Active: failed (Result: exit-code) since Sun, 30 Sep 2012 12:00:34 +0200; 54min ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 127 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/systemd-modules-load.service
Code : Tout sélectionner
1 yannick@yannick ~ % sudo journalctl
[sudo] password for yannick:
Logs begin at Sun, 30 Sep 2012 12:00:34 +0200, end at Sun, 30 Sep 2012 12:53:11 +0200.
Sep 30 12:00:34 yannick systemd-journal[137]: Allowing runtime journal files to
Sep 30 12:00:34 yannick kernel: Initializing cgroup subsys cpuset
Sep 30 12:00:34 yannick kernel: Initializing cgroup subsys cpu
Sep 30 12:00:34 yannick kernel: Linux version 3.5.4-1-ARCH (tobias@T-POWA-LX) (g
Sep 30 12:00:34 yannick kernel: Command line: root=/dev/sda1 ro initrd=../initr
Sep 30 12:00:34 yannick kernel: e820: BIOS-provided physical RAM map:
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x0000000000000000-0x00000000000
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000000009d800-0x00000000000
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001ff
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x0000000020200000-0x000000003ff
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000401
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x0000000040200000-0x000000007ad
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007ad89000-0x000000007ad
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007addb000-0x000000007ae
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007ae08000-0x000000007ae
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007ae09000-0x000000007ae
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007ae0c000-0x000000007ae
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007ae0d000-0x000000007ae
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007ae17000-0x000000007ae
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007ae3c000-0x000000007ae
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007ae7f000-0x000000007af
:
Sep 30 12:00:34 yannick systemd-journal[137]: Allowing runtime journal files to grow to 395.1M.
Sep 30 12:00:34 yannick kernel: Initializing cgroup subsys cpuset
Sep 30 12:00:34 yannick kernel: Initializing cgroup subsys cpu
Sep 30 12:00:34 yannick kernel: Linux version 3.5.4-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.1 20120721 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Sep 15 08:12:04 CEST 2012
Sep 30 12:00:34 yannick kernel: Command line: root=/dev/sda1 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
Sep 30 12:00:34 yannick kernel: e820: BIOS-provided physical RAM map:
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x0000000020200000-0x000000003fffffff] usable
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000401fffff] reserved
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x0000000040200000-0x000000007ad88fff] usable
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007ad89000-0x000000007addafff] ACPI NVS
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007addb000-0x000000007ae07fff] reserved
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007ae08000-0x000000007ae08fff] usable
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007ae09000-0x000000007ae0bfff] ACPI NVS
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007ae0c000-0x000000007ae0cfff] ACPI data
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007ae0d000-0x000000007ae16fff] ACPI NVS
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007ae17000-0x000000007ae3bfff] reserved
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007ae3c000-0x000000007ae7efff] ACPI NVS
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007ae7f000-0x000000007affffff] usable
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x000000007b800000-0x000000007f9fffff] reserved
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed3ffff] reserved
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 30 12:00:34 yannick kernel: BIOS-e820: [mem 0x0000000100000000-0x000000027fdfffff] usable
Sep 30 12:00:34 yannick kernel: NX (Execute Disable) protection: active
Sep 30 12:00:34 yannick kernel: DMI 2.6 present.
Sep 30 12:00:34 yannick kernel: DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./Z68 Pro3 Gen3, BIOS P1.10 09/09/2011
Sep 30 12:00:34 yannick kernel: e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
Sep 30 12:00:34 yannick kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 30 12:00:34 yannick kernel: No AGP bridge found
Sep 30 12:00:34 yannick kernel: e820: last_pfn = 0x27fe00 max_arch_pfn = 0x400000000
Sep 30 12:00:34 yannick kernel: MTRR default type: uncachable
Sep 30 12:00:34 yannick kernel: MTRR fixed ranges enabled:
Sep 30 12:00:34 yannick kernel: 00000-9FFFF write-back
Sep 30 12:00:34 yannick kernel: A0000-BFFFF uncachable
Sep 30 12:00:34 yannick kernel: C0000-CFFFF write-protect
Sep 30 12:00:34 yannick kernel: D0000-E7FFF uncachable
Sep 30 12:00:34 yannick kernel: E8000-FFFFF write-protect
Sep 30 12:00:34 yannick kernel: MTRR variable ranges enabled:
Sep 30 12:00:34 yannick kernel: 0 base 000000000 mask E00000000 write-back
:
oups un oubli:dans /etc/modules-load.d/ y a: *conf qui contient Dbus,fuse.conf et loop.conf.
Re: [systemd-modules-load.service] loaded failed failed
Publié : dim. 30 sept. 2012, 13:52
par FoolEcho
yannpk a écrit :oups un oubli:dans /etc/modules-load.d/ y a: *conf qui contient Dbus,fuse.conf et loop.conf.
Pourquoi dbus (ce n'est pas un module) ?
Et leur contenu ?
Re: [systemd-modules-load.service] loaded failed failed
Publié : dim. 30 sept. 2012, 14:01
par Kainny
ben je ne sais pas pourquoi Dbus,je me suis posé la question,surement une mauvaise manipulation,car je ne me souviens pas avoir créer ce fichier.
Je le supprime?
Code : Tout sélectionner
yannick@yannick ~ % cat /etc/modules-load.d/*conf
Dbus
#Load fuse at boot
fuse
loop
yannick@yannick ~ % cat /etc/modules-load.d/loop.conf
loop
yannick@yannick ~ % cat /etc/modules-load.d/fuse.conf
#Load fuse at boot
fuse
yannick@yannick ~ %
Re: [systemd-modules-load.service] loaded failed failed
Publié : dim. 30 sept. 2012, 14:59
par FoolEcho
Re: [systemd-modules-load.service] loaded failed failed
Publié : dim. 30 sept. 2012, 15:13
par Kainny
merci
et je suppose que c'est normal que tail /var/log/messages.log ne me renvoie rien?
Sinon je dois ouvrir un autre topic pour les erreurs que me renvoie la commande systemctl -t service -a --full | grep error
Re: [systemd-modules-load.service] loaded failed failed(res
Publié : dim. 30 sept. 2012, 15:23
par FoolEcho
Regarde également sur le forum/wiki, il est normal que certains services échouent (je pense à plymouth notamment, car non installé) mais il est possible de les cacher.
Re: [systemd-modules-load.service] loaded failed failed(res
Publié : dim. 30 sept. 2012, 15:27
par Kainny
okay, je fais comme ça.
J'avais vu pour masquer.Et merci pour plymouth.
Au revoir
