You are not logged in.
Pages: 1
I have posted the error information and the output of /etc/systemd/journald.conf at
Offline
Please don't post screenshots of text, paste the actual text.
Offline
ok, during boot,
[14.672...] systemd [1] : Failed to start Journal Service
FAILED Failed to start journal service
see 'systemctl status systemd-journald.service' for details
DEPEND Dependency failed for flush journal to persistent storage
OK Stopped Journal service.
starting journal service...
starting create volatile files and directories...
[14.716780] systemd-journald[284]: [/etc/systemd/journald.conf : 15] Failed
OK Started journal service
then a normal boot happens
The output of systemctl status systemd-journald.service is:
● systemd-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static; vendor preset: disabled)
Active: active (running) since Tue 2016-03-15 10:39:06 MYT; 34min ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 283 (systemd-journal)
Status: "Processing requests..."
CGroup: /system.slice/systemd-journald.service
└─283 /usr/lib/systemd/systemd-journald
Mar 15 10:39:06 Acer-Aspire-ES1-311-C9T9 systemd-journald[283]: Runtime journal (/run/log/journal/) is 8.0M, max 191.9M, 183.9M free.
Mar 15 10:39:06 Acer-Aspire-ES1-311-C9T9 systemd-journald[283]: System journal (/var/log/journal/) is 48.0M, max 4.0G, 3.9G free.
Mar 15 10:39:06 Acer-Aspire-ES1-311-C9T9 systemd-journald[283]: Time spent on flushing to /var is 2.153ms for 2 entries.
Mar 15 10:39:06 Acer-Aspire-ES1-311-C9T9 systemd-journald[283]: Journal started
~
Last edited by Kishan9778 (2016-03-15 06:38:24)
Offline
Please use code tags when posting code.
[14.716780] systemd-journald[284]: [/etc/systemd/journald.conf : 15] Failed
Something wrong in your journald.conf at line 15? Post the config if you can't find any error yourself.
Offline
Here's my /etc/systemd/journald.conf I cant find any errors though
# 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.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See journald.conf(5) for details.
[Journal]
Storage=200M
#Compress=yes
#Seal=yes
#SplitMode=uid
#SyncIntervalSec=5m
#RateLimitInterval=30s
#RateLimitBurst=1000
##SystemMaxUse=
#SystemKeepFree=
#SystemMaxFileSize=
#SystemMaxFiles=100
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#RuntimeMaxFiles=100
#MaxRetentionSec=
#MaxFileSec=1month
#ForwardToSyslog=no
#ForwardToKMsg=no
#ForwardToConsole=no
#ForwardToWall=yes
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#MaxLevelWall=emerg
Last edited by Kishan9778 (2016-03-15 06:31:45)
Offline
You were asked to use code tags. Please pay attention to this before you piss the mods off.
Did you read the man page? Do you know what the "Storage" option is?
Last edited by Scimmia (2016-03-15 06:14:16)
Online
well,the storage option controls where to store journal data. One of "volatile", "persistent", "auto" and "none". If "volatile", journal log data will be stored only in memory, i.e. below the /run/log/journal hierarchy (which is created if needed). If "persistent", data will be stored preferably on disk, i.e. below the /var/log/journal hierarchy (which is created if needed), with a fallback to /run/log/journal (which is created if needed), during early boot and if the disk is not writable. "auto" is similar to "persistent" but the directory /var/log/journal is not created if needed, so that its existence controls where log data goes. "none" turns off all storage, all log data received will be dropped. Forwarding to other targets, such as the console, the kernel log buffer, or a syslog socket will still work however. It defaults to "auto".
Offline
Right, so you see the problem?
Online
Yes haha,isn't it to replace 200M with auto? Or even better to delete the whole file so that a default one could be generated
Offline
Yes haha,isn't it to replace 200M with auto? Or even better to delete the whole file so that a default one could be generated
Or comment out the option so it uses the default value.
If you delete the file, it would only get regenerated once you (re)install the package that it belongs to.
Offline
so the 2nd error was solved,thanks to Scimmia & ooo
now only the 1st problem persists:
[14.672...] systemd [1] : Failed to start Journal Service
FAILED Failed to start journal service
see 'systemctl status systemd-journald.service' for details
DEPEND Dependency failed for flush journal to persistent storage
OK Stopped Journal service.
starting journal service...
starting create volatile files and directories...
Offline
I had the same issue:
systemd[1]: Failed to start Journal Service.
systemd[1]: Dependency failed for Flush Journal to Persistent Storage.
systemd[1]: systemd-journal-flush.service: Job systemd-journal-flush.service/start failed with result 'dependenc
systemd[1]: systemd-journald.service: Unit entered failed state.
In my case the reason was that I had set in /etc/systemd/system.conf:
DefaultTimeoutStartSec=10s
DefaultTimeoutStopSec=10s
because of that annoying 'a stop job is running for user c1...' bug which freezed my pc for 90sec on reboot/shutdown regulary.
By commenting out '# DefaultTimeoutStartSec=10s' or setting it to a higher value (30s) the issue was solved for me.
Offline
Pages: 1