
Originally Posted by
ccmpj806
eUKhost staff offered to add free monitoring to my VPS (via watch.eukhost.com), when there was a recent issue with another VPS on the same node taking down the whole node.
Great, I thought. However, not.
After literally hundreds of emails reporting that the snmp service is offline and the failure to resolve the issue, I requested that the monitoring service be disabled. I thought that this would just mean that the service at watch.eukhost.com would be disabled and stop sending me alerts that the snmp service was offline.
This is not what happened.
I received an email at about 01:30 this morning telling me that changes had been made on the server and I would stop receiving the emails. I had no further email after this point. Good, I thought, so a little earlier I just logged into watch.eukhost.com to see what the status was. The server was being reported as dead - I just assumed that was because monitoring was disabled. The thought also crossed my mind that maybe the firewall on the server was blocking the monitoring service, so I quickly logged into WHM to check.
My firewall service was disabled!!!! Not only that, but the services that I had set up as being monitored locally (and if required, restarted), had their monitoring disabled.
It may have been as a result of the several server restarts (some carried out in the middle of the UK working day - I know as I was using the server at the time when it just disappeared), that the FTP service that I had disabled was also running and I could see in the logs that there had been a login. However, I couldn't see much more as there are no log entries in messages, cron, or secure since about 02:00 this morning.
Can someone please let me know what has been going on? I am getting very little feedback from the ticket system.
Up until now, I have had exemplary technical support for my VPS. What is going on?
**Update**
I have just restarted the system logger, which had been disabled and I immediately get a report that the watch.eukhost.com ip had been blocked via the SSH port.
Jason.