Search results

After blocking 5 key attacking IPs the server is up and running well now for some time.

Seems there is a website under a large attack, working to block it and restore access to the server.

We're checking an issue on win40 that has it unresponsive at the moment.

We found some websites had their config file named as config.config which was making some sites down. It was resolved a bit later.

Please follow updates at Facebook: https://www.facebook.com/JodoHost/

We're seeing pings working quite well, but network traffic is crawling. We are checking for any possible issue or attack maybe causing this right now.

All maintenance completed.

one node is complete now and VMs back up in 19 min on that node, others still running.

All nodes are in the windows pre-reboot updating/restart process at this time now. VMs may be shut down for the proper reboot at any point now.

Due to some major storms rolling in while I was driving to Dallas, this had almost a 2 hours delay to start but we left enough room in the schedule it should still be completed within announced times.

We will be performing windows updates and regular maintenance on nodes starting at 9PM and going until 4 am Sunday morning. During this time there may be a handful of reboots on the client virtual machines as well. there will be downtime caused by this maintenance anywhere from 20 minutes to an...

The server is all up, for about 30 minutes now.

We're checking WIN14 now as it was given what was supposed to be a quick and routine reboot after critical windows updates to address recent major security patches, and it is not wanting to boot into windows properly now. We are trying to get it up without a rollback/restore of the OS since...

The server has been up for quite a while now just checking it out further with it up and going!

The win11 server on Cluster2 is being checked, not working at the moment.

Oh forgotton update we had things resolved about 15 minutes later on all

The iSCSI service has stopped responding on a couple nodes linked to SAN backed, we're having to reboot servers utilizing those services.

We're having to reboot the node now to resolve this matter. So other VMs will be impacted again.

All but web9 cl2 are back up and running now, and we're still checking into it.

We will be performing maintenance tasks on the database and the server both for CL2 Control Panel. These will be done as routine maintenance to optimize the database as it's gotten a bit slow this week, as well as server maintenance to do routine maintenance on the server. The window is large...