[Xymon] [Devmon] devmon mysterious behaviour

[Becker Christian]

Hello Ryan,

hm, i should have thought about this by myself already.

Your description regarding the concurrent snmp polls sounds reasonable to me. I'll give this a try over the weekend and deactivate devmon in the "old" environment, so that I have devmon activated in the "new" environment only.
The issue with the lib paths and sym links is OK since devmon is running in general; further, the "old" environment is 64 Bit too.

Thank so far!

Regards

Christian Becker
IT-Services

Christian.Becker at rhein-zeitung.net
_________________________________
Mittelrhein-Verlag GmbH
August-Horch-Straße 28
D-56070 Koblenz
Verleger und Geschäftsführer: Walterpeter Twer
Reg.-Gericht Koblenz HRB 121
Finanzamt Koblenz Str.Nr. 22 65 10 285 2
www.rhein-zeitung.de

-----Ursprüngliche Nachricht-----
Von: Ryan Rush [mailto:ryanmrush at gmail.com] 
Gesendet: Freitag, 31. Oktober 2014 09:16
An: devmon-support at lists.sourceforge.net
Cc: xymon at xymon.com
Betreff: Re: [Devmon] devmon mysterious behaviour

Are there any concurrent snmp polls running? I have noticed that when testing, older Cisco hardware will queue new walks when one is running. If the runtime if the current poll exceeds timeout on the new poll, one might experience the symptoms you are describing.

Verify no other polls are occurring, then check your lib paths. I have experienced issues when migrating older code to 64 bit Linux systems, and resolved the problems with sym links after reviewing debugs.
On Oct 31, 2014 1:05 AM, "Becker Christian" < christian.becker at rhein-zeitung.net> wrote:

> Hello folks,
>
> we are running a Xymon 4.3.11 environment that persists of a server 
> running Red Hat Enterprise Linux 6.1 64 Bit. This setup also includes 
> devmon (0.3.1-beta1). In this environment, devmon works like a charm.
>
> Now we are in the situation to go away from Red Hat Enterprise Linux 
> and go ahead to Ubuntu 14.0.4.1 LTS 64 Bit. This is an internal decision.
> On this new environment I have set up Xymon 4.3.17, including devmon, 
> which is the same release as in our "old" environment.
>
> But here, I have mysterious problem, for which I cannot find an
> explanation:
> In the "old" environment, there is a Cisco 6506, that is "asked" by devmon.
> For any reason, in this environment devmon doesn't get any data out of 
> this Cisco device. It says "Missing repeater data for primary OID #######"
> (the "#######" is just an example....).
>
> The mysterious thing now is, that in the "new" environment, devmon 
> (some
> times...) extracts data out of this Cisco device, but -and this is the 
> most confusing thing- every now and then it is changing from "purple" to "clear"
> (again saying "Missing repeater data for primary OID ####### ".), and 
> on any time it changes back to "green" containing current data.
>
> The devmon logfile doesn't seem to contain any hint on this situation.
>
> I have really no idea why this could happen.
>
> Does anybody of you have an idea about this behavior?
>
> Greetings
> Christian
>
> Christian Becker
> IT-Services
>
> Christian.Becker at rhein-zeitung.net<mailto:
> Christian.Becker at rhein-zeitung.net>
> _________________________________
> Mittelrhein-Verlag GmbH
> August-Horch-Straße 28
> D-56070 Koblenz
> Verleger und Geschäftsführer: Walterpeter Twer Reg.-Gericht Koblenz 
> HRB 121 Finanzamt Koblenz Str.Nr. 22 65 10 285 2 
> www.rhein-zeitung.de<http://www.rhein-zeitung.de/>
>
>
> ----------------------------------------------------------------------
> -------- _______________________________________________
> Devmon-support mailing list
> Devmon-support at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>
------------------------------------------------------------------------------
_______________________________________________
Devmon-support mailing list
Devmon-support at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/devmon-support