Jump to content

Recommended Posts

Posted (edited)

Image%207.png

Eddie : Online

Image%202.png

Eddie's Clock : -975 days

 

How did that happen?

 

It's like its an April Fools joke!

Edited by ziad0
Posted

Ah you’re right. That time and date is actually wrong.

 

Going to escalated this to change it back.

Posted

It's been like this for ages. Probably due to the physical time on the actual Eddie server (it's hardware not a VM)

Posted (edited)

Yeah, probably time to get it fixed :)

 

(You can already tell that its real physical hardware by the fact the name ends with "ie". VMs end in "y")

 

Maybe the CMOS battery died...

(but the server is online!)

Edited by ziad0
Posted (edited)

I just looked, and it's not a problem with the monitor either.

 

The clock is actually set to July 31, 2015 for some reason on that server...I'd set it, but for all I know Krydos intentionally has it set back for some reason (I personally maintain a server running old software for someone where the clock has to be kept behind intentionally, no later than 1/19/2014 or it breaks).

Edited by wolstech
Can't move it because it's already there...
Posted (edited)

I wonder why you would have to set it back...

Isnt Eddie supposed to only be running ESXi? (with a Cody VM)

Edited by ziad0
Posted

It is ESXI. Eddie contains Tommy and Cody.

 

Odds are high that it's just a dead battery in the server. The servers did lose power a few weeks back during an HE outage and it probably lost the time then. To my knowledge, the clock on Eddie isn't actually used for anything beyond ESX internal functions/logs, since the VMs set their clock over NTP, hence why it's gone unnoticed until now.

Posted

I doubt it happened a few weeks ago because it’s been like that for about 8 months, since I noticed it. But I didn’t report it because I was new and didn’t want to be a hassle. Anyway, it wasn’t causing an issue.

Guest
This topic is now closed to further replies.
×
×
  • Create New...