kreatious downtime reports(current and past)

Rules and server information... but mostly rules.

Re: kreatious downtime reports(current and past)

by SDOR3 » Sat Jul 06, 2013 12:14 am

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.
Image
Image
Image
User avatar
SDOR3
Moderator
 
Posts:
Joined: Sun Apr 08, 2012 10:10 pm
Location: Over thy hill, behind Nezark.

Re: kreatious downtime reports(current and past)

by Neko92 » Thu Jul 18, 2013 4:48 pm

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.
User avatar
Neko92
Veteran
 
Posts:
Joined: Mon Oct 31, 2011 7:26 pm
Location: Massachusetts, U.S.A.

Re: kreatious downtime reports(current and past)

by SDOR3 » Fri Nov 15, 2013 11:48 pm

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.
Last edited by Nezark123 on Sat Nov 16, 2013 12:06 am, edited 1 time in total.
Reason: Adjusted the time since I was on when it went down
Image
Image
Image
User avatar
SDOR3
Moderator
 
Posts:
Joined: Sun Apr 08, 2012 10:10 pm
Location: Over thy hill, behind Nezark.

Re: kreatious downtime reports(current and past)

by Icefang113 » Sat Nov 16, 2013 1:22 am

SDOR3 Wrote: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.


Just going to add to this. According to Nezark a player by the of "jordanwilliams14" coincidentally threatened to DDOS the server before it went down, just throwing it out there. I'd say server went down sometime at 5:20 PM CST.

Remember kids, DDOSing is bad. M'kay.
Image
Image

"Without deviation from the norm, progress is not possible." -Frank Zappa
User avatar
Icefang113
Moderator
 
Posts:
Joined: Sat Mar 24, 2012 3:54 am
Location: Tulsa, Oklahoma

Re: kreatious downtime reports(current and past)

by Icefang113 » Wed Jan 15, 2014 6:03 pm

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

"Without deviation from the norm, progress is not possible." -Frank Zappa
User avatar
Icefang113
Moderator
 
Posts:
Joined: Sat Mar 24, 2012 3:54 am
Location: Tulsa, Oklahoma

Re: kreatious downtime reports(current and past)

by maxmmm1501 » Tue Mar 27, 2018 3:06 am

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
Moderator
 
Posts:
Joined: Sat May 11, 2013 8:11 pm
Location: Nebraska

Re: kreatious downtime reports(current and past)

by maxmmm1501 » Fri Mar 30, 2018 5:32 pm

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.
maxmmm1501
Moderator
 
Posts:
Joined: Sat May 11, 2013 8:11 pm
Location: Nebraska

Previous

Return to Rules, & Server Information.

Who is online

Users browsing this forum: No registered users and 2 guests