kreatious downtime reports(current and past)

[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.

[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.

[SDOR3]

Downtime started: November 15th 2013 5:23 pm CST.
Reason: Unknown, attempted to log in and found the server down. It's been down for a while as of now.
Downtime ended:
Note: Webchat's down. Unable to reboot from that.

[Icefang113]

[Icefang113]

Downtime started: Jan 15th, 2014, sometime before 7:30 am CST.
Reason is unknown at this point.
Downtime ended: Jan 15th, 2014, sometime after 2:00 pm CST
Note: At this time we don't have access to console, I would expect the server to be up in the afternoon when Zerg returns from work. Until then I would try doing something else in the meantime.

[maxmmm1501]

Reviving this because why not
Downtime started: March 26, 2018 9:42 CST
Reason: No idea, just timed out. Was shortly after sanshon joined, could be corrupt chunk? I think it would crash sooner than it did if it was that though
Note: Console is down so I can't reboot - I've contacted zerg.

[maxmmm1501]

Downtime started: March 30, 2018 12:19 CST
Reason: Attempted reboot to fix lag
Note: Console is down, can't try to reboot again from there. I've contacted zerg.