Skip Menu |
 

This queue is for tickets about the Sys-Syslog CPAN distribution.

Report information
The Basics
Id: 27732
Status: resolved
Priority: 0/
Queue: Sys-Syslog

People
Owner: Nobody in particular
Requestors: jujfalus [...] tgs-solutions.com
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: (no value)
Fixed in: (no value)



Subject: syslog causes zombie processes if syslogd has failed
Download (untitled) / with headers
text/plain 986b
We have a long running process that writes to syslog. However we have observed that if the syslogd is not running aparently forked off child processes related to syslog calls are left in a defunct state. We are running on hpux 11i on a PA-RISC platform. I realize our version is old aparently 0.03 of Sys::Syslog. I have tried google searches, however have not come up with a good solution. Other than wrapping each preceding each call to syslog with a check to see if syslogd is running, which seems rather costly. perl -v This is perl, v5.8.0 built for PA-RISC1.1 Copyright 1987-2002, Larry Wall Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which may be found in the Perl 5 source kit. Complete documentation for Perl, including FAQ lists, should be found on this system using `man perl' or `perldoc perl'. If you have access to the Internet, point your browser at http://www.perl.com/, the Perl Home Page.
Subject: Re: [rt.cpan.org #27732] syslog causes zombie processes if syslogd has failed
Date: Tue, 26 Jun 2007 00:20:11 +0200
To: bug-Sys-Syslog [...] rt.cpan.org
From: Sébastien Aperghis-Tramoni <saper [...] cpan.org>
Download (untitled) / with headers
text/plain 1.3k
Hello, Show quoted text
> We have a long running process that writes to syslog. However we have > observed that if the syslogd is not running aparently forked off child > processes related to syslog calls are left in a defunct state. We are > running on hpux 11i on a PA-RISC platform. I realize our version is > old > aparently 0.03 of Sys::Syslog. I have tried google searches, however > have not come up with a good solution. Other than wrapping each > preceding each call to syslog with a check to see if syslogd is > running, which seems rather costly. > > This is perl, v5.8.0 built for PA-RISC1.1
Well, these are indeed quite old versions of Perl and Sys::Syslog. I'm not really surprised that a non-running syslogd causes problems because old versions of Sys::Syslog were opening a network or stream socket. I strongly suggest to upgrade Sys::Syslog to version 0.15 or later, which by default use native syslog(3) functions from the C library. With the new version of Sys::Syslog, Perl programs will behave exactly as normal programs using syslog(3). Even though it may require a little more effort, I also suggest to upgrade your Perl installation, either from the sources or using the binaries from http://mirrors.develooper.com/hpux/ (maintained by a Perl5 Porter who probably knows more HP-UX than he'd like to). Regards -- Sébastien Aperghis-Tramoni Close the world, txEn eht nepO.
Download (untitled) / with headers
text/plain 1.4k
Hello, I didn't hear anything back from you? Did you try upgrading Sys::Syslog in order to resolve your problem? Show quoted text
> > We have a long running process that writes to syslog. However we have > > observed that if the syslogd is not running aparently forked off child > > processes related to syslog calls are left in a defunct state. We are > > running on hpux 11i on a PA-RISC platform. I realize our version is > > old > > aparently 0.03 of Sys::Syslog. I have tried google searches, however > > have not come up with a good solution. Other than wrapping each > > preceding each call to syslog with a check to see if syslogd is > > running, which seems rather costly. > > > > This is perl, v5.8.0 built for PA-RISC1.1
> > Well, these are indeed quite old versions of Perl and Sys::Syslog. > I'm not really surprised that a non-running syslogd causes problems > because old versions of Sys::Syslog were opening a network or stream > socket. I strongly suggest to upgrade Sys::Syslog to version 0.15 or > later, which by default use native syslog(3) functions from the C > library. With the new version of Sys::Syslog, Perl programs will > behave exactly as normal programs using syslog(3). > > Even though it may require a little more effort, I also suggest to > upgrade your Perl installation, either from the sources or using the > binaries from http://mirrors.develooper.com/hpux/ (maintained by a > Perl5 Porter who probably knows more HP-UX than he'd like to).
-- Close the world, txEn eht nepO.
Subject: RE: [rt.cpan.org #27732] syslog causes zombie processes if syslogd has failed
Date: Thu, 26 Jul 2007 11:00:50 -0700
To: <bug-Sys-Syslog [...] rt.cpan.org>
From: "Joseph Ujfalusi" <jujfalus [...] tgs-solutions.com>
Download (untitled) / with headers
text/plain 2.2k
Joseph Ujfalusi Tekmark Global Solutions Tel: 1-604-214-8675 Fax: 1-604-214-8674 jujfalus@tgs-solutions.com http://www.tekmarkinc.com This message is for the designated recipient only and it, as well as any attachments, may contain privileged, proprietary or confidential information. If you are not the intended recipient, do not read, copy or distribute it. Please notify the sender immediately and delete the original at once. Any other use of the email by you is prohibited. Thank you. Show quoted text
-----Original Message----- From: Sébastien Aperghis-Tramoni via RT [mailto:bug-Sys-Syslog@rt.cpan.org] Sent: Wednesday, July 25, 2007 5:05 PM To: undisclosed-recipients: Subject: [rt.cpan.org #27732] syslog causes zombie processes if syslogd has failed <URL: http://rt.cpan.org/Ticket/Display.html?id=27732 > Hello, I didn't hear anything back from you? Did you try upgrading Sys::Syslog in order to resolve your problem?
> > We have a long running process that writes to syslog. However we have > > observed that if the syslogd is not running aparently forked off child > > processes related to syslog calls are left in a defunct state. We are > > running on hpux 11i on a PA-RISC platform. I realize our version is > > old > > aparently 0.03 of Sys::Syslog. I have tried google searches, however > > have not come up with a good solution. Other than wrapping each > > preceding each call to syslog with a check to see if syslogd is > > running, which seems rather costly. > > > > This is perl, v5.8.0 built for PA-RISC1.1
> > Well, these are indeed quite old versions of Perl and Sys::Syslog. > I'm not really surprised that a non-running syslogd causes problems > because old versions of Sys::Syslog were opening a network or stream > socket. I strongly suggest to upgrade Sys::Syslog to version 0.15 or > later, which by default use native syslog(3) functions from the C > library. With the new version of Sys::Syslog, Perl programs will > behave exactly as normal programs using syslog(3). > > Even though it may require a little more effort, I also suggest to > upgrade your Perl installation, either from the sources or using the > binaries from http://mirrors.develooper.com/hpux/ (maintained by a > Perl5 Porter who probably knows more HP-UX than he'd like to).
-- Close the world, txEn eht nepO.
Subject: RE: [rt.cpan.org #27732] syslog causes zombie processes if syslogd has failed
Date: Thu, 26 Jul 2007 11:04:26 -0700
To: <bug-Sys-Syslog [...] rt.cpan.org>, <undisclosed-recipients: [...] mail.tgs-solutions.com>
From: "Joseph Ujfalusi" <jujfalus [...] tgs-solutions.com>
Download (untitled) / with headers
text/plain 2.7k
Sorry Sebastien, I did not upgrade to a more recent Sys::Syslog (I guess my email filter must have knocked out your previous email). We just worked around calls to syslog and put our errors out via another mechanism. Was there a recognized issue in earlier releases of Sys::Syslog or is upgrade just the pat answer so that we are all looking / patching the same release of the code. Thanks for your response and again sorry for my apparent slow responsiveness. Joseph Ujfalusi Tekmark Global Solutions Tel: 1-604-214-8675 Fax: 1-604-214-8674 jujfalus@tgs-solutions.com http://www.tekmarkinc.com This message is for the designated recipient only and it, as well as any attachments, may contain privileged, proprietary or confidential information. If you are not the intended recipient, do not read, copy or distribute it. Please notify the sender immediately and delete the original at once. Any other use of the email by you is prohibited. Thank you. Show quoted text
-----Original Message----- From: Sébastien Aperghis-Tramoni via RT [mailto:bug-Sys-Syslog@rt.cpan.org] Sent: Wednesday, July 25, 2007 5:05 PM To: undisclosed-recipients: Subject: [rt.cpan.org #27732] syslog causes zombie processes if syslogd has failed <URL: http://rt.cpan.org/Ticket/Display.html?id=27732 > Hello, I didn't hear anything back from you? Did you try upgrading Sys::Syslog in order to resolve your problem?
> > We have a long running process that writes to syslog. However we have > > observed that if the syslogd is not running aparently forked off child > > processes related to syslog calls are left in a defunct state. We are > > running on hpux 11i on a PA-RISC platform. I realize our version is > > old > > aparently 0.03 of Sys::Syslog. I have tried google searches, however > > have not come up with a good solution. Other than wrapping each > > preceding each call to syslog with a check to see if syslogd is > > running, which seems rather costly. > > > > This is perl, v5.8.0 built for PA-RISC1.1
> > Well, these are indeed quite old versions of Perl and Sys::Syslog. > I'm not really surprised that a non-running syslogd causes problems > because old versions of Sys::Syslog were opening a network or stream > socket. I strongly suggest to upgrade Sys::Syslog to version 0.15 or > later, which by default use native syslog(3) functions from the C > library. With the new version of Sys::Syslog, Perl programs will > behave exactly as normal programs using syslog(3). > > Even though it may require a little more effort, I also suggest to > upgrade your Perl installation, either from the sources or using the > binaries from http://mirrors.develooper.com/hpux/ (maintained by a > Perl5 Porter who probably knows more HP-UX than he'd like to).
-- Close the world, txEn eht nepO.
Subject: Re: [rt.cpan.org #27732] syslog causes zombie processes if syslogd has failed
Date: Thu, 26 Jul 2007 23:06:10 +0200
To: bug-Sys-Syslog [...] rt.cpan.org
From: Sébastien Aperghis-Tramoni <saper [...] cpan.org>
Download (untitled) / with headers
text/plain 1.4k
Show quoted text
> Sorry Sebastien, > > I did not upgrade to a more recent Sys::Syslog (I guess my email > filter must > have knocked out your previous email). We just worked around calls > to syslog > and put our errors out via another mechanism. > > Was there a recognized issue in earlier releases of Sys::Syslog or is > upgrade just the pat answer so that we are all looking / patching > the same > release of the code.
Searching in Perl RT, I see the ticket #36848, "Sys::Syslog::syslog kills program if syslogd not running" » http://rt.perl.org/rt3/Public/Bug/Display.html?id=36848 This is not exactly the same problem, but a wild guess would make me think this is related. As I said in my previous mail, recent versions of Sys::Syslog (v0.15 and later) now provides the "native" mechanism which uses the functions from the C library, therefore Perl programs using Sys::Syslog version 0.15 and later behave exactly like other Unix programs. So the upgrade mantra is not a way to wave you off but should correct the problems as well as provide reliability and performance improvements. All you need in order to install Sys::Syslog is a C compiler. Don't hesitate to ask me if you have any problem to install or if the upgrade didn't resolve your problems. Show quoted text
> Thanks for your response and again sorry for my apparent slow > responsiveness.
No problem. -- Sébastien Aperghis-Tramoni Close the world, txEn eht nepO.
Subject: RE: [rt.cpan.org #27732] syslog causes zombie processes if syslogd has failed
Date: Thu, 26 Jul 2007 15:34:52 -0700
To: <bug-Sys-Syslog [...] rt.cpan.org>
From: "Joseph Ujfalusi" <jujfalus [...] tgs-solutions.com>
Download (untitled) / with headers
text/plain 2.2k
Thanks, I will forward onto development team to try upgrade. Joseph Ujfalusi Tekmark Global Solutions Tel: 1-604-214-8675 Fax: 1-604-214-8674 jujfalus@tgs-solutions.com http://www.tekmarkinc.com This message is for the designated recipient only and it, as well as any attachments, may contain privileged, proprietary or confidential information. If you are not the intended recipient, do not read, copy or distribute it. Please notify the sender immediately and delete the original at once. Any other use of the email by you is prohibited. Thank you. Show quoted text
-----Original Message----- From: Sébastien Aperghis-Tramoni via RT [mailto:bug-Sys-Syslog@rt.cpan.org] Sent: Thursday, July 26, 2007 2:07 PM To: jujfalus@tgs-solutions.com Subject: Re: [rt.cpan.org #27732] syslog causes zombie processes if syslogd has failed <URL: http://rt.cpan.org/Ticket/Display.html?id=27732 >
> Sorry Sebastien, > > I did not upgrade to a more recent Sys::Syslog (I guess my email > filter must > have knocked out your previous email). We just worked around calls > to syslog > and put our errors out via another mechanism. > > Was there a recognized issue in earlier releases of Sys::Syslog or is > upgrade just the pat answer so that we are all looking / patching > the same > release of the code.
Searching in Perl RT, I see the ticket #36848, "Sys::Syslog::syslog kills program if syslogd not running" » http://rt.perl.org/rt3/Public/Bug/Display.html?id=36848 This is not exactly the same problem, but a wild guess would make me think this is related. As I said in my previous mail, recent versions of Sys::Syslog (v0.15 and later) now provides the "native" mechanism which uses the functions from the C library, therefore Perl programs using Sys::Syslog version 0.15 and later behave exactly like other Unix programs. So the upgrade mantra is not a way to wave you off but should correct the problems as well as provide reliability and performance improvements. All you need in order to install Sys::Syslog is a C compiler. Don't hesitate to ask me if you have any problem to install or if the upgrade didn't resolve your problems.
> Thanks for your response and again sorry for my apparent slow > responsiveness.
No problem. -- Sébastien Aperghis-Tramoni Close the world, txEn eht nepO.
Subject: Re: [rt.cpan.org #27732] syslog causes zombie processes if syslogd has failed
Date: Thu, 3 Jan 2008 01:29:54 +0100
To: bug-Sys-Syslog [...] rt.cpan.org, Joseph Ujfalusi <jujfalus [...] tgs-solutions.com>
From: Sébastien Aperghis-Tramoni <saper [...] cpan.org>
Download (untitled) / with headers
text/plain 854b
Hello, Joseph Ujfalusi wrote: Show quoted text
>> As I said in my previous mail, recent versions of Sys::Syslog (v0.15 >> and later) now provides the "native" mechanism which uses the >> functions from the C library, therefore Perl programs using >> Sys::Syslog version 0.15 and later behave exactly like other Unix >> programs. So the upgrade mantra is not a way to wave you off but >> should correct the problems as well as provide reliability and >> performance improvements. >> >> All you need in order to install Sys::Syslog is a C compiler. Don't >> hesitate to ask me if you have any problem to install or if the >> upgrade didn't resolve your problems.
> > > Thanks, > > I will forward onto development team to try upgrade.
Getting back to you to know if there was any news on this subject. -- Sébastien Aperghis-Tramoni Close the world, txEn eht nepO.
Subject: RE: [rt.cpan.org #27732] syslog causes zombie processes if syslogd has failed
Date: Thu, 3 Jan 2008 07:12:22 -0800
To: <bug-Sys-Syslog [...] rt.cpan.org>
From: "Joseph Ujfalusi" <jujfalus [...] tgs-solutions.com>
Download (untitled) / with headers
text/plain 1.7k
Sabastien, Please close the bug report. We ended up working around the issue, rather than upgrading Sys::Syslog. Thanks, Joseph Ujfalusi Tekmark Global Solutions Tel: 1-604-214-8675 Fax: 1-604-214-8674 jujfalus@tgs-solutions.com http://www.tekmarkinc.com This message is for the designated recipient only and it, as well as any attachments, may contain privileged, proprietary or confidential information. If you are not the intended recipient, do not read, copy or distribute it. Please notify the sender immediately and delete the original at once. Any other use of the email by you is prohibited. Thank you. Show quoted text
-----Original Message----- From: Sébastien Aperghis-Tramoni via RT [mailto:bug-Sys-Syslog@rt.cpan.org] Sent: Wednesday, January 02, 2008 4:30 PM To: jujfalus@tgs-solutions.com Subject: Re: [rt.cpan.org #27732] syslog causes zombie processes if syslogd has failed <URL: http://rt.cpan.org/Ticket/Display.html?id=27732 > Hello, Joseph Ujfalusi wrote:
>> As I said in my previous mail, recent versions of Sys::Syslog (v0.15 >> and later) now provides the "native" mechanism which uses the >> functions from the C library, therefore Perl programs using >> Sys::Syslog version 0.15 and later behave exactly like other Unix >> programs. So the upgrade mantra is not a way to wave you off but >> should correct the problems as well as provide reliability and >> performance improvements. >> >> All you need in order to install Sys::Syslog is a C compiler. Don't >> hesitate to ask me if you have any problem to install or if the >> upgrade didn't resolve your problems.
> > > Thanks, > > I will forward onto development team to try upgrade.
Getting back to you to know if there was any news on this subject. -- Sébastien Aperghis-Tramoni Close the world, txEn eht nepO.
Subject: Re: [rt.cpan.org #27732] syslog causes zombie processes if syslogd has failed
Date: Thu, 3 Jan 2008 19:59:15 +0100
To: bug-Sys-Syslog [...] rt.cpan.org, Joseph Ujfalusi <jujfalus [...] tgs-solutions.com>
From: Sébastien Aperghis-Tramoni <saper [...] cpan.org>
Download (untitled) / with headers
text/plain 400b
Joseph Ujfalusi wrote: Show quoted text
> Please close the bug report. We ended up working around the issue, > rather > than upgrading Sys::Syslog.
Seems to me a strange way to handle the issue, but well.. I'd still advice to upgrade to a newer version because it will probably be a little faster than the version you're using. Best Regards -- Sébastien Aperghis-Tramoni Close the world, txEn eht nepO.
Subject: RE: [rt.cpan.org #27732] syslog causes zombie processes if syslogd has failed
Date: Thu, 3 Jan 2008 12:00:03 -0800
To: <bug-Sys-Syslog [...] rt.cpan.org>
From: "Joseph Ujfalusi" <jujfalus [...] tgs-solutions.com>
Download (untitled) / with headers
text/plain 1.1k
20-30 customers to upgrade otherwise. Plus test cycle. When time permits we will upgrade. Thanks for your response. Joseph This message is for the designated recipient only and it, as well as any attachments, may contain privileged, proprietary or confidential information. If you are not the intended recipient, do not read, copy or distribute it. Please notify the sender immediately and delete the original at once. Any other use of the email by you is prohibited. Thank you. Show quoted text
-----Original Message----- From: Sébastien Aperghis-Tramoni via RT [mailto:bug-Sys-Syslog@rt.cpan.org] Sent: Thursday, January 03, 2008 11:00 AM To: jujfalus@tgs-solutions.com Subject: Re: [rt.cpan.org #27732] syslog causes zombie processes if syslogd has failed <URL: http://rt.cpan.org/Ticket/Display.html?id=27732 > Joseph Ujfalusi wrote:
> Please close the bug report. We ended up working around the issue, > rather > than upgrading Sys::Syslog.
Seems to me a strange way to handle the issue, but well.. I'd still advice to upgrade to a newer version because it will probably be a little faster than the version you're using. Best Regards -- Sébastien Aperghis-Tramoni Close the world, txEn eht nepO.
Subject: Re: [rt.cpan.org #27732] syslog causes zombie processes if syslogd has failed
Date: Fri, 4 Jan 2008 01:06:06 +0100
To: bug-Sys-Syslog [...] rt.cpan.org, Joseph Ujfalusi <jujfalus [...] tgs-solutions.com>
From: Sébastien Aperghis-Tramoni <saper [...] cpan.org>
Download (untitled) / with headers
text/plain 332b
Joseph Ujfalusi wrote: Show quoted text
> 20-30 customers to upgrade otherwise. Plus test cycle. When time > permits we will upgrade. Thanks for your response.
Oh ok. This makes sense. Don't hesitate to create a new ticket here if you encounter another problem. Best Regards -- Sébastien Aperghis-Tramoni Close the world, txEn eht nepO.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.