Henrik,
I managed to reproduce the issue:
- I start the XYMON as a proxy server => Non pbl
- Stop the XYMON => Process remains alive (xymonlaunch)
- Kill the xymonlaunch
- Start the XYMON as aproxy server => The pbl occurs again
Could some files in the ./tmp of XYMON influence this ?
Cordialement, Regards,Mit freundlichen Grüßen,
Gautier BEGIN
From: user-ce4a2c883f75@xymon.invalid
To: <xymon at xymon.com>
Date: 01/14/2014 03:00 PM
Subject: Re: [Xymon] xymonproxy perf issue
Sent by: "Xymon" <xymon-bounces at xymon.com>
Den 14.01.2014 14:23, Gautier Begin skrev:
Last Sunday, I wanted to start a xymonproxy (vers 4.3.12) on a Solaris 10.5 with 900 targets . I had a performance issue: - The xymonproxy process used 100% of only one CPU (no multithread seen).
- On the main XYMON server, data from this proxy (I have one other on Ubuntu with 50 targets working fine) came with difficulties (delays and lacks).
I tried to used the -lqueue option for the proxy with no success. Nothing special seen in any logs. The UNIX admin said me that the xymonproxy was just making 'time()' command all the time.
I've had the proxy handling about 5000 hosts simultaneously. On Linux, though.
I have not heard of such behaviour before, and I am sure there must be others running the proxy on Solaris in a similar setup. If you can make it happen again, please do a "kill -USR2" on the xymonproxy process to toggle debugging on/off.
None of the Xymon tools are multithreaded - so far I have stuck to the traditional Unix way of doing things.
Regards,
Henrik