search

TeamSpeak-Systems / teamspeak-linux-docker-images

docker build files for TeamSpeak servers
Other
114 stars 52 forks source link

Accounting: Error contacting server RESOLVE_ERROR: Host not found (non-authoritative) #35

Closed Questlog closed 4 years ago

Questlog commented 4 years ago

Hey, I have this issue that my Teamspeak server is able to do everything except resolve the Hostame of accounting2.teamspeak.com.

2019-08-18 07:36:07.853863|INFO    |ServerLibPriv |   |TeamSpeak 3 Server 3.9.1 (2019-07-02 13:17:23)
2019-08-18 07:36:07.853945|INFO    |ServerLibPriv |   |SystemInformation: Linux 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 Binary: 64bit
2019-08-18 07:36:07.853968|INFO    |ServerLibPriv |   |Using hardware aes
2019-08-18 07:36:07.854115|INFO    |DatabaseQuery |   |dbPlugin name:    SQLite3 plugin, Version 3, (c)TeamSpeak Systems GmbH
2019-08-18 07:36:07.854143|INFO    |DatabaseQuery |   |dbPlugin version: 3.11.1
2019-08-18 07:36:07.854239|INFO    |DatabaseQuery |   |checking database integrity (may take a while)
2019-08-18 07:36:08.044709|INFO    |SQL           |   |database updated successfully to revision: 32
2019-08-18 07:36:08.045391|INFO    |DatabaseQuery |   |database busy, waiting for finishing index tasks, may take some time!
2019-08-18 07:36:48.108056|INFO    |Accounting    |   |Licensing Information
2019-08-18 07:36:48.108113|INFO    |Accounting    |   |type              : Non-Profit License
2019-08-18 07:36:48.108157|INFO    |Accounting    |   |starting date     : Mon May 13 00:00:00 2019
2019-08-18 07:36:48.108210|INFO    |Accounting    |   |ending date       : Wed Nov 13 00:00:00 2019
2019-08-18 07:36:48.108251|INFO    |Accounting    |   |max virtualservers: 10
2019-08-18 07:36:48.108288|INFO    |Accounting    |   |max slots         : 512
2019-08-18 07:36:48.141810|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-08-18 07:36:48.580562|INFO    |              |   |Puzzle precompute time: 453
2019-08-18 07:36:48.580823|INFO    |FileManager   |   |listening on 0.0.0.0:30033
2019-08-18 07:36:48.624339|INFO    |Query         |   |listening for query on 0.0.0.0:10011
2019-08-18 07:36:48.624480|INFO    |Query         |   |listening for query ssh on 0.0.0.0:10022
2019-08-18 07:36:48.624559|INFO    |CIDRManager   |   |updated query_ip_whitelist ips: 127.0.0.1/32, ::1/128,
2019-08-19 07:36:48.297166|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-08-20 07:36:48.349982|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-08-21 07:36:48.414763|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-08-22 07:36:48.513870|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-08-23 07:36:48.619805|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-08-24 07:36:48.722937|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-08-25 07:36:48.818401|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-08-26 07:36:48.930666|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-08-27 07:36:49.026239|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-08-28 07:36:49.124153|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-08-29 07:36:49.221283|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-08-30 07:36:49.326039|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-08-31 07:36:49.422871|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-09-01 00:00:48.178261|INFO    |VirtualSvrMgr |   |executing monthly interval
2019-09-01 00:00:48.178909|INFO    |VirtualSvrMgr |   |reset virtualserver traffic statistics
2019-09-01 07:36:49.527806|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-09-02 07:36:49.628393|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-09-03 07:36:49.761873|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-09-04 07:36:49.868373|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-09-05 07:36:49.962651|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-09-05 10:37:53.174543|ERROR   |Accounting    |   |Error contacting server https://accounting2.teamspeak.com: RESOLVE_ERROR: Host not found (non-authoritative), try again later
2019-09-05 10:37:58.181066|ERROR   |Accounting    |   |Error contacting server https://backupaccounting2.teamspeak.com: RESOLVE_ERROR: Host not found (non-authoritative), try again later
2019-09-05 14:37:53.167755|ERROR   |Accounting    |   |Error contacting server https://accounting2.teamspeak.com: RESOLVE_ERROR: Host not found (non-authoritative), try again later
2019-09-05 14:37:55.062264|ERROR   |Accounting    |   |Error contacting server https://backupaccounting2.teamspeak.com: RESOLVE_ERROR: Host not found (authoritative)

If I exec into the container I can do the following: 

/var/ts3server # nslookup accounting2.teamspeak.com
nslookup: can't resolve '(null)': Name does not resolve

Name:      accounting2.teamspeak.com
Address 1: 104.20.74.196
Address 2: 104.20.75.196

Nslookup kinda works. I get this first message with any alpine docker baseimage. It looks better if I use one of my DNS entries from /etc/resolv.conf.

/var/ts3server # cat /etc/resolv.conf
### Hetzner Online GmbH installimage
# nameserver config
nameserver 213.133.98.98
nameserver 213.133.100.100
nameserver 213.133.99.99
/var/ts3server # nslookup accounting2.teamspeak.com 213.133.98.98
Server:    213.133.98.98
Address 1: 213.133.98.98 ns1-coloc.hetzner.de

Name:      accounting2.teamspeak.com
Address 1: 104.20.74.196
Address 2: 104.20.75.196

Strange thing is that it takes solid 5 seconds to resolve the name, even with the DNS parameter. I don't know if it is missing a cache or something but on my Ubuntu 18.04.3 host it resolves instantly.

/var/ts3server # ping accounting2.teamspeak.com
PING accounting2.teamspeak.com (104.20.75.196): 56 data bytes
64 bytes from 104.20.75.196: seq=0 ttl=59 time=11.740 ms
64 bytes from 104.20.75.196: seq=1 ttl=59 time=11.611 ms
64 bytes from 104.20.75.196: seq=2 ttl=59 time=11.782 ms
64 bytes from 104.20.75.196: seq=3 ttl=59 time=11.678 ms
64 bytes from 104.20.75.196: seq=4 ttl=59 time=11.626 ms
64 bytes from 104.20.75.196: seq=5 ttl=59 time=11.792 ms
^C
--- accounting2.teamspeak.com ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 11.611/11.704/11.792 ms

Everything else works fine. It's running for several weeks without any issues. It can reach other servers, or else it would not have been able to download the myTeamSpeak identifier revocation list.

What I don't understand is how often Ts3 tries to reach accounting. I worry if I can't fix this and it does not retry it before Nov 13 the license will be gone. The last time I got this message was 14 days ago and before that at 2019-06-24. Is there any method to trigger it manually?

muenchow commented 4 years ago

the server checks for accounting every 1h. If he never could reach the accounting, he shuts down after 2h of waiting. If he could reach accounting at some point he instead waits for 24h.

You are right to worry, if the server can not reach accounting he will not be able to download the renewed license, and a non expired license is need for a accounting to be reached.

Questlog commented 4 years ago

It pulled the new license, seems like it was a short lived problem and worried too much. Thanks for the response!