Clients not loading custom client-local.cfg values
Greetings,
We have a variety of servers in our environment which we¹re looking to monitor with Xymon. I¹ve recently built a Xymon server 4.3.7 and compiled some clients on our SUSE 9 machines. When running the clients they only seem to match the entries in the client-local.cfg file on the server for [linux] and not the custom entries which I created [suse-srvs]. I¹ve tried launching the client with with class=suse-srv but to no avail. I feel like I¹m missing something, can anyone give me some feedback?
-- Thanks, Josh Bradley
This message is a PRIVATE communication. If you are not the intended recipient, please do not read, copy, use, or disclose to others. If you have received this message in error, please reply to sender and delete this message from your system. Thank you.
What does your "client data" page show as your config class? It's the last word of the first line in the [collector:] section.
I note that you show "-class" set to "suse-srv" but your client-local.cfg entry set to "suse-srvs" instead. Was that a typo in your email, or in your configuration?
Also, the "--class" suffix has two dashes, and you listed only one.
Also, after changes to client-local.cfg, you might need to kill the "xymond" process (it should restart automatically) to have the changes take effect.
It should work for you. The man page for client-local.cfg states that only the hostname and OS name are used when matching the relevant section, and doesn't mention the config class. Despite this, I see posts indicating that people are using this. Indeed Henrik has said that it's actually the class that's matched, and the class defaults to the OS type. I think the doco needs updating in this regard.
On Wed, May 2, 2012 at 3:37 AM, Bradley, Joshua E. <jbradley at ems.com> wrote:
Greetings,
We have a variety of servers in our environment which we’re looking to monitor with Xymon. I’ve recently built a Xymon server 4.3.7 and compiled some clients on our SUSE 9 machines. When running the clients they only seem to match the entries in the client-local.cfg file on the server for [linux] and not the custom entries which I created [suse-srvs]. I’ve tried launching the client with with —class=suse-srv but to no avail. I feel like I’m missing something, can anyone give me some feedback?
-- Thanks, Josh Bradley
- This message is a PRIVATE communication. If you are not the intended recipient, please do not read, copy, use, or disclose to others. If you have received this message in error, please reply to sender and delete this message from your system. Thank you. *
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
These are very helpful suggestions to use for troubleshooting. The ³client data² page was showing something like [collector:] client server,name,ems,com.linux linux
Which was clearly not respecting the ³--class=suse-srvs² that was being applied to the startup script.
I¹ve tried starting the client now with: ³./runclient.sh --os=suse-srvs start² which does adjust the OS value reported accordingly, but as there isn¹t a ³xymonclient-suse-srvs.sh² script the msgs just pile up in the ./tmp/ and are never delivered to the server.
Any other thoughts or suggestions are welcomed.
-- Thanks, Josh Bradley
From: Jeremy Laidman <jlaidman at rebel-it.com.au> Date: Wed, 2 May 2012 12:06:40 +1000 To: Joshua Bradley <jbradley at ems.com> Cc: <xymon at xymon.com> Subject: Re: [Xymon] Clients not loading custom client-local.cfg values
What does your "client data" page show as your config class? It's the last word of the first line in the [collector:] section.
I note that you show "-class" set to "suse-srv" but your client-local.cfg entry set to "suse-srvs" instead. Was that a typo in your email, or in your configuration?
Also, the "--class" suffix has two dashes, and you listed only one.
Also, after changes to client-local.cfg, you might need to kill the "xymond" process (it should restart automatically) to have the changes take effect.
It should work for you. The man page for client-local.cfg states that only the hostname and OS name are used when matching the relevant section, and doesn't mention the config class. Despite this, I see posts indicating that people are using this. Indeed Henrik has said that it's actually the class that's matched, and the class defaults to the OS type. I think the doco needs updating in this regard.
On Wed, May 2, 2012 at 3:37 AM, Bradley, Joshua E. <jbradley at ems.com> wrote:
Greetings,
We have a variety of servers in our environment which we¹re looking to monitor with Xymon. I¹ve recently built a Xymon server 4.3.7 and compiled some clients on our SUSE 9 machines. When running the clients they only seem to match the entries in the client-local.cfg file on the server for [linux] and not the custom entries which I created [suse-srvs]. I¹ve tried launching the client with with class=suse-srv but to no avail. I feel like I¹m missing something, can anyone give me some feedback?
-- Thanks, Josh Bradley
This message is a PRIVATE communication. If you are not the intended recipient, please do not read, copy, use, or disclose to others. If you have received this message in error, please reply to sender and delete this message from your system. Thank you.
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
This message is a PRIVATE communication. If you are not the intended recipient, please do not read, copy, use, or disclose to others. If you have received this message in error, please reply to sender and delete this message from your system. Thank you.
If "--os" works, then "--class" should work also. Perhaps a typo? Perhaps
check the value of CONFIGCLASS in the running xymonlaunch process (eg:
strings /proc/pgrep xymonlaunch/environ | grep CONFIGCLASS).
On Thu, May 3, 2012 at 7:09 AM, Bradley, Joshua E. <jbradley at ems.com> wrote:
These are very helpful suggestions to use for troubleshooting. The “client data” page was showing something like [collector:] client server,name,ems,com.linux linux
Which was clearly not respecting the “--class=suse-srvs” that was being applied to the startup script.
I’ve tried starting the client now with: “./runclient.sh --os=suse-srvs start” which does adjust the OS value reported accordingly, but as there isn’t a “xymonclient-suse-srvs.sh” script the msgs just pile up in the ./tmp/ and are never delivered to the server.
Any other thoughts or suggestions are welcomed.
-- Thanks, Josh Bradley
*From: *Jeremy Laidman <jlaidman at rebel-it.com.au> *Date: *Wed, 2 May 2012 12:06:40 +1000 *To: *Joshua Bradley <jbradley at ems.com> *Cc: *<xymon at xymon.com> *Subject: *Re: [Xymon] Clients not loading custom client-local.cfg values
What does your "client data" page show as your config class? It's the last word of the first line in the [collector:] section.
I note that you show "-class" set to "suse-srv" but your client-local.cfg entry set to "suse-srvs" instead. Was that a typo in your email, or in your configuration?
Also, the "--class" suffix has two dashes, and you listed only one.
Also, after changes to client-local.cfg, you might need to kill the "xymond" process (it should restart automatically) to have the changes take effect.
It should work for you. The man page for client-local.cfg states that only the hostname and OS name are used when matching the relevant section, and doesn't mention the config class. Despite this, I see posts indicating that people are using this. Indeed Henrik has said that it's actually the class that's matched, and the class defaults to the OS type. I think the doco needs updating in this regard.
On Wed, May 2, 2012 at 3:37 AM, Bradley, Joshua E. <*jbradley at ems.com*> wrote:
Greetings,
We have a variety of servers in our environment which we’re looking to monitor with Xymon. I’ve recently built a Xymon server 4.3.7 and compiled some clients on our SUSE 9 machines. When running the clients they only seem to match the entries in the client-local.cfg file on the server for [linux] and not the custom entries which I created [suse-srvs]. I’ve tried launching the client with with —class=suse-srv but to no avail. I feel like I’m missing something, can anyone give me some feedback?
-- Thanks, Josh Bradley
*This message is a PRIVATE communication. If you are not the intended recipient, please do not read, copy, use, or disclose to others. If you have received this message in error, please reply to sender and delete this message from your system. Thank you. *
Xymon mailing list *Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon *
- This message is a PRIVATE communication. If you are not the intended recipient, please do not read, copy, use, or disclose to others. If you have received this message in error, please reply to sender and delete this message from your system. Thank you. *
Hi, in xymon 4.3.7 seems that until a column (only for user test s, not for client standard test es. cpu, disk, conn etc) is green no history files are generated .. is correct ?
Marco
I would think the test would have to actually run (eg smtp would be checked by the xymon server) for a history to be made, it doesn't matter if it has a green or red result in my experience. If you just put in a test name and nothing acts on it, then there is nothing to put in the history, no?
On 4/05/2012 at 7:51 PM, in message <4FA3AD8F.5060901 at regione.toscana.it>, Marco Avvisano <marco.avvisano at regione.toscana.it> wrote:
Hi, in xymon 4.3.7 seems that until a column (only for user test s, not for client standard test es. cpu, disk, conn etc) is green no history files are generated .. is correct ?
Marco
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
On Friday 04 May 2012 12:21:03 Marco Avvisano wrote:
Hi, in xymon 4.3.7 seems that until a column (only for user test s, not for client standard test es. cpu, disk, conn etc) is green no history files are generated .. is correct ? Only when the color changes, the original status is copied as history. So if the color is green (or red, or ...) forever, there are no history files created.
Stef
cat /var/xymon-data/hist/wallace,orix,com,au.smtp
Mon May 7 16:45:57 2012 red 1336373157
Isn't this a history file?
On 7/05/2012 at 3:47 PM, in message <13502212.GcxD4rLlb3 at scne>, Stef Coene <stef.coene at docum.org> wrote: On Friday 04 May 2012 12:21:03 Marco Avvisano wrote: Hi, in xymon 4.3.7 seems that until a column (only for user test s, not for client standard test es. cpu, disk, conn etc) is green no history files are generated .. is correct ? Only when the color changes, the original status is copied as history. So if the color is green (or red, or ...) forever, there are no history files created.
Stef
participants (5)
-
jbradley＠ems.com
-
jlaidman＠rebel-it.com.au
-
marco.avvisano＠regione.toscana.it
-
Phil.Crooker＠orix.com.au
-
stef.coene＠docum.org