Hi Hugo, I hope you can help me with this issue. Ever since I updated to monitor 1.3 and now to 1.4 the monitor can no longer fetch the logs.
When I run it in debug in shell I get: ""Error while getting statistics logfile index from webserver"
I added debug outputs so I can see it calls the server on port 80 and it gets back a status 0. It runs for about 1-2 minutes before giving the error so it does fill like a timeout.
Both monitor and actual server are on the same IP address and I've set the MonitorServer=IP in the config as required. When I try to load the IP:port in my browser it loads just fine.
Any advice on how I can debug or resolve it?
Thanks!
Hugo Leisink
11 February 2016, 14:02
Did you do a database update via the /setup page?
Gilad
11 February 2016, 14:16
Yes I did. The CMS and Monitor site itself loads great and are fully functional but with no data. The problem is in the /database/fetch_webserver_logs call which fails with the above information.
Hugo Leisink
11 February 2016, 14:19
Weird. What is the content of the $result record at line 311? Please add the following line right after that and rerun:
print_r($result);
Gilad
11 February 2016, 14:38
It's super strange and I can't figure it out. Result is:
Array ( [status] => 0 [headers] => Array ( )
[body] => )
Hugo Leisink
11 February 2016, 14:39
Super strange indeed. Is it possible I get access to the server to do some debugging?
Gilad
11 February 2016, 14:52
I'll need to check as it holds customer data and I need their approval.
I just printed the headers - they are empty as well. It is as if it times out on the hiawatha server for some reason.
Is there any issue with running both Hiawatha and the monitor on the same machine? Any special configs needed to do that? Does it matter which sites sits on the IP host name (as the default site)?
Hugo Leisink
11 February 2016, 14:53
No, I have the Monitor running on my main server as well.