You are not logged in.
The wiki has this item:
https://wiki.archlinux.org/index.php/Sy … log_daemon
I'm just wondering what that is all about. Is that for causing systemd to be the source of syslog log entries rather than syslog?
I don't really see the point of this, and don't want to be double-logging everything. I'm happy with the systemd journal (for now). Should I just shut down syslog-ng? I assume the command is "systemctl disable syslog-ng.service"?
Last edited by PaulBx1 (2012-08-30 07:14:39)
Offline
Yes, I believe the wiki tells you this is a reasonable option on the systemd page.
Offline
I didn't see that anywhere, but I will go ahead and disable it.
I tried the analyze thing, which crashed:
[root@myhost ~]# systemd-analyze
Traceback (most recent call last):
File "/usr/bin/systemd-analyze", line 3, in <module>
import getopt, dbus, sys, os
ImportError: No module named dbus
Offline
You'll need python2-dbus for this tool to work.
...
Optional Deps : initscripts: legacy support for /etc/rc.conf
python2-cairo: systemd-analyze
python2-dbus: systemd-analyze
systemd-sysvcompat: symlink package to provide sysvinit binaries
cryptsetup: required for encrypted block devices
...
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
Thanks, that did it, although how you figured that out has me wondering...
I can stop syslog-ng, and then disable it, and verify it's no longer in the list of services. But when I reboot it is running again.
Offline
Thanks, that did it, although how you figured that out has me wondering...
Why do you think the package info in pacman contains a list with optional dependencies? And the error said that analyze is missing a dbus module. It is even mentioned in the wiki.
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
I found some information on killing syslog-ng:
5. Consider disabling syslog. The journal is used anyway on newer systemd systems, and is usually more than sufficient for desktops, and embedded, and even many servers. Just uninstall all syslog implementations and remember that "journalctl" will get you a pixel perfect copy of the classic /var/log/messages message log. To make journal logs persistent (i.e. so that they aren't lost at boot) make sure to run "mkdir -p /var/log/journal".
http://freedesktop.org/wiki/Software/sy … imizations
So it looks like I have to uninstall syslog-ng, not just disable it.
Offline
Ah, I found it in my rc.conf daemons array. Just took it out of there and it is gone now. Guess I really didn't go through the whole process of getting rid of rc.conf...
Offline
When I disable syslog-ng, I can no longer use the 'logger foo' command (the message is not shown in journalctl). Is it intended behaviour or am I doing something wrong?
Last edited by lahwaacz (2012-08-30 09:36:11)
Offline
When I disable syslog-ng, I can no longer use the 'logger foo' command (the message is not shown in journalctl). Is it intended behaviour or am I doing something wrong?
Works here.
Offline
lahwaacz wrote:When I disable syslog-ng, I can no longer use the 'logger foo' command (the message is not shown in journalctl). Is it intended behaviour or am I doing something wrong?
Works here.
Can you please post your /etc/systemd/journald.conf file? I'd really like to make this work...
Offline
"logger foo" works for me too. I have not messed with the conf file at all; it is the stock file. Have you modified yours? Back out the mods if you have...
I'm using "journalctl -f" to see what goes into the log. "foo" shows up there...
Offline
I renamed my rc.conf to rc.conf.old and my rc.local to rc.local.old. Now I get complaints in the log about not finding rc.conf and rc.local. I tried disabling rc-local.service but that didn't help. Anyone know how to stop systemd looking for these files? I will dig through the systemd docs some more...
Offline
I renamed my rc.conf to rc.conf.old and my rc.local to rc.local.old. Now I get complaints in the log about not finding rc.conf and rc.local. I tried disabling rc-local.service but that didn't help. Anyone know how to stop systemd looking for these files? I will dig through the systemd docs some more...
Install systemd-sysvcompat, and remove initscripts and sysvinit. Those compatibility units are part of initscripts, so that's the best way to get rid of them.
Offline
"logger foo" works for me too. I have not messed with the conf file at all; it is the stock file. Have you modified yours? Back out the mods if you have...
I'm using "journalctl -f" to see what goes into the log. "foo" shows up there...
Even if I comment out everything in /etc/systemd/journald.conf, stop syslog-ng.service and restart systemd-journald.service, it still doesn't work. I've also noticed that there are several options regarding logging in /etc/systemd/system.conf - are those relevant?
Offline
Did you make sure syslog does not show up in your rc.conf "daemons" array? That was what was screwing me up. You can tell if syslog is still operating by doing a "systemctl list-units".
This is my conf file:
# 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]
#Compress=yes
#RateLimitInterval=10s
#RateLimitBurst=200
#SystemMaxUse=
#SystemKeepFree=
#SystemMaxFileSize=
#SystemMinFileSize=
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#RuntimeMinFileSize=
#ForwardToSyslog=yes
#ForwardToKMsg=no
#ForwardToConsole=no
#ImportKernel=no
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#Storage=auto
Last edited by PaulBx1 (2012-08-30 20:35:16)
Offline
Did you make sure syslog does not show up in your rc.conf "daemons" array? That was what was screwing me up. You can tell if syslog is still operating by doing a "systemctl list-units".
I don't have rc.conf file and I'm pretty sure syslog-ng was not running. But maybe the mere presence of syslog-ng.service, which contains 'Alias=syslog.service', caused this behaviour. Will try uninstalling syslog-ng.
Offline
Install systemd-sysvcompat, and remove initscripts and sysvinit.
And so it says there, right in the systemd wiki. Just because it's nicely written down, and just because I read it, does not mean I will understand it. <sigh>
Anyway thanks, now I am "pure" systemd. Still have some oddities in my log but I will see if I can chase them down.
lahwaacz, did you install systemd-sysvcompat too? Might take care of your problems...
Offline
Just uninstalled syslog-ng, and it's working! Thanks for the suggestions.
Offline