Omnimaga
Omnimaga => News => Topic started by: DJ Omnimaga on February 22, 2012, 02:50:56 am
-
Well, it looks like the update took longer than expected, because Netham45 didn't notice this update included a service pack, so instead of the usual 15 minutes, it took a few hours.
Stuff seems to be working well so far. If you run up into any new problem since the upgrade, don't hesitate to report it here (http://www.omnimaga.org/index.php?board=13.0).
Our apologies for the inconveniences this downtime may have caused. Hopefully Juju's server and the Omnimaga Radio will also return online soon and OmnomIRC and the bots linked back to IRC. Hopefully no extra downtime occurs again soon, too.
-
Lucky for me I haven't noticed any downtime. Probably because it happened in the night(for me). :P
-
Does 57o9.org being down have anything to do with this? Because my site (toppagedesign.com) is hosted there and is currently down, causing a lot of images, etc I have hosted there not to work.
-
Does 57o9.org being down have anything to do with this? Because my site (toppagedesign.com) is hosted there and is currently down, causing a lot of images, etc I have hosted there not to work.
No, Omni's completely seperate from 57o9.
And DJ, the update shouldn't have had any affect on Omni. It was done to fix an exploit that was used to DoS the server.
Also, sorry for not getting the bots on last night, I fell asleep waiting for it to finish.
-
Thats funny because 57o9 and omni went down at about the same time...
-
Does 57o9.org being down have anything to do with this? Because my site (toppagedesign.com) is hosted there and is currently down, causing a lot of images, etc I have hosted there not to work.
No, Omni's completely seperate from 57o9.
And DJ, the update shouldn't have had any affect on Omni. It was done to fix an exploit that was used to DoS the server.
Well, I was refering to how the server runs Windows and that Windows historically had problems with compatibility from an update to another, or things screwing up after a SP upgrade.
An example is my old computer running XP that is now stuck with Service Pack 2. Installing SP3 renders it so unstable that it's useless anymore, so I just downgraded back to SP2.
Btw the #omnimaga-fr post notifications are still down. Also it seems like the 57o9 issue was still not solved. I'm starting to wonder if it wouldn't be best to move our personal sites and files on Julosoft.net for now...
-
prizmwiki is still down...
-
That too. Same for Axe Wiki. There are possibilities that anything on 57o9 might never be back up, because two years ago, 57o9 went down for 6 months once...
-
Actually it wasn't the same server last time, with a different provider. And no news yet, I'm beginning to be kinda worried...
-
Ah ok, but it looks like the current ones who are managing it or at least the datacenter seems incompetent or something. Do you pay for this host btw? Because if it's the case, I would just move to another VPS provider.
-
I'm really, really sorry - I edited "Transcolator" to "Translocator" in my game name, but I was doing it on a mobile device, so some bug must have truncated the rest D:
Sorry DJ_O and all who were affected D:
-
Strange. I guess the good thing was that it wasn't intentional or something. This is why I asked other staff, in case something in my article was against the rules, and they had no clue about the edit.
It seems now you accidentally posted in the wrong news thread, though. :P
-
I'm really, really sorry - I edited "Transcolator" to "Translocator" in my game name, but I was doing it on a mobile device, so some bug must have truncated the rest D:
Sorry DJ_O and all who were affected D:
This is what brought down 57o9???
-
My website is kinda up, about 1/4 of the time.
-
I'm really, really sorry - I edited "Transcolator" to "Translocator" in my game name, but I was doing it on a mobile device, so some bug must have truncated the rest D:
Sorry DJ_O and all who were affected D:
This is what brought down 57o9???
O.O
Actually it was a router problem. At first we worried that the datacenter nullrouted 57o9 or something in response to it being used for DoS attacks two weeks before and Juju had received warnings about the attacks. This would have sucked since it was someone else who performed the attacks, using the server as a proxy/bouncer, although I guess it was juju who was responsible to take action if such attack occurs.
Finally it was just the router, but it's weird that they took this long to fix it or replace it...