Xymon Mailing List Archive search

monitoring listen local socket

5 messages in this thread

list Robert Schetterer · Mon, 14 Feb 2011 09:50:38 +0100 ·
Hi @ll
anyone an example with how to monitor
a socket for exist and listen in hobbit-clients
i.e
/var/run/clamav/clamav-milter.ctl
i am not sure with file statement and/or/nor ports

-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria
list Henrik Størner · Mon, 14 Feb 2011 10:03:47 +0000 (UTC) ·
quoted from Robert Schetterer
In <user-5182ce55e919@xymon.invalid> Robert Schetterer <user-56c160449604@xymon.invalid> writes:
anyone an example with how to monitor
a socket for exist and listen in hobbit-clients
i.e
/var/run/clamav/clamav-milter.ctl
i am not sure with file statement and/or/nor ports
You could do it with a check in the Xymon client.
In client-local.cfg, add
  file:/var/run/clamav/clamav-milter.ctl
to have the client send information about this
(socket) file. Then in the analysis.cfg config
(hobbit-clients.cfg in older versions), add

   HOST=blabla
      FILE /var/run/clamav/clamav-milter.ctl type=socket COLOR=red

This should give you an alert if the file does not
exist, or it is not a socket-type file.


Regards,
Henrik
list Robert Schetterer · Mon, 14 Feb 2011 12:08:37 +0100 ·
Am 14.02.2011 11:03, schrieb Henrik Størner:
quoted from Robert Schetterer
In <user-5182ce55e919@xymon.invalid> Robert Schetterer <user-56c160449604@xymon.invalid> writes:
anyone an example with how to monitor
a socket for exist and listen in hobbit-clients
i.e
/var/run/clamav/clamav-milter.ctl
i am not sure with file statement and/or/nor ports
You could do it with a check in the Xymon client.
In client-local.cfg, add
  file:/var/run/clamav/clamav-milter.ctl
to have the client send information about this
(socket) file. Then in the analysis.cfg config
(hobbit-clients.cfg in older versions), add

   HOST=blabla
      FILE /var/run/clamav/clamav-milter.ctl type=socket COLOR=red

This should give you an alert if the file does not
exist, or it is not a socket-type file.


Regards,
Henrik

thx for recommend
done it , still not works
any idea how to debug?

-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria
list Robert Schetterer · Mon, 14 Feb 2011 12:31:03 +0100 ·
Am 14.02.2011 12:08, schrieb Robert Schetterer:
quoted from Robert Schetterer
Am 14.02.2011 11:03, schrieb Henrik Størner:
In <user-5182ce55e919@xymon.invalid> Robert Schetterer <user-56c160449604@xymon.invalid> writes:
anyone an example with how to monitor
a socket for exist and listen in hobbit-clients
i.e
/var/run/clamav/clamav-milter.ctl
i am not sure with file statement and/or/nor ports
You could do it with a check in the Xymon client.
In client-local.cfg, add
  file:/var/run/clamav/clamav-milter.ctl
to have the client send information about this
(socket) file. Then in the analysis.cfg config
(hobbit-clients.cfg in older versions), add

   HOST=blabla
      FILE /var/run/clamav/clamav-milter.ctl type=socket COLOR=red

This should give you an alert if the file does not
exist, or it is not a socket-type file.


Regards,
Henrik

thx for recommend
done it , still not works
any idea how to debug?
sorry for the noise , looks like it need time
for update, now it apears

-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria
list Henrik Størner · Mon, 14 Feb 2011 12:44:06 +0000 (UTC) ·
quoted from Robert Schetterer
In <user-dd94401f63b1@xymon.invalid> Robert Schetterer <user-56c160449604@xymon.invalid> writes:
thx for recommend
done it , still not works
any idea how to debug?
Check the "Client data" link found on any of the status-
pages for this host, and verify that the expected file
information is included. It should look somewhat like
this, except the filename and information differs:

[file:/var/log/apache2/hswn.log]
type:100000 (file)
mode:644 (-rw-r--r--)
linkcount:1
owner:0 (root)
group:4 (adm)
size:1039307
clock:1297687186 (2011/02/14-13:39:46)
atime:1297686728 (2011/02/14-13:32:08)
ctime:1297687180 (2011/02/14-13:39:40)
mtime:1297687180 (2011/02/14-13:39:40)


If that information is not present for the socket/file
you want to monitor, then you need to look at why the
client is not providing the information.

If it is there, then the problem is probably in the
analysis.cfg (hobbit-clients.cfg) setup.


Regards,
Henrik