My server is located in Shanghai, China. Ping result to accounting2.teamspeak.com is as follows:
In the log file, I receive a triple message TS3ANetwork::Send failed error: 111 every 10 minutes. Only once in a single day I will get myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated.
And the last message in my log is Accounting | |failed to register local accounting service: Bad file descriptor. After this my server crashed, I have to restart it manually before I can connect to the server again.
For some reason, the shared memory became unavailable for the system (Bad file descriptor).This problem seems to be related to low memory that is available and yes, it needs a few bytes of shared memory, if all the shared memory is being used by other processes it will have problems. But for now, please make sure that you have enough shared memory is available on your system.
What have you for Server Version? Please make sure that you have the latest Server Version is installed (3.13.7) and that you turn off the Weblist. The Weblist report the server tries to send fails. As a local fix turning off reporting to the Weblist does fix this.
thanks a lot, my server version is exactly 3.13.7 and my memory amount is 2GiB, is that enough?
i’ll check the memory log of the entire server next time when ts server crashed
It depends on how many slots the server uses, but 2GB should be enough.
Another Question:
Have you opened all the necessary TeamSpeak ports? It could be that your Server hoster may miss a port forwarding or has a bad firewall config or maybe your Hoster block the Shared Memory at all.
Yes, both necessary and optional ports are opened. How can I make the Shared Memory available for the server process. My operation system is Ubuntu 22.04 64bit. I checked the memory usage of the last 14 days just now, but no case of excess usage detected.
In early August, my server encountered this issue. By resetting all the ports in the server, it mysteriously started working again. It reappeared yesterday, so I’m trying to turning off reporting to the Weblis this time.
I have used various services to check whether port 2010 is open on TeamSpeak’s side, and the result was that it is closed. Therefore, the request from the server cannot pass through to weblist.teamspeak.com.
