Systemd journald logging before /sbin/init?

dear arch experts---I understand that I have an initrd stage that eventually invokes /sbin/init (which is systemd) on a switch_root.  the initrd stage can echo various log information, too.  so, now I am curious: how can the pre-systemd process log output be logged to journald?  can the pre-systemd initrd write to an area of RAM that survives the switch_root and will then be picked up by journald as soon as journald becomes available? 
sincerely,  /iaw

Probably this:
In this page we attempt to roughly describe the interfaces that exist between the initrd and systemd. These interfaces are currently used by dracut and the ?ArchLinux initrds.
- The initrd should mount /run as a tmpfs and pass it pre-mounted when jumping into the main system when executing systemd. The mount options should be mode=755,nodev
http://www.freedesktop.org/wiki/Softwar … Interface/
Would have to re-check the mkinitcpio sources (bash scripts) to see how it "passes over".
There's even more information logged, before systemd actually starts, e.g. from Kernel. (http://0pointer.de/blog/projects/journalctl.html)
You can see that in your log, there's alot of information before:
[...] systemd[1]: systemd 217 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR [...]

Similar Messages

  • Can't see systemd-journald log

    Hi I'm new about arch linux
    I have tired enabling systemd log with system.conf and journald.conf like below.
    But I can't see log
    system.conf
    13 [Manager]                                                                       
    14 LogLevel=debug                                                                 
    15 LogTarget=journal                                                               
    16 LogColor=yes                                                                   
    17 LogLocation=yes
    journald.conf
    13 [Journal]                                                                       
    14 Storage=auto
    after set conf file they show below log only
    Apr 08 17:35:52 MyArch systemd-journal[287]: Journal started
    Apr 08 17:35:52 MyArch systemd-journald[246]: Received SIGTERM from PID 1 (systemd).
    Apr 08 17:37:48 MyArch systemd-journal[299]: Permanent journal is using 24.0M (max allowed 100.0M, trying to leave 108.9M free of 24.0G available → current limit 100.0M).
    Apr 08 17:37:48 MyArch systemd-journal[299]: Journal started
    Apr 08 17:37:54 MyArch systemd-journal[299]: Journal stopped
    Apr 08 17:40:25 MyArch systemd-logind[169]: New session c3 of user jae-young.

    Please use code tags and also include the command that produced the output. Now I'm going to guess you ran `journalctl` as a regular user:
    man journalctl wrote:All users are granted access to their private per-user journals. However, by default, only root and users who are members of the "systemd-journal" group get access to the system journal and the journals of other users.
    There should be no need to enable the journal.
    Last edited by Raynman (2015-04-08 09:27:26)

  • /sbin/init high CPU usage (80%)

    My PC run slowly, I viewed the processes by htop utility and it revealed that /sbin/init has a constantly high CPU usage, around 70-80%. I scanned it with clamscan virus scanner, but not infected. What can I do to fix this problem?

    Did you mean "ps -ef" ? Then:
    UID PID PPID C STIME TTY TIME CMD
    root 1 0 8 Sep22 ? 08:27:41 /usr/lib/systemd/systemd --system --deserialize 131
    root 2 0 0 Sep22 ? 00:00:00 [kthreadd]
    root 3 2 0 Sep22 ? 00:45:38 [ksoftirqd/0]
    root 5 2 0 Sep22 ? 00:00:00 [kworker/0:0H]
    root 7 2 0 Sep22 ? 00:05:10 [rcu_preempt]
    root 8 2 0 Sep22 ? 00:00:03 [rcu_sched]
    root 9 2 0 Sep22 ? 00:00:00 [rcu_bh]
    root 10 2 0 Sep22 ? 00:00:02 [migration/0]
    root 11 2 0 Sep22 ? 00:00:01 [watchdog/0]
    root 12 2 0 Sep22 ? 00:00:01 [watchdog/1]
    root 13 2 0 Sep22 ? 00:00:02 [migration/1]
    root 14 2 0 Sep22 ? 00:54:35 [ksoftirqd/1]
    root 16 2 0 Sep22 ? 00:00:00 [kworker/1:0H]
    root 17 2 0 Sep22 ? 00:00:00 [khelper]
    root 18 2 0 Sep22 ? 00:00:00 [kdevtmpfs]
    root 19 2 0 Sep22 ? 00:00:00 [netns]
    root 20 2 0 Sep22 ? 00:00:00 [khungtaskd]
    root 21 2 0 Sep22 ? 00:00:00 [writeback]
    root 22 2 0 Sep22 ? 00:00:00 [ksmd]
    root 23 2 0 Sep22 ? 00:00:52 [khugepaged]
    root 24 2 0 Sep22 ? 00:00:00 [crypto]
    root 25 2 0 Sep22 ? 00:00:00 [kintegrityd]
    root 26 2 0 Sep22 ? 00:00:00 [bioset]
    root 27 2 0 Sep22 ? 00:00:00 [kblockd]
    root 30 2 0 Sep22 ? 00:05:54 [kswapd0]
    root 31 2 0 Sep22 ? 00:00:00 [fsnotify_mark]
    root 35 2 0 Sep22 ? 00:00:00 [kthrotld]
    root 36 2 0 Sep22 ? 00:00:00 [ipv6_addrconf]
    root 37 2 0 Sep22 ? 00:00:00 [deferwq]
    root 63 2 0 Sep22 ? 00:00:00 [khubd]
    root 64 2 0 Sep22 ? 00:00:00 [firewire]
    root 65 2 0 Sep22 ? 00:00:00 [firewire_ohci]
    root 66 2 0 Sep22 ? 00:00:00 [ata_sff]
    root 68 2 0 Sep22 ? 00:00:00 [scsi_eh_0]
    root 69 2 0 Sep22 ? 00:00:00 [scsi_tmf_0]
    root 70 2 0 Sep22 ? 00:00:00 [scsi_eh_1]
    root 71 2 0 Sep22 ? 00:00:00 [scsi_tmf_1]
    root 74 2 0 Sep22 ? 00:00:00 [scsi_eh_2]
    root 75 2 0 Sep22 ? 00:00:00 [scsi_tmf_2]
    root 76 2 0 Sep22 ? 00:00:00 [scsi_eh_3]
    root 77 2 0 Sep22 ? 00:00:00 [scsi_tmf_3]
    root 88 2 0 Sep22 ? 00:01:22 [kworker/0:1H]
    root 89 2 0 Sep22 ? 00:00:00 [scsi_eh_4]
    root 90 2 0 Sep22 ? 00:00:00 [scsi_tmf_4]
    root 91 2 0 Sep22 ? 00:00:07 [usb-storage]
    root 99 2 0 Sep22 ? 00:00:00 [kworker/1:1H]
    root 101 2 0 Sep22 ? 00:00:27 [jbd2/sda1-8]
    root 102 2 0 Sep22 ? 00:00:00 [ext4-rsv-conver]
    root 130 1 0 Sep22 ? 00:08:22 /usr/lib/systemd/systemd-journald
    root 145 2 0 Sep22 ? 00:00:00 [rpciod]
    root 147 2 0 Sep22 ? 00:00:00 [nfsiod]
    root 163 1 0 Sep22 ? 00:00:00 /usr/lib/systemd/systemd-udevd
    root 221 2 0 Sep22 ? 00:00:00 [kpsmoused]
    root 243 1 1 Sep22 ? 01:39:24 /sbin/mount.ntfs-3g /dev/sda2 /mnt/ntfs -n -o rw,uid=1000,gid=100,dmask=022,fmask=133
    root 251 1 0 Sep22 ? 00:00:34 /usr/lib/systemd/systemd-logind
    dbus 253 1 0 Sep22 ? 00:02:38 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
    root 254 1 0 Sep22 ? 00:02:32 /usr/bin/haveged -w 1024 -v 1
    root 255 1 0 Sep22 ? 00:00:00 /usr/bin/dhcpcd -q -b
    rpc 258 1 0 Sep22 ? 00:00:00 /usr/bin/rpcbind -w
    root 288 1 0 Sep22 ? 00:00:13 /usr/bin/NetworkManager --no-daemon
    root 295 1 0 Sep22 ? 00:00:00 /usr/sbin/rpc.idmapd
    root 330 2 0 Sep22 ? 00:00:00 [cfg80211]
    polkitd 333 1 0 Sep22 ? 00:00:09 /usr/lib/polkit-1/polkitd --no-debug
    tor 436 1 0 Sep22 ? 00:03:27 /usr/bin/tor -f /etc/tor/torrc
    privoxy 438 1 0 Sep22 ? 00:00:00 /usr/bin/privoxy --pidfile /run/privoxy.pid --user privoxy.privoxy /etc/privoxy/config
    root 445 1 0 Sep22 ? 00:00:00 /usr/sbin/rpc.statd --no-notify
    root 449 1 0 Sep22 ? 00:00:00 /usr/sbin/rpc.mountd
    root 466 2 0 Sep22 ? 00:00:00 [nfsv4.0-svc]
    root 500 1 0 Sep22 ? 00:00:00 /usr/sbin/lxdm-binary
    root 503 500 6 Sep22 tty7 06:37:07 /usr/bin/Xorg.bin :0 vt07 -nolisten tcp -novtswitch
    root 1755 500 0 Sep22 ? 00:00:00 /usr/lib/lxdm/lxdm-session
    walaki 1756 1 0 Sep22 ? 00:00:00 /usr/lib/systemd/systemd --user
    walaki 1757 1756 0 Sep22 ? 00:00:00 (sd-pam)
    walaki 1763 1755 0 Sep22 ? 00:00:00 /bin/sh /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/xserverrc
    walaki 1773 1 0 Sep22 ? 00:00:00 dbus-launch --sh-syntax --exit-with-session
    walaki 1774 1 0 Sep22 ? 00:00:21 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
    walaki 1781 1763 0 Sep22 ? 00:00:46 xfce4-session
    walaki 1784 1 0 Sep22 ? 00:00:00 /usr/lib/xfce4/xfconf/xfconfd
    walaki 1789 1 0 Sep22 ? 00:00:16 /usr/bin/gpg-agent --sh --daemon --enable-ssh-support --write-env-file /home/walaki/.cache/gpg-agent-info
    walaki 1792 1781 0 Sep22 ? 00:01:54 xfwm4 --display :0.0 --sm-client-id 23fec2b63-e849-4a72-8ded-64b47902bd41
    walaki 1795 1781 0 Sep22 ? 00:00:35 Thunar --sm-client-id 2d0147b28-0a91-4a3b-a669-064fc26ae553 --daemon
    walaki 1797 1781 0 Sep22 ? 00:09:43 xfce4-panel --display :0.0 --sm-client-id 247d7309b-f81b-4064-adbd-0875fed923d4
    walaki 1798 1781 0 Sep22 ? 00:00:18 xfdesktop --display :0.0 --sm-client-id 2e572e480-670a-4c6f-af62-2339f19929ef
    walaki 1799 1 0 Sep22 ? 00:00:36 xfsettingsd --display :0.0 --sm-client-id 26269b48e-af0b-4399-b385-5305502e24f1
    walaki 1802 1781 1 Sep22 ? 01:24:09 /usr/lib/skype/skype -session 21d1f7d38-8c0a-41de-98b7-021e4f2a5bd7_1410900031_251500
    walaki 1803 1781 0 Sep22 ? 00:00:06 kruler -session 20c051002-8d7b-4c2c-bf0b-c384f149b9b5_1410900031_629257
    walaki 1806 1 0 Sep22 ? 00:00:01 xfce4-power-manager --restart --sm-client-id 2154ad16d-be90-40bc-8354-c2647728cf16
    walaki 1810 1 0 Sep22 ? 00:00:00 /usr/lib/gvfs/gvfsd
    walaki 1823 1 0 Sep22 ? 00:00:00 /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
    walaki 1825 1797 0 Sep22 ? 00:00:02 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libsystray.so 6 14680094 systray Notification Area Area where notification icons appear
    walaki 1833 1797 0 Sep22 ? 00:00:07 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libmixer.so 15 14680095 mixer Audio Mixer Adjust volume levels
    walaki 1834 1797 0 Sep22 ? 00:44:27 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libweather.so 16 14680096 weather Weather Update Show current weather conditions
    walaki 1835 1797 0 Sep22 ? 00:46:02 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libsystemload.so 17 14680097 systemload System Load Monitor Monitor CPU load, swap usage and memory footprint
    walaki 1836 1797 0 Sep22 ? 00:00:03 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libactions.so 2 14680098 actions Action Buttons Log out, lock or other system actions
    walaki 1841 1797 0 Sep22 ? 00:00:03 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libthunar-tpa.so 8 14680102 thunar-tpa Trash Applet Display the trash can
    walaki 1843 1 0 Sep22 ? 00:00:04 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
    walaki 1846 1 0 Sep22 ? 00:00:03 /usr/lib/gvfs/gvfsd-trash --spawner :1.9 /org/gtk/gvfs/exec_spaw/0
    root 1856 1 0 Sep22 ? 00:00:00 /usr/lib/upower/upowerd
    root 1857 1 0 Sep22 ? 00:02:10 /usr/lib/udisks2/udisksd --no-debug
    walaki 1862 1 0 Sep22 ? 00:09:10 kwooty -session 2fc05dbf4-9492-4cf1-bd80-efe7e47dfb90_1410900031_251208
    walaki 1895 1 0 Sep22 ? 00:00:00 /usr/lib/GConf/gconfd-2
    walaki 1904 1 0 Sep22 ? 00:00:05 /usr/bin/python2 /usr/bin/glipper
    walaki 1907 1 0 Sep22 ? 00:00:06 nm-applet
    walaki 1922 1 0 Sep22 ? 00:00:00 /usr/lib/at-spi2-core/at-spi-bus-launcher
    walaki 1926 1922 0 Sep22 ? 00:00:25 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
    walaki 1930 1 0 Sep22 ? 00:00:03 /usr/lib/evolution/3.12/evolution-alarm-notify
    walaki 1936 1 1 Sep22 ? 01:59:26 firefox
    walaki 1938 1 0 Sep22 ? 00:01:08 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
    walaki 2023 1 0 Sep22 ? 00:00:00 /usr/lib/evolution-data-server/evolution-source-registry
    walaki 2043 1 0 Sep22 ? 00:00:25 /usr/lib/gnome-online-accounts/goa-daemon
    walaki 2058 1 0 Sep22 ? 00:00:01 /usr/lib/evolution-data-server/evolution-calendar-factory
    walaki 2084 1 0 Sep22 ? 00:00:00 kdeinit4: kdeinit4 Runnin e
    walaki 2089 2084 0 Sep22 ? 00:00:00 kdeinit4: klauncher [kdei e
    walaki 2101 1 0 Sep22 ? 00:00:06 kdeinit4: kded4 [kdeinit]
    walaki 5752 1 0 Sep22 ? 00:00:01 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
    walaki 5887 1789 0 Sep22 ? 00:01:01 scdaemon --multi-server
    walaki 7557 11505 0 11:19 pts/8 00:00:00 /bin/bash
    walaki 8876 19571 0 12:04 pts/4 00:00:03 mc
    walaki 8878 8876 0 12:04 pts/9 00:00:00 bash -rcfile .bashrc
    root 10950 2 0 18:10 ? 00:00:02 [kworker/u4:1]
    walaki 10953 18727 0 18:10 pts/6 00:00:04 mc
    walaki 10955 10953 0 18:10 pts/7 00:00:00 bash -rcfile .bashrc
    walaki 11492 1797 0 Sep23 ? 00:02:06 /usr/bin/python2 /usr/bin/terminator
    walaki 11504 11492 0 Sep23 ? 00:00:00 gnome-pty-helper
    walaki 11505 11492 0 Sep23 pts/8 00:00:00 /bin/bash
    walaki 12283 1797 0 13:19 ? 00:00:26 /usr/bin/python2 /usr/bin/terminator
    walaki 12299 12283 0 13:19 ? 00:00:00 gnome-pty-helper
    walaki 12300 12283 0 13:19 pts/1 00:00:00 /bin/bash
    walaki 12707 1797 0 13:23 ? 00:02:59 geany
    walaki 12713 12707 0 13:23 ? 00:00:00 gnome-pty-helper
    walaki 12714 12707 0 13:23 pts/11 00:00:00 /bin/bash
    walaki 13471 1797 0 18:31 ? 00:00:18 /usr/bin/python2 /usr/bin/terminator
    walaki 13487 13471 0 18:31 ? 00:00:00 gnome-pty-helper
    walaki 13488 13471 0 18:31 pts/3 00:00:00 /bin/bash
    walaki 13751 13488 0 18:33 pts/3 00:00:00 /bin/bash
    walaki 16906 1797 46 13:59 ? 04:12:08 /usr/lib/opera-next/opera-next
    walaki 18711 1797 0 Sep23 ? 00:05:05 /usr/bin/python2 /usr/bin/terminator
    walaki 18726 18711 0 Sep23 ? 00:00:00 gnome-pty-helper
    walaki 18727 18711 0 Sep23 pts/6 00:00:00 /bin/bash
    walaki 19550 1797 0 Sep22 ? 00:01:48 /usr/bin/python2 /usr/bin/terminator
    walaki 19570 19550 0 Sep22 ? 00:00:00 gnome-pty-helper
    walaki 19571 19550 0 Sep22 pts/4 00:00:00 /bin/bash
    walaki 21931 23464 3 20:17 ? 00:04:59 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=AutoReloadExperiment/Enabled/ChromeSuggestions/Most Likely with Kodachrome/ExtensionInstallVerification/None/OmniboxBundledExperimentV1/StandardR4/Prerender/PrerenderEnabled/PrerenderFromOmnibox/OmniboxPrerenderEnabled/PrerenderLocalPredictorSpec/LocalPredictor=Disabled/SPDY/SpdyDisabled/SettingsEnforcement/no_enforcement/Test0PercentDefault/group_01/UMA-Dynamic-Binary-Uniformity-Trial/default/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Population-Restrict/normal/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-1-Percent/group_22/UMA-Uniformity-Trial-10-Percent/group_05/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_03/UMA-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-50-Percent/default/VoiceTrigger/Install/ --renderer-print-preview --enable-offline-auto-reload --enable-threaded-compositing --enable-delegated-renderer --disable-accelerated-video-decode --disable-webrtc-hw-encoding --disable-gpu-compositing --channel=23445.24.769536197
    walaki 22985 23464 0 20:39 ? 00:00:55 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=AutoReloadExperiment/Enabled/ChromeSuggestions/Most Likely with Kodachrome/ExtensionInstallVerification/None/OmniboxBundledExperimentV1/StandardR4/Prerender/PrerenderEnabled/PrerenderFromOmnibox/OmniboxPrerenderEnabled/PrerenderLocalPredictorSpec/LocalPredictor=Disabled/SPDY/SpdyDisabled/SettingsEnforcement/no_enforcement/Test0PercentDefault/group_01/UMA-Dynamic-Binary-Uniformity-Trial/default/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Population-Restrict/normal/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-1-Percent/group_22/UMA-Uniformity-Trial-10-Percent/group_05/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_03/UMA-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-50-Percent/default/VoiceTrigger/Install/ --renderer-print-preview --enable-offline-auto-reload --enable-threaded-compositing --enable-delegated-renderer --disable-accelerated-video-decode --disable-webrtc-hw-encoding --disable-gpu-compositing --channel=23445.25.841939391
    walaki 23052 23464 2 20:40 ? 00:03:57 /opt/google/chrome/chrome --type=ppapi --channel=23445.26.1843768387 --ppapi-flash-args --lang=en-US
    walaki 23445 1 3 15:02 ? 00:16:57 /opt/google/chrome/chrome
    walaki 23453 23445 0 15:02 ? 00:00:05 /opt/google/chrome/chrome --type=sandbox-ipc
    walaki 23454 23445 0 15:02 ? 00:00:00 /opt/google/chrome/chrome-sandbox /opt/google/chrome/chrome --type=zygote
    walaki 23455 23454 0 15:02 ? 00:00:00 /opt/google/chrome/chrome --type=zygote
    walaki 23461 23455 0 15:02 ? 00:00:00 /opt/google/chrome/chrome-sandbox /opt/google/chrome/nacl_helper
    walaki 23462 23461 0 15:02 ? 00:00:00 /opt/google/chrome/nacl_helper
    walaki 23464 23455 0 15:02 ? 00:00:00 /opt/google/chrome/chrome --type=zygote
    walaki 23484 23445 0 15:03 ? 00:00:04 /opt/google/chrome/chrome --type=gpu-process --channel=23445.0.587379006 --supports-dual-gpus=false --gpu-driver-bug-workarounds=1,14,20,23,43 --disable-accelerated-video-decode --gpu-vendor-id=0x10de --gpu-device-id=0x0322 --gpu-driver-vendor --gpu-driver-version
    walaki 23672 23464 0 15:04 ? 00:01:06 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=AutoReloadExperiment/Enabled/ChromeSuggestions/Most Likely with Kodachrome/ExtensionInstallVerification/None/OmniboxBundledExperimentV1/StandardR4/Prerender/PrerenderEnabled/PrerenderFromOmnibox/OmniboxPrerenderEnabled/PrerenderLocalPredictorSpec/LocalPredictor=Disabled/SPDY/SpdyDisabled/SettingsEnforcement/no_enforcement/Test0PercentDefault/group_01/UMA-Dynamic-Binary-Uniformity-Trial/default/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Population-Restrict/normal/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-1-Percent/group_22/UMA-Uniformity-Trial-10-Percent/group_05/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_03/UMA-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-50-Percent/default/VoiceTrigger/Install/ --renderer-print-preview --enable-offline-auto-reload --enable-threaded-compositing --enable-delegated-renderer --disable-accelerated-video-decode --disable-webrtc-hw-encoding --disable-gpu-compositing --channel=23445.5.858801638
    root 23962 288 0 Sep25 ? 00:00:00 /usr/bin/dhclient -d -sf /usr/lib/networkmanager/nm-dhcp-helper -pf /var/run/dhclient-enp2s8.pid -lf /var/lib/NetworkManager/dhclient-a8966a98-c9d9-4425-9e4d-459c41d83921-enp2s8.lease -cf /var/lib/NetworkManager/dhclient-enp2s8.conf enp2s8
    root 24159 1 0 15:08 tty2 00:00:00 /sbin/agetty --noclear tty2 linux
    root 24165 1 0 15:08 tty3 00:00:00 /sbin/agetty --noclear tty3 linux
    root 24169 1 0 15:08 tty5 00:00:00 /sbin/agetty --noclear tty5 linux
    root 24174 1 0 15:08 tty6 00:00:00 /sbin/agetty --noclear tty6 linux
    walaki 25161 1 2 Sep23 ? 02:22:03 audacious
    root 25840 2 0 21:32 ? 00:00:01 [kworker/1:1]
    walaki 27082 23464 4 21:51 ? 00:02:56 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=AutoReloadExperiment/Enabled/ChromeSuggestions/Most Likely with Kodachrome/ExtensionInstallVerification/None/OmniboxBundledExperimentV1/StandardR4/Prerender/PrerenderEnabled/PrerenderFromOmnibox/OmniboxPrerenderEnabled/PrerenderLocalPredictorSpec/LocalPredictor=Disabled/SPDY/SpdyDisabled/SettingsEnforcement/no_enforcement/Test0PercentDefault/group_01/UMA-Dynamic-Binary-Uniformity-Trial/default/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Population-Restrict/normal/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-1-Percent/group_22/UMA-Uniformity-Trial-10-Percent/group_05/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_03/UMA-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-50-Percent/default/VoiceTrigger/Install/ --renderer-print-preview --enable-offline-auto-reload --enable-threaded-compositing --enable-delegated-renderer --disable-accelerated-video-decode --disable-webrtc-hw-encoding --disable-gpu-compositing --channel=23445.29.1207326524
    root 27424 2 0 22:00 ? 00:00:00 [kworker/0:1]
    root 27664 2 0 15:42 ? 00:00:04 [kworker/u4:2]
    root 27769 2 0 22:07 ? 00:00:00 [kworker/1:2]
    walaki 28865 1 0 Sep25 ? 00:00:00 /usr/lib/gvfs/gvfsd-http --spawner :1.9 /org/gtk/gvfs/exec_spaw/1
    walaki 29628 8878 0 22:54 pts/9 00:00:02 /usr/bin/ruby /home/walaki/util/mr1 Nekem az ég - hazafutás
    walaki 29652 23464 0 22:54 ? 00:00:00 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=AutoReloadExperiment/Enabled/ChromeSuggestions/Most Likely with Kodachrome/ExtensionInstallVerification/None/OmniboxBundledExperimentV1/StandardR4/Prerender/PrerenderEnabled/PrerenderFromOmnibox/OmniboxPrerenderEnabled/PrerenderLocalPredictorSpec/LocalPredictor=Disabled/SPDY/SpdyDisabled/SettingsEnforcement/no_enforcement/Test0PercentDefault/group_01/UMA-Dynamic-Binary-Uniformity-Trial/default/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Population-Restrict/normal/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-1-Percent/group_22/UMA-Uniformity-Trial-10-Percent/group_05/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_03/UMA-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-50-Percent/default/VoiceTrigger/Install/ --renderer-print-preview --enable-offline-auto-reload --enable-threaded-compositing --enable-delegated-renderer --disable-accelerated-video-decode --disable-webrtc-hw-encoding --disable-gpu-compositing --channel=23445.30.161699173
    root 29693 2 0 22:55 ? 00:00:00 [kworker/0:2]
    root 29915 2 0 23:00 ? 00:00:00 [kworker/0:0]
    root 29930 27664 89 23:00 ? 00:00:31 /usr/lib/systemd/systemd-coredump 29431 1000 100 6 1411765249 wavparse1374:si
    walaki 29946 10955 0 23:01 pts/7 00:00:00 ps -ef
    walaki 29948 10955 0 23:01 pts/7 00:00:00 leafpad
    walaki 30148 1 0 Sep23 ? 00:00:00 /usr/lib/dconf/dconf-service
    walaki 30523 1 0 Sep25 ? 00:00:00 /bin/sh /home/walaki/jdownloader/JDLauncher
    walaki 30544 30523 0 Sep25 ? 00:04:54 /usr/lib/jvm/java-default-runtime/bin/java -Dinstall4j.jvmDir=/usr -Dexe4j.moduleName=/home/walaki/jdownloader/JDLauncher -Xmx512m -Xms64m -Dinstall4j.launcherId=26 -Dinstall4j.swt=false -Di4j.vmov=true -Di4j.vmov=true -Di4j.vmov=true -Di4j.vmov=true -Di4j.vmov=true -Di4j.vpt=true -classpath /home/walaki/jdownloader/.install4j/i4jruntime.jar:/home/walaki/jdownloader/JDownloader.jar com.install4j.runtime.launcher.Launcher launch jd.Main true false true true false true true 0 0 20 20 Arial 0,0,0 8 500 version 0.9 20 40 Arial 0,0,0 8 500 -1

  • (Solved) systemd-journald extremely high CPU usage

    I started noticing this problem a few days ago, but I thought it was because I was running too much with too little RAM. But when running nothing more than a KDE desktop, my CPU usage bounces between 50% and 100%, making things laggy. It looks like systemd-journald is to blame, as it is using 50% of the CPU. This is an AMD Phenom II dual core, so this definitely shouldn't be happening. I noticed journal logs were more than 2 GB, so I deleted everything within /var/log/journal/. Rebooted, no change, so I disabled journal storage, but that did not solve the problem.
    Nothing in the logs looks like a problem to me:
    $ sudo journalctl
    -- Logs begin at Tue 2013-03-12 17:31:37 PDT, end at Tue 2013-03-12 18:15:56 PDT. --
    Mar 12 17:31:37 silverstone systemd-journal[149]: Allowing runtime journal files to grow to 298.6M.
    Mar 12 17:31:37 silverstone kernel: Initializing cgroup subsys cpuset
    Mar 12 17:31:37 silverstone kernel: Initializing cgroup subsys cpu
    Mar 12 17:31:37 silverstone kernel: Linux version 3.7.10-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.2 (G
    Mar 12 17:31:37 silverstone kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=31669ea0-76db
    Mar 12 17:31:37 silverstone kernel: e820: BIOS-provided physical RAM map:
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000000e2000-0x00000000000fffff] reserved
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cff8ffff] usable
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cff90000-0x00000000cff9dfff] ACPI data
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cff9e000-0x00000000cffdffff] ACPI NVS
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cffe0000-0x00000000cfffffff] reserved
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000100000000-0x00000001afffffff] usable
    Mar 12 17:31:37 silverstone kernel: NX (Execute Disable) protection: active
    Mar 12 17:31:37 silverstone kernel: SMBIOS 2.5 present.
    Mar 12 17:31:37 silverstone kernel: DMI: MSI MS-7642/890GXM-G65 (MS-7642) , BIOS V1.2 03/31/2010
    Mar 12 17:31:37 silverstone kernel: e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
    Mar 12 17:31:37 silverstone kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Mar 12 17:31:37 silverstone kernel: No AGP bridge found
    Mar 12 17:31:37 silverstone kernel: e820: last_pfn = 0x1b0000 max_arch_pfn = 0x400000000
    Mar 12 17:31:37 silverstone kernel: MTRR default type: uncachable
    Mar 12 17:31:37 silverstone kernel: MTRR fixed ranges enabled:
    Mar 12 17:31:37 silverstone kernel: 00000-9FFFF write-back
    Mar 12 17:31:37 silverstone kernel: A0000-EFFFF uncachable
    Mar 12 17:31:37 silverstone kernel: F0000-FFFFF write-protect
    Mar 12 17:31:37 silverstone kernel: MTRR variable ranges enabled:
    Mar 12 17:31:37 silverstone kernel: 0 base 000000000000 mask FFFF80000000 write-back
    Mar 12 17:31:37 silverstone kernel: 1 base 000080000000 mask FFFFC0000000 write-back
    Mar 12 17:31:37 silverstone kernel: 2 base 0000C0000000 mask FFFFF0000000 write-back
    Mar 12 17:31:37 silverstone kernel: 3 disabled
    Mar 12 17:31:37 silverstone kernel: 4 disabled
    Mar 12 17:31:37 silverstone kernel: 5 disabled
    Mar 12 17:31:37 silverstone kernel: 6 disabled
    Mar 12 17:31:37 silverstone kernel: 7 disabled
    Mar 12 17:31:37 silverstone kernel: TOM2: 00000001b0000000 aka 6912M
    Mar 12 17:31:37 silverstone kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Mar 12 17:31:37 silverstone kernel: e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved
    Mar 12 17:31:37 silverstone kernel: e820: last_pfn = 0xcff90 max_arch_pfn = 0x400000000
    Mar 12 17:31:37 silverstone kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [ffff880
    Mar 12 17:31:37 silverstone kernel: initial memory mapped: [mem 0x00000000-0x1fffffff]
    Mar 12 17:31:37 silverstone kernel: Base memory trampoline at [ffff880000099000] 99000 size 24576
    $ systemctl status systemd-journald
    systemd-journald.service - Journal Service
    Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
    Active: active (running) since Tue 2013-03-12 18:10:41 PDT; 8min ago
    Docs: man:systemd-journald.service(8)
    man:journald.conf(5)
    Main PID: 142 (systemd-journal)
    Status: "Processing requests..."
    CGroup: name=systemd:/system/systemd-journald.service
    `-142 /usr/lib/systemd/systemd-journald
    However, it looks like the log files keep getting corrupted:
    $ sudo journalctl --verify
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-000000000007f543-0004d7c4445effa4.journal
    Invalid object contents at 124687944ââââââââââââââââââââââââââââââââââââââââââ 49%
    File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000a8cb7-0004d7c3d52e9748.journal:124687944 (of 134074368, 92%).
    FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000a8cb7-0004d7c3d52e9748.journal (Bad message)
    Invalid object contents at 75715936âââââââââââââââââââââââââââââââââââââââââââ 49%
    File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system.journal:75715936 (of 76156928, 99%).
    FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system.journal (Bad message)
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000290d6-0004d7c3a0033472.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-0000000000000001-0004d7c413227650.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/[email protected]~
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000fcfc0-0004d7c3fd8ee9c5.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/[email protected]~
    Invalid object contents at 124701856ââââââââââââââââââââââââââââââââââââââââââ 49%
    File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-0000000000000001-0004d7c3876dda65.journal:124701856 (of 134049792, 93%).
    FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-0000000000000001-0004d7c3876dda65.journal (Bad message)
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-00000000000a9da8-0004d7c45187e39e.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000d26b1-0004d7c3ea1b73f7.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-000000000002a43f-0004d7c425785944.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000539fb-0004d7c3b2d1f935.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-0000000000054d23-0004d7c4354da4ef.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/user-1000@2c1af599e637441985385fe37ded2a2c-0000000000001706-0004d7c38cd3de88.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/user-1000@5e6edd359123491f9998a310206ccbf9-00000000000019b4-0004d7c4153f8628.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-000000000007e345-0004d7c3c3ed8197.journal
    I am using a two or three year old SSD, so maybe it has gotten some bad sectors? But that doesn't explain why journald still bricks things when it isn't logging anything. The install is 10 months old, and I switched from init to systemd around October. Is there anything I can do, short of reinstalling?
    Thanks,
    Nicholas
    Last edited by bicyclingrevolution (2013-03-14 05:57:13)

    Thanks for the tip ilkyest, but it didn't make any difference to the systemd-journald problem.
    However, I looked at journalctl again and found it cluttered with CUPS failures:
    -- Logs begin at Tue 2013-03-12 19:17:00 PDT, end at Wed 2013-03-13 22:31:31 PDT. --
    Mar 12 19:17:00 silverstone spideroak_inotify[796]: Program started
    Mar 12 19:21:30 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 7199 messages from /system
    Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
    Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 5471 messages from /system
    Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 5699 messages from /system
    Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
    Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
    Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
    Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
    Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
    Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
    Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:30 silverstone systemd-coredump[1592]: Process 1590 (cupsd) dumped core.
    Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_3840-Gray..
    Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_3840-RGB..
    Mar 12 19:21:28 silverstone colord[354]: Device added: cups-Deskjet_3840
    Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_F4100-Gray..
    Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_F4100-RGB..
    Mar 12 19:21:28 silverstone colord[354]: Device added: cups-Deskjet_F4100
    Mar 12 19:21:28 silverstone dbus[337]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Mar 12 19:21:28 silverstone dbus[337]: [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
    Mar 12 19:21:28 silverstone colord[354]: Profile removed: Deskjet_3840-Gray..
    Mar 12 19:21:28 silverstone colord[354]: Profile removed: Deskjet_3840-RGB..
    Mar 12 19:21:28 silverstone colord[354]: device removed: cups-Deskjet_3840
    Mar 12 19:21:31 silverstone colord[354]: Profile removed: Deskjet_F4100-Gray..
    Mar 12 19:21:31 silverstone colord[354]: Profile removed: Deskjet_F4100-RGB..
    Mar 12 19:21:31 silverstone colord[354]: device removed: cups-Deskjet_F4100
    Mar 12 19:21:31 silverstone dbus-daemon[337]: dbus[337]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Mar 12 19:21:31 silverstone dbus-daemon[337]: dbus[337]: [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 director
    Mar 12 19:21:31 silverstone systemd-journal[143]: Missed 6365 kernel messages
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone cupsd[1590]: Unknown directive DefaultAuthType on line 9.
    Mar 12 19:21:31 silverstone cupsd[1590]: cupsd: client.c:757: avahi_client_get_host_name: Assertion `client' failed.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone cupsd[1594]: Unknown directive DefaultAuthType on line 9.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Disabling cups solved the CPU usage issue.
    It looks like the root of the problem is Avahi failing to start, but I have no idea why it isn't working.
    $ systemctl status dbus-org.freedesktop.Avahi.service
    dbus-org.freedesktop.Avahi.service
    Loaded: error (Reason: No such file or directory)
    Active: inactive (dead)

  • [SOLVED] systemd-journald & tmpfiles-setup Failures

    Hello,
    I have a weird situation. After I've finished installing my system, I got errors with journald...
    After logging as root I get the following errors:
    systemd-journald[338]: Failed to get machine id: No such file or directory
    systemd-journald[340]: Failed to get machine id: No such file or directory
    systemd-journald[345]: Failed to get machine id: No such file or directory
    systemd-journald[347]: Failed to get machine id: No such file or directory
    systemd-journald[349]: Failed to get machine id: No such file or directory
    systemd[1]: Failed to start Journal Service.
    systemd[1]: Dependency failed for Trigger Flushing of Journal to Presistent Storage.
    systemd[1]: Failed to start Journal Service
    and after I typed
    systemctl
    to see what's more, I got errors at the following:
    systemd-journal-flush.service loaded failed failed
    systemd-journald.service loaded failed failed
    systemd-tmpfiles-setup-dev.service loaded failed failed
    systemd-tmpfiles-setup.service loaded failed failed
    systemd-journald-dev-log.socket loaded failed failed
    systemd-journald.socket loaded failed failed
    and other problems related to the above like
    Failed to start Cleanup of Temporary Directories.
    Note that it is my first time I have problems with journald and tmpfiles-setup and I'm not sure what happened...
    Any help would be very appreciated and thank you very much in advance.
    Last edited by heyom (2014-08-30 09:24:24)

    I just had the same problem while installing a new Arch system. I managed to fix it by running `systemd-machine-id-setup` as root (not sudo).
    Also, before I did that, while installing a package I got an error message about dbus not finding a machine id, and that error message suggested running `dbus-uuidgen > /var/lib/dbus/machine-id` (again as root, not sudo). So, you may need to do that, too.

  • Systemd services starting before network is up

    I have a couple services that need the network to be up before they start. I have After=network.target in my .service unit. I have also tried After=netctl@ovh_net_eth0.service both did not work. Services error because no network when they are started. I have tried Google and searching the forums here and I am stumped.
    Services
    systemctl --type=service
    UNIT LOAD ACTIVE SUB DESCRIPTION
    cronie.service loaded active running Periodic Command Scheduler
    dbus.service loaded active running D-Bus System Message Bus
    [email protected] loaded active running Getty on tty1
    kmod-static-nodes.service loaded active exited Create list of required static device nodes for the current kernel
    netctl@ovh_net_eth0.service loaded active exited A basic static ethernet connection
    sshd.service loaded active running OpenSSH Daemon
    systemd-backlight@backlight:acpi_video0.service loaded active exited Load/Save Screen Backlight Brightness of backlight:acpi_video0
    systemd-journal-flush.service loaded active exited Flush Journal to Persistent Storage
    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 Systems
    systemd-sysctl.service loaded active exited Apply Kernel Variables
    systemd-timesyncd.service loaded active running Network Time Synchronization
    systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
    systemd-tmpfiles-setup.service loaded active exited Create 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-update-utmp.service loaded active exited Update UTMP about System Boot/Shutdown
    systemd-user-sessions.service loaded active exited Permit User Sessions
    systemd-vconsole-setup.service loaded active exited Setup Virtual Console
    [email protected] loaded active running User Manager for UID 1000
    UNIT LOAD ACTIVE SUB DESCRIPTION
    proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point
    sys-devices-pci0000:00-0000:00:02.0-backlight-acpi_video0.device loaded active plugged /sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video0
    sys-devices-pci0000:00-0000:00:1c.0-0000:01:00.0-net-eth0.device loaded active plugged 82574L Gigabit Network Connection
    sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda1.device loaded active plugged INTEL_SSDSA2CT040G3 1
    sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda2.device loaded active plugged INTEL_SSDSA2CT040G3 swap-sda2
    sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda.device loaded active plugged INTEL_SSDSA2CT040G3
    sys-devices-platform-serial8250-tty-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
    sys-devices-platform-serial8250-tty-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
    sys-devices-pnp0-00:08-tty-ttyS1.device loaded active plugged /sys/devices/pnp0/00:08/tty/ttyS1
    sys-devices-pnp0-00:09-tty-ttyS0.device loaded active plugged /sys/devices/pnp0/00:09/tty/ttyS0
    sys-module-configfs.device loaded active plugged /sys/module/configfs
    sys-subsystem-net-devices-eth0.device loaded active plugged 82574L Gigabit Network Connection
    -.mount loaded active mounted /
    dev-hugepages.mount loaded active mounted Huge Pages File System
    dev-mqueue.mount loaded active mounted POSIX Message Queue File System
    run-user-1000.mount loaded active mounted /run/user/1000
    sys-kernel-config.mount loaded active mounted Configuration File System
    sys-kernel-debug.mount loaded active mounted Debug File System
    tmp.mount loaded active mounted Temporary Directory
    systemd-ask-password-console.path loaded active waiting Dispatch Password Requests to Console Directory Watch
    systemd-ask-password-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch
    session-c2.scope loaded active running Session c2 of user concopa
    cronie.service loaded active running Periodic Command Scheduler
    dbus.service loaded active running D-Bus System Message Bus
    [email protected] loaded active running Getty on tty1
    kmod-static-nodes.service loaded active exited Create list of required static device nodes for the current kern
    netctl@ovh_net_eth0.service loaded active exited A basic static ethernet connection
    sshd.service loaded active running OpenSSH Daemon
    systemd-backlight@backlight:acpi_video0.service loaded active exited Load/Save Screen Backlight Brightness of backlight:acpi_video0
    systemd-journal-flush.service loaded active exited Flush Journal to Persistent Storage
    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 Systems
    systemd-sysctl.service loaded active exited Apply Kernel Variables
    systemd-timesyncd.service loaded active running Network Time Synchronization
    systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
    systemd-tmpfiles-setup.service loaded active exited Create 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-update-utmp.service loaded active exited Update UTMP about System Boot/Shutdown
    systemd-user-sessions.service loaded active exited Permit User Sessions
    systemd-vconsole-setup.service loaded active exited Setup Virtual Console
    [email protected] loaded active running User Manager for UID 1000
    -.slice loaded active active Root Slice
    system-getty.slice loaded active active system-getty.slice
    system-netctl.slice loaded active active system-netctl.slice

    I tried adding "Requires=" still not working as planned. OVH dedicated box that had networking installed out of the box. I wonder if I need to do some tweaking there.  I just looked at boot log and services are starting before the network is up. Removed some lines to make it more readable. Dec 29 15:35:52 systemd[254]: Starting autodl screen irssi... is what I need to wait for network to be up before starting.
    Dec 29 15:35:52 systemd[254]: pam_unix(systemd-user:session): session opened for user by (uid=0)
    Dec 29 15:35:52 systemd[254]: Starting Paths.
    Dec 29 15:35:52 systemd[254]: Reached target Paths.
    Dec 29 15:35:52 systemd[254]: Starting Timers.
    Dec 29 15:35:52 systemd[254]: Reached target Timers.
    Dec 29 15:35:52 systemd[254]: Starting -.slice.
    Dec 29 15:35:52 systemd[254]: Created slice -.slice.
    Dec 29 15:35:52 systemd[254]: Starting Sockets.
    Dec 29 15:35:52 systemd[254]: Reached target Sockets.
    Dec 29 15:35:52 systemd[254]: Starting Basic System.
    Dec 29 15:35:52 systemd[254]: Reached target Basic System.
    Dec 29 15:35:52 systemd[254]: Starting autodl screen irssi...
    Dec 29 15:35:52 systemd[254]: Started autodl screen irssi.
    Dec 29 15:35:52 systemd[254]: Starting Default.
    Dec 29 15:35:52 systemd[254]: Reached target Default.
    Dec 29 15:35:52 systemd[254]: Startup finished in 156ms.
    Dec 29 15:35:57 network[294]: Starting network profile 'ovh_net_eth0'...
    Dec 29 15:35:57 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    Dec 29 15:35:58 kernel: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
    Dec 29 15:35:58 kernel: e1000e 0000:01:00.0 eth0: 10/100 speed: disabling TSO
    Dec 29 15:35:58 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    Dec 29 15:36:00 network[294]: Started network profile 'ovh_net_eth0'

  • [SOLVED] after upgrade : /sbin/init does not exist. Bailing out, ...

    hi, after having upgraded today my archlinux, I cannot boot it. I get the following message : "ERROR: Root device mounted successfully, but /sbin/init does not exist. Bailing out, you are on you own. Good luck."
    The last time the system was upgraded was in june 2013, before the "Binaries move to /usr/bin requiring update intervention" advisory (https://www.archlinux.org/news/binaries … ervention/). So before upgrading I followed the instructions given in this article and was able to upgrade. But after reboot I got the error message I'm reporting here.
    Here is a copy  of the config I'm using to boot arch in grub:
    menuentry "Archlinux" {
            load_video
            set gfxpayload=keep
            insmod gzio
            insmod part_msdos
            insmod ext2
            set root='hd0,msdos7'
            echo 'Loading of Archlinux, kernel v.3.xx.xx ...'
            linux /boot/vmlinuz-linux root=/dev/sda7 ro
            initrd /boot/initramfs-linux.img
    Last edited by heavytull (2014-03-06 21:24:48)

    karol wrote:
    There have been quite a few changes since you last updated e.g. we're using 'rw' instead of 'ro'. Try
    linux /boot/vmlinuz-linux root=/dev/sda7 rw init=/usr/lib/systemd/systemd
    It's now much better. But a lot of errors are reported and the system hangs, but still rebootable with Ctrl + Alt + Del.
    Here are the error messages:
    [FAILED] Failed to mount Configuration File System.
    See 'systemctl status sys-kernel-config.mount' for details.
    [FAILED] Failed to mount Huge Pages File System.
    See 'systemctl status dev-hugepages.mount' for details.
    [FAILED] Failed to mount POSIX Message Queue File System.
    See 'systemctl status dev-mqueue.mount' for details.
    [FAILED] Failed to mount Temporary Directory.
    See 'systemctl status tmp.mount' for details.
    [FAILED] Failed to start Remount Root and Kernel File System.
    See 'systemctl status systemd-remount-fs.service' for details.

  • Root device mounted successfully, but /sbin/init does not exist ???

    I'm having the issue where when I boot after doing a fresh install, it gives me:
    ERROR: Root device mounted successfully, but /sbin/init does not exist
    Bailing out, you are on your own. Good luck
    sh: can't access tty; job control turned off
    [rootfs /]#
    My fstab:
    # /etc/fstab
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sda1 LABEL=homerroot
    UUID=877deab9-624d-4e1d-90a1-ccc1d6ebc0c6 / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda2 LABEL=homerboot
    UUID=77835da5-8a38-44c1-bf27-bb657df4484b /boot ext4 rw,relatime,data=ordered 0 2
    # /dev/sda3 LABEL=homeretc
    UUID=8a1b5bd8-b147-41e0-87df-70a4a9e12df2 /etc ext4 rw,relatime,data=ordered 0 2
    # /dev/sda4 LABEL=homervar
    UUID=8eb2e7b1-cdf1-46ce-9dc1-439d002bfae4 /var ext4 rw,relatime,data=ordered 0 2
    # /dev/sda5 LABEL=homerusr
    UUID=bce162b4-d27f-450c-a0e6-4d3ebc6242dc /usr ext4 rw,relatime,data=ordered 0 2
    # /dev/sda6 LABEL=home
    UUID=62de76ab-b6d4-4e3d-a423-c287b81813a9 /home ext4 rw,relatime,data=ordered 0 2
    # /dev/sda7 LABEL=public
    UUID=d98a9c8e-2301-4e66-8c7f-26167633a4b0 /public ext4 rw,relatime,data=ordered 0 2
    This looks fine to me, but when /dev/sda1 is mounted at /new_root, none of the other devices are mounted....
    I don't know if this is what's causing the problem since /etc, and /usr are on separate partitions from root, but
    this would be the first time I get a problem dividing things this way (on ubuntu, mint, fedora, et cetera).
    So I tried:
    https://bbs.archlinux.org/viewtopic.php … 3#p1283343
    I get "* is owned by filesystem 2013.05-2" for all three dirs from step three.
    None of the other steps have any effect....
    I also tried:
    https://bbs.archlinux.org/viewtopic.php?id=172943
    My /dev/sda1 mounts to new_root, so I don't think I'm having his problem.
    And:
    https://bbs.archlinux.org/viewtopic.php?id=166423
    I reinstalled systemd-sysvcompat, and I'm sure that's not my problem.
    Interestingly enough, /usr/lib/systemd/systemd is an elf file on my target hard disk.
    Is this an outdated issue or something? Or should /usr/lib/systemd/systemd be a text file?
    Thanks in advance for your help guys!

    WorMzy wrote:Oh, and /usr/lib/systemd/systemd is supposed to be an ELF binary. Not sure why you think it should be a text file.
    I saw another thread saying that adding an entry there would help. I think it was "init=<something>".
    WonderWoofy wrote:A separate /etc is not supported whatsoever.  There needs to be initial access to a few things there.  I'm sure it could be made to work with some initramfs hackery.  But it is neither supported or wise to do so IMO.
    I'll not do the separate partitions then. Thanks. I'll check back if it works/doesn't-works.

  • [SOLVED] /sbin/init does not exist error on boot

    Hi all,
    Let me first say that Arch Linux is a great distribution and I couldn't be more happier with it! Thanks to everyone who is involved in building it.
    However, as the subject line suggests, I have run into a problem. I have tried every trick in my book and every suggestion on Google but the problem still persists.
    The setup
    * UEFI boot loader on /dev/sda1
    * BTRFS file system on /dev/sda2 in __active subvolume
    * The system was installed in Jan using the latest install CD (I presume systemd changes were already applied)
    The problem
    Booting halts on rEFInd screen
    What I have tried
    Since the last pacman command upgraded git and kernel to 3.7.6-1 (this is not the first kernel upgrade on this system)my first idea was to rollback to 3.7.5-1 which results in /sbin/init not found error.
    Re-installing 3.7.6-1 halts the system on rEFInd boot screen. I tried booting from rEFI shell and it results in the same /sbin/init not found error (on 3.7.6-1 kernel) so I presume that's the main issue here.
    From there on (as suggested by various posts online) I have verified that rEFInd points to the correct root partition. Also, I've tried passing /bin/systemd explicitly but the error still persists.
    I can boot into Live install environment and chroot into the setup on my drive. I have checked that /sbin/init exists (as well as /bin/systemd).
    I am out of options here. Any help will be much appreciated.
    Please let me know if you require any other information from me.
    Last edited by clalbus (2013-02-10 20:59:42)

    OK, now that I have marked the __active subvolume as default I can boot (using EFI shell) without using the rootflags=subvol=__active kernel parameter.
    However, rEFInd boot loader is still not working (with or without rootflags=subvol=__active). Unfortunately I don't see any error messages as the system hangs at rEFInd boot screen.
    Here's my archlinux.nsh (that I use to boot through EFI shell):
    echo -on
    \EFI\arch\vmlinuz-arch.efi root=PARTUUID=626f545b-44f5-4a72-b1f3-d942fbcd0b46 ro rootfstype=btrfs add_efi_memmap systemd.unit=graphical.target initrd=\EFI\arch\initramfs-linux.img rootflags=subvol=__active
    Here's my refind_linux.conf from (/boot/efi/EFI/arch)
    "Boot with defaults" "root=PARTUUID=626f545b-44f5-4a72-b1f3-d942fbcd0b46 ro rootfstype=btrfs add_efi_memmap systemd.unit=graphical.target rootflags=subvol=__active"
    "Boot to terminal" "root=PARTUUID=626f545b-44f5-4a72-b1f3-d942fbcd0b46 ro rootfstype=btrfs add_efi_memmap systemd.unit=multi-user.target rootflags=subvol=__active"
    Any idea why booting through EFI shell would work but not through rEFInd?
    Is it worthwhile rebuilding /boot?

  • Journalctl don't show logs before transmission-daemon crash

    Hello,
    When I'm checking systemd's logs after transmission segfault it shows only the latest entries:
    $ sudo journalctl -b
    -- Logs begin at Sun 2013-12-15 17:48:08 SAMT, end at Sun 2013-12-15 18:06:31 SAMT. --
    Dec 15 17:48:08 gensokyo mpd[292]: player: played "incom/transmission/The_Fantasy/6_THE_APOLOGY.mp3"
    Dec 15 17:49:14 gensokyo sudo[15024]: aidan : TTY=pts/4 ; PWD=/home/aidan ; USER=root ; COMMAND=/usr/bin/journalctl -b
    Dec 15 17:49:14 gensokyo sudo[15024]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Dec 15 17:49:14 gensokyo sudo[15024]: pam_unix(sudo:session): session closed for user root
    <snip/>
    But my laptop was started several hours ago, and in /var/log/everything.log I can find previous entries:
    Dec 15 17:47:22 gensokyo transmission-daemon[245]: archlinux-2013.12.01-dual.iso Queued for verification (verify.c:267)
    Dec 15 17:47:22 gensokyo transmission-daemon[245]: archlinux-2013.12.01-dual.iso Verifying torrent (verify.c:222)
    Dec 15 17:47:31 gensokyo kernel: [18288.640820] transmission-da[294]: segfault at 7fbd6e531d50 ip 00007fbd6e531d50 sp 00007fbd67ffecd8 error 15 in libcrypto.so.1.0.0[7fbd6e52c000+b000]
    Dec 15 17:47:33 gensokyo systemd[1]: transmissiond.service: main process exited, code=dumped, status=11/SEGV
    Dec 15 17:47:33 gensokyo systemd[1]: Unit transmissiond.service entered failed state.
    Dec 15 17:47:33 gensokyo systemd-coredump[13914]: Process 245 (transmission-da) dumped core.
    Dec 15 17:47:37 gensokyo [18294.909539] systemd-journald[106]: Deleted empty journal /var/log/journal/91e98d29abb1492896e1797004a6c680/[email protected]00000000000.journal (3735552 bytes).
    Dec 15 17:47:37 gensokyo [18294.914412] systemd-journald[106]: Vacuuming done, freed 12603392 bytes
    Dec 15 17:47:38 gensokyo [18295.497767] systemd-journald[106]: Failed to write entry (25 items, 569221814 bytes) despite vacuuming, ignoring: Argument list too long
    <^^^ previous entries ^^^>
    Dec 15 17:48:08 gensokyo mpd: player: played "incom/transmission/The_Fantasy/6_THE_APOLOGY.mp3"
    Dec 15 17:49:22 gensokyo dbus-daemon[238]: dbus[238]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
    Dec 15 17:49:22 gensokyo dbus[238]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'

    Hi instrumento, 
    There are two locations I am aware of in LabVIEW.ini that may be what you are looking for.  The neverShowLicensingStartupDialog token can be marked as true, at which point the batch licensing startup dialog will never be shown.  Additionally, the neverShowAddonLicensingStartup token controls the add-on licensing startup dialog.  When it is marked as true, the dialog will not be shown regardless of the state of any third party add-on licenses. 
    I would try changing the neverShowLicensingStartupDialog first, since your problem is with the Vision Development Module.  The token for addons may be useful if you experience this problem in the future with any third-party addons to LabVIEW.
    Regards,
    Kelly B.
    Applications Engineering
    National Instruments

  • [SOLVED] systemd-journald errors

    I set up a MythTV box the other day based on Arch (basically Arch+Openbox+Mythtv) and I get strange errors on shut down. It goes by extremely fast, but what I'm able to catch is:
    systemd-journald failed to write entry 25 items
    And some other stuff.
    I'm not sure if it's related but in dmesg I see:
    File /var/log/journal/eaa2513b7edf4267912b45e38d85d0e1/user-1000.journal corrupted or uncleanly shut down, renaming and replacing
    I've deleted the entire /var/log/journal/eaa2513b7edf4267912b45e38d85d0e1 folder so it would be regenerated, but it didn't help.
    Also, I've Googled this issue and found a bunch of topics with symptoms that match mine, but none of them have any solutions.
    Last edited by jlacroix (2014-02-02 05:15:28)

    WonderWoofy wrote:
    I don't know, that is why I posed the possibility of sending an upstream report as a question...
    Have you tried XBMC?  I use that and it is pretty great (of course I have no other point of comparison).  It also appears to have infrared remote control support (lirc) and also has android remote control application that works quite well (and some nice unofficial ones as well).
    No, I've not had a reason to try XBMC because MythTV has worked so well for me. I'm not sure what XBMC's capabilities are, but in Myth TV I was able to create custom menus using XML for my games, which is very helpful (I prefer to do this by hand, so I avoid the mythgame plugin). This HTPC is working _extremely_ well, I'm just trying to eliminate errors so I can take a clean image of it in case it needs to be restored down the road. I noticed another error regarding cgroup stating "option or name mismatch" on shut down which from what I'm reading appears to be harmless but I'm still investigating this one.

  • [Solved] systemd-journald periodically uses 50% CPU

    Hello!
    I run KDE 4.11 on Arch fully upgraded. Since shortly my system seems to choke periodically at the systemd-journald process. It takes 50% of the CPU power available and everything else is starting to studder and freeze. using jounalctl only shows normal log entries and not (like suggested somewhere else) a huge amount of error entries within seconds.
    I have tried to remedy this:
    - I disabled cups as mentioned somewhere else
    - I deleted all configuration files concerning alsa and pulseaudio (cause I found errors with journalctl) and reinstalled both
    - I set /var/log/journal to "copy on write" because it is on a btrfs partition (another suggestion in a thread)
    - I tried to somehow to disable systemd-journald (seems this is not possible)
    Nothing seems to solve the problem - still my the systemd-journald process peaks to 50% CPU every few minutes and stays at this ressource eating level for a few minutes. Then it drops down to normal again using only minimal ressources for a few minutes ...
    I am lost here. My system is really quite unusable though it is a fresh install from only two weeks ago. I only noticed this behaviour three days ago - afterwards I upgraded to kernel 3.10.9 but this hasn't changed anything either.
    Any ideas anyone?
    thx for reading,
    piedro
    Last edited by piedro (2015-02-08 18:24:45)

    Hi jrusell!
    Well I think I could solve it ... here is what I did:
    - I deleted /var/log/journal
    - rebooted and looked at the fresh log via journalctl: now it generated fresh entries again and there it was: (like in similar problems) the log has been flushed with hundreds fo fail messages! ... something like a "user burst limit exceeded" for rtkit and I found a problem with nepomukindexer (should have guessed it's KDE again - after the update to 4.11)
    - so I stopped all nepomuk stuff and deleted ~/.kde4/share/apps/nepomuk, then let nepomuk trun again recreating the whole indexing database in the process (to be honest it's still in the process but ressources aren't used excessively)
    Since then there hasn't been any problem with the journald process yet ... :-)
    thx everybody for reading,
    p.
    Last edited by piedro (2013-08-26 14:11:32)

  • /sbin/init not found after Solaris10-x86 first reboot

    Hello all,
    I just installed Solaris 10 on a x86. Nothing seemed to go awry, AFAIK.
    After the very first reboot it fails to boot with this:
    WARNING: exec(/sbin/init) file not found
    (Could not start init)
    Press any key to reboot.
    So I'm stuck, it seems.
    It does not seem that the / slice is missing as I guess I'd have a totally different error message, something like "could not mount root fs", I dunno.
    I'm sure that if I could boot the install DVD in single mode I'd be able to go and really check if /sbin/init really exists.
    Except that... I'm used to Sparc with its OPB, dunno how to get x86's equivalent to OpenBoot.
    Anyway, anyone came across the same "missing file" problem after initial install, and if so, how did you get out of it ?
    Bonus question, is there an equivalent to OpenBoot on x86 and how to reach it ?
    Before you ask.. this PC ran on Solaris 9/x86 a looooong time ago, no hardware changes, so no need to send me to the HCL :)
    Thanks,
    Jeff

    WARNING: exec(/sbin/init) file not foundSorry, can't help you with this since I never encountered such an error.
    Except that... I'm used to Sparc with its OPB, dunno
    how to get x86's equivalent to OpenBoot.That would be the configuration manager. Its the question you get in the beginning where it asks you what image to boot ('press b or enter to boot normally'). If you press escape there you get into the section where you can determine the default boot device and add new hardware drivers when needed.

  • [SOLVED] Some systemd processes (e.g. systemd-journald) can't start.

    After a fresh install on a new laptop (dual boot with Windows 8.1 vie rEFInd) I notice some error messages whilst booting. systemd-journald fails to start, and I also see some errors relating to the creation of the volatile filesystem. It's hard for me to give a lot detail about this as without journaling as I'm not sure how to get the error messages.
    I did see this from dmesg:
    [ 128.638674] systemd[1]: Starting Stop Read-Ahead Data Collection...
    [ 128.662550] systemd[1]: Started Stop Read-Ahead Data Collection.
    [ 194.545294] systemd[1]: Starting Journal Socket (/dev/log).
    [ 194.545391] systemd[1]: Listening on Journal Socket (/dev/log).
    [ 194.545471] systemd[1]: Starting Journal Socket.
    [ 194.545540] systemd[1]: Listening on Journal Socket.
    [ 194.545613] systemd[1]: Starting Journal Service...
    [ 194.546604] systemd[1]: Started Journal Service.
    [ 194.549797] systemd-journald[711]: Failed to get machine id: No such file or directory
    [ 194.553931] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
    [ 194.554205] systemd[1]: Stopping Journal Service...
    [ 24.362121] systemd-tmpfiles[330]: [/usr/lib/tmpfiles.d/systemd.conf:26] Failed to replace specifiers: /run/log/journal/%m
    [ 24.364106] systemd-tmpfiles[330]: [/usr/lib/tmpfiles.d/systemd.conf:29] Failed to replace specifiers: /var/log/journal/%m
    [ 24.404888] systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
    [ 24.409499] systemd[1]: Failed to start Create Volatile Files and Directories.
    [ 24.412303] systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
    And if I check the status of journald through systemctl I get:
    systemd-journald.service - Journal Service
    Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
    Active: failed (Result: start-limit) since Wed 2014-08-27 10:37:50 UTC; 1h 2min ago
    Docs: man:systemd-journald.service(8)
    man:journald.conf(5)
    Process: 720 ExecStart=/usr/lib/systemd/systemd-journald (code=exited, status=1/FAILURE)
    Main PID: 720 (code=exited, status=1/FAILURE)
    Status: "Shutting down..."
    I've tried reinstalling systemd, and adding systemd to HOOKS in mkinitcpio.conf, neither of these things seem to help. I also can't start the services manually.
    If anybody can help it would be greatly appreciated, thanks!
    Last edited by Tim Butters (2014-08-28 15:49:50)

    Normally, as Loqs said, 'systemd-firstboot --setup-machine-id' should have been run when you first installed the systemd package.
    You can verify if the '/etc/machine-id' file exists:
    $ ls -l /etc/machine-id
    -rw-r--r-- 1 root root 33 25 mars 2009 /etc/machine-id
    If you don't find one, maybe use 'systemd-machine-id-setup' instead to create one.
    But have you seen error messages during the Arch installation? Because that should not be necessary.
    Edit: 'systemd-firstboot' is new in systemd 216, so should not be found in the live installation disk 2014.08.
    Last edited by berbae (2014-08-28 15:44:52)

  • [SOLVED]Will not boot: "/sbin/init does not exist...

    There is another thread about this, but as of today (26-07-2013) it is 3 years old and Arch no longer uses sysvinit.
    (https://bbs.archlinux.org/viewtopic.php?id=93197)
    I tried re-installing systemd-sysvcompat, as that now handles /sbin/init, no luck.
    Is there some skeleton init file I could copy/regenerate from somewhere?
    NOTE: This is a new installation. Haven't booted cleanly yet
    Last edited by drasticraft (2013-07-28 17:30:48)

    Any chance you have more than one drive attached?  There are  no guarantees as to which drive is mapped to sda and which is mapped to sdb.
    If not that, from the shell into which you get dumped, go look around and see that /sbin is a link to /usr/bin.
    You might also add an option to point at your init.   (/usr/bin/init)   It will make your option line look like:
    options        root=/dev/sda1 ro init=/usr/bin/init
    Also, ensure that /usr/bin/init is linked to systemd.  :
    /sbin/init -> ../lib/systemd/systemd
    I'll still wager that the filesystem upgrade went awry.

Maybe you are looking for

  • Moving a folder from iPhoto

    I want to know how to permanently move a folder from iPhoto to my Time Machine, while retaining easy access to that folder. I'm looking to free up some space on my hard drive. I have a MacBook Pro with 4 GB RAM and 320 GB hard drive and we're running

  • "Error during transfer of tax condition AP4E"

    Hi Guys Please help me with the above error log. "error during transfer of tax condition AP4E" I came across this error whiles trying to create an order. How do i resolve this. Cheers.

  • Render out to QT problems

    Hi Shot/editing a seq in HDV 1080i 60, all my MOTION files are the same, looks good in timeline...my render control codec is Apple Pro RES 422...now when I render out the QT movie with the current settings I get this horrible double image on all move

  • Shopping cart on Iweb site

    Does anyone have a shopping cart on their website? I am creating a personal website with items to sell and I am having trouble using a hyperlink on my pages for a shopping cart. I am using Mal's e-commerce shopping cart. Can anyone help? Ron Morris

  • I am trying to configure Outlook in my pc but unable to configure that in 2013.

    I got the following errors. "Log onto incoming mail server (POP3): Outlook cannot connect to your incoming (POP3) e-mail server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP). " Thanking