So I did a test on a Windows 11 host machine that's local to the Xymon Server instead of outside the network.? The host has been using the regular HTTP method (port 1984) successfully for a long time without any problems.
Here's the redacted xymonclient_config.xml it uses that works fine.
<XymonSettings> ? <servers>REDACTED.REDACTED.com</servers> ? <clientlogfile>c:\program files\xymon\xymonclient.log</clientlogfile> ? <clientconfigfile>c:\program files\xymon\clientconfig.cfg</clientconfigfile> ? <clientfqdn>0</clientfqdn> ? <clientlower>0</clientlower> ? <wanteddisks>2 3 4</wanteddisks> ? <clientremotecfgexec>1</clientremotecfgexec> </XymonSettings>
I then edited the xymonclient_config.xml to use HTTPS and restarted the XymonPSClient service.? The 'CPU' graphs stopped populating and the 'Files' tests that previously worked fine all now say 'Could not determine size of directory'. Here's the HTTPS (port 443) config.
<XymonSettings> <serverUrl>https://REDACTED.REDACTED.com/xymon-cgi/xymoncgimsg.cgi</serverUrl> ? <serverHttpUsername>REDACTED</serverHttpUsername> ? <serverHttpPassword>REDACTED</serverHttpPassword> ? <clientlogfile>c:\program files\xymon\xymonclient.log</clientlogfile> ? <clientconfigfile>c:\program files\xymon\clientconfig.cfg</clientconfigfile> ? <clientfqdn>0</clientfqdn> ? <clientlower>0</clientlower> ? <wanteddisks>2 3 4</wanteddisks> ? <clientremotecfgexec>1</clientremotecfgexec> </XymonSettings>
I feel like anyone can easily reproduce this issue. I would appreciate it if anyone could give me a clue as to how to resolve this. I've also been working with ChatGPT to resolve this issue, but none of the suggestions it's offered have resolved the issue, and it's advising the Xymon community will be able to help better. :-)
Kris Springer
On 1/26/24 9:17 AM, Kris Springer wrote:
I increased the following values on the server, then rebooted, but it didn't result in any change with this issue.
MAXMSG_CLIENT=25600 MAXMSG_STATUS=25600 MAXMSG_DATA=25600
Kris Springer
On 1/25/24 16:15, J.C. Cleaver wrote:
It really should be seeing it the same way, as apache is handing off to the CGI after terminating the SSL, and the clientlog data will be whatever xymond received from the cgi, not the incoming web connection.
The next step would probably be enabling debug on xymond_client to see how it's processing the two different hosts. Are *any* of the client tests being created properly for the ones over https?
-jc
On Thu, January 25, 2024 15:07, Kris Springer wrote:
The clientlog looks to be making it into the server completely.?? It appears mostly identical except the https version contains the url and user/pass info at the bottom.
Could this issue be with the xymoncgimsg.cgi not processing the data correctly somehow?
Kris Springer
On 1/25/24 15:54, J.C. Cleaver wrote:
Are the outputs of the clientlog otherwise identical for the system between the http and https submissions?
Off the top of my head, the only thing I think would cause this on the server side would be a permanently/consistently truncated client report, causing the load not be scanned for hostsvc.test status generation.
-jc
On Thu, January 25, 2024 14:50, Kris Springer wrote:
Additional info: I just realized the 'files' test that I have defined to check a few Windows folders also is not working either when using the https method.???? The defined Windows folders are read and appear in the 'clientlog', but the Server's webpage says 'Could not determine size of directory', probably because there are no 'filesizes' rrd's being created.???? When the client sends over http the rrd's are created and the folders graph just fine on the server.
Kris Springer
On 1/25/24 15:19, Kris Springer wrote:
I'm using the XymonPSClient 2.42 on a Windows server, and all works fine except when I choose to send the data from the client to the server over https the CPU graph doesn't display on the server side. If I change the XymonPSClient to send over http the CPU graph displays correctly.???? I've tried this on different hosts and results are always the same when using https.???? Server is v4.3.30, but it was happening on an older version too.???? Can anyone give me a clue how to resolve this??? There's no errors happening that I can see anywhere. I looked in the rrd folder and there is no 'cpu' or 'la' rrd file being created for the hosts that use the XymonPSClient over https.
Thanks, Kris Springer
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon