TIME SYNCH - Crashes Server?

[Lavamike]

Well today our IRC server just went offline and needed to be restarted. I got this in my IRC client:

(21:54:33) * [10053] Software caused connection abort
(21:54:33) * Disconnected
(21:54:38) * Connect retry #1 IP (6667)
(21:54:41) * Unable to connect to server (Connection refused)

After it was started back up everyone could connect fine. The only thing I see in the ircd.log at that time is this:

[Fri Aug 28 11:28:19 2009] - TIME SYNCH: timeserver=1251451699, our=1251451699, offset = 0 [old offset: -7]

I have no idea what this TIME SYNCH even is, what causes it to get off-synch or if this could even contribute to the problem...
Does anyone know what could be causing this problem? Thanks.

[0x3a]

Don't use the TimeSynch block or use proper TimeSynch servers.

Code: Select all

set::timesynch::enabled <yes|no>
Enable or disable time synchronization on-boot. Default is yes.

set::timesynch::server <IP>
Server to synchronize time with. This can be up to 4 IP's seperated by comma's. The servers must support NTP protocol version 4. The default is to use 3 time servers (US, EU, AU). Requests to these servers are sent in parallel, fastest reply wins.

set::timesynch::timeout <time>
Maximum time to wait for a time server reply. This is a value between 1 and 5, more is not possible because it causes too much inaccuracy. This setting is 3 by default and there's probably no good reason to change it.

Or....
Remove any 3rd party addons and then restart/rehash, if it still gives errors report it too: http://bugs.unrealircd.org/
If it doesn't crash with one of those modules, then there's a bug in an unofficial module, and you should contact the author of that module

[Lavamike]

I'm not using any extra addons and I don't have any TimeSynch block. I guess that's something in the new 3.2.8 or something. I am using 3.2.7. Should I upgrade then I guess? lol

[Syzop]

Timesynch is only done on start-up, so whenever the ircd is booted, timesynch cannot cause any crash.

So, it was something else. When the ircd crashes, or is deliberately killed (sometimes by hosting providers), it does not log anything.

If it did crash, though, then there should be a core file (ircd.core, core, core.428942, a filename with 'core' in it). See the bugtracker for information how to report such a crash (unless you don't want to report, or think it's because of a faulty 3rd party module).

[Lavamike]

I'm not running any 3rd party modules (At least I don't think I am...) The only loadmodule I have in my unrealircd.conf is the default:

Code: Select all

/* FOR Windows, uncomment the following 2 lines: */
loadmodule "modules/commands.dll";
loadmodule "modules/cloak.dll";

So then if it's not crashing i'll have to see if the host has anything to do with it... Anyway, it's worth upgrading to 3.2.8 though right? Maybe upgrading would fix the problem if it ever occurs again.