[Xymon] Serial alarm feeds

[Kevin King]

The link hack did not work. If it would then I would expect to see the
msg.host.txt in the tmp directory. I am thinking we might need more in the
client message.

 

Still trying.

 

-Kevin

 

From: Jeremy Laidman [mailto:jlaidman at rebel-it.com.au] 
Sent: Tuesday, August 27, 2013 4:54 PM
To: Kevin King
Cc: KING, KEVIN; xymon at xymon.com
Subject: Re: [Xymon] Serial alarm feeds

 

On 28 August 2013 06:20, Kevin King <kc6ovd at gmail.com> wrote:

I have this running. I am getting the logfetch-special.status  it is
tracking the lines it has processed.

 

Great.

 

  I am not getting a msg file or a column and nothing in
xymonclientl-speacial.log.


*sad face*

 

Check your ghost report.  Also see if you can view a client data page for
the device.  Do this by viewing the conn page for another device, click on
the link for "client data" for that device, and then change the device name
in the URL to eagle.example.com (or whatever).  You should get a client
message page.

 

If there's no client data page, then the xymond_client handler is rejecting
the message for some reason.  Have a look at the output for xymond_client
and see if it's complaining about something.  I wonder if there's a critical
section from the client message that's critical.  For example, maybe
xymond_client rejects the client data message if it has no [date] and/or
[uname] sections.

 

By the way, as you're going to implement this as a separate script, you
might consider capturing the output from the command that sends the client
message, and that can be used for your logfetch-special.cfg file.  The
"client" protocol not only accepts the client data but it gives back the
section from client-local.cfg that matches the hostname in the client
message header.  But I'd add this bit later.

 

J

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20130827/6de6ae50/attachment.html>