ofir
-
Joined
-
Last visited
Posts posted by ofir
-
-
-
-
-
-
That's strange.
Just to rule out any local issues:
- Kill the web server on 443
- Make it listen on port 80
- Start the web server again
- Check the logs and make sure there are no issues
- Do a telnet localhost 80 to be sure that the port is open
- Change pcmonitor to monitor port 80
- Check if port is correctly displayed as open.
- Change pcmonitor to monitor website on localhost port 80
- Check if webpage response is 200
- If everything ok change the web server to port 443 and repeat these steps.
Regards,
Mark
I've done all that - on 3 Macs - still doesn't work and now my demo has run out. The web servers I tried all work perfectly and respond to other monitoring software. This looks like a bug. I also haven't had any response regarding the Mac update. As it stands the Mac version is seriously lacking in features and in my case, doesn't really work.
Not sure how to proceed now, I was pretty excited a month ago…
-
Hi,
According to your log looks like you have some local issues:
servermgrd[70165]: Got error -9805 for SSLHandshake remote address is 127.0.0.1:44765Server[39262]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9812)servermgrd[70165]: Exception in SessionController threadListen: Socket: Connect failedcom.mobilepcmonitor.PCMonitorHelper[8566]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9812)PCMonitorHelper[8566]: --> port:443 on hostname:localhost is closedpcmonitor throw same kCFStreamErrorDomainSSL error like servermgrd(ServerAdmin) and Server processes. Port monitor corectly response back with "close" port status.Can you, please send us screenshots (from mobile device) with port monitor and web site monitor ?Regards,MarkNo local issues, the server works fine. It uses a self generated SSL certificate, but the same test on a 'proper' SSL certificate also fails.
https://www.dropbox.com/s/xo54ev2qio1azx0/IMG_4312.PNG
https://www.dropbox.com/s/uc7g7c5sz3wajqg/IMG_4311.PNG
You also see that the 2nd web test fails in a different way. By the way, the reason it's localhost in one and odmaster.iefiles.co.uk in the other is because I tried both options. The results were the same.
-
Sorry about the duplication: OK, here's the log: https://www.dropbox....98uu/system.log
This is happening on all the systems I tried.
-
Quitting PC Monitor fixed the authentication issue. The ports still report as down.
OK, here's the log: https://www.dropbox.com/s/5seyt6tf6sc98uu/system.log
Thanks
-
-
Hi again
My demo is about to run out and I still have not been able to get port monitoring to work on the Mac. I was hoping the new Mac version you mention will be released before my demo runs out. Right now the Mac version is like a Lite version when compared to the PC one. Any thoughts on this? Could you extend the demo and add more systems than 5?
-
-
-
The Mac agent has the same priority for us as the Windows and Linux agents.
We just completed version 4.3 of Mac agent with a new monitoring engine and we plan to release it in 2-3 weeks.
As for server modules, we have no plans to add Microsoft IIS, Exchange, AD and the rest for the Mac.
I understand. Would be nice to see the Mac server equivalents of IIS, AD supported via modules - monitor BIND, Apache, SQL (Post and My), OpenDirectory, DHCP, VPN, etc.
I can't find process monitoring in the Mac version either.
-
-
-
I setup port monitors on Mac for port 443 (web server) and ports 4280 (CrashPlan).
https://www.dropbox.com/s/ogn71zdbyqnjiz4/Screen%20Shot%202014-03-26%20at%2023.58.38.PNG
-
-
-
I setup port monitoring on port 443 localhost and I get a red blob.
Web monitoring works on same.
PulseWay Helper Crashing Constantly
in Bugs
Any news? We are coming up to 3 months where Pulseway has been useless, I now have a filter to delete all the alerts because I get 100 a day.