Someone is causing wincf to use so much cpu on a process that it is taking 15 minutes to even open the command prompt. We are working on this now.
Deepak resolved this about 10 minutes after I posted. We have monitored and it has run well since checking the backups and restarting the CF services
We have performed major Service Pack updates on WinCF and the server is going to have to be taken down for about 25 minutes.
This will be done in about 2 hours from now
We apologise for the inconvenience and are working hard to permanently resolve all WinCF issues
20 minutes before maintenance…
WinCF is having intermitten downtime issues after the reboot.. We believe they are OS related.
The next 40 minutes we are going to try troubleshooting them. If that fails, we will proceed with an OS reinstallation.
WinCF’s OS has been giving us continuous issues since December, but we have managed to avoid a system reinstall. However this seems necessary. We’d be able to double the RAM with a reinstall.
If we go for a reinstall, the effective downtime would be apprximately 3 to 4 hours. We plan to compensate affected customers under our SLA.
We apologise for some of the issues WinCF has been facing. After this reinstall, we expect it to be rock solid
Reinstallation has begun..
We expect the restoration process to be completed by 2PM EST.
We are hoping to finish it much sooner… While the OS installation has been completed.. Hardware issues on the existing WinCF have complicated issues.. We are now swapping hardware
The WinCF restoration is entering its final stages, we see services being up within 2 hours. Along with the reinstall of the OS, we have been able to isolate and solve a number of small issues that customers have been complaining about on WinCF.
We’ve upgraded ColdFusion MX 6.1 on WinCF to the next minor version. As a result, a large number of DSNs are no longer being recognised by ColdFusion despite our efforts to restore them from backup. We will need to manually recreate most DSNs. We request customers to submit tickets with their WinCF DSN details so we can setup your DSNs ahead of the completion of the restoration
It is currently 1:30PM EST.
The HSphere Recreation tool has been running for 3 hours, and is running much slower than our expectations and all our experience in the last 3 years. This is first time however we are recovering an all-CF server and the extra time could be due to the large number of ColdFusion extensions it has to install individually on each site, apart from recreating users, directories, etc.
At the moment, I am expecting to to take at the very most 3.5 more hours. So I’m going to have to revise the estimated restoration time to 5AM EST, today.
I apologise for the delay and the incorrect ETA given earlier. Once the Resource Recreator finishes, we’d be able to put sites up within a matter of 15 minutes.
This is the first crash WinCF has faced in 2 years. We apologise for the issue. As most of you know, WinCF hasn’t been performing at its best recently, and we had planned to migrate WinCF to a new server which was scheduled for early next month. However, with this reinstallation, we are confident the server will be stable and deliver near 100% uptime
Futher updates can be found here: http://support.jodohost.com/showthread.php?p=38285#post38285
A large number of sites are already up, however some continue to remain down to permission issues. A permission script is running to correct these sites and from this moment, we expect it to take no longer than 120 minutes to finish