Page 1 of 2

kreatious downtime reports(current and past)

Posted: Tue Jun 26, 2012 7:17 am
by tempestfeir
This section will be updated as needed about kreatious minecraft server downtimes.
For Players: This will have oldest to newest downtimes for the past month in order of oldest below this post, newest at bottom. The posts should never be more than 1 page.

For Moderators: Please within a reasonable time of you noticing a downtime on your watch, post to this forum thread with a new post. After 1 month start deleting the oldest posts (not all of them) to keep this page clean and fresh. A downtime is considered a downtime if the server is not back up within 5 - 10 minutes.

Re: kreatious downtime reports(current and past)

Posted: Tue Oct 23, 2012 11:59 pm
by TheOWCA
Downtime Started: 4:53pm PST
Reason: The server just stopped, thats the best way i can explain it
Downtime Ended: Some time before 5:10pm PST

Re: kreatious downtime reports(current and past)

Posted: Wed Dec 26, 2012 5:30 am
by Icefang113
Downtime Started: 11:25 PM CST
Reason: Best way to explain is the server crashed, a mod attempted to reboot, then it crashed contsantly
Downtime Ended: About 11:32 PM CST

Re: kreatious downtime reports(current and past)

Posted: Sun Jan 20, 2013 3:49 am
by Icefang113
Downtime Started: Around 9:41 PM CST
Reason: Mod attempted reboot to fix broken commands
Downtime Ended: Server came back up around 9:56 PM CST

Re: kreatious downtime reports(current and past)

Posted: Sat Mar 02, 2013 6:31 pm
by tempestfeir
Downtime Started: Saturday March 2nd 2013 @ 1:10PM EST
Reason: The Data Centre our server is connected to is experiencing network issues, they're attempting to resolve this ASAP.
Downtime Ended: Saturday March 2nd 2013 @ 2:20PM EST

Re: kreatious downtime reports(current and past)

Posted: Sun May 26, 2013 4:37 pm
by SDOR3
Downtime Started: May 26th, 2013 11:35 AM CST
Reason: Attempted reboot to fix broken commands.
Downtime Ended: May 26th, 2013 12:02 PM CST
Note: Web puTTY and console puTTY were both down, so it was not possible to attempt a reboot from those.

Re: kreatious downtime reports(current and past)

Posted: Wed May 29, 2013 6:18 am
by Nezark123
Downtime Started: May 29th, 2013 2:09 AM EST
Reason: Certain commands were attempted by one whom shall not be named.
Downtime Ended: May 29th 3:45 AM CST
Note: Out of nowhere, everyone became default rank, and chat couldn't be seen. No commands worked, and we couldn't do anything except log out and back in. Also, anti-grief and Eve were still working, despite the fact you couldn't see chat.

Re: kreatious downtime reports(current and past)

Posted: Thu Jun 27, 2013 3:04 am
by Icefang113
Downtime started: June 26th, 2013 9:50 PM CST
Reason: Possible host issues
Downtime ended: June 26th, 2013 10:52 PM CST

Re: kreatious downtime reports(current and past)

Posted: Sat Jul 06, 2013 12:14 am
by SDOR3
Downtime started: July 5th 2013, at 7:10 PM CST
Reason: No known reason, the server just went down, commands stopped working.
Downtime ended: July 5th 2013, approx. 8:15 PM CST
Note: I wasn't able to reboot, it wouldn't let me.

Re: kreatious downtime reports(current and past)

Posted: Thu Jul 18, 2013 4:48 pm
by Neko92
Downtime started: July 18 2013 12:34 pm EST
Reason: Unknown, Died unexpectedly
Downtime ended: unknown
Note: Putty not working to reboot

Client Log (because we can do that now with the new launcher)
Spoiler:
Client> 2013-07-18 12:34:44 [CLIENT] [INFO] [CHAT] Logging thread encountered a null
Client> 2013-07-18 12:34:44 [CLIENT] [INFO] [CHAT] CRITICAL: The database logger thread died.
Client> 2013-07-18 12:34:44 [CLIENT] [INFO] [CHAT] Grief alerts are not active, and blocks are
Client> 2013-07-18 12:34:44 [CLIENT] [INFO] [CHAT] not being recorded!!!
Client> 2013-07-18 12:34:44 [CLIENT] [INFO] [CHAT] java.lang.NullPointerException
Client> at com.mysql.jdbc.ResultSetImpl.buildIndexMapping(ResultSetImpl.java:754)
Client> at com.mysql.jdbc.ResultSetImpl.findColumn(ResultSetImpl.java:1108)
Client> at com.mysql.jdbc.ResultSetImpl.getBoolean(ResultSetImpl.java:1761)
Client> at com.bukkit.kreatious.helper.KreatiousHelper.parsePreference(KreatiousHelper.java:610)
Client> at com.bukkit.kreatious.helper.KreatiousHelper.getPreference(KreatiousHelper.java:925)
Client> at com.bukkit.kreatious.alert.KreatiousAlert.playSounds(KreatiousAlert.java:4065)
Client> at com.bukkit.kreatious.alert.KreatiousAlert.addAlertSound(KreatiousAlert.java:4036)
Client> at com.bukkit.kreatious.alert.KreatiousAlert.constructMsg(KreatiousAlert.java:4134)
Client> at com.bukkit.kreatious.alert.KreatiousAlert.broadcastAlert(KreatiousAlert.java:3887)
Client> at com.bukkit.kreatious.alert.DBLogger.onKillAlert(DBLogger.java:3449)
Client> at com.bukkit.kreatious.alert.DBLogger.run(DBLogger.java:1343)
Client>
Client> 2013-07-18 12:34:44 [CLIENT] [INFO] [CHAT] ABSOLUTELY FATAL ERROR - Rebooting NOW
Client> 2013-07-18 12:34:44 [CLIENT] [INFO] [CHAT] --- BRACE FOR IMPACT!!! ---
Client> 2013-07-18 12:34:44 [CLIENT] [INFO] [CHAT] If reboot doesn't happen in 1 minute, tell a mod to /hardreboot. ts.kreatious.net works good.