Re: [Nagios-devel] TODO with embedded Perl support.
Posted: Thu Jan 20, 2005 7:03 am
Dear Stanley,
running Nagios with embedded perl on Linux in the current cvs version I =
have also problems with a memory leak. The memory consumption after =
sending a SIGHUP to the nagios core process grows sometimes > 5 MB / =
SIGHUP. Maybe this helps analyzing the problem.
Thanks and Best Regards
Marcus Hildenbrand
-----Urspr=FCngliche Nachricht-----
Von: [email protected] =
[mailto:[email protected]] Im Auftrag von Stanley =
Hopcroft
Gesendet: Montag, 17. Januar 2005 02:53
An: [email protected]
Betreff: [Nagios-devel] TODO with embedded Perl support.
Dear Folks,
I am writing to enumerate the known problems with embedded Perl support=20
in Nagios.
Since moving from Perl 5.005 I have become aware of these issues. I=20
don't think they have much, if anything, to do with Nagios.
It seems that the embedded Perl support with a threaded Perl suffers=20
from
1 heavy leak rate 600 kB - 1 MB/hour=20
This is way above what I was happy to tolerate with a non threaded Perl.
2 Problems with p1.pl
Perl will SEGV (taking an embedded Perl Nag) with it if the p1.pl=20
debugging hooks are used ie
setting DEBUG or GARRULOUS in the p1.pl text and an accompanying log=20
file does not track the plugin execution (as it did with older Perls)=20
but causes a SEGV in Perl.
p1.pl with the default log level (ie no plugin trace) works Ok subject=20
to the leak above
(FWIW, the SEGV comes from Perl whether called from C or from Perl; it=20
is not the C code in checks.c that is causing this; the fault is in=20
p1.pl or in libperl in the Perl port on this system. It seems strange=20
that a Perl program can cause Perl to SEGV)
I am investigating both matters.
These things have only been checked on FreeBSD 4-10-RELEASE/Perl 5.8.5=20
built with threads.
(if people want to contribute to this latter problem [SEGV], there is no =
need to have a working Nagios to do so. The problems can be duplicated=20
from Perl. There is a tarball of code to play around with it).
Yours sincerely.
--=20
Stanley Hopcroft
IP Australia
Ph: (02) 6283 3189 Fax: (02) 6281 1353
PO Box 200 Woden ACT 2606
http://www.ipaustralia.gov.au
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
running Nagios with embedded perl on Linux in the current cvs version I =
have also problems with a memory leak. The memory consumption after =
sending a SIGHUP to the nagios core process grows sometimes > 5 MB / =
SIGHUP. Maybe this helps analyzing the problem.
Thanks and Best Regards
Marcus Hildenbrand
-----Urspr=FCngliche Nachricht-----
Von: [email protected] =
[mailto:[email protected]] Im Auftrag von Stanley =
Hopcroft
Gesendet: Montag, 17. Januar 2005 02:53
An: [email protected]
Betreff: [Nagios-devel] TODO with embedded Perl support.
Dear Folks,
I am writing to enumerate the known problems with embedded Perl support=20
in Nagios.
Since moving from Perl 5.005 I have become aware of these issues. I=20
don't think they have much, if anything, to do with Nagios.
It seems that the embedded Perl support with a threaded Perl suffers=20
from
1 heavy leak rate 600 kB - 1 MB/hour=20
This is way above what I was happy to tolerate with a non threaded Perl.
2 Problems with p1.pl
Perl will SEGV (taking an embedded Perl Nag) with it if the p1.pl=20
debugging hooks are used ie
setting DEBUG or GARRULOUS in the p1.pl text and an accompanying log=20
file does not track the plugin execution (as it did with older Perls)=20
but causes a SEGV in Perl.
p1.pl with the default log level (ie no plugin trace) works Ok subject=20
to the leak above
(FWIW, the SEGV comes from Perl whether called from C or from Perl; it=20
is not the C code in checks.c that is causing this; the fault is in=20
p1.pl or in libperl in the Perl port on this system. It seems strange=20
that a Perl program can cause Perl to SEGV)
I am investigating both matters.
These things have only been checked on FreeBSD 4-10-RELEASE/Perl 5.8.5=20
built with threads.
(if people want to contribute to this latter problem [SEGV], there is no =
need to have a working Nagios to do so. The problems can be duplicated=20
from Perl. There is a tarball of code to play around with it).
Yours sincerely.
--=20
Stanley Hopcroft
IP Australia
Ph: (02) 6283 3189 Fax: (02) 6281 1353
PO Box 200 Woden ACT 2606
http://www.ipaustralia.gov.au
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]