Devmon issue 🔗 link

This is really a devmon issue, but I think it will probably bite other
folks here sooner or later, so here it is.

I've been trying to set up a template to get information from some
Windows servers, and it turns out that the string I get back for the
ifDescr oid (.1.3.6.1.2.1.2.2.1.2) contains a null byte.  The problem
with that is that the interface name is being sent on to Hobbit,
complete with the null byte.  Hobbit interprets the null byte as
end-of-message within a combo stream and chops off the rest of the
message.

If I were a Perl programmer I could probably fix it, but I'm not so
I'm working around it by simply not including the interface names in
the message.

I don't know if the same thing will affect *all* character strings
coming from a Windows server, but I expect I'll find out soon enough.

So, if some kind soul can figure out where to patch devmon to remove
the null, it would certainly help me, and probably other folks too.

Thanks,

Ralph Mitchell

Hello all,

I have an issue with devmon. Perhaps someone has encountered the same and found a solution.
Devmon works without problems, except when there is no oid data to be read. When this happens for a test, all the other tests seem to get into trouble.
Result is that not just the single test goes white, but also other test which do have correct data.
I have checked if I am not using double oid's.
Any tips are welcome.

Thanks
Jurgen Claessens


This e-mail and all files transmitted as attachment(s) thereto are confidential and solely intended for the individual to whom or the organization to which they are addressed. If you received this e-mail by mistake, please notify Cegeka's Service user-8170e541d067@xymon.invalid at cegeka.be or call +32 (0)11 240 363. We thank you in advance. Cegeka hereby confirms that this message has been swept by Sophos for the presence of viruses.