Cannot get custom script column back.
list Lenny Hewitt
Hi, I'm having problems with how xymon is reporting a status and wanted to give you a step-by-step detailed description of what I did to get in the state that it is in so that it will hopefully describe what to do to fix this anomally. I set up a custom script to monitor the status of process, more than just monitoring to see if the daemon is up or down, etc, etc. In testing the script I used the example of the client-side script on my client. I created the script on the clients and everything showed up on the xymon webpage and worked perfectly. I then realized that I wanted to rename the script on the client to something better describing it. So I proceeded to rename the script and update the clientlaunch.cfg in etc on each client to reflect the new name. After a short period the column on the xymon website showing the status of the original name of the script went purple because that script name was not reporting anymore. I removed this purple column by running xymon 127.0.0.1 "drop <HOSTNAME> <columname>". The problem is I can't get the column to show back up again with the status from the newly named script that is currently configured. The names of the columns were the same, just the script name changed. I suspect that is why it is behaving this way but don't know what to do to fix this state that it's in. Any help would be greatly appreciated. Lenny
list John Thurston
▸
On 2/12/2014 7:34 AM, Hewitt, Lenny wrote:
Hi, I'm having problems with how xymon is reporting a status and wanted to give you a step-by-step detailed description of what I did to get in the state that it is in so that it will hopefully describe what to do to fix this anomally.
I set up a custom script to monitor the status of process, more than just monitoring to see if the daemon is up or down, etc, etc. In testing the script I used the example of the client-side script on my client. I created the script on the clients and everything showed up on the xymon webpage and worked perfectly. I then realized that I wanted to rename the script on the client to something better describing it. So I proceeded to rename the script and update the clientlaunch.cfg in etc on each client to reflect the new name. After a short period the column on the xymon website showing the status of the original name of the script went purple because that script name was not reporting anymore. I removed this purple column by running xymon 127.0.0.1 "drop <HOSTNAME> <columname>". The problem is I can't get the column to show back up again with the status from the newly named script that is currently configured. The names of the columns were the same, just the script name cha
nged. I suspect that is why it is behaving this way but don't know what to do to fix this state that it's in.
Any help would be greatly appreciated.
The column went purple because the test result stopped arriving.
If the test name was not changed as part of the script-rename, then I have to assume that the script is not actually running. Check the spelling in the clientlaunch.cfg and confirm your newly renamed script is still executable.
Does the test result appear if you launch the script by hand on one host?
--
Do things because you should, not just because you can.
John Thurston XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Enterprise Technology Services
Department of Administration
State of Alaska
list Lenny Hewitt
Hi, I'm having problems with how xymon is reporting a status and wanted to give you a step-by-step detailed description of what I did to get in the state that it is in so that it will hopefully describe what to do to fix this anomally. I set up a custom script to monitor the status of process, more than just monitoring to see if the daemon is up or down, etc, etc. In testing the script I used the example of the client-side script on my client. I created the script on the clients and everything showed up on the xymon webpage and worked perfectly. I then realized that I wanted to rename the script on the client to something better describing it. So I proceeded to rename the script and update the clientlaunch.cfg in etc on each client to reflect the new name. After a short period the column on the xymon website showing the status of the original name of the script went purple because that script name was not reporting anymore. I removed this purple column by running xymon 127.0.0.1 "drop <HOSTNAME> <columname>". The problem is I can't get the column to show back up again with the status from the newly named script that is currently configured. The names of the columns were the same, just the script name changed. I suspect that is why it is behaving this way but don't know what to do to fix this state that it's in. Any help would be greatly appreciated. Lenny
list Phil Crooker
▸
From: Xymon on behalf of Hewitt, Lenny Sent: Thursday, 13 February 2014 5:13 AM To: 'xymon at xymon.com' Subject: [Xymon] Cannot get custom script column back. Hi, I'm having problems with how xymon is reporting a status and wanted to give you a step-by-step detailed description of what I did to get in the state that it is in so that it will hopefully describe what to do to fix this anomally. I set up a custom script to monitor the status of process, more than just monitoring to see if the daemon is up or down, etc, etc. In testing the script I used the example of the client-side script on my client. I created the script on the clients and everything showed up on the xymon webpage and worked perfectly. I then realized that I wanted to rename the script on the client to something better describing it. So I proceeded to rename the script and update the clientlaunch.cfg in etc on each client to reflect the new name. After a short period the column on the xymon website showing the status of the original name of the script went purple because that script name was not reporting anymore. I removed this purple column by running xymon 127.0.0.1 "drop <HOSTNAME> <columname>". The problem is I can't get the column to show back up again with the status from the newly named script that is currently configured. The names of the columns were the same, just the script name changed. I suspect that is why it is behaving this way but don't know what to do to fix this state that it's in. Any help would be greatly appreciated. Lenny
The name of the script wouldn't affect the test status if the renamed script is still running, it should not have gone purple. Did you change the name of the script in clientlaunch.cfg? What if you run the script manually as the xymon user, does that appear at the server? Are you sure the script is actually running and the client is sending the results to the server - try running tcpdump to capture that traffic. Do you see any anominalies under the xymond page of the xymon server? Are other tests from that xymon client working?
cheers, Phil
list Lenny Hewitt
I actually didn't rename the script. I ended up copying the script to a new name. Keeping the old script there. Then changing the clientlaunch.cfg to reflect the new name and the old name was not in there anymore. I believe that is why it went purple. Did you change the name of the script in clientlaunch.cfg? Yes What if you run the script manually as the xymon user, does that appear at the server? No Do you see any anominalies under the xymond page of the xymon server? No Are other tests from that xymon client working? Yes
▸
From: Phil Crooker [mailto:user-e8e31cd73303@xymon.invalid]
Sent: Thursday, February 13, 2014 6:04 PM
To: Hewitt, Lenny; 'xymon at xymon.com'
Subject: RE: Cannot get custom script column back.
From: Xymon on behalf of Hewitt, Lenny
Sent: Thursday, 13 February 2014 5:13 AM
To: 'xymon at xymon.com'
Subject: [Xymon] Cannot get custom script column back.
Hi,
I'm having problems with how xymon is reporting a status and wanted to give you a step-by-step detailed description of what I did to get in the state that it is in so that it will hopefully describe what to do to fix this anomally.
I set up a custom script to monitor the status of process, more than just monitoring to see if the daemon is up or down, etc, etc. In testing the script I used the example of the client-side script on my client. I created the script on the clients and everything showed up on the xymon webpage and worked perfectly. I then realized that I wanted to rename the script on the client to something better describing it. So I proceeded to rename the script and update the clientlaunch.cfg in etc on each client to reflect the new name. After a short period the column on the xymon website showing the status of the original name of the script went purple because that script name was not reporting anymore. I removed this purple column by running xymon 127.0.0.1 "drop <HOSTNAME> <columname>". The problem is I can't get the column to show back up again with the status from the newly named script that is currently configured. The names of the columns were the same, just the script name changed. I suspect that is why it is behaving this way but don't know what to do to fix this state that it's in.
Any help would be greatly appreciated.
Lenny
The name of the script wouldn't affect the test status if the renamed script is still running, it should not have gone purple. Did you change the name of the script in clientlaunch.cfg? What if you run the script manually as the xymon user, does that appear at the server? Are you sure the script is actually running and the client is sending the results to the server - try running tcpdump to capture that traffic. Do you see any anominalies under the xymond page of the xymon server? Are other tests from that xymon client working?
cheers, Phil
--Please consider the environment before printing this e-mail This message from ORIX Australia may contain confidential and/or privileged information. If you are not the intended recipient, any use, disclosure or copying of this message (or of any attachments to it) is not authorised. If you have received this message in error, please notify the sender immediately and delete the message and any attachments from your system. Please inform the sender if you do not wish to receive further communications by email. ORIX handles personal information according to a Privacy Policy that is consistent with the National Privacy Principles. Please let us know if you would like a copy. It is also available at http://www.orix.com.au
list Lenny Hewitt
Never mind I found it. I made an error in my puppet configuration that was overwriting the file with the wrong script. Doh! Thanks, Lenny
▸
From: Phil Crooker [mailto:user-e8e31cd73303@xymon.invalid] Sent: Thursday, February 13, 2014 6:04 PM To: Hewitt, Lenny; 'xymon at xymon.com' Subject: RE: Cannot get custom script column back. From: Xymon on behalf of Hewitt, Lenny Sent: Thursday, 13 February 2014 5:13 AM To: 'xymon at xymon.com' Subject: [Xymon] Cannot get custom script column back. Hi, I'm having problems with how xymon is reporting a status and wanted to give you a step-by-step detailed description of what I did to get in the state that it is in so that it will hopefully describe what to do to fix this anomally. I set up a custom script to monitor the status of process, more than just monitoring to see if the daemon is up or down, etc, etc. In testing the script I used the example of the client-side script on my client. I created the script on the clients and everything showed up on the xymon webpage and worked perfectly. I then realized that I wanted to rename the script on the client to something better describing it. So I proceeded to rename the script and update the clientlaunch.cfg in etc on each client to reflect the new name. After a short period the column on the xymon website showing the status of the original name of the script went purple because that script name was not reporting anymore. I removed this purple column by running xymon 127.0.0.1 "drop <HOSTNAME> <columname>". The problem is I can't get the column to show back up again with the status from the newly named script that is currently configured. The names of the columns were the same, just the script name changed. I suspect that is why it is behaving this way but don't know what to do to fix this state that it's in. Any help would be greatly appreciated. Lenny The name of the script wouldn't affect the test status if the renamed script is still running, it should not have gone purple. Did you change the name of the script in clientlaunch.cfg? What if you run the script manually as the xymon user, does that appear at the server? Are you sure the script is actually running and the client is sending the results to the server - try running tcpdump to capture that traffic. Do you see any anominalies under the xymond page of the xymon server? Are other tests from that xymon client working? cheers, Phil -- Please consider the environment before printing this e-mail This message from ORIX Australia may contain confidential and/or privileged information. If you are not the intended recipient, any use, disclosure or copying of this message (or of any attachments to it) is not authorised. If you have received this message in error, please notify the sender immediately and delete the message and any attachments from your system. Please inform the sender if you do not wish to receive further communications by email. ORIX handles personal information according to a Privacy Policy that is consistent with the National Privacy Principles. Please let us know if you would like a copy. It is also available at http://www.orix.com.au
list Jeremy Laidman
▸
On 13 February 2014 03:34, Hewitt, Lenny <user-e5be3ca8ee9a@xymon.invalid> wrote:
describing it. So I proceeded to rename the script and update the clientlaunch.cfg in etc on each client to reflect the new name. After a short period the column on the xymon website showing the status of the original name of the script went purple because that script name was not reporting
Check the xymonlaunch.log file to see if it's not being launched for some reason. J