Check out what is happening with the servers!
 #158927  by jawfin
 
From NFO
Upstream problem wrote:
Our connections to Internap in Dallas appear to have gone down at approximately 1:37am CDT. We contacted Internap and they told us that there is a maintenance going on at the location that should not have impacted us (only one of our two links to Internap should be offline). We are currently waiting for their maintenance to complete and will continue to follow up with them afterward to ensure that this won't happen again in a later maintenance event of theirs.
 #162361  by HolyWarrior
 
KR2 down ? I input the correct IP displayed you have on forums for the second server and it's not showing up. Prim was going to have trials there. Thought of heading off to watch it. Hope it gets fixed soon. I may have missed it.
 #162369  by jawfin
 
HolyWarrior wrote:KR2 down ? I input the correct IP displayed you have on forums for the second server and it's not showing up. Prim was going to have trials there. Thought of heading off to watch it. Hope it gets fixed soon. I may have missed it.
It's the same IP as the public server; it's on a different port.
/connect 192.223.29.244:29071
If you found a different IP in a post somewhere please let us know where so we can correct it, thanks.
 #162375  by Primordial
 
HolyWarrior wrote:KR2 down ? I input the correct IP displayed you have on forums for the second server and it's not showing up. Prim was going to have trials there. Thought of heading off to watch it. Hope it gets fixed soon. I may have missed it.
You missed me :/ I got Jedi though <3
 #163100  by Lurch
 
It would be nice if they gave advanced notice that they will be doing that. Or did they?
 #163101  by jawfin
 
It was me, well, not me per se but the script which drives the server.
In it there is a routine to delete temporary files in cleaning up, but somehow a temporary file got read-only access so the script was waiting on a prompt to delete a read-only file. I fixed the script to delete regardless and re-ran the game.
 #163105  by John
 
Jawfin the scripter! :o
 #163863  by Sakito
 
Servers are down btw :o someone please save it XD
 #163865  by jawfin
 
The virtual machine got paused. Nothing we did, and no event recorded by nfo of work done by them, so before I bring it up I just want to confirm with them that it is healthy!

Edit: Seems all good, attempting to restore.

Edit: Edit: Up and running. nfo says probably a glitch in the virtual machine manager. Rebooted and all good :)
 #163866  by g0dchris
 
Another evidence that rebooting a system can solve every problem. : >
Hooray to our emporer!
 #165154  by jawfin
 
Das Wolf wrote:Server seems to be down
Is this post still relevant for you, because it's not down - 18 people on right now!
 #165155  by Das Wolf
 
Yeah I get an infinite await connection, but can connect to other servers. Not sure if it’s on my end
 #165156  by jawfin
 
Its case its a firewall rule that's blocking your connection packets (there are a few rules to block application specific DOS) I've added your IP to the WhiteList. So if you can connect now it's possible that your client mimics a software DOS.
 #165159  by jawfin
 
OK, so I've stuck your white-listed IP higher in the chain than the software firewall rules - so if your IP changes this may become an issue for you again - if so just post and I'll sort it :)
 #166344  by jawfin
 
The whole VM is dead, both servers are out and no rcon - so waiting for nfo to solve - unknown how long.

Edit: From their Event Log support page
All of our equipment except for our core router in Dallas is currently offline. We are currently investigating why this is; it may be a failed PDU or failed switch. We will continue to work to bring everything back up ASAP.

Update @ 9:16pm CDT: We submitted a ticket with the facility prior to posting the original event. We continue to wait for them to call us back. We will quickly know more about the culprit and be able to proceed in restoring services after they call us.
 #166345  by HiddenSpy
 
WHAT? Well that's a bummer. I had free time tonight too. You can use my server as a backup place to meet if you want, I only use it to test my mods. I don't recruit or anything. Just a server. 67.231.246.10:29070
 #166353  by Glenhal
 
@Hiddenspy "WHAT? Well that's a bummer. I had free time tonight too. You can use my server as a backup place to meet if you want, I only use it to test my mods. I don't recruit or anything. Just a server. [Censure]"

Sorry, but you can't post your ip server on our forum, that's could insist new player to come at your server
 #166461  by jawfin
 
Message from NFO: -

We are planning to reboot the machine hosting your VDS at approximately 1:30am Central Time on June 20, in order to apply critical Intel microcode and Xen updates to address a new speculation-related vulnerability (Microarchitectural Data Sampling/MDS).

We have generally avoided the need for reboots over the last couple of years by invisibly using the Xen livepatching functionality to update running code. Because this specific new flaw requires the application of updated microcode at boot-time, and because its Xen code updates cannot be patched into a running system, that was not possible in this case. We plan to continue avoiding reboots on our end as much as possible in the future.

We also recommend that all customers take this opportunity to apply the latest security updates from their OS distributions. The vendors for all currently-supported operating systems have released patches for the new vulnerability.

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 on occasion this doesn't work perfectly, so you may consider turning off applications that might write to disk before the maintenance event. If you are running Windows 2012 R2, please also note your VDS may need additional reboots to work properly, due to a bug within Xen related to how it boots up (that only occurs during bootup) -- our system will attempt to detect when this is the case and perform the extra reboot operations, but we recommend checking afterward yourself, as well.
 #168681  by jawfin
 
Post from NFO: -

We are planning to reboot the machine hosting your VDS at approximately 1:30am Central Time on December 15, in order to apply critical platform updates that address serious vulnerabilities. We are also scheduling a backup maintenance window for the next day at the same time; this backup will be used if there are problems on the first day (such as an issue with packaging the update, or last-minute bugs that are found in the code) such that we have to try again.

We have generally avoided the need for reboots over the last several years by invisibly using livepatches to update running code. However, the new security patches (and microcode updates that also need to be applied) cannot be applied to a running system.

For the reboot, your VDS will need to be shut down for approximately 15-60 minutes. We will attempt to gracefully shut it down on our end through Xen, but on occasion this doesn't work perfectly, so you may consider turning off applications that might write to disk before the maintenance event. If you are running Windows 2012 R2 or later, please also note your VDS may need additional reboots to work properly, due to a bug within Xen related to how it boots up (that only occurs during bootup) -- our system will attempt to detect when this is the case and perform the extra reboot operations, but we recommend checking afterward yourself, as well.

While we don't expect any problems related to the reboot of your machine, most machines here have not been rebooted in over a year, and there is always a remote possibility that hardware could fail as a result of the reboot. We recommend performing an extra external backup of irreplaceable files today, just to be completely safe.
 #168957  by Jack Skywalker
 
KR1 is down since today's "server restart" warning. I typed /reconnect and waited for about half an hour by now and it hasn't come back yet.

Edit: nvm, it's back.
  • 1
  • 5
  • 6
  • 7
  • 8
  • 9