You are not logged in.
Pages: 1
Hi all,
I am really confused, since journald is not logging anything. Actually there is no log file at all. I did not change anything, so I have no idea what's going on. So, do you have an idea, what I should try next (re-installing the packets didn't fix the problem).
Thank's in advance!!
no log files:
% journalctl -xn
No journal files were found.
The reason is that, journald is not running.
% systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● systemd-journal-flush.service loaded failed failed Trigger Flushing of Journal to Persistent Storage
● systemd-journald.service loaded failed failed Journal Service
● systemd-journald.socket loaded failed failed Journal Socket
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.
The status for the journald-service is:
% systemctl status systemd-journald.service :(
● systemd-journald.service - Journal Service
Loaded: loaded (/etc/systemd/system/systemd-journald.service; static)
Active: failed (Result: start-limit) since Sat 2014-09-27 14:20:03 CEST; 4h 9min ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Process: 432 ExecStart=/usr/lib/systemd/systemd-journald (code=exited, status=1/FAILURE)
Main PID: 432 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
and the status of the socket
% systemctl status systemd-journald.socket :(
● systemd-journald.socket - Journal Socket
Loaded: loaded (/etc/systemd/system/systemd-journald.socket; static)
Active: failed (Result: service-failed-permanent) since Sat 2014-09-27 14:20:03 CEST; 4h 9min ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Listen: /run/systemd/journal/stdout (Stream)
/run/systemd/journal/socket (Datagram)
/dev/log (Datagram)
Last edited by mkind (2014-09-28 15:30:00)
Offline
Are the files present? Post the output of 'ls -l /var/log/journal'.
Offline
nope. no files there
% ls -l /var/log/journal
total 0
drwxr-sr-x+ 1 root systemd-journal-remote 0 Aug 20 19:39 remote/
% ls -l /var/log/journal/remote
total 0
Last edited by mkind (2014-09-27 18:50:02)
Offline
Check your configuration. Maybe you told journald not to create any log files.
Offline
my config is not configured at all:
% cat /etc/systemd/journald.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# See journald.conf(5) for details
[Journal]
#Storage=volatile
#Compress=yes
#Seal=yes
#SplitMode=uid
#SyncIntervalSec=5m
#RateLimitInterval=30s
#RateLimitBurst=1000
#SystemMaxUse=100M
#SystemKeepFree=
#SystemMaxFileSize=
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#MaxRetentionSec=
#MaxFileSec=1month
#ForwardToSyslog=yes
#ForwardToKMsg=no
#ForwardToConsole=no
#ForwardToWall=yes
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#MaxLevelWall=emerg
Offline
Try configuring it.
Offline
Well, I tried setting storage to persistent, but this does not work Do you thing the configuration has something to do with the failed start of the services? The same configuration worked once. My first intuition was, that the reseason for the systemd.service to not successfully boot up is the failed .service bootup. But I have no idea, what this causes.
Offline
That's weird; I don't have /etc/systemd/system/systemd-journald.service, only /usr/lib/systemd/system/systemd-journald.service. What is in the service in /etc?
Offline
% cat /etc/systemd/system/systemd-journald.socket
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
[Unit]
Description=Journal Socket
Documentation=man:systemd-journald.service(8) man:journald.conf(5)
DefaultDependencies=no
Before=sockets.target
# Mount and swap units need this. If this socket unit is removed by an
# isolate request the mount and swap units would be removed too,
# hence let's exclude this from isolate requests.
IgnoreOnIsolate=yes
[Socket]
ListenStream=/run/systemd/journal/stdout
ListenDatagram=/run/systemd/journal/socket
ListenDatagram=/dev/log
SocketMode=0666
PassCredentials=yes
PassSecurity=yes
ReceiveBuffer=8M
Offline
Well that's the socket; I was talking about the service. But I don't have the socket in /etc either.. Who put it there? I'm pretty sure it's not needed
$ pacman -Qo /{usr/lib,etc}/systemd/system/systemd-journald.{service,socket}
/usr/lib/systemd/system/systemd-journald.service is owned by systemd 216-3
/usr/lib/systemd/system/systemd-journald.socket is owned by systemd 216-3
error: failed to read file 'etc/systemd/system/systemd-journald.service': No such file or directory
error: failed to read file 'etc/systemd/system/systemd-journald.socket': No such file or directory
Also; that file differs from what I have in /usr/lib; so it seems you somehow overloaded those with other/older versions of those files?
Last edited by Spider.007 (2014-09-28 12:56:12)
Offline
hm.. here my output of the service:
% cat /etc/systemd/system/systemd-journald.service
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
[Unit]
Description=Journal Service
Documentation=man:systemd-journald.service(8) man:journald.conf(5)
DefaultDependencies=no
Requires=systemd-journald.socket
After=systemd-journald.socket syslog.socket
Before=sysinit.target
[Service]
ExecStart=/usr/lib/systemd/systemd-journald
Restart=always
RestartSec=0
NotifyAccess=all
StandardOutput=null
CapabilityBoundingSet=CAP_SYS_ADMIN CAP_DAC_OVERRIDE CAP_SYS_PTRACE CAP_SYSLOG CAP_AUDIT_CONTROL CAP_CHOWN CAP_DAC_READ_SEARCH CAP_FOWNER CAP_SETUID CAP_SETGID
WatchdogSec=1min
# Increase the default a bit in order to allow many simultaneous
# services being run since we keep one fd open per service.
LimitNOFILE=16384
and pacman says they are owned by no package
% pacman -Qo /{usr/lib,etc}/systemd/system/systemd-journald.{service,socket}
/usr/lib/systemd/system/systemd-journald.service is owned by systemd 216-3
/usr/lib/systemd/system/systemd-journald.socket is owned by systemd 216-3
error: No package owns /etc/systemd/system/systemd-journald.service
error: No package owns /etc/systemd/system/systemd-journald.socket
actually no package owns any of the services in /etc/systemd/system/.
Last edited by mkind (2014-09-28 13:29:31)
Offline
You could try to be a bit more pro-active; but I'll spell it out for you.
How about removing those two files (in /etc) and see if your problem is fixed after a reboot? Other services aren't owned because you enabled them manually. That shouldn't be necessary for the two mentioned files. Also; these are normally symlinks, not actual files
Last edited by Spider.007 (2014-09-28 14:47:08)
Offline
ok. thanks a lot. next time I'll be more pro-active There is no reason, I couldn't have figured out this bug by myself. Thanks
Offline
Pages: 1