Forum


Notice to all users

We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020

Results 1 to 6 of 6
  1. #1
    Join Date
    June 2011
    Location
    Russian Federation
    Posts
    204

    permanent errors and the server is incorrectly

    OS: Debian 6 [x86]
    RAM: 1GB
    HDD: 8GB
    CPU: 2 (Intel Xeon)

    TeamSpeak 3 Server 3.0.6.1 logs
    Code:
    2013-01-25 06:08:07.583020|INFO    |ServerLibPriv |   | TeamSpeak 3 Server 3.0.6.1 (2012-06-29 07:59:05)
    2013-01-25 06:08:07.935389|INFO    |DatabaseQuery |   | dbPlugin name:    SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
    2013-01-25 06:08:08.013365|INFO    |DatabaseQuery |   | dbPlugin version: 3.7.3
    2013-01-25 06:08:08.178252|INFO    |DatabaseQuery |   | checking database integrity (may take a while)
    2013-01-25 06:08:14.486392|INFO    |Accounting    |   | Licensing Information
    2013-01-25 06:08:14.486473|INFO    |Accounting    |   | type              : Non-profit
    2013-01-25 06:08:14.486536|INFO    |Accounting    |   | starting date     : Mon Sep  3 00:00:00 2012
    2013-01-25 06:08:14.486576|INFO    |Accounting    |   | ending date       : Fri Mar 22 00:00:00 2013
    2013-01-25 06:08:14.486603|INFO    |Accounting    |   | max virtualservers: 10
    2013-01-25 06:08:14.486627|INFO    |Accounting    |   | max slots         : 512
    2013-01-25 06:08:14.606994|INFO    |FileManager   |   | listening on 0.0.0.0:30033
    2013-01-25 06:08:15.941153|INFO    |CIDRManager   |   | updated query_ip_whitelist ips: 127.0.0.1, 85.25.120.233, 68.232.0.0/16, 208.167.0.0/16,
    2013-01-25 06:08:15.991293|INFO    |Query         |   | listening on 0.0.0.0:10011
    2013-01-25 23:37:21.875518|ERROR   |              |   | resolving '*.*.*.*.' to binary ip failed, using 0.0.0.0 instead
    2013-01-26 14:12:01.211256|ERROR   |              |   | resolving '*.*.*.*.' to binary ip failed, using 0.0.0.0 instead
    2013-01-28 03:22:22.181472|ERROR   |              |   | resolving '*.*.*.*.' to binary ip failed, using 0.0.0.0 instead
    2013-01-28 04:35:04.972900|ERROR   |              |   | resolving '*.*.*.*.' to binary ip failed, using 0.0.0.0 instead
    2013-01-28 09:06:15.343488|ERROR   |              |   | resolving '*.*.*.*.' to binary ip failed, using 0.0.0.0 instead
    2013-01-28 15:39:28.537086|WARNING |PktHandler    |   | detected incorrectly running system clock (>)
    2013-01-28 15:39:28.537279|WARNING |PktHandler    |   | detected incorrectly running system clock (>)
    2013-01-29 10:45:14.139020|ERROR   |              |   | resolving '*.*.*.*.' to binary ip failed, using 0.0.0.0 instead
    2013-01-30 12:53:27.626214|WARNING |PktHandler    |   | detected incorrectly running system clock (>)
    2013-01-30 12:53:27.634887|WARNING |PktHandler    |   | detected incorrectly running system clock (>)
    2013-01-30 12:53:27.634953|WARNING |PktHandler    |   | detected incorrectly running system clock (>)
    2013-01-30 12:53:27.635072|WARNING |PktHandler    |   | detected incorrectly running system clock (>)
    2013-01-30 12:53:27.635245|WARNING |PktHandler    |   | detected incorrectly running system clock (>)
    2013-01-30 12:53:27.635353|WARNING |PktHandler    |   | detected incorrectly running system clock (>)
    2013-01-30 12:53:27.635424|WARNING |PktHandler    |   | detected incorrectly running system clock (>)
    2013-01-30 12:53:27.635551|WARNING |PktHandler    |   | detected incorrectly running system clock (>)
    2013-01-30 13:11:41.742145|WARNING |PktHandler    |   | detected incorrectly running system clock (>)
    2013-01-30 13:11:41.742276|WARNING |PktHandler    |   | detected incorrectly running system clock (>)
    2013-01-30 13:19:57.306259|ERROR   |              |   | resolving '*.*.*.*.' to binary ip failed, using 0.0.0.0 instead
    2013-01-31 19:04:37.513802|WARNING |PktHandler    |   | detected incorrectly running system clock (>)
    2013-02-01 00:02:13.814049|INFO    |VirtualSvrMgr |   | executing monthly interval
    2013-02-01 00:02:13.814263|INFO    |VirtualSvrMgr |   | reset virtualserver traffic statistics
    2013-02-01 23:47:10.310639|ERROR   |              |   | resolving '*.*.*.*.' to binary ip failed, using 0.0.0.0 instead
    2013-02-02 19:08:53.228528|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
    2013-02-03 13:56:47.138332|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
    2013-02-03 13:59:18.894813|ERROR   |              |   | resolving '*.*.*.*.' to binary ip failed, using 0.0.0.0 instead
    2013-02-04 08:31:20.700588|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
    2013-02-04 09:46:46.067822|ERROR   |              |   | resolving '*.*.*.*.' to binary ip failed, using 0.0.0.0 instead
    2013-02-04 13:33:53.360837|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
    2013-02-04 14:42:21.461408|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
    2013-02-04 15:37:02.355582|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
    2013-02-04 16:14:33.038526|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
    2013-02-04 18:42:08.046259|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
    iptables -L
    Code:
    Chain INPUT (policy ACCEPT)
    target     prot opt source               destination
    ACCEPT     udp  --  anywhere             anywhere            udp dpt:9987
    ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:10011
    ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:30033
    ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:41144
    
    Chain FORWARD (policy ACCEPT)
    target     prot opt source               destination
    
    Chain OUTPUT (policy ACCEPT)
    target     prot opt source               destination
    ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:2008
    ACCEPT     udp  --  anywhere             anywhere            udp dpt:2010
    iptables -S
    Code:
    -P INPUT ACCEPT
    -P FORWARD ACCEPT
    -P OUTPUT ACCEPT
    -A INPUT -p udp -m udp --dport 9987 -j ACCEPT
    -A INPUT -p tcp -m tcp --dport 10011 -j ACCEPT
    -A INPUT -p tcp -m tcp --dport 30033 -j ACCEPT
    -A INPUT -p tcp -m tcp --dport 41144 -j ACCEPT
    -A OUTPUT -p tcp -m tcp --dport 2008 -j ACCEPT
    -A OUTPUT -p udp -m udp --dport 2010 -j ACCEPT
    cat /etc/resolv.conf
    Code:
    nameserver 8.8.4.4
    nameserver 8.8.8.8
    netstat -tulpn
    Code:
    (Not all processes could be identified, non-owned process info
     will not be shown, you would have to be root to see it all.)
    Active Internet connections (only servers)
    Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
    tcp        0      0 0.0.0.0:30033           0.0.0.0:*               LISTEN      1677/ts3server_linu
    tcp        0      0 0.0.0.0:10011           0.0.0.0:*               LISTEN      1677/ts3server_linu
    udp      688      0 0.0.0.0:9987            0.0.0.0:*                           1677/ts3server_linu
    ping accounting.teamspeak.com -c 10
    Code:
    PING accounting.teamspeak.com (80.190.145.215) 56(84) bytes of data.
    64 bytes from 80.190.145.215: icmp_req=1 ttl=47 time=67.4 ms
    64 bytes from 80.190.145.215: icmp_req=2 ttl=47 time=66.7 ms
    64 bytes from 80.190.145.215: icmp_req=3 ttl=47 time=66.9 ms
    64 bytes from 80.190.145.215: icmp_req=4 ttl=47 time=67.2 ms
    64 bytes from 80.190.145.215: icmp_req=5 ttl=47 time=67.0 ms
    64 bytes from 80.190.145.215: icmp_req=6 ttl=47 time=67.3 ms
    64 bytes from 80.190.145.215: icmp_req=7 ttl=47 time=67.1 ms
    64 bytes from 80.190.145.215: icmp_req=8 ttl=47 time=66.9 ms
    64 bytes from 80.190.145.215: icmp_req=9 ttl=47 time=66.9 ms
    64 bytes from 80.190.145.215: icmp_req=10 ttl=47 time=66.7 ms
    
    --- accounting.teamspeak.com ping statistics ---
    10 packets transmitted, 10 received, 0% packet loss, time 9010ms
    rtt min/avg/max/mdev = 66.722/67.055/67.422/0.340 ms
    I beg to explain all the errors present in the logs

    1. resolving '*.*.*.*.' to binary ip failed, using 0.0.0.0 instead
    2. detected incorrectly running system clock (>)
    3. Protocol mismatch, old client or old server?

    Found answers to your forum for all three errors

    1. http://forum.teamspeak.com/showthrea...und-to-0-0-0-0 - nothing does not help.
    2. http://forum.teamspeak.com/showthrea...ot-log-message - nothing does not help.
    3. http://forum.teamspeak.com/showthrea...-or-old-server - nothing does not help.

    what do I do? give me a clear and understandable answer to cure it all, to correct these errors.

  2. #2
    Join Date
    September 2012
    Posts
    6,079
    1) Your answer is in the linked thread, 2nd Post actually answers it.
    2) As explained in the thread you linked your time jumps too much, or is running too fast / slow. Nothing we can do about that. You need to fix your server's time issues.
    3) A really really old client connected to your server, which is not supported and the client got rejected. The server just logs it since it received invalid data.

  3. #3
    Join Date
    June 2011
    Location
    Russian Federation
    Posts
    204
    Hello, thank you for answering me.

    1) honestly did not understand about the message flow.
    2) You can explain exactly what you need to change where it is correct, that the edit, all step by step, please. (time)
    3) Explain why bother to inform it on the server side, if the problem is with a particular client, I think it is not worth, do not understand the meaning of display - if the error is on the client side. If it does not play a role, what he did I can notify?

  4. #4
    Join Date
    September 2012
    Posts
    6,079
    Quote Originally Posted by SilentStorm View Post
    It looks like you have created an ini File for the Server (or specified the following in other places) and specified "212.12.*.*" as voice_ip, filetranfer_ip or query_ip. Obviously that is not a valid IP Address and hence causes that Error. The Server still works because it's using 0.0.0.0 instead which is whatever IP(s) the Machine running the Server has available.

    Please edit whatever place you specified that Value and replace it by 0.0.0.0
    3) So the owner knows some invalid data was received? If you don't need / want this information, just ignore it.

  5. #5
    Join Date
    June 2011
    Location
    Russian Federation
    Posts
    204
    thank you tell me about the 2 and 3 problems !?

  6. #6
    Join Date
    June 2008
    Posts
    18,506
    2. We can not do anything from here. This is system/os related. Peter explained it already.
    3. This happens, when an older client than last stable connects to your server. Or when an beta user connects and ask for new feature on an old server. (these are examples and nothing, to worry about)

    do not bump this thread without any new information or question please.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Replies: 1
    Last Post: August 19th, 2012, 12:30 AM
  2. Replies: 5
    Last Post: May 26th, 2012, 08:44 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
  •