TIMESYNCH errors...

These are old archives. They are kept for historic purposes only.
Post Reply
Stormx

TIMESYNCH errors...

Post by Stormx » Mon Aug 07, 2006 8:53 pm

Older problem, but left in incase it effects the new one:
Few problems folks. This is my first time setting up an IRC server so please do forgive me if I am being very naive!

I'm having a few problems with IRCd and such. It was working fine last night, until it errored and quit. We tried to restart it but it gave us TIMESYNCH errors:

Code: Select all

#
* Loading IRCd configuration ..
#
* Configuration loaded without any problems ..
#
* Loading tunefile..
#
* Dynamic configuration initialized .. booting IRCd.
#
---------------------------------------------------------------------
#
Possible error encountered (IRCd seemily not started)
#
=====================================================
#
Check above for possible errors, and this output of
#
ircd.log. If you cannot solve the problem, read
#
Unreal.nfo on where to get support
#
=====================================================
#
[Mon Aug  7 20:23:48 2006] - TimeSync: WARNING: Was unable to send message to server #2...
#
[Mon Aug  7 20:23:48 2006] - TIME SYNCH: Unable to synchronize time: Timeout. This happens sometimes, no error on your part.
#
[Mon Aug  7 20:24:23 2006] - TimeSync: WARNING: Was unable to send message to server #0...
#
[Mon Aug  7 20:24:23 2006] - TimeSync: WARNING: Was unable to send message to server #1...
#
[Mon Aug  7 20:24:23 2006] - TimeSync: WARNING: Was unable to send message to server #2... 
I'm admining the server from SSH at the moment. Rebooting the server didn't help. The server is running CentOS and is also acting as a webserver. I checked the clock settings, it is set perfectly to GMT:

root@serv [~/Unreal3.2]# ntpdate
7 Aug 20:44:28 ntpdate[3448]: no servers can be used, exiting
root@serv [~/Unreal3.2]# date
Mon Aug 7 20:47:52 GMT 2006

Which I verified at timeanddate.com. I don't know what the error means. I know that the server isn't working, however I do know that ircd is actually running. It seems odd.. but meh. Any help much appreciated!
I just solved the above by adding a timesynch block to the config. Now the only problem is that I can't connect to the server at all, and no one else can. netstat looks like this:

Code: Select all

root@serv [~/Unreal3.2]# netstat -plant
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name
tcp        0      0 0.0.0.0:2082                0.0.0.0:*                   LISTEN      4331/cpsrvd - waiti
tcp        0      0 0.0.0.0:8067                0.0.0.0:*                   LISTEN      6030/ircd
tcp        0      0 0.0.0.0:2083                0.0.0.0:*                   LISTEN      4378/stunnel-4.15lo
tcp        0      0 0.0.0.0:2084                0.0.0.0:*                   LISTEN      4350/entropychat
tcp        0      0 0.0.0.0:2086                0.0.0.0:*                   LISTEN      4331/cpsrvd - waiti
tcp        0      0 0.0.0.0:2087                0.0.0.0:*                   LISTEN      4378/stunnel-4.15lo
tcp        0      0 0.0.0.0:6697                0.0.0.0:*                   LISTEN      6030/ircd
tcp        0      0 0.0.0.0:3306                0.0.0.0:*                   LISTEN      4624/mysqld
tcp        0      0 0.0.0.0:6666                0.0.0.0:*                   LISTEN      4355/startmelange
tcp        0      0 0.0.0.0:6667                0.0.0.0:*                   LISTEN      6030/ircd
tcp        0      0 0.0.0.0:2095                0.0.0.0:*                   LISTEN      4331/cpsrvd - waiti
tcp        0      0 127.0.0.1:783               0.0.0.0:*                   LISTEN      4069/spamd.pid --ma
tcp        0      0 0.0.0.0:2096                0.0.0.0:*                   LISTEN      4378/stunnel-4.15lo
tcp        0      0 0.0.0.0:80                  0.0.0.0:*                   LISTEN      4084/httpd
tcp        0      0 0.0.0.0:465                 0.0.0.0:*                   LISTEN      4037/exim
tcp        0      0 0.0.0.0:21                  0.0.0.0:*                   LISTEN      5797/pure-ftpd (SER
tcp        0      0 66.90.109.32:53             0.0.0.0:*                   LISTEN      3900/named
tcp        0      0 66.90.109.31:53             0.0.0.0:*                   LISTEN      3900/named
tcp        0      0 66.90.109.30:53             0.0.0.0:*                   LISTEN      3900/named
tcp        0      0 66.90.109.29:53             0.0.0.0:*                   LISTEN      3900/named
tcp        0      0 66.90.109.28:53             0.0.0.0:*                   LISTEN      3900/named
tcp        0      0 66.90.109.27:53             0.0.0.0:*                   LISTEN      3900/named
tcp        0      0 66.90.109.26:53             0.0.0.0:*                   LISTEN      3900/named
tcp        0      0 66.90.109.25:53             0.0.0.0:*                   LISTEN      3900/named
tcp        0      0 66.90.109.24:53             0.0.0.0:*                   LISTEN      3900/named
tcp        0      0 66.90.109.23:53             0.0.0.0:*                   LISTEN      3900/named
tcp        0      0 66.90.109.22:53             0.0.0.0:*                   LISTEN      3900/named
tcp        0      0 66.90.109.3:53              0.0.0.0:*                   LISTEN      3900/named
tcp        0      0 127.0.0.1:53                0.0.0.0:*                   LISTEN      3900/named
tcp        0      0 0.0.0.0:22                  0.0.0.0:*                   LISTEN      3935/sshd
tcp        0      0 0.0.0.0:25                  0.0.0.0:*                   LISTEN      4032/exim
tcp        0      0 127.0.0.1:953               0.0.0.0:*                   LISTEN      3900/named
tcp        0      0 0.0.0.0:443                 0.0.0.0:*                   LISTEN      4084/httpd
tcp        0      0 66.90.109.3:80              80.60.11.25:47933           TIME_WAIT   -
tcp        0    321 66.90.109.3:80              80.60.11.25:47944           ESTABLISHED 4377/httpd
tcp        0      0 66.90.109.3:80              71.70.143.71:2543           ESTABLISHED 4125/httpd
tcp        0      0 66.90.109.3:80              80.60.11.25:47943           ESTABLISHED 4123/httpd
tcp        0      0 66.90.109.3:80              74.137.222.208:2031         TIME_WAIT   -
tcp        0      0 66.90.109.3:80              74.137.222.208:2027         TIME_WAIT   -
tcp        0      0 66.90.109.3:80              74.137.222.208:2035         TIME_WAIT   -
tcp        0      0 66.90.109.3:80              71.70.143.71:4211           ESTABLISHED 6359/httpd
tcp        0      0 66.90.109.3:80              62.253.96.44:45129          ESTABLISHED 4122/httpd
tcp        0      0 66.90.109.3:80              71.70.143.71:4199           TIME_WAIT   -
tcp        0      0 66.90.109.3:80              71.70.143.71:4197           TIME_WAIT   -
tcp        0      0 66.90.109.3:80              71.57.7.149:62852           FIN_WAIT2   -
tcp        0      0 66.90.109.3:80              83.40.225.98:4761           ESTABLISHED 4124/httpd
tcp        0      1 66.90.109.3:33640           80.195.218.245:183          SYN_SENT    6378/php
tcp        0      0 66.90.109.3:80              84.68.105.150:1864          ESTABLISHED 4126/httpd
tcp        0      0 66.90.109.3:80              84.68.105.150:1846          TIME_WAIT   -
tcp        0   9168 66.90.109.32:22             87.240.137.127:34927        ESTABLISHED 5144/0
tcp        0      0 :::993                      :::*                        LISTEN      3992/couriertcpd
tcp        0      0 :::995                      :::*                        LISTEN      4006/couriertcpd
tcp        0      0 :::110                      :::*                        LISTEN      3999/couriertcpd
tcp        0      0 :::143                      :::*                        LISTEN      3984/couriertcpd
tcp        0      0 :::21                       :::*                        LISTEN      5797/pure-ftpd (SER

cculha
Posts: 79
Joined: Tue Sep 13, 2005 1:16 am

Post by cculha » Wed Dec 06, 2006 10:11 pm

TIME SYNCH: Unable to synchronize time: Timeout. This happens sometimes, no error on your part.




i have the same problem. how you resolve?

owine
Posts: 8
Joined: Sat Oct 01, 2005 10:13 pm
Location: CT, USA
Contact:

Post by owine » Wed Dec 06, 2006 11:39 pm

have you checked if your ircd is actually running? that is not a fatal error so it seems like your ircd should still run. your netstat shows port 6667 used by a process named ./ircd which is what the unrealircd binary file actually is.

wax
Posts: 72
Joined: Tue Oct 04, 2005 6:32 am
Location: ByNets@Belarus
Contact:

Post by wax » Thu Dec 07, 2006 7:28 am

cculha wrote:TIME SYNCH: Unable to synchronize time: Timeout. This happens sometimes, no error on your part.




i have the same problem. how you resolve?
read docs about tymesync. :P

Post Reply