Henrik,
I applied the patch on my test machine that has not pbl => all continues to run well
I applied the patch on the machine with the 100%CPU issue. I get the same behaviour, the content of the xymonproxy.log is the following lines looping:
1166 2014-01-28 18:09:00 state 0: reading from client
1166 2014-01-28 18:09:00 state 1: reading from client
1166 2014-01-28 18:09:00 state 2: request combining
1166 2014-01-28 18:09:00 state 3: sending to server
1166 2014-01-28 18:09:00 state 4: reading from client
2014-01-28 18:09:00 select() failed: Invalid argument
Could the issue come from the fact that le @IP of the machine in the DNS is associated with 2 hostnames (not alias) ?
Cordialement, Regards,Mit freundlichen Grüßen,
Gautier BEGIN
System Tools Team Lead
CACEIS and APERAM accounts
CSC Computer Sciences Luxembourg S.A.
12D Impasse Drosbach
L-1882 Luxembourg
Global Outsourcing Service | p:+352 24 834 276 | m:+352 621 229 172 | user-083785ae1711@xymon.invalid | www.csc.com
CSC • This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose
• CSC Computer Sciences SAS • Registered Office: Immeuble Le Balzac, 10 Place des Vosges, 92072 Paris La Défense Cedex, France • Registered in France: RCS Nanterre B 315 268 664
From: user-ce4a2c883f75@xymon.invalid
To: <xymon at xymon.com>
Date: 01/20/2014 11:42 AM
Subject: Re: [Xymon] xymonproxy perf issue
Sent by: "Xymon" <xymon-bounces at xymon.com>
Den 17.01.2014 16:14, Gautier Begin skrev:
Could it comes from how the xymonproxy program handles the MACHINE variable ?
I say that because when the process becomes nuts, he makes only 'gettimer' action. Then I have a look in the source file and found this line (line 452) that could correspond:
if (proxyname && ((now = gettimer()) >= (laststatus+300))) {
[snip]
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 suspect some kind of error happened with the network socket handling. Could you add this patch and try to reproduce the problem? It doesn't change the behaviour, but it does add some error-reporting in case the core select() call fails.
Regards,
Henrik
[attachment "proxyerror.diff" deleted by Gautier Begin/LUX/CSC]