- Joined
- Aug 28, 2010
- Messages
- 150
try to connect but it's not connecting, is there any maintenance going on?
TS is down!
- Thread starter GunshipSoldier
- Start date
- Joined
- Jan 13, 2013
- Messages
- 5,996
confirmed down.
Sent by Tapatalk carrier pigeon via Nexus 5.
Sent by Tapatalk carrier pigeon via Nexus 5.
- Joined
- Jan 2, 2008
- Messages
- 26,333
- Age
- 38
They emailed saying our box running procon and ts would go down early morning
Due to a recently identified serious security concern, we will need to reboot most of the machines hosting our VDSes early on September 30. These reboots will begin at 11pm PDT / midnight MDT / 1am CDT / 2am EDT / 08:00 CEST, occurring at different times for each timezone as we handle them individually (starting with our Frankfurt machines and then moving west to the NYC machines and so on). We expect all reboots to be finished by approximately 3am PDT.
For the reboot, your VDS will need to be shut down for approximately 15-30 minutes. We will attempt to gracefully shut it down on our end through Xen, but sometimes this doesn't work perfectly, so we advise that you turn off unnecessary applications that might write to disk before the maintenance event, if possible. We also recommend backing up critical files, just to be safe in the case of a problem with the machine post-boot.
Also, please note that Windows 2012 R2 has a bug that causes it to sometimes not boot properly, then go to a recovery screen. If you are running a Windows 2012 R2-based VDS, you may need to log in with the VNC console to check for a recovery message and cancel out of it to try again. Eventually the OS will boot properly, and there are no further symptoms after the boot succeeds.
Due to a recently identified serious security concern, we will need to reboot most of the machines hosting our VDSes early on September 30. These reboots will begin at 11pm PDT / midnight MDT / 1am CDT / 2am EDT / 08:00 CEST, occurring at different times for each timezone as we handle them individually (starting with our Frankfurt machines and then moving west to the NYC machines and so on). We expect all reboots to be finished by approximately 3am PDT.
For the reboot, your VDS will need to be shut down for approximately 15-30 minutes. We will attempt to gracefully shut it down on our end through Xen, but sometimes this doesn't work perfectly, so we advise that you turn off unnecessary applications that might write to disk before the maintenance event, if possible. We also recommend backing up critical files, just to be safe in the case of a problem with the machine post-boot.
Also, please note that Windows 2012 R2 has a bug that causes it to sometimes not boot properly, then go to a recovery screen. If you are running a Windows 2012 R2-based VDS, you may need to log in with the VNC console to check for a recovery message and cancel out of it to try again. Eventually the OS will boot properly, and there are no further symptoms after the boot succeeds.
- Joined
- Mar 6, 2011
- Messages
- 8,654
Except for it never came up fast. I had to manually start the process. The box actually had an error message over the login screen stating that some processes had failed to start.
Pretty much happens every reboot. It's alright install .Net 4.0 and watch how ALL services fail. Love windows 2003 and or whatever the hell is wrong with that server.
I actually have serious issues with NFO's Window's VPS's. They don't have up to date drivers and the host machines aren't up to date on patches. I can crash the machine just by doing a large file transfer.
Pretty much happens every reboot. It's alright install .Net 4.0 and watch how ALL services fail. Love windows 2003 and or whatever the hell is wrong with that server.
I actually have serious issues with NFO's Window's VPS's. They don't have up to date drivers and the host machines aren't up to date on patches. I can crash the machine just by doing a large file transfer.