Forum

Page 3 of 4 FirstFirst 1234 LastLast
Results 31 to 45 of 53
  1. #31
    Join Date
    November 2006
    Location
    USA
    Posts
    55
    Is it possible that this is a result of hack attempts or an exploit to cause servers to crash.

    We all know there are hacks floating around on the internet.

    It strange that it happens at times of the most inconvenience, when something is going on in-game and you need communications to be up.

  2. #32
    Join Date
    September 2005
    Location
    Netherlands
    Posts
    13

    Cool

    I can actually confirm that it is most likely a hack... I found the following in my logs today (just half an hour after updating the horrible TS3 permission system database... But that should not be related!):

    Code:
    ... (around 100 messages, starting at 10:45:44.760582) ...
    2010-12-02 10:45:44.850184|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-12-02 10:45:44.850678|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-12-02 10:45:44.851203|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-12-02 10:45:44.851677|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-12-02 10:45:44.852080|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-12-02 10:45:44.852336|INFO    |VirtualServer | 30| client disconnected 'USER_A'(id:25068) reason 'reasonmsg=ik weet dat jullie noob zijn daarom tot ziens:P'
    2010-12-02 10:45:44.852519|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-12-02 10:45:44.853592|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-12-02 10:45:44.854084|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-12-02 10:45:44.854631|WARNING |PktHandler    |   | detected incorrectly running system clock
    2010-12-02 10:45:44.855132|WARNING |PktHandler    |   | detected incorrectly running system clock
    ... (around 100 messages, ending at 10:45:45.144074) ...
    2010-12-02 10:45:45.250333|INFO    |VirtualServer |357| stopped
    2010-12-02 10:45:45.251174|ERROR   |Query         |   | onRemoveConnection called with an invalid clientSocketID: 111
    2010-12-02 10:45:45.251231|ERROR   |Query         |   | onRemoveConnection called with an invalid clientSocketID: 32
    2010-12-02 10:45:45.251257|ERROR   |Query         |   | onRemoveConnection called with an invalid clientSocketID: 141
    2010-12-02 10:45:45.251489|ERROR   |Query         |   | onRemoveConnection called with an invalid clientSocketID: 32
    A translation for "ik weet dat jullie noob zijn daarom tot ziens:P" (dutch): "I know you people are noobs and therefore goodbye:P"

    I'll report this to "Premium support", hacks should be fixed a.s.a.p. in my opinion Especially as this is not limited to the Virtual Server in question...!

    Update 1:

    I can confirm this is NOT NTP RELATED, since the last NTP update was 10 minutes before the problems started:
    Dec 2 11:35:18 s25 ntpd[6577]: kernel time sync status change 0001
    Last edited by pietermx; December 2nd, 2010 at 12:48 PM. Reason: Replaced username with "USER_A" for privacy reasons ;)

  3. #33
    Join Date
    September 2005
    Location
    Netherlands
    Posts
    13
    Update 2:

    Just a few minutes ago another crash, this time without any suspicious messages... No NTP sync, standard Debian GNU/Linux (Lenny dist.) kernel... Help!!!

    Downgrading to beta29 (or beta28) might be an option since this seems to be a (serious) TS3 beta30 bug or leak... However I'm not sure if the beta30 database is 100% backwards compatible with beta29...? Any ideas?
    Last edited by pietermx; December 2nd, 2010 at 12:49 PM. Reason: Corrected "beta29" to "beta30", since I'm running beta30 at this moment...

  4. #34
    Join Date
    July 2002
    Location
    Germany
    Posts
    2,192
    Hello,

    when you get this warning you can expect clients to drop from your server, since the packet handler is trying to measure how long pings took until they are answered, packets have been waiting for an acknowledgement...if your time fails then, there is no choice but to drop the client.

    I do not see how somebody could "hack" your time source though, except if they control the time server you use to sync or something? I put together a little programme that tries to fetch the current time approximately 1000 times per second and that will detect it when the time jumps, it is attached.

    If you give it a try run it like "./timeTest > timstamp.log", it will print messages in console when it detects any failure (if it finds a certain error in time it will also stop), the timestamp.log can then be examined to view the exact behaviour of your timestamps.

    Note that the attached programme is for amd64 linux systems...if you require x86 I can build you one too, just say.
    You think my answer is stupid ? Read This:
    http://www.catb.org/~esr/faqs/smart-...ons.html#intro

    In a world without fences and walls - who needs windows and gates ?

  5. #35
    Join Date
    September 2005
    Location
    Netherlands
    Posts
    13
    Running your viru.. uh timeTest at this moment ( ), I'll report back within a few hours (or sooner, if an error occurred).

    Just a small notice: No errors occurred since I (temporary) disabled the Virtual Server "USER_A" was (ab)using...! This, in combination with his message during the first occurrence of this problem, supports the idea that there is a kind of hack around here...

  6. #36
    Join Date
    September 2005
    Location
    Netherlands
    Posts
    13
    Running it for over 1,5 hours doesn't detect any time jumps:

    sh-3.2$ date; ./timeTest > 1.log; date
    Thu Dec 2 14:15:55 CET 2010
    ^C
    Thu Dec 2 15:46:28 CET 2010

    The log file (1.log in my case) is 72M and ends with no error... Any ideas?

    Note: This server is actually running 2 TS3 servers with both a bunch of Virtual Servers. The problem only occurred on one of the TS3 servers...!

  7. #37
    Join Date
    July 2002
    Location
    Germany
    Posts
    2,192
    I do not know when or why your time jumps...it would help to have it running WHILE ts3 server are reporting the time is broken.
    You think my answer is stupid ? Read This:
    http://www.catb.org/~esr/faqs/smart-...ons.html#intro

    In a world without fences and walls - who needs windows and gates ?

  8. #38
    Join Date
    September 2005
    Location
    Netherlands
    Posts
    13
    I'll leave it running in the background for now... I'll report back later.

  9. #39
    Join Date
    September 2005
    Location
    Netherlands
    Posts
    13
    Still running fine... My timeTest log is 4.2 GB at this moment, no errors...!

    Also, no errors on TS3.... Strange :|

  10. #40
    Join Date
    September 2005
    Location
    Netherlands
    Posts
    13
    Update: Still running fine... My timeTest log is 12 GB at this moment, no errors...!

    Also, no errors on TS3.... Strange :|

    ... I call this one "fixed", timeCheck app. has been killed.

  11. #41
    Join Date
    July 2005
    Location
    SK
    Posts
    44

    for me solved...

    Just for the case someone has the same problem with TS3-server kicking everybody out and message "detected incorrectly running system clock", I describe how I fixed this problem:

    The message seems pretty clear: something (or somebody) changed system-time in such a step which TS3 considers as problem. As a result TS3-server kicks everybody out, and needs some time to recover. It could happen i.e. when system time is updated by ntp-daemon, as it was in my case: I noticed I have this problem only when I have ntpd running. So I checked what ntpd was doing when this happened, comparing logs for TS3 and ntpd. And I found messages like this in /var/log/ntpd.log (about one per hour):

    2010-11-04 T 17:14:45+00:00 obelix ntpd[15932]: time reset -0.182409 s

    After a little digging into ntp documentation I found:

    "...Normally, the time is slewed if the offset is less than the step threshold, which is 128 ms by default, and stepped if above the threshold..."

    It means, if difference between local time and ntp-server time is >0.128s, system time is adjusted using stepping, because ntpd considers with slewing it would take too much time (in my case, kernel allows about +/- 0.5ms per second, so correcting ~0.18s deviation would take ~6min). And that is exactly what was causing problems for TS3-server in my case (and some other software, e.g. dovecot, which died a few times too). Finally, I have found solution using ntpd docu again:

    "...tinker [ step step ]
    Spedifies the step threshold in seconds. The default without this command is 0.128 s. If set to zero, step adjustments will never occur..."

    So I included "tinker step 0" in my /etc/ntpd.conf, restarted ntpd, and I have no more "incorrectly running system clock" messages in TS3-log, and clients have never been kicked off my TS3-server since then (I've been testing it for about 3 weeks, using intentionally still the same old beta29 version).

    This helped me, but I do not say it must help you too. But if you have this "incorrectly running system clock" message in TS3-server log, I would definitelly check if there is some time-updating software running, and look into its log. FYI, even most of Windows (XP, Vista, 7) have it running, they call it "Windows Time" service...

  12. #42
    Join Date
    September 2005
    Location
    Netherlands
    Posts
    13
    Thx Teddy, I'll adjust my NTP settings.

  13. #43
    Join Date
    June 2010
    Location
    Russia
    Posts
    11

    Unhappy Problem in beta 30

    Hello.
    More recently, there was a server error ...
    PHP Code:
    PktHandler detected incorrectly running system clock 
    At first, everything starts to slow down and then restart the server.
    Yesterday, update the system time. But the bug had appeared, and today

  14. #44
    Join Date
    December 2009
    Location
    Germany
    Posts
    79

    detected incorrectly running system clock

    Hey,

    my Teamspeak3-Server is keeping to disconnect others and me; this is what the log shows:

    Code:
    2011-01-03 17:16:56.525566|INFO    |ServerLibPriv |   | Server Version: 3.0.0-beta30 [Build: 12998], Linux
    2011-01-03 17:16:56.757282|INFO    |DatabaseQuery |   | dbPlugin name:    SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
    2011-01-03 17:16:56.847314|INFO    |DatabaseQuery |   | dbPlugin version: 3.7.3
    2011-01-03 17:16:57.235565|INFO    |DatabaseQuery |   | checking database integrity (may take a while)
    2011-01-03 17:17:05.929579|INFO    |SQL           |   | pruning old database log entries where timestamp is older than 90 days
    2011-01-03 17:17:06.032458|INFO    |SQL           |   | pruning old guest clients where last connected time is older than 30 days, clients to remove: 36
    2011-01-03 17:17:07.053312|INFO    |Accounting    |   | Licensing Information
    2011-01-03 17:17:07.053423|INFO    |Accounting    |   | type              : Non-profit
    2011-01-03 17:17:07.053550|INFO    |Accounting    |   | starting date     : Mon Dec 20 00:00:00 2010
    2011-01-03 17:17:07.053611|INFO    |Accounting    |   | ending date       : Wed Dec 21 00:00:00 2011
    2011-01-03 17:17:07.053669|INFO    |Accounting    |   | max virtualservers: 10
    2011-01-03 17:17:07.053717|INFO    |Accounting    |   | max slots         : 512
    2011-01-03 17:17:07.701023|INFO    |FileManager   |   | listening on 0.0.0.0:30033
    2011-01-03 17:17:08.865068|INFO    |VirtualServer |  1| listening on 0.0.0.0:9987
    2011-01-03 17:17:09.254343|INFO    |VirtualServer |  2| listening on 0.0.0.0:8888
    2011-01-03 17:17:09.856116|INFO    |VirtualServer |  3| listening on 0.0.0.0:1896
    2011-01-03 17:17:10.421522|INFO    |VirtualServer |  5| listening on 0.0.0.0:1234
    2011-01-03 17:17:10.790764|INFO    |VirtualServer |  6| listening on 0.0.0.0:1111
    2011-01-03 17:17:10.884951|INFO    |CIDRManager   |   | updated query_ip_whitelist ips: 127.0.0.1, 85.25.120.233, 
    2011-01-03 17:17:10.887182|INFO    |Query         |   | listening on 0.0.0.0:10011
    2011-01-03 17:18:14.039813|INFO    |VirtualServer |  5| query client connected 'Unknown from 68.232.160.177:59941'(id:354)
    2011-01-03 17:18:15.092045|INFO    |VirtualServer |  5| query client disconnected 'Unknown from 68.232.160.177:59941'(id:354) reason 'reasonmsg=connection lost'
    2011-01-03 17:19:27.478737|INFO    |VirtualServer |  5| query client connected 'Unknown from 66.55.131.14:55110'(id:354)
    2011-01-03 17:19:28.222270|INFO    |VirtualServer |  5| query client disconnected 'Unknown from 66.55.131.14:55110'(id:354) reason 'reasonmsg=connection lost'
    2011-01-03 17:20:42.454297|INFO    |VirtualServer |  5| query client connected 'Unknown from 4.79.145.85:56575'(id:354)
    2011-01-03 17:20:43.404554|INFO    |VirtualServer |  5| query client disconnected 'Unknown from 4.79.145.85:56575'(id:354) reason 'reasonmsg=connection lost'
    2011-01-03 17:22:27.725387|INFO    |VirtualServer |  5| query client connected 'Unknown from 216.155.146.44:46970'(id:354)
    2011-01-03 17:22:27.773963|INFO    |VirtualServer |  5| query client disconnected 'Unknown from 216.155.146.44:46970'(id:354) reason 'reasonmsg=connection lost'
    2011-01-03 17:23:29.690978|INFO    |VirtualServer |  5| query client connected 'Unknown from 208.167.242.182:39874'(id:354)
    2011-01-03 17:23:30.193753|INFO    |VirtualServer |  5| query client disconnected 'Unknown from 208.167.242.182:39874'(id:354) reason 'reasonmsg=connection lost'
    2011-01-03 17:24:01.424861|INFO    |VirtualServer |  5| query client connected 'Unknown from 85.25.120.233:32953'(id:354)
    2011-01-03 17:24:01.668364|INFO    |VirtualServer |  5| query client disconnected 'TSViewer.com DBscan REG 939678'(id:354) reason 'reasonmsg=disconnecting'
    2011-01-03 17:24:46.389011|INFO    |VirtualServer |  5| query client connected 'Unknown from 94.75.248.150:59621'(id:354)
    2011-01-03 17:24:46.566509|INFO    |VirtualServer |  5| query client disconnected 'Unknown from 94.75.248.150:59621'(id:354) reason 'reasonmsg=connection lost'
    2011-01-03 17:25:45.444359|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:25:45.692180|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:25:45.693501|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:25:45.696713|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:25:45.810412|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:25:46.199293|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:26:36.466035|INFO    |VirtualServer |  5| query client connected 'Unknown from 208.167.243.62:59004'(id:354)
    2011-01-03 17:26:37.238699|INFO    |VirtualServer |  5| query client disconnected 'Unknown from 208.167.243.62:59004'(id:354) reason 'reasonmsg=connection lost'
    2011-01-03 17:28:19.170813|INFO    |VirtualServer |  5| query client connected 'Unknown from 208.167.247.210:48454'(id:354)
    2011-01-03 17:29:09.726158|INFO    |VirtualServer |  5| query client disconnected 'Unknown from 208.167.247.210:48454'(id:354) reason 'reasonmsg=connection lost'
    2011-01-03 17:29:11.078077|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:11.345130|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:11.353967|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:11.429557|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:11.541749|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:11.647868|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:11.656341|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:11.751847|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:11.895943|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:11.899530|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:11.906018|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.184430|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.519073|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.544474|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.548120|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.558322|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.617069|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.619406|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.623648|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.726038|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.728099|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.755654|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.758719|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.762267|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.764285|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.794744|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.796994|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.866942|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.869146|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.908112|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.909170|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.916606|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.990692|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.991909|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.992762|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.994390|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.995433|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.996857|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.998666|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:12.999441|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.000149|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.001033|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.003100|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.003859|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.004772|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.005499|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.006197|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.051002|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.053927|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.070620|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.082545|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.129964|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.131035|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.134585|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.142225|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.144960|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.146149|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.151128|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.156618|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.161989|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.171574|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.176993|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.181687|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.186943|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.192139|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.193134|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.194274|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.206341|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.218596|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.222472|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.224800|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.226929|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.228019|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.228812|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.231705|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.233680|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.234833|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.236027|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.239149|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.241081|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.243327|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.244303|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.246334|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.249508|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.250696|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.253075|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.277148|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.282278|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.284325|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.288711|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.292676|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.294972|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.296889|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.297880|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.299583|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.300785|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.303098|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.304129|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.307170|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.310516|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.311435|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.312329|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.313720|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.317262|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.318904|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.319817|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.338632|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.344493|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.347545|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.353076|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.355781|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.359214|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.608870|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.612666|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.615136|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.647049|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.654246|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.661838|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.678838|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.684984|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.687023|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.710396|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.717314|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.789898|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.792517|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.796606|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:13.889227|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:14.917327|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:15.103586|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:15.128032|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:15.133527|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:15.134745|WARNING |PktHandler    |   | detected incorrectly running system clock
    2011-01-03 17:29:15.218151|WARNING |PktHandler    |   | detected incorrectly running system clock
    What could that be?

    Thanks

  15. #45
    Join Date
    June 2010
    Location
    Russia
    Posts
    11
    Some error.... server beta30 (linux debian 32bit)

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. [Resolved] "Detected incorrectly running system clock" log message
    By Peter in forum Linux / FreeBSD
    Replies: 21
    Last Post: February 24th, 2019, 08:54 PM
  2. Replies: 1
    Last Post: August 18th, 2012, 11:30 PM
  3. Replies: 7
    Last Post: June 10th, 2011, 04:33 PM
  4. "detected incorrectly running system clock"
    By meliorus in forum Bug Reports [EN/DE]
    Replies: 43
    Last Post: February 3rd, 2011, 01:10 PM
  5. Replies: 8
    Last Post: December 26th, 2009, 09:26 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •