I've been getting many "syslog-ng.service start request repeated too quickly..." issues in systemd journal . The syslog-ng service would always fail. I noticed there seems to be a bug in which systemd executes syslog-ng with the "-n" flag. I recently posted the bug here: https://bugs.freedesktop.org/show_bug.cgi?id=61324 After modifying lib/gprocess.c to accept "-n" in place of "-F", recompiling, and reinstalling, the problem has disappeared and the syslog-ng process remains up. Is this a systemd bug? I have been googling for 2 days to see if it relates to any other bugs and have found nothing. I just started using systemd 4 days ago and its my impression that syslog-ng has supported systemd for some time. So, could there be something on my end causing the issue?
P Levine <nsane457@gmail.com> writes:
I've been getting many "syslog-ng.service start request repeated too quickly..." issues in systemd journal . The syslog-ng service would always fail. I noticed there seems to be a bug in which systemd executes syslog-ng with the "-n" flag.
I recently posted the bug here: https://bugs.freedesktop.org/show_bug.cgi?id=61324
After modifying lib/gprocess.c to accept "-n" in place of "-F", recompiling, and reinstalling, the problem has disappeared and the syslog-ng process remains up.
Is this a systemd bug?
Can you show your syslog-ng.service file? I've grepped through the systemd sources, and didn't find any sign of implicit -n (but I might have missed it too).
I have been googling for 2 days to see if it relates to any other bugs and have found nothing. I just started using systemd 4 days ago and its my impression that syslog-ng has supported systemd for some time. So, could there be something on my end causing the issue?
I'm fairly sure this is an issue with one of the unit files. But if it turns out that systemd does add an implicit -n under some circumstances, then syslog-ng should support that, for compatibility's sake. What OS are you running, by the way? -- |8]
On 2013-02-23, Gergely Nagy wrote:
I'm fairly sure this is an issue with one of the unit files. But if it turns out that systemd does add an implicit -n under some circumstances, then syslog-ng should support that, for compatibility's sake.
*If* systemd added an implicit -n somewhere, that would be an extremely stupid idea, and I really see no reason why apps should change just to accomodate such idiocy. Regards, Jakub. -- Jakub Jankowski|shasta@toxcorp.com|http://toxcorp.com/ GPG: FCBF F03D 9ADB B768 8B92 BB52 0341 9037 A875 942D
Jakub Jankowski <shasta@toxcorp.com> writes:
On 2013-02-23, Gergely Nagy wrote:
I'm fairly sure this is an issue with one of the unit files. But if it turns out that systemd does add an implicit -n under some circumstances, then syslog-ng should support that, for compatibility's sake.
*If* systemd added an implicit -n somewhere, that would be an extremely stupid idea, and I really see no reason why apps should change just to accomodate such idiocy.
I'm quite sure it is not systemd itself, but in the off-chance it is, an alias of -n to -F is about one line. If it were more than that, I would be strongly against it too. But chances are, it's a rogue unit file somewhere. -- |8]
Just to weigh in on this, I am seeing similar problems. It seems to have started with the upgrade to fedora fc18 and syslog-ng-3.3.8-1.fc18.i686. In my case I get the error constantly scrolled across ALL terminal screens at boot-up. The only way of getting control of the system back is to ssh in from another machine and killing syslog-ng. I have taken to disabling syslog-ng (and enabling rsyslog) before reboots (which are thankfully seldom required) and then reversing that after the boot is complete. That seems to solve the problem, and syslog-ng stays up. -----Original Message----- From: Gergely Nagy [mailto:algernon@balabit.hu] Sent: Saturday, February 23, 2013 8:14 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] No "-n" switch for syslog-ng? Jakub Jankowski <shasta@toxcorp.com> writes:
On 2013-02-23, Gergely Nagy wrote:
I'm fairly sure this is an issue with one of the unit files. But if it turns out that systemd does add an implicit -n under some circumstances, then syslog-ng should support that, for compatibility's sake.
*If* systemd added an implicit -n somewhere, that would be an extremely stupid idea, and I really see no reason why apps should change just to accomodate such idiocy.
I'm quite sure it is not systemd itself, but in the off-chance it is, an alias of -n to -F is about one line. If it were more than that, I would be strongly against it too. But chances are, it's a rogue unit file somewhere. -- |8] ____________________________________________________________________________ __ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
"w3euu" <w3euu@arrl.net> writes:
Just to weigh in on this, I am seeing similar problems. It seems to have started with the upgrade to fedora fc18 and syslog-ng-3.3.8-1.fc18.i686.
I can't see anythign wrong with the unit file in that package, so it's possibly somewhere else. I'll see if I can get an fc18 up and reproduce the problem. -- |8]
Thanks, and let me know if there is anything I can do to help. -----Original Message----- From: Gergely Nagy [mailto:algernon@balabit.hu] Sent: Saturday, February 23, 2013 11:35 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] No "-n" switch for syslog-ng? "w3euu" <w3euu@arrl.net> writes:
Just to weigh in on this, I am seeing similar problems. It seems to have started with the upgrade to fedora fc18 and syslog-ng-3.3.8-1.fc18.i686.
I can't see anythign wrong with the unit file in that package, so it's possibly somewhere else. I'll see if I can get an fc18 up and reproduce the problem. -- |8] ____________________________________________________________________________ __ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
"w3euu" <w3euu@arrl.net> writes:
Thanks, and let me know if there is anything I can do to help.
Well, while I download and install, if you could tar up your /usr/lib/systemd/system and send it to me (not to the list), that may help, perhaps i can figure out from that what goes wrong. Not much of a chance I'll find anything, but still. My network at the moment is kind of slow, so anything I can look at while waiting for the download to finish can help. :) -- |8]
"w3euu" <w3euu@arrl.net> writes:
Just to weigh in on this, I am seeing similar problems. It seems to have started with the upgrade to fedora fc18 and syslog-ng-3.3.8-1.fc18.i686.
Interesting. I have a fresh FC18 install, with syslog-ng-3.3.8-1.fc18.x86_64, and can't reproduce the issue. Nor do I see anything wrong with w3euu's unit files :/ Can you perhaps tell me the output of systemctl status syslog-ng.service at the time the issue is present? -- |8]
On 2013-02-23, Gergely Nagy wrote:
I'm fairly sure this is an issue with one of the unit files. But if it turns out that systemd does add an implicit -n under some circumstances, then syslog-ng should support that, for compatibility's sake.
*If* systemd added an implicit -n somewhere, that would be an extremely stupid idea, and I really see no reason why apps should change just to accomodate such idiocy.
I'm quite sure it is not systemd itself, but in the off-chance it is, an alias of -n to -F is about one line. If it were more than that, I would be strongly against it too.
I would be strongly against it even if would just be one character. One shouldn't bend over for stuff like that, really. *If* there's an assumption in systemd about command line switches in 3rd party software, it's a bug in systemd and you should shout at them LOUD until it is fixed there, not here. *If*, because...
But chances are, it's a rogue unit file somewhere.
Agreed. Regards, Jakub. -- Jakub Jankowski|shasta@toxcorp.com|http://toxcorp.com/ GPG: FCBF F03D 9ADB B768 8B92 BB52 0341 9037 A875 942D
Here's the service file: [Unit] Description=System Logger Daemon Documentation=man:syslog-ng(8) [Service] Sockets=syslog.socket ExecStart=/usr/sbin/syslog-ng -F ExecReload=/bin/kill -HUP $MAINPID StandardOutput=null Restart=on-failure [Install] WantedBy=multi-user.target Alias=syslog.service Also note, the line "About to execute /usr/sbin/syslog-ng -n" only shows up in the journal in debug mode (i.e. LogLevel=debug is in system.conf). I also grepped the source and found nothing to explain the 'n' flag. Nonetheless, the fact that it is displayed in the example file at http://www.freedesktop.org/wiki/Software/systemd/syslog would make it a strange coincidence. On Sat, Feb 23, 2013 at 4:52 AM, Gergely Nagy <algernon@balabit.hu> wrote:
P Levine <nsane457@gmail.com> writes:
I've been getting many "syslog-ng.service start request repeated too quickly..." issues in systemd journal . The syslog-ng service would always fail. I noticed there seems to be a bug in which systemd executes syslog-ng with the "-n" flag.
I recently posted the bug here: https://bugs.freedesktop.org/show_bug.cgi?id=61324
After modifying lib/gprocess.c to accept "-n" in place of "-F", recompiling, and reinstalling, the problem has disappeared and the syslog-ng process remains up.
Is this a systemd bug?
Can you show your syslog-ng.service file? I've grepped through the systemd sources, and didn't find any sign of implicit -n (but I might have missed it too).
I have been googling for 2 days to see if it relates to any other bugs and have found nothing. I just started using systemd 4 days ago and its my impression that syslog-ng has supported systemd for some time. So, could there be something on my end causing the issue?
I'm fairly sure this is an issue with one of the unit files. But if it turns out that systemd does add an implicit -n under some circumstances, then syslog-ng should support that, for compatibility's sake.
What OS are you running, by the way?
-- |8]
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
P Levine <nsane457@gmail.com> writes:
Also note, the line "About to execute /usr/sbin/syslog-ng -n" only shows up in the journal in debug mode (i.e. LogLevel=debug is in system.conf).
I also grepped the source and found nothing to explain the 'n' flag. Nonetheless, the fact that it is displayed in the example file at http://www.freedesktop.org/wiki/Software/systemd/syslog would make it a strange coincidence.
Indeed.. that page needs some correcting. I have not been able to reproduce the problem yet, but I'll try to catch some systemd folk on IRC, perhaps they can shed a light on the issue. -- |8]
On Tue, Feb 26, 2013 at 6:30 AM, Gergely Nagy <algernon@balabit.hu> wrote:
P Levine <nsane457@gmail.com> writes:
Also note, the line "About to execute /usr/sbin/syslog-ng -n" only shows up in the journal in debug mode (i.e. LogLevel=debug is in system.conf).
I also grepped the source and found nothing to explain the 'n' flag. Nonetheless, the fact that it is displayed in the example file at http://www.freedesktop.org/wiki/Software/systemd/syslog would make it a strange coincidence.
Indeed.. that page needs some correcting. I have not been able to reproduce the problem yet, but I'll try to catch some systemd folk on IRC, perhaps they can shed a light on the issue.
-- |8]
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
Just to clarify, when you try to reproduce the problem, does the journal display "About to execute /usr/sbin/syslog-ng -n" or "About to execute /usr/sbin/syslog-ng --F" in debug mode? And can you confirm syslog-ng, afterwards, shows up as a process (i.e., *ps -A")?
On Fri, Feb 22, 2013 at 11:25 PM, P Levine <nsane457@gmail.com> wrote:
I've been getting many "syslog-ng.service start request repeated too quickly..." issues in systemd journal . The syslog-ng service would always fail. I noticed there seems to be a bug in which systemd executes syslog-ng with the "-n" flag.
I recently posted the bug here: https://bugs.freedesktop.org/show_bug.cgi?id=61324
After modifying lib/gprocess.c to accept "-n" in place of "-F", recompiling, and reinstalling, the problem has disappeared and the syslog-ng process remains up.
Is this a systemd bug?
I have been googling for 2 days to see if it relates to any other bugs and have found nothing. I just started using systemd 4 days ago and its my impression that syslog-ng has supported systemd for some time. So, could there be something on my end causing the issue?
Okay, the bug has gotten stranger. Refiled it at: https://bugs.freedesktop.org/show_bug.cgi?id=61535. Not sure at all why this is happening but I think I'm probably going to go back to openrc soon, anyway.
https://bugs.freedesktop.org/show_bug.cgi?id=61535On Tue, Feb 26, 2013 at 7:44 PM, P Levine <nsane457@gmail.com> wrote:
On Fri, Feb 22, 2013 at 11:25 PM, P Levine <nsane457@gmail.com> wrote:
I've been getting many "syslog-ng.service start request repeated too quickly..." issues in systemd journal . The syslog-ng service would always fail. I noticed there seems to be a bug in which systemd executes syslog-ng with the "-n" flag.
I recently posted the bug here: https://bugs.freedesktop.org/show_bug.cgi?id=61324
After modifying lib/gprocess.c to accept "-n" in place of "-F", recompiling, and reinstalling, the problem has disappeared and the syslog-ng process remains up.
Is this a systemd bug?
I have been googling for 2 days to see if it relates to any other bugs and have found nothing. I just started using systemd 4 days ago and its my impression that syslog-ng has supported systemd for some time. So, could there be something on my end causing the issue?
Okay, the bug has gotten stranger. Refiled it at: https://bugs.freedesktop.org/show_bug.cgi?id=61535.
Not sure at all why this is happening but I think I'm probably going to go back to openrc soon, anyway.
Bad address. Filed here: <Refiled it at: https://bugs.freedesktop.org/show_bug.cgi?id=61535> https://bugs.freedesktop.org/show_bug.cgi?id=61535
On Fri, Feb 22, 2013 at 11:25 PM, P Levine <nsane457@gmail.com> wrote:
I've been getting many "syslog-ng.service start request repeated too quickly..." issues in systemd journal . The syslog-ng service would always fail. I noticed there seems to be a bug in which systemd executes syslog-ng with the "-n" flag.
I recently posted the bug here: https://bugs.freedesktop.org/show_bug.cgi?id=61324
After modifying lib/gprocess.c to accept "-n" in place of "-F", recompiling, and reinstalling, the problem has disappeared and the syslog-ng process remains up.
Is this a systemd bug?
I have been googling for 2 days to see if it relates to any other bugs and have found nothing. I just started using systemd 4 days ago and its my impression that syslog-ng has supported systemd for some time. So, could there be something on my end causing the issue?
Please disregard the bug. I had forgotten that earlier I had setup a syslog-ng.system file in /etc/systemd/system. It was overriding the one installed later. I feel like an idiot. :<
participants (4)
-
Gergely Nagy
-
Jakub Jankowski
-
P Levine
-
w3euu