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

Page 1 of 3 123 LastLast
Results 1 to 15 of 37
  1. #1
    Join Date
    October 2004
    Location
    California
    Posts
    12

    ResolveHostName failed error: -2

    Anyone else seen this error?


    2010-03-06 08:17:46.597209|INFO |SQL | | pruning old database log entries where timestamp is older than 90 days
    2010-03-06 08:18:06.626516|DEVELOP | | | TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
    2010-03-06 08:18:06.654916|CRITICAL| | | TS3ANetwork::IPFamilyToAf SHOULD NOT REACH THIS

    Server shuts down after this pops up on the display. Is it really doing a reverse lookup on my key and failing? Just moved servers and the PTR has not poplulated fully yet. That is my only guess.

    If I pull my license dat file, it runs...


    DOUGH! This should have been in the server section.. sorry...
    Last edited by Psybertech; March 6th, 2010 at 08:28 AM. Reason: Had to note I was stupid and posted in the wrong section.

  2. #2
    Join Date
    October 2004
    Location
    California
    Posts
    12

    Thumbs down ResolveHostName failed error: -2

    2010-03-09 02:39:32.216488|DEVELOP | | | TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0


    If you get the above error... it is because your DNS Name servers are configured wrong on your server. You either do not have your set up or you are pointed to the wrong or no DNS servers to resolve to.
    Last edited by Psybertech; March 9th, 2010 at 04:29 AM.

  3. #3
    Join Date
    June 2008
    Posts
    18,513
    It Seems that, your DNS service isn't running on your server. The TeamSpeak server trys to reach an DNS address. Pleasce check that you DNS service is running.

  4. #4
    Join Date
    June 2012
    Posts
    17

    TS3ANetwork::ResolveHostName failed error: -2

    Hi,

    a few minutes ago my Server lost all Connection to all client for 5 minutes, but the Root-Server Running, website work etc. only one error was in the Instance log.

    TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0

    anyone know the issus?

    Scincerly Budy93

  5. #5
    Join Date
    December 2005
    Location
    Germany
    Posts
    164
    Maybe your server or its network was dropping some UDP packets in this 5 minutes.

  6. #6
    Join Date
    June 2012
    Posts
    17
    Hi,

    I have checked in my Iptables but all ports are Open(input and output)(udp: 53,9987,9989-9990; tcp:10011,2008,30033,2010,41144)
    or I'm missing a port?

    Sincerly Budy

    p.s. Sorry for my englisch.

  7. #7
    Join Date
    December 2005
    Location
    Germany
    Posts
    164
    Iptables doesn't log anything nor temporary network problems, therefore you have to check for this on another part. Has this happened multiple times now? Maybe your server provider had dropped UDP packets for some reason?

  8. #8
    Join Date
    June 2012
    Posts
    17
    Hi,

    not always only very rare, but it can also be due to provider network of my Server. Today I has the error TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11, in my Syslog I found a denied Package via Iptable Port 10011, from a TS Viewer website. I just want to test if this is the problem. I will reported back in 3 Days.

    Sincerly Budy

  9. #9
    Join Date
    June 2012
    Posts
    17
    Ok, after a long time the error is back, can the DOS protection blame for the problems?

    Sincerly Budy93

  10. #10
    Join Date
    November 2012
    Posts
    11

    TS3ANetwork connect failed and ResolveHostName failed

    I've been running my server for over a year now, and I've been running the 3.0.10 x64 (linux) server version for over a week or two.

    I'm running into the problem below on boot.

    I've got these ports open:
    2008 all out
    2010 all both
    8767 udp both
    9987 udp both
    9988 udp both
    10011 tcp in
    30033 tcp in

    Code:
    2013-10-15 23:29:11.251368|INFO    |ServerLibPriv |   | TeamSpeak 3 Server 3.0.10 (2013-09-27 10:13:58)
    2013-10-15 23:29:11.251583|INFO    |ServerLibPriv |   | SystemInformation: Linux 2.6.32-20130307.60.9.bh6.x86_64 #1 SMP Thu Mar 7 15:58:33 EST 2013 x86_64 Binary: 64bit
    2013-10-15 23:29:11.253119|INFO    |DatabaseQuery |   | dbPlugin name:    SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
    2013-10-15 23:29:11.253175|INFO    |DatabaseQuery |   | dbPlugin version: 3.7.3
    2013-10-15 23:29:11.253572|INFO    |DatabaseQuery |   | checking database integrity (may take a while)
    2013-10-15 23:29:33.946176|ERROR   |              |   | TS3ANetwork::Connect failed error: 110
    2013-10-15 23:29:33.946340|ERROR   |              |   | Unable to connect to primary address, trying secondary
    2013-10-15 23:29:33.966069|ERROR   |              |   | TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
    2013-10-15 23:29:33.969786|ERROR   |Accounting    |   | Unable to connect to accounting server
    2013-10-15 23:29:33.969832|INFO    |Accounting    |   | Licensing Information
    2013-10-15 23:29:33.969857|INFO    |Accounting    |   | type              : Non-profit
    2013-10-15 23:29:33.969913|INFO    |Accounting    |   | starting date     : Mon Jul  1 00:00:00 2013
    2013-10-15 23:29:33.969939|INFO    |Accounting    |   | ending date       : Fri Jan 17 00:00:00 2014
    2013-10-15 23:29:33.969960|INFO    |Accounting    |   | max virtualservers: 10
    2013-10-15 23:29:33.969978|INFO    |Accounting    |   | max slots         : 512
    2013-10-15 23:29:34.757728|INFO    |              |   | Puzzle precompute time: 771
    2013-10-15 23:29:34.758498|INFO    |FileManager   |   | listening on 67.222.48.89:30033
    2013-10-15 23:29:34.879241|INFO    |CIDRManager   |   | updated query_ip_whitelist ips: 127.0.0.1, 91.121.99.210, 68.45.184.116, 67.222.48.89, 80.190.145.215, 
    2013-10-15 23:29:34.881167|INFO    |Query         |   | listening on 67.222.48.89:10011
    2013-10-15 23:29:55.987083|ERROR   |              |   | TS3ANetwork::Connect failed error: 110
    2013-10-15 23:29:55.987249|ERROR   |              |   | Unable to connect to primary address, trying secondary
    2013-10-15 23:29:55.987408|ERROR   |              |   | TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0

  11. #11
    Join Date
    September 2013
    Location
    Germany
    Posts
    63
    The server wants to verify your NPL but it can't reach the accounting server.
    Try:
    Code:
    ping accounting.teamspeak.com

    If it works, you have to contact a staff member.

  12. #12
    Join Date
    November 2012
    Posts
    11
    I'm not able to do a ping command via SSH.

    I contacted customer service, and they've verified all my ports are still open as they were.
    Last edited by Drumstix42; October 21st, 2013 at 06:21 PM.

  13. #13
    Join Date
    November 2012
    Posts
    11
    CSR replied with this:

    I tried to ping accounting.teamspeak.com from your server and it appears that they have pings blocked. I also tried ping it from a VPS server I have that is not on our network and got the same error of icmp open socket: Operation not permitted


    A trace route show the following.

    ***@***.com [~]# traceroute accounting.teamspeak.com
    traceroute to accounting.teamspeak.com (80.190.145.215), 30 hops max, 60 byte packets
    1 66-147-240-3.unifiedlayer.com (66.147.240.3) 123.761 ms 123.843 ms 123.946 ms
    2 port100.ar04.prov.acedc.net (199.58.199.113) 7.624 ms 7.796 ms 7.794 ms
    3 te0-0-0-16.ccr21.slc01.atlas.cogentco.com (38.104.174.17) 1.604 ms 1.645 ms 1.719 ms
    4 be2089.mpd22.sfo01.atlas.cogentco.com (154.54.24.61) 22.990 ms be2086.ccr21.sfo01.atlas.cogentco.com (154.54.3.185) 22.434 ms 22.611 ms
    5 be2166.ccr21.sjc01.atlas.cogentco.com (154.54.28.70) 22.605 ms be2164.ccr21.sjc01.atlas.cogentco.com (154.54.28.34) 22.771 ms 22.656 ms
    6 be2000.ccr21.sjc03.atlas.cogentco.com (154.54.6.106) 23.122 ms be2047.ccr21.sjc03.atlas.cogentco.com (154.54.5.114) 23.156 ms 23.246 ms
    7 level3.sjc03.atlas.cogentco.com (154.54.11.118) 20.399 ms te-3-3.car3.SanJose1.Level3.net (4.68.110.137) 20.419 ms level3.sjc03.atlas.cogentco.com (154.54.11.118) 20.480 ms
    8 vlan80.csw3.SanJose1.Level3.net (4.69.152.190) 157.371 ms vlan60.csw1.SanJose1.Level3.net (4.69.152.62) 158.125 ms vlan70.csw2.SanJose1.Level3.net (4.69.152.126) 160.176 ms
    9 ae-61-61.ebr1.SanJose1.Level3.net (4.69.153.1) 157.846 ms ae-81-81.ebr1.SanJose1.Level3.net (4.69.153.9) 156.668 ms ae-91-91.ebr1.SanJose1.Level3.net (4.69.153.13) 159.198 ms
    10 ae-2-2.ebr2.NewYork1.Level3.net (4.69.135.186) 158.194 ms 158.035 ms 158.083 ms
    11 ae-62-62.csw1.NewYork1.Level3.net (4.69.148.34) 159.521 ms ae-82-82.csw3.NewYork1.Level3.net (4.69.148.42) 158.562 ms ae-72-72.csw2.NewYork1.Level3.net (4.69.148.38) 158.421 ms
    12 ae-61-61.ebr1.NewYork1.Level3.net (4.69.134.65) 160.595 ms 160.564 ms ae-91-91.ebr1.NewYork1.Level3.net (4.69.134.77) 159.235 ms
    13 ae-41-41.ebr2.London1.Level3.net (4.69.137.65) 157.142 ms ae-44-44.ebr2.London1.Level3.net (4.69.137.77) 171.565 ms 158.947 ms
    14 ae-23-23.ebr2.Frankfurt1.Level3.net (4.69.148.194) 158.052 ms ae-24-24.ebr2.Frankfurt1.Level3.net (4.69.148.198) 168.979 ms ae-21-21.ebr2.Frankfurt1.Level3.net (4.69.148.186) 157.895 ms
    15 ae-82-82.csw3.Frankfurt1.Level3.net (4.69.140.26) 158.579 ms ae-72-72.csw2.Frankfurt1.Level3.net (4.69.140.22) 159.475 ms ae-62-62.csw1.Frankfurt1.Level3.net (4.69.140.18) 157.949 ms
    16 ae-91-91.ebr1.Frankfurt1.Level3.net (4.69.140.13) 158.391 ms ae-61-61.ebr1.Frankfurt1.Level3.net (4.69.140.1) 158.386 ms ae-71-71.ebr1.Frankfurt1.Level3.net (4.69.140.5) 157.616 ms
    17 ae-1-19.bar1.Munich1.Level3.net (4.69.153.245) 159.535 ms 159.524 ms 159.455 ms
    18 IP-EXCHANGE.bar1.Munich1.Level3.net (62.140.24.174) 161.842 ms 162.265 ms 162.871 ms
    19 p2-94.rtr2.colo2.MUC2.content-colo.net (212.123.127.103) 161.167 ms 161.103 ms 161.188 ms
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *

  14. #14
    Join Date
    January 2010
    Location
    El Prat de Llobregat (Barcelona, Spain)
    Posts
    2,698
    As example, from home:
    Code:
    Microsoft Windows [Versión 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.
    
    C:\Users\PotaBlava>ping accounting.teamspeak.com
    
    Haciendo ping a accounting.teamspeak.com [80.190.145.215] con 32 bytes de datos:
    
    Respuesta desde 80.190.145.215: bytes=32 tiempo=127ms TTL=48
    Respuesta desde 80.190.145.215: bytes=32 tiempo=127ms TTL=48
    Respuesta desde 80.190.145.215: bytes=32 tiempo=125ms TTL=48
    Respuesta desde 80.190.145.215: bytes=32 tiempo=128ms TTL=48
    
    Estadísticas de ping para 80.190.145.215:
        Paquetes: enviados = 4, recibidos = 4, perdidos = 0
        (0% perdidos),
    Tiempos aproximados de ida y vuelta en milisegundos:
        Mínimo = 125ms, Máximo = 128ms, Media = 126ms
    
    C:\Users\PotaBlava>tracert accounting.teamspeak.com
    
    Traza a la dirección accounting.teamspeak.com [80.190.145.215]
    sobre un máximo de 30 saltos:
    
      1    <1 ms    <1 ms    <1 ms  192.168.1.1
      2    47 ms    48 ms    47 ms  84-18-16-1.usul.arrakis.es [84.18.16.1]
      3    62 ms    61 ms    62 ms  84-18-0-206.usul.arrakis.es [84.18.0.206]
      4    63 ms    62 ms    61 ms  t2a1-ge6-2.es-mad3.eu.bt.net [166.49.224.13]
      5    61 ms    61 ms    62 ms  t2c2-ge4-0.es-mad3.eu.bt.net [166.49.141.105]
      6    75 ms    79 ms    77 ms  t2c2-ge3-0-0.es-bar.eu.bt.net [166.49.195.138]
      7    77 ms    76 ms    75 ms  t2c1-ge6-1.es-bar.eu.bt.net [166.49.164.37]
      8   107 ms   106 ms   107 ms  t2c3-xe-11-0-0-0.nl-ams2.eu.bt.net [166.49.195.0]
      9   108 ms   108 ms   106 ms  asd-s17-rou-1041.NL.eurorings.net [195.69.146.108]
     10   109 ms   107 ms   110 ms  asd2-rou-1043.NL.eurorings.net [134.222.232.9]
     11   110 ms   110 ms   110 ms  rt2-rou-1022.NL.eurorings.net [134.222.199.104]
     12   128 ms   127 ms   129 ms  sdns-s1-rou-1101.FR.eurorings.net [134.222.232.118]
     13   127 ms   128 ms   127 ms  nntr-s1-rou-1101.FR.eurorings.net [134.222.232.85]
     14   124 ms   126 ms   123 ms  kehl-s2-rou-1103.DE.eurorings.net [134.222.227.121]
     15   128 ms   126 ms   127 ms  mchn-s1-rou-1102.DE.eurorings.net [134.222.230.241]
     16   127 ms   127 ms   126 ms  Tenge1-3.cr3.MUC1.content-core.net [134.222.112.62]
     17   128 ms   128 ms   128 ms  p1-93.rtr2.colo2.MUC2.content-colo.net [212.123.127.71]
     18   130 ms   127 ms   127 ms  80.190.145.215
    
    Traza completa.

  15. #15
    Join Date
    August 2013
    Location
    Poland
    Posts
    9
    What can I do when my server provider blocked all incoming connections from other countries due continous DDoS attack on my server?

    TS3 server can not validate NPL License and sometimes I have to restart serverinstance manually. Is there any solution for that?

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. ResolveHostName failed error: 4
    By notjohn in forum Linux / FreeBSD
    Replies: 2
    Last Post: December 8th, 2015, 05:07 AM
  2. TS3ANetwork::ResolveHostName failed error: -1
    By blzsr in forum Linux / FreeBSD
    Replies: 1
    Last Post: May 18th, 2010, 09:23 AM
  3. ResolveHostName failed error: -2
    By Psybertech in forum Server Support
    Replies: 0
    Last Post: March 9th, 2010, 02:42 AM
  4. ResolveHostName failed error: -2
    By Psybertech in forum General Questions
    Replies: 0
    Last Post: March 6th, 2010, 08:23 AM

Tags for this Thread

Posting Permissions

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