Journal Service delays startup on diskless clients

nomorewindows · 2015-01-05 21:58:27

Do I just need to disable the journal on diskless clients or something else?

karol · 2015-01-05 22:58:57

How did you setup the journal?

nomorewindows · 2015-01-05 23:40:19

It just does the default behavior through systemd, but it probably squawks because it wants permanent storage for the logs.

karol · 2015-01-07 09:39:25

Try an alternative journal setup.

nomorewindows · 2015-01-07 13:29:38

Didn't know there were alternates with systemd.

karol · 2015-01-07 14:10:23

I mean edit your journald.conf and change the options.

nomorewindows · 2015-01-07 21:25:10

Looks like the only feasible option here is to change Storage=volatile. This will store logs in memory, which prevents different stateless clients writing over each other, but might be nice to know what crashed before I could find out.

Head_on_a_Stick · 2015-01-07 21:32:07

Why not just mask the service?

# systemctl mask systemd-journald.service
# systemctl mask systemd-journal-flush.service
# systemctl mask systemd-journald-dev-log.socket
# systemctl mask systemd-journald.socket

That's probably overkill -- you may only need to mask the .sockets

EDIT: Ooops! Sorry!

Last edited by Head_on_a_Stick (2015-01-08 20:57:27)

falconindy · 2015-01-08 14:43:07

Head_on_a_Stick wrote:

Why not just mask the service?
# systemctl mask systemd-journald.service
# systemctl mask systemd-journal-flush.service
# systemctl mask systemd-journald-dev-log.socket
# systemctl mask systemd-journald.socket
That's probably overkill -- you may only need to mask the .sockets

Why not? Its unsupported. It will cause logs to be lost. Programs may break in strange ways. Do not do this. Using volatile storage (or none) is a supported option.

Last edited by falconindy (2015-01-08 14:43:40)

nomorewindows · 2015-01-08 15:00:09

falconindy wrote:

Head_on_a_Stick wrote:
Why not just mask the service?
# systemctl mask systemd-journald.service
# systemctl mask systemd-journal-flush.service
# systemctl mask systemd-journald-dev-log.socket
# systemctl mask systemd-journald.socket
That's probably overkill -- you may only need to mask the .sockets
Why not? Its unsupported. It will cause logs to be lost. Programs may break in strange ways. Do not do this. Using volatile storage (or none) is a supported option.

This problem was only starting to show up with a fresh PXE client, but this hasn't been a problem previously. Is there an option that maybe hasn't been considered for the fact that diskless would be on an nfs or sshfs mount instead of "permanent" storage?

Arch Linux

#1 2015-01-05 21:58:27

Journal Service delays startup on diskless clients

#2 2015-01-05 22:58:57

Re: Journal Service delays startup on diskless clients

#3 2015-01-05 23:40:19

Re: Journal Service delays startup on diskless clients

#4 2015-01-07 09:39:25

Re: Journal Service delays startup on diskless clients

#5 2015-01-07 13:29:38

Re: Journal Service delays startup on diskless clients

#6 2015-01-07 14:10:23

Re: Journal Service delays startup on diskless clients

#7 2015-01-07 21:25:10

Re: Journal Service delays startup on diskless clients

#8 2015-01-07 21:32:07

Re: Journal Service delays startup on diskless clients

#9 2015-01-08 14:43:07

Re: Journal Service delays startup on diskless clients

#10 2015-01-08 15:00:09

Re: Journal Service delays startup on diskless clients

Board footer