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 15 of 22

Hybrid View

  1. #1
    Join Date
    June 2011
    Location
    Russian Federation
    Posts
    204

    resolving '212.12.*.*.' to binary ip failed, using 0.0.0.0 instead

    Put the latest server version 3.0.6, per day, and after that I see in the logs:
    Code:
    2012-06-22 11:25:04.611287|ERROR   |              |   | resolving '212.12.*.*.' to binary ip failed, using 0.0.0.0 instead
    2012-06-22 14:10:53.903978|ERROR   |              |   | resolving '212.12.*.*.' to binary ip failed, using 0.0.0.0 instead
    2012-06-22 14:15:30.169065|ERROR   |              |   | resolving '212.12.*.*.' to binary ip failed, using 0.0.0.0 instead
    what it is and how to solve?

    ---merged---

    TS Version: 3.0.6 (21.06.2012 8:43:35) on Linux
    OS: Linux (debian)

    where and what I need to edit the error was no more, because today is the same, another appeared in the logs!?
    Last edited by dante696; June 25th, 2012 at 11:50 AM.

  2. #2
    Join Date
    January 2010
    Location
    Germany
    Posts
    2,029
    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. #3
    Join Date
    June 2011
    Location
    Russian Federation
    Posts
    204
    Thank you for your reply.

    I have one VPS, running 2 physical server, 2 different licenses, 2 different databases (sqlite)

    @: the first server for the Public, I run it: ./ts3server_startscript.sh
    @: a second server for a large clan, I run it: ./ts3server_startscript.sh inifile=ts3server.ini

    Code:
    machine_id=2
    default_voice_port=9988 (port of the second physical server)
    voice_ip=212.12.*.*
    licensepath=
    filetransfer_port=30333 (Port 30333 - 30033 because the server is busy Public)
    filetransfer_ip=212.12.*.*
    query_port=10111 (Port 10111 - 10011 because the server is busy Public)
    query_ip=212.12.*.*
    query_ip_whitelist=query_ip_whitelist.txt
    query_ip_blacklist=query_ip_blacklist.txt
    dbplugin=ts3db_sqlite3
    dbpluginparameter=
    dbsqlpath=sql/
    dbsqlcreatepath=create_sqlite/
    dbconnections=10
    logpath=logs
    logquerycommands=0
    dbclientkeepdays=30
    error occurs on the server that is Public, error occurs on the server that is Public, that is, the server that is running just the usual script ./ts3server_startscript.sh
    but the fact that the server that is running a clan script ./ts3server_startscript.sh inifile=ts3server.ini error in the logs are not to be. But only in his ini file to specify the exact ip instead of 0.0.0.0.

    I understand how you want to replace in the ini file to 212.12.*.* to 0.0.0.0 !?
    the fact is un specified only on a clan server. It is specified un 212.12.*.*
    But in the logs it does not have nothing to

  4. #4
    Join Date
    January 2010
    Location
    Germany
    Posts
    2,029
    Im sorry to say that I didn't understand 50% of your Post but anyway...

    In the ts3server.ini File replace all 212.12.*.* with 0.0.0.0 (or a valid IP that is bindable) then start the Server. I also hope all those Comments in above Code Block are NOT in your File!

  5. #5
    Join Date
    June 2011
    Location
    Russian Federation
    Posts
    204
    I'm sorry I use a translator ....
    I understand you completely ... try and accomplish your goal. Not to close the topic!

  6. #6
    Join Date
    June 2012
    Posts
    2

    error resolving

    Hello all! After I updated the server to version 3.0.6 and 3.0.6.1, I in ravines had unclear error's:
    Code:
    2012-06-30 09:43:54.959866|ERROR   |              |   | resolving '*.*.*.*.' to binary ip failed, using 0.0.0.0 instead
    2012-06-30 10:10:12.328450|ERROR   |              |   | resolving '*.*.*.*.' to binary ip failed, using 0.0.0.0 instead
    2012-06-30 11:05:11.334444|ERROR   |              |   | resolving '*.*.*.*.' to binary ip failed, using 0.0.0.0 instead
    2012-06-30 13:11:28.925044|ERROR   |              |   | resolving '*.*.*.*.' to binary ip failed, using 0.0.0.0 instead
    2012-06-30 15:25:41.260899|ERROR   |              |   | resolving '*.*.*.*.' to binary ip failed, using 0.0.0.0 instead
    the server is started, with ts3server.ini, ip there everywhere is specified 0.0.0.0

    VPS: Debian
    TeamSpeak: 3.0.6

    All versions to 3.0.6 - were without mistakes, after updating such mistakes, the server works well, at this mistake all people work, simply it would be desirable to learn the reason!

  7. #7
    Join Date
    June 2008
    Posts
    18,510
    Are you sure, that your ip has not changed and maybe the same error message also appeared on server 3.0.6?
    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?

  8. #8
    Join Date
    June 2012
    Posts
    2
    Hello, thank you that answered my message and! I can tell with confidence that at me IP didn't change! and within half a year should what works at provider. All this occurred after updating of the server of the hardware on 3.0.6. and 3.0.6.1

  9. #9
    Join Date
    June 2011
    Location
    Russian Federation
    Posts
    204
    developers so it is possible to make with it?

  10. #10
    Join Date
    June 2008
    Posts
    18,510
    Quote Originally Posted by Ar2rJke View Post
    developers so it is possible to make with it?
    What? I don't understand your question.

    I can bind my Ip and the server does start
    Code:
    2012-07-02 11:22:39.042030|INFO    |ServerLibPriv |   | TeamSpeak 3 Server 3.0.6.1 (2012-06-29 04:29:45)
    2012-07-02 11:22:39.043030|INFO    |DatabaseQuery |   | dbPlugin name:    SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
    2012-07-02 11:22:39.043030|INFO    |DatabaseQuery |   | dbPlugin version: 3.7.3
    2012-07-02 11:22:39.044030|INFO    |DatabaseQuery |   | checking database integrity (may take a while)
    2012-07-02 11:22:39.091033|INFO    |ServerLibPriv |   | updated server query admin password
    2012-07-02 11:22:39.562060|INFO    |Accounting    |   | Licensing Information
    2012-07-02 11:22:39.562060|INFO    |Accounting    |   | type              : Non-profit
    2012-07-02 11:22:39.562060|INFO    |Accounting    |   | starting date     : Wed Jan 04 00:00:00 2012
    2012-07-02 11:22:39.562060|INFO    |Accounting    |   | ending date       : Sun Jan 06 00:00:00 2013
    2012-07-02 11:22:39.563060|INFO    |Accounting    |   | max virtualservers: 10
    2012-07-02 11:22:39.563060|INFO    |Accounting    |   | max slots         : 512
    2012-07-02 11:22:39.587061|INFO    |FileManager   |   | listening on 192.168.0.xxx:30033
    2012-07-02 11:22:39.588061|INFO    |VirtualSvrMgr |   | executing monthly interval
    2012-07-02 11:22:39.589061|INFO    |VirtualSvrMgr |   | reset virtualserver traffic statistics
    2012-07-02 11:22:39.669066|INFO    |CIDRManager   |   | updated query_ip_blacklist ips: 123.123.132.113, 
    2012-07-02 11:22:39.669066|INFO    |CIDRManager   |   | updated query_ip_whitelist ips: 127.0.0.1, 123.123.132.123, 
    2012-07-02 11:22:39.670066|INFO    |Query         |   | listening on 192.168.0.xxx:10011
    2012-07-02 11:27:49.209770|INFO    |GetWanIP      |   | WAN ip: xxx.xxx.xxx.xxx
    Code:
    2012-07-02 11:22:39.669066|INFO    |VirtualServer |  1| listening on 192.168.0.xxx:9987

    My entries in my server.ini
    Code:
    default_voice_port=9987
    voice_ip=192.168.0.xxx
    filetransfer_port=30033
    filetransfer_ip=192.168.0.xxx
    query_port=10011
    query_ip=192.168.0.xxx
    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?

  11. #11
    Join Date
    September 2007
    Location
    California
    Posts
    6

    Server Bound to 0.0.0.0

    What is happening?

    Code:
    sh-4.1$ ./ts3server_minimal_runscript.sh
    2012-07-03 05:47:04.366707|INFO    |ServerLibPriv |   | TeamSpeak 3 Server 3.0.6.1 (2012-06-29 07:59:05)
    2012-07-03 05:47:04.368385|INFO    |DatabaseQuery |   | dbPlugin name:    SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
    2012-07-03 05:47:04.368455|INFO    |DatabaseQuery |   | dbPlugin version: 3.7.3
    2012-07-03 05:47:04.368854|INFO    |DatabaseQuery |   | checking database integrity (may take a while)
    2012-07-03 05:47:04.413762|WARNING |Accounting    |   | Unable to find valid license key, falling back to limited functionality
    2012-07-03 05:47:04.444979|INFO    |FileManager   |   | listening on 0.0.0.0:30033
    2012-07-03 05:47:04.605509|INFO    |VirtualServer |  1| listening on 0.0.0.0:9987
    2012-07-03 05:47:04.606429|INFO    |CIDRManager   |   | updated query_ip_whitelist ips: 127.0.0.1,
    2012-07-03 05:47:04.607784|INFO    |Query         |   | listening on 0.0.0.0:10011
    Code:
    machine_id=
    default_voice_port=9987
    voice_ip=198.245.59.65
    licensepath=
    filetransfer_port=30033
    filetransfer_ip=198.245.59.65
    query_port=10011
    query_ip=198.245.59.65
    query_ip_whitelist=query_ip_whitelist.txt
    query_ip_blacklist=query_ip_blacklist.txt
    dbplugin=ts3db_sqlite3
    dbpluginparameter=
    dbsqlpath=sql/
    dbsqlcreatepath=create_sqlite/
    dbconnections=10
    logpath=logs
    logquerycommands=0
    dbclientkeepdays=30
    logappend=0
    When I try to connect to the server I get

    Code:
    <22:05:14>  Trying to connect to server on 198.245.59.65
    <22:05:20>  Failed to connect to server
    ---------------merged---------------

    Code:
    machine_id=
    default_voice_port=9987
    voice_ip=0.0.0.0
    licensepath=
    filetransfer_port=30033
    filetransfer_ip=0.0.0.0
    query_port=10011
    query_ip=0.0.0.0
    query_ip_whitelist=query_ip_whitelist.txt
    query_ip_blacklist=query_ip_blacklist.txt
    dbplugin=ts3db_sqlite3
    dbpluginparameter=
    dbsqlpath=sql/
    dbsqlcreatepath=create_sqlite/
    dbconnections=10
    logpath=logs
    logquerycommands=0
    dbclientkeepdays=30
    logappend=0
    Doesn't work either

    ---------------merged---------------

    Code:
    Chain INPUT (policy ACCEPT)
    target     prot opt source               destination
    
    Chain FORWARD (policy ACCEPT)
    target     prot opt source               destination
    
    Chain OUTPUT (policy ACCEPT)
    target     prot opt source               destination
    Current IP Tables

    ----------merged-----------

    I'm still trying to figure out why I cant connect to my teamspeak server...

    <01:04:58> Trying to connect to server on 198.245.59.65
    <01:05:04> Failed to connect to server

    is what it says even though the server is running.

    Still isn't working =/ is anything wrong? by looking at my settings?

    Edit: also I didn't have an OLD server this is a completely fresh install I just put it on the server like an hour ago.

    in version 3.0.5 not what mistakes weren't, and in settings interface who nothing changed.
    Last edited by dante696; July 3rd, 2012 at 10:07 AM.

  12. #12
    Join Date
    July 2006
    Posts
    1,600

    resolving to binary ip failed

    I checked my server's logs and came upon this errors (Serverversion 3.0.6.1):

    Code:
    2012-08-15 13:12:03.620126|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-15 17:06:33.972160|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-15 22:15:42.601877|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-17 11:58:33.268864|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-18 14:06:09.585633|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-18 15:00:24.536588|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-19 17:32:20.847950|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-19 20:18:19.486270|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-23 09:58:30.604515|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
    2012-08-23 09:58:52.467043|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
    2012-08-23 21:26:45.027493|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-24 08:19:08.404707|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-24 08:49:00.757839|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-24 09:19:02.939241|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-24 11:51:38.135232|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    I replaced my server's wan ip with xxx.xxx.xxx.xxx. (but notice the dot at the end of the string).

    Does anyone know why and how this error occurs?

    This thread was merged from a moderator
    Last edited by dante696; August 24th, 2012 at 02:55 PM.

  13. #13
    Join Date
    June 2011
    Location
    Russian Federation
    Posts
    204
    I still have the same inifile because the answer was not who did not say all that I have written is to edit inifile put ip 0.0.0.0. I tried in the end nothing happened. tried to enter my external IP - all the same. deleted inifile run standard server - all the same. and this is all after version 3.0.6

  14. #14
    Join Date
    July 2006
    Posts
    1,600
    Quote Originally Posted by maxi1990 View Post
    I checked my server's logs and came upon this errors (Serverversion 3.0.6.1):

    Code:
    2012-08-15 13:12:03.620126|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-15 17:06:33.972160|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-15 22:15:42.601877|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-17 11:58:33.268864|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-18 14:06:09.585633|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-18 15:00:24.536588|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-19 17:32:20.847950|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-19 20:18:19.486270|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-23 09:58:30.604515|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
    2012-08-23 09:58:52.467043|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
    2012-08-23 21:26:45.027493|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-24 08:19:08.404707|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-24 08:49:00.757839|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-24 09:19:02.939241|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-24 11:51:38.135232|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    I replaced my server's wan ip with xxx.xxx.xxx.xxx. (but notice the dot at the end of the string).

    Does anyone know why and how this error occurs?

    This thread was mered from a moderator
    Thanks for merging the threads.
    However, my server works flawlessly and I did not experience any problems but I still wonder why or how this error appears.
    All binding is set to 0.0.0.0 and was never set to anything else.

  15. #15
    Join Date
    December 2009
    Location
    Germany
    Posts
    4
    Hi, sorry for reactivating the old thread. But I am encountering the same problem with my Ubuntu server. The error message "resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead" continues to appear, although all bindings (voice/query/filetransfer) are set to 0.0.0.0 in the inifile. The external ip xxx.xxx.xxx.xxx isn't mentioned anywhere in my configuration. The .ini is being loaded correctly. It is not a big deal because the server is working properly, but nevertheless it annoys me seeing this error message popping up in the log all the time and being unable to fix it.
    Are there any new ideas on how to solve this issue?

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Music bound to a channel
    By Toelieloe in forum General Questions
    Replies: 1
    Last Post: May 9th, 2013, 07:50 PM
  2. TS3 - Website registration and Nickname bound tokens
    By Frederikoo in forum Linux / FreeBSD
    Replies: 1
    Last Post: December 27th, 2010, 09:38 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
  •