[opensuse] sistemad / journal / syslog ?
I am migrating some test systems from openSUSE 11.0 to 13.2 - systemd is in fact making things quite a lot easier. However, I have a problem with getting syslog-ng started early enough. This is probably due to a DNS problem, which will have be looked at separately. However, due to this late starting I've noticed other daemons not being able to use syslog, not even once it is started. E.g. openvpn - it is started quite early, so the startup messages are not logged, but later on it also does not seem to be able to log. This can't be right? -- Per Jessen, Zürich (5.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
I am migrating some test systems from openSUSE 11.0 to 13.2 - systemd is in fact making things quite a lot easier.
However, I have a problem with getting syslog-ng started early enough. This is probably due to a DNS problem, which will have be looked at separately.
syslog-ng has a After=var-run.mount - # systemctl status var-run.mount var-run.mount - Runtime Directory Loaded: loaded (/usr/lib/systemd/system/var-run.mount; static) Active: inactive (dead) start condition failed at Thu 2015-03-12 10:54:08 CET; 40min ago ConditionPathIsSymbolicLink=!/var/run was not met Where: /var/run What: /run Might this be causing the late start of syslog-ng ? -- Per Jessen, Zürich (5.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Per Jessen wrote:
I am migrating some test systems from openSUSE 11.0 to 13.2 - systemd is in fact making things quite a lot easier.
However, I have a problem with getting syslog-ng started early enough. This is probably due to a DNS problem, which will have be looked at separately.
syslog-ng has a After=var-run.mount -
# systemctl status var-run.mount var-run.mount - Runtime Directory Loaded: loaded (/usr/lib/systemd/system/var-run.mount; static) Active: inactive (dead) start condition failed at Thu 2015-03-12 10:54:08 CET; 40min ago ConditionPathIsSymbolicLink=!/var/run was not met Where: /var/run What: /run
Might this be causing the late start of syslog-ng ?
Doesn't look like it, I've done a few tests. It's looking like it's really my DNS issue that is still causing the delay. I'll be looking closer at that. -- Per Jessen, Zürich (5.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Per Jessen wrote:
Per Jessen wrote:
I am migrating some test systems from openSUSE 11.0 to 13.2 - systemd is in fact making things quite a lot easier.
However, I have a problem with getting syslog-ng started early enough. This is probably due to a DNS problem, which will have be looked at separately.
syslog-ng has a After=var-run.mount -
# systemctl status var-run.mount var-run.mount - Runtime Directory Loaded: loaded (/usr/lib/systemd/system/var-run.mount; static) Active: inactive (dead) start condition failed at Thu 2015-03-12 10:54:08 CET; 40min ago ConditionPathIsSymbolicLink=!/var/run was not met Where: /var/run What: /run
Might this be causing the late start of syslog-ng ?
Doesn't look like it, I've done a few tests. It's looking like it's really my DNS issue that is still causing the delay. I'll be looking closer at that.
Okay, it really is the DNS problem that is causing the delayed startup. Sorry about the noise. -- Per Jessen, Zürich (5.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Mar 12, 2015 at 1:20 PM, Per Jessen <per@computer.org> wrote:
I am migrating some test systems from openSUSE 11.0 to 13.2 - systemd is in fact making things quite a lot easier.
However, I have a problem with getting syslog-ng started early enough. This is probably due to a DNS problem, which will have be looked at separately. However, due to this late starting I've noticed other daemons not being able to use syslog, not even once it is started.
In 13.2 standard syslog socket (/dev/log) is owned by journald which is started very early. Syslog daemons are supposed to listen on private socket and journald forwards messages to syslog over this private socket. This is by design. What exactly "other daemons not being able to use syslog" means? Please also show syslog-ng.service definition.
E.g. openvpn - it is started quite early, so the startup messages are not logged, but later on it also does not seem to be able to log. This can't be right?
-- Per Jessen, Zürich (5.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov wrote:
On Thu, Mar 12, 2015 at 1:20 PM, Per Jessen <per@computer.org> wrote:
I am migrating some test systems from openSUSE 11.0 to 13.2 - systemd is in fact making things quite a lot easier.
However, I have a problem with getting syslog-ng started early enough. This is probably due to a DNS problem, which will have be looked at separately. However, due to this late starting I've noticed other daemons not being able to use syslog, not even once it is started.
In 13.2 standard syslog socket (/dev/log) is owned by journald which is started very early. Syslog daemons are supposed to listen on private socket and journald forwards messages to syslog over this private socket. This is by design.
Okay, thats' fine.
What exactly "other daemons not being able to use syslog" means?
Well, for instance - openvpn is started before syslog-ng, so the startup messages are not written to /var/log/messages. However, once syslog-ng is up and running, I would expect messages from openvpn to start appearing in /var/log/messages, but they don't. I see messages from openvpn with e.g. "systemctl status openvpn", but they are not in /var/log/messages. If I restart openvpn when syslog is running, the messages start being written to /var/log/messages.
Please also show syslog-ng.service definition.
<---------- # cat /etc/systemd/system/syslog-ng.service [Unit] Description=System Logging Service Requires=var-run.mount Requires=syslog.socket After=var-run.mount Conflicts=rsyslog.service syslogd.service [Service] Environment=SYSLOG_NG_PARAMS= ExecStartPre=/usr/bin/host service2.example.com ExecStartPre=/usr/sbin/syslog-ng-service-prepare EnvironmentFile=-/etc/sysconfig/syslog ExecStart=/usr/sbin/syslog-ng -F $SYSLOG_NG_PARAMS ExecReload=/bin/kill -HUP $MAINPID StandardOutput=null Restart=on-abort [Install] WantedBy=multi-user.target Alias=syslog.service ---------> I've added ExecStartPre=/usr/bin/host due to DNS problems, bug#921252. /Per -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/12/2015 09:02 AM, Andrei Borzenkov wrote:
I am migrating some test systems from openSUSE 11.0 to 13.2 - systemd is in fact making things quite a lot easier.
However, I have a problem with getting syslog-ng started early enough. This is probably due to a DNS problem, which will have be looked at separately. However, due to this late starting I've noticed other daemons not being able to use syslog, not even once it is started. In 13.2 standard syslog socket (/dev/log) is owned by journald which is started very early. Syslog daemons are supposed to listen on
On Thu, Mar 12, 2015 at 1:20 PM, Per Jessen <per@computer.org> wrote: private socket and journald forwards messages to syslog over this private socket. This is by design.
how is that being accomplished?
?
What exactly "other daemons not being able to use syslog" means?
Please also show syslog-ng.service definition.
E.g. openvpn - it is started quite early, so the startup messages are not logged, but later on it also does not seem to be able to log. This can't be right?
-- Per Jessen, Zürich (5.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Thu, 12 Mar 2015 11:56:47 -0400 Ruben Safir <ruben.safir@my.liu.edu> пишет:
On 03/12/2015 09:02 AM, Andrei Borzenkov wrote:
I am migrating some test systems from openSUSE 11.0 to 13.2 - systemd is in fact making things quite a lot easier.
However, I have a problem with getting syslog-ng started early enough. This is probably due to a DNS problem, which will have be looked at separately. However, due to this late starting I've noticed other daemons not being able to use syslog, not even once it is started. In 13.2 standard syslog socket (/dev/log) is owned by journald which is started very early. Syslog daemons are supposed to listen on
On Thu, Mar 12, 2015 at 1:20 PM, Per Jessen <per@computer.org> wrote: private socket and journald forwards messages to syslog over this private socket. This is by design.
how is that being accomplished?
"Syslog daemons are supposed to listen on
private socket and journald forwards messages to syslog over this private socket. " -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/12/2015 01:09 PM, Andrei Borzenkov wrote:
В Thu, 12 Mar 2015 11:56:47 -0400 Ruben Safir <ruben.safir@my.liu.edu> пишет:
On 03/12/2015 09:02 AM, Andrei Borzenkov wrote:
I am migrating some test systems from openSUSE 11.0 to 13.2 - systemd is in fact making things quite a lot easier.
However, I have a problem with getting syslog-ng started early enough. This is probably due to a DNS problem, which will have be looked at separately. However, due to this late starting I've noticed other daemons not being able to use syslog, not even once it is started. In 13.2 standard syslog socket (/dev/log) is owned by journald which is started very early. Syslog daemons are supposed to listen on
On Thu, Mar 12, 2015 at 1:20 PM, Per Jessen <per@computer.org> wrote: private socket and journald forwards messages to syslog over this private socket. This is by design. how is that being accomplished?
"Syslog daemons are supposed to listen on
private socket and journald forwards messages to syslog over this private socket. "
how are you getting systemd to start on "private sockets", whatever that is? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Thu, 12 Mar 2015 13:46:55 -0400 Ruben <ruben.safir@my.liu.edu> пишет:
On 03/12/2015 01:09 PM, Andrei Borzenkov wrote:
В Thu, 12 Mar 2015 11:56:47 -0400 Ruben Safir <ruben.safir@my.liu.edu> пишет:
On 03/12/2015 09:02 AM, Andrei Borzenkov wrote:
I am migrating some test systems from openSUSE 11.0 to 13.2 - systemd is in fact making things quite a lot easier.
However, I have a problem with getting syslog-ng started early enough. This is probably due to a DNS problem, which will have be looked at separately. However, due to this late starting I've noticed other daemons not being able to use syslog, not even once it is started. In 13.2 standard syslog socket (/dev/log) is owned by journald which is started very early. Syslog daemons are supposed to listen on
On Thu, Mar 12, 2015 at 1:20 PM, Per Jessen <per@computer.org> wrote: private socket and journald forwards messages to syslog over this private socket. This is by design. how is that being accomplished?
"Syslog daemons are supposed to listen on
private socket and journald forwards messages to syslog over this private socket. "
how are you getting systemd to start on "private sockets", whatever that is?
Sorry, I do not see any occurrence of word "systemd" in what I wrote so I do not understand your question. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi, can you please not misspell systemd? It is annoying. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thursday 12 March 2015, Marcus Meissner wrote:
Hi,
can you please not misspell systemd? It is annoying.
Is the string "systemd" un-blacklisted again? If it's still blacklisted by list moderators then we should better avoid it like Per did to not make them angry. cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Ruediger Meier wrote:
On Thursday 12 March 2015, Marcus Meissner wrote:
Hi,
can you please not misspell systemd? It is annoying.
Is the string "systemd" un-blacklisted again? If it's still blacklisted by list moderators then we should better avoid it like Per did to not make them angry.
I'm deliberately using 'sistemad' because using systemd in the subject frequently causes long delays, presumably due to systemd being blacklisted :-). I'm sorry it's annoying, but the delays are even more annoying. /Per PS: it's not really a misspeling, it's only systemd in Italian :-) -- Per Jessen, Zürich (5.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thursday 12 March 2015, Per Jessen wrote:
/Per PS: it's not really a misspeling, it's only systemd in Italian :-)
Ahhh "Sistema D". I thought it must be something about "something mad" but couldn't get it. :) cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Andrei Borzenkov -
Marcus Meissner -
Per Jessen -
Ruben -
Ruben Safir
-
Ruediger Meier