Re: [opennms-devel] Bug#: 2235

Hello,

Thanks for catch it.

It fixed on rev 8336

Alejandro.

On Feb 4, 2008, at 2:59 PM, Rabie Van der Merwe wrote:

> Hi,
>
> I see bug 2235 is fixed, just a note, nothing big, there is a typo in
> the debug output attached to the bug:
>
> "Ignoring value because of sysUpTime chaned"
> Should read:
> "Ignoring value because of sysUpTime changed" :)
>
> Regards
> Rabie
>
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of  
> Rabie
> Van der Merwe
> Sent: 04 February 2008 17:50 PM
> To: OpenNMS Code Development and Bugs
> Subject: Re: [opennms-devel] Bug#: 2235
>
> Mmm I have seen the uptime issue on some older boxes here ...
> On a side note I run a threshold check on sysUptime to catch any  
> system
> restarts that falls between the 5 min ping checks :)
>
> Rabie
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of  
> Mike M
> Sent: 04 February 2008 14:37 PM
> To: OpenNMS Code Development and Bugs
> Subject: Re: [opennms-devel] Bug#: 2235
>
> On Feb 4, 2008 6:43 AM, Rabie Van der Merwe <[email protected]>  
> wrote:
>> Hi,
>>
>> Just a thought, but it might not be a bad idea to extent on this a
>> little
>> and trigger a rescan of a node if it picks up that the sysuptime has
>> reset,
>> that way if anything moved because of a reboot we would catch it?
>> (think cisco :) )
>
> I think this would be cool, especially since we occasionally see nodes
> kernel panic and reboot faster than OpenNMS can catch them.  My only
> concern is that sysuptime is not exactly reliable, especially for
> high-uptime Linux machines which have the jiffies rollover problem
> after 497 days.
>
> Mike
>
> ------------------------------------------------------------------------
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> http://www.opennms.org/index.php/Mailing_List_FAQ
>
> opennms-devel mailing list
>
> To *unsubscribe* or change your subscription options, see the bottom  
> of
> this page:
> https://lists.sourceforge.net/lists/listinfo/opennms-devel
>
> ------------------------------------------------------------------------
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> http://www.opennms.org/index.php/Mailing_List_FAQ
>
> opennms-devel mailing list
>
> To *unsubscribe* or change your subscription options, see the bottom  
> of
> this page:
> https://lists.sourceforge.net/lists/listinfo/opennms-devel
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> http://www.opennms.org/index.php/Mailing_List_FAQ
>
> opennms-devel mailing list
>
> To *unsubscribe* or change your subscription options, see the bottom  
> of this page:
> https://lists.sourceforge.net/lists/listinfo/opennms-devel






-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-devel mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel