xymonnet runtime long on ping tests results sent
list Michael Baydoun
What could cause a very long time to send ping test results? PING test completed (166 hosts) 593954.047266 9.117369 PING test results sent 594410.634681 456.587415
list Henrik Størner
▸
On 30-04-2012 16:13, Michael Baydoun wrote:
What could cause a very long time to send ping test results? PING test completed (166 hosts) 593954.047266 9.117369 PING test results sent 594410.634681 456.587415
Usually a network problem between the host doing the network tests, and the Xymon server - if those are two different systems. If you're running the network tests on the Xymon server itself, then I have no idea why that would take so long. Regards, Henrik
list Michael Baydoun
The tests are running on the xymon server itself Somehow, 6 days ago, the xymon server processes were starting using root (even though that would seem to be impossible, as there is a username check in /usr/lib64/xymon/server/hobbit.sh). The OS was patched around that time. That was causing histlog files to be created with root ownership and mode 600, preventing accessing those details from the web gui. I killed all the xymon processes and restarted (service xymon start), which started them up correctly as user xymon However, once I did that, the Ping test results all started failing, even though fping from the command line to the clients was working correctly, and xymonnet went yellow with the long run time warning. Eventually, to get the ping tests working again for now I had to bypass the username check in /usr/lib64/xymon/server/hobbit.sh and start everything back up as the root user I will have to find a time to switch it back to the xymon user, figure out the ping test failures, and correct all the histlog file permissions.
▸
On Mon, Apr 30, 2012 at 12:36 PM, Henrik Størner <user-ce4a2c883f75@xymon.invalid> wrote:
On 30-04-2012 16:13, Michael Baydoun wrote:What could cause a very long time to send ping test results? PING test completed (166 hosts) 593954.047266 9.117369 PING test results sent 594410.634681 456.587415Usually a network problem between the host doing the network tests, and the Xymon server - if those are two different systems. If you're running the network tests on the Xymon server itself, then I have no idea why that would take so long. Regards, Henrik ______________________________**
Xymon at xymon.com<
list Michael Baydoun
▸
On Mon, Apr 30, 2012 at 1:10 PM, Michael Baydoun <user-105c655da53d@xymon.invalid>wrote:
The tests are running on the xymon server itself Somehow, 6 days ago, the xymon server processes were starting using root (even though that would seem to be impossible, as there is a username check in /usr/lib64/xymon/server/hobbit.sh). The OS was patched around that time. That was causing histlog files to be created with root ownership and mode 600, preventing accessing those details from the web gui. I killed all the xymon processes and restarted (service xymon start), which started them up correctly as user xymon However, once I did that, the Ping test results all started failing, even though fping from the command line to the clients was working correctly, and xymonnet went yellow with the long run time warning. Eventually, to get the ping tests working again for now I had to bypass the username check in /usr/lib64/xymon/server/hobbit.sh and start everything back up as the root user I will have to find a time to switch it back to the xymon user, figure out the ping test failures, and correct all the histlog file permissions. On Mon, Apr 30, 2012 at 12:36 PM, Henrik Størner <user-ce4a2c883f75@xymon.invalid> wrote:On 30-04-2012 16:13, Michael Baydoun wrote:What could cause a very long time to send ping test results? PING test completed (166 hosts) 593954.047266 9.117369 PING test results sent 594410.634681 456.587415Usually a network problem between the host doing the network tests, and the Xymon server - if those are two different systems. If you're running the network tests on the Xymon server itself, then I have no idea why that would take so long. Regards, Henrik ______________________________** Xymon at xymon.com<
To followup, I figured out this issue. The ownership of /usr/lib64/xymon/server/bin/xymonping was changed at some point, which clears the set-uid. Setting owner to root first, then chmod 4755 resolved the issue.