MonsterMegs - Notice history

The issue with the Hurricane server has been resolved and all services are running as normal. If you are still facing issues, please submit a ticket to our Support department.

We have heard back from the billing department and have confirmed that it is indeed a billing malfunction on their end. While they wait for certain billing staff to be available, they have issued emergency licenses for all servers for temporary reactivation. Once the appropriate staff is available, this should be resolved swiftly and we do not anticipate any further access issues.

Cpanel response:

"Thank you for contacting cPanel Customer Support! I hope this communication finds you well!
 
This month there was a billing issue causing some customers who had already paid for the month of August to be suspended. I am the only one in the office today, and I have asked my team if anyone can help out. In the meantime, I am working on these concerns in the order that they come in.
 
I do not want you to be further affected by this so, while I am in the process of working through these requests, I have activated emergency cPanel licenses on the following IP(s): "

The drive and the maintenance has been completed.

The motherboard and memory have been replaced. The server is now back online. With all new hardware except for the hard drives. This should resolve the reboot issues. So we are gonna consider this closed.

There have been a few random reboots, but not quite as frequently as they were. Since this is still ongoing, the datacenter is going to replace the memory and motherboard, that we have replaced all components with new ones.

The server is going offline now and is expected to be down for about 30-60 minutes. We will update when the server is back online.

We are monitoring the server for random reboots to track down the cause. There may be short interruptions though out the day as we attempt to capture logs on the random reboots.

The server seems to be stable at this time. We will reopen this incident if there are any further issues.

Upon a kernel crash, the server did not come up properly. We initiated a manual reboot and now the server is back online. We will monitor closely and update if there are any further issues.

We are gonna close this incident for now. Meanwhile we will monitor the server closely and if any further issues arrive, we will once again reopen it with additional updates.

The cpu has been replaced and we will continue to monitor closely to watch for any further reboots.

Well the server was running fine for about 1 1/2 hours with no reboots and then the issued returned. We are gonna try to swap out the cpu and hopefully this resolves the problem. If that does not work, the last resort would be to change out the chassis completely.

The server will be going down in about 5 minutes to replace the cpu.

It appears the PSU replacement did the trick and the server is no longer rebooting every few minutes. We will continue to monitor closely over the next few hours and will reopen this incident if the issue arises again.

The Power supply has been replaced and the server is back online. We are going to monitor closely for any further repeated reboots over the next couple hours.

In talks with the datacenter, it appears that the power supply may have become faulty. They are going to take the server down and replace the power supply.

We are working out an issue with repeated reboots on the server. We will update when we have more information.