mac osx 10.4
emac 1.25G 1GIG ram
320GIG HD
Cable high speed internet
build: 2008-03-08 latest dedicated build
I got this error in my terminal window for the first time in my hosting history using the new dedicated build that is in the beta section. I started using this build only 3 days ago. I have no idea how to check the timer.
Timer hickup of 21102.1 seconds detected and compensated. If this happens frequently, you should check whether your system timer is operating correctly.
Could you plz define NTP? National Time Protocol? And like i said this is the first time it happens. I hve been hosting for quite some time without adding anything to my system.
How about reading the message (it's new in the alpha builds)? It says "If this happens frequently...", and nowhere does it say "Error", and it is none. It's just an information that your timer had an odd jump. It's nothing to worry about UNLESS it happens often.
NTP = Network Time Protocol. It's what is commonly used to synchronize timers on the internet.
Gah i think i figured out why... yesterday i set my energy saving to put the comp to sleep after 15 mins of idle. I think that the app looses contact and shuts down. Could this be the reason because i got the error again
Yeah Sleep or hibernation periods also appear as timer hickups to AA. To players on the server at that time, they look like server crashes, so you should disable power management on a server machine. It would be nice if there was a way to only wake up a server when there are players who actually want to play on it, but that would be a true nightmare to officially support (for example, you'd need to instruct your router to answer server browser ping packets while your real server is asleep, and you would need to forward those magic wake-on-lan packets, and your server needs to support wake-on-lan in the first place.)
Sleep or hibernation periods also appear as timer hickups to AA. To players on the server at that time, they look like server crashes, so you should disable power management on a server machine. It would be nice if there was a way to only wake up a server when there are players who actually want to play on it, but that would be a true nightmare to officially support (for example, you'd need to instruct your router to answer server browser ping packets while your real server is asleep, and you would need to forward those magic wake-on-lan packets, and your server needs to support wake-on-lan in the first place.)