Skip Menu |

This queue is for tickets about the SNMP-Persist CPAN distribution.

Report information
The Basics
Id: 24287
Status: open
Priority: 0/
Queue: SNMP-Persist

People
Owner: Nobody in particular
Requestors: cyriel.de.grijs [...] capgemini.com
Cc:
AdminCc:

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



Subject: Bug in SNMP::Persist
Date: Tue, 9 Jan 2007 18:35:54 +0100
To: <bug-SNMP-Persist [...] rt.cpan.org>
From: "Grijs, Cyriel de" <cyriel.de.grijs [...] capgemini.com>
Dear Anna, First of all, thanks for this plug-in: It makes my writing of per-scripts for Cacti-monitoring a log easier! However, I have encountered a bug in the module that causes perlscripts using this module to crash. It can be reproduced like this: 1) use the sample script that you wrote, (replace the missing # symbol before 'next application) 2) Run the script from the commandline and wait for twice the amount of time in the "sleep" statement. The script will now crash with message "panic: MUTEX_DESTROY.". This is during the call of define_subtree(\%subtree); If you keep feeding the script get-requests within the sleep-period, the crash won't occur. (Oh, btw, the sample script makes more sense if you place the "my $index=1;" within the while-loop.) Regards, Cyriel de Grijs This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Subject: RE: [rt.cpan.org #24287] AutoReply: Bug in SNMP::Persist
Date: Fri, 26 Jan 2007 15:11:43 +0100
To: <bug-SNMP-Persist [...] rt.cpan.org>
From: "Grijs, Cyriel de" <cyriel.de.grijs [...] capgemini.com>
Dear Anna, I've created a patch for the issues in this bug. Please test it and see if I haven't broken anything. Regards, CdG Show quoted text
-----Original Message----- From: Bugs in SNMP-Persist via RT [mailto:bug-SNMP-Persist@rt.cpan.org] Sent: Tuesday, January 09, 2007 6:36 PM To: Grijs, Cyriel de Subject: [rt.cpan.org #24287] AutoReply: Bug in SNMP::Persist Greetings, This message has been automatically generated in response to the creation of a trouble ticket regarding: "Bug in SNMP::Persist", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [rt.cpan.org #24287]. Your ticket is accessible on the web at: http://rt.cpan.org/Ticket/Display.html?id=24287 Please include the string: [rt.cpan.org #24287] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, bug-SNMP-Persist@rt.cpan.org ------------------------------------------------------------------------ - Dear Anna, First of all, thanks for this plug-in: It makes my writing of per-scripts for Cacti-monitoring a log easier! However, I have encountered a bug in the module that causes perlscripts using this module to crash. It can be reproduced like this: 1) use the sample script that you wrote, (replace the missing # symbol before 'next application) 2) Run the script from the commandline and wait for twice the amount of time in the "sleep" statement. The script will now crash with message "panic: MUTEX_DESTROY.". This is during the call of define_subtree(\%subtree); If you keep feeding the script get-requests within the sleep-period, the crash won't occur. (Oh, btw, the sample script makes more sense if you place the "my $index=1;" within the while-loop.) Regards, Cyriel de Grijs This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

Message body is not shown because sender requested not to inline it.

Subject: Re: [rt.cpan.org #24287] AutoReply: Bug in SNMP::Persist
Date: Mon, 29 Jan 2007 12:39:55 +0000
To: bug-SNMP-Persist [...] rt.cpan.org
From: "Anna Wiejak" <anna.wiejak [...] gmail.com>
Hi, Thanks for pointing out the problem with the crash! Its fixed in 0.04 version of SNMP::Persist - I created a separate mutex variable - mutex can't be reused to store other values (in this case it was a shared mib tree reference). Regards! -- Anna Wiejak On 1/26/07, Grijs, Cyriel de via RT <bug-SNMP-Persist@rt.cpan.org> wrote: Show quoted text
> > Queue: SNMP-Persist > Ticket <URL: http://rt.cpan.org/Ticket/Display.html?id=24287 > > > > Dear Anna, > > I've created a patch for the issues in this bug. Please test it and see > if I haven't broken anything. > > Regards, > > CdG > > -----Original Message----- > From: Bugs in SNMP-Persist via RT [mailto:bug-SNMP-Persist@rt.cpan.org] > Sent: Tuesday, January 09, 2007 6:36 PM > To: Grijs, Cyriel de > Subject: [rt.cpan.org #24287] AutoReply: Bug in SNMP::Persist > > > Greetings, > > This message has been automatically generated in response to the > creation of a trouble ticket regarding: > "Bug in SNMP::Persist", > a summary of which appears below. > > There is no need to reply to this message right now. Your ticket has > been > assigned an ID of [rt.cpan.org #24287]. Your ticket is accessible > on the web at: > > http://rt.cpan.org/Ticket/Display.html?id=24287 > > Please include the string: > > [rt.cpan.org #24287] > > in the subject line of all future correspondence about this issue. To do > so, > you may reply to this message. > > Thank you, > bug-SNMP-Persist@rt.cpan.org > > ------------------------------------------------------------------------ > - > > Dear Anna, > > > > First of all, thanks for this plug-in: It makes my writing of > per-scripts for Cacti-monitoring a log easier! > > > > However, I have encountered a bug in the module that causes perlscripts > using this module to crash. It can be reproduced like this: > > > > 1) use the sample script that you wrote, (replace the missing # > symbol before 'next application) > > 2) Run the script from the commandline and wait for twice the > amount of time in the "sleep" statement. > > > > The script will now crash with message "panic: MUTEX_DESTROY.". This is > during the call of define_subtree(\%subtree); > > > > If you keep feeding the script get-requests within the sleep-period, the > crash won't occur. > > > > (Oh, btw, the sample script makes more sense if you place the "my > $index=1;" within the while-loop.) > > > > Regards, > Cyriel de Grijs > > > > > > > > > > > > This message contains information that may be privileged or confidential > and is the property of the Capgemini Group. It is intended only for the > person to whom it is addressed. If you are not the intended recipient, > you are not authorized to read, print, retain, copy, disseminate, > distribute, or use this message or any part thereof. If you receive this > message in error, please notify the sender immediately and delete all > copies of this message. > > > > This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. > > > >