Yes, it was from the same host...
...for my current workaround I just modified the Request-Portion in the Settings of the NetworkService-Object by appending the filename of the aforementioned txt-file:
Doens't work: host.domain.tld:/
Workaround: host.domain.tld:/test.txt
Hi,
I've jsut upgraded from 4.2 to 4.4, thus implicitly migrating from PortCheck to NetSVC.
One of my HTTPS-WebService-Objects went into (and stayed in) status CRITICAL.
Multiple other HTTPS-WebService-Objects are absolutely fine (status NORMAL), even the other one on the same Web-Server...
...I think, it might be related to the Size of the actual Reply of queried WebService (446238 Bytes for the failed case).
I created a nearly empty text-file "test.txt" on the Web-Server (with content "success") for the HTTPS-WebService-Object to query, which succeeded with the check and the status changed back to NORMAL.
Is there such a limitations with NetSVC?
Best regards,
Manuel Schneider
PS.: Please find an excerpt of nxagent-LOG with debug level 9 in the attachments, as well as the output of "curl --head" for the same WebService.
