Bug#762700: systemd: journald fails to forward most boot messages to syslog
Christian Seiler
christian at iwakd.de
Thu Feb 26 10:32:16 GMT 2015
Small correction to my previous observations:
Am 2015-02-25 18:59, schrieb Christian Seiler:
> - SendBuffer=8M will increase the max size of a single log message
> that may be sent via this socket (8M is probably at bit much)
Actually that's not true. I've misread the kernel source here, and a
couple of tests I did after a good night's sleep actually shows that
the SendBuffer should be increased in order for there to be enough
space for log messages.
So the fix/workaround/whatever you want to call it would be twofold:
- increase max_dgram_qlen sysctl
- increase SendBuffer for syslog.socket
So basically something like:
/lib/systemd/system/syslog.socket:
+Wants=systemd-setup-dgram-qlen.service
+SendBuffer=8M
create /lib/systemd/system/systemd-setup-dgram-qlen.service:
[Unit]
DefaultDependencies=no
Before=syslog.socket
[Service]
Type=oneshot
ExecStart=/sbin/sysctl -w net.unix.max_dgram_qlen=512
StandardOutput=null
(the values 8M and 512 are debatable, of course)
Christian
More information about the Pkg-systemd-maintainers
mailing list