Hello,
I have an issue with my TeamSpeak 3 Linux server. The server logs constantly show the following warning message:
WARNING |Connection | |packet dropped because max packet cache size reached
Could you please explain what causes this issue and what I should do to fix it?
Does this warning have any negative impact on my server performance, voice quality, or client connections?
My server is running TeamSpeak 3 on Linux.
Thank you.
This warning indicates that the TeamSpeak server has dropped packets because the internal packet cache reached its maximum size; …who would’ve thought?
This can occur due to an unstable network connection, packet loss, or high server load.
However, the warning itself is not necessarily critical. If it only appears occasionally and there are no issues such as voice dropouts, connection interruptions, or increased latency, there is generally no need to worry.
If the warning occurs continuously or users are experiencing voice or connection issues at the same time, please let us know. This will help us narrow down the underlying issue.
There is another issue that may or may not be related to this problem.
Recently, my TeamSpeak server sometimes becomes unreachable after running for a period of time (for example, after 2 hours, 5 hours, or sometimes 1 day). The server suddenly times out, and after a few seconds it becomes accessible again.
When it reconnects, the server uptime is reset to zero, which means the TeamSpeak server appears to have crashed and restarted.
I checked the TeamSpeak system logs and found the following errors. Could you please help me understand what is causing this issue and what steps I should take to fix it?
Thank you.
root@TG-38314:\~# journalctl -u teamspeak --since “10 days ago” --no-pager
Jul 06 15:15:52 TG-38314 systemd\[1\]: Stopping TeamSpeak 3 Server…
Jul 06 15:17:22 TG-38314 systemd\[1\]: teamspeak.service: Stopping timed out. Terminating.
Jul 06 15:17:22 TG-38314 ts3server_startscript.sh\[3534335\]: Stopping the TeamSpeak 3 server …
Jul 06 15:17:22 TG-38314 systemd\[1\]: teamspeak.service: Control process exited, code=killed, status=15/TERM
Jul 06 15:17:22 TG-38314 systemd\[1\]: teamspeak.service: Failed with result ‘timeout’.
Jul 06 15:17:22 TG-38314 systemd\[1\]: Stopped TeamSpeak 3 Server.
Jul 06 15:17:22 TG-38314 systemd\[1\]: teamspeak.service: Consumed 6d 49min 59.868s CPU time.
Jul 06 15:17:27 TG-38314 systemd\[1\]: Starting TeamSpeak 3 Server…
Jul 06 15:17:27 TG-38314 ts3server_startscript.sh\[3534536\]: Starting the TeamSpeak 3 server
Jul 06 15:17:27 TG-38314 ts3server_startscript.sh\[3534536\]: TeamSpeak 3 server started, for details please view the log file
Jul 06 15:17:27 TG-38314 systemd\[1\]: Started TeamSpeak 3 Server.
Jul 06 16:43:57 TG-38314 systemd\[1\]: teamspeak.service: Main process exited, code=killed, status=7/BUS
Jul 06 16:43:57 TG-38314 systemd\[1\]: teamspeak.service: Failed with result ‘signal’.
Jul 06 16:43:57 TG-38314 systemd\[1\]: teamspeak.service: Consumed 1h 28min 986ms CPU time.
Jul 06 16:44:12 TG-38314 systemd\[1\]: teamspeak.service: Scheduled restart job, restart counter is at 1.
Jul 06 16:44:12 TG-38314 systemd\[1\]: Stopped TeamSpeak 3 Server.
Jul 06 16:44:12 TG-38314 systemd\[1\]: teamspeak.service: Consumed 1h 28min 986ms CPU time.
Jul 06 16:44:12 TG-38314 systemd\[1\]: Starting TeamSpeak 3 Server…
Jul 06 16:44:12 TG-38314 ts3server_startscript.sh\[3536137\]: Starting the TeamSpeak 3 server
Jul 06 16:44:12 TG-38314 ts3server_startscript.sh\[3536137\]: TeamSpeak 3 server started, for details please view the log file
Jul 06 16:44:12 TG-38314 systemd\[1\]: Started TeamSpeak 3 Server.
Jul 06 18:47:09 TG-38314 systemd\[1\]: Stopping TeamSpeak 3 Server…
Jul 06 18:47:11 TG-38314 ts3server_startscript.sh\[3552568\]: Stopping the TeamSpeak 3 server ..
Jul 06 18:47:11 TG-38314 ts3server_startscript.sh\[3552568\]: done
Jul 06 18:47:11 TG-38314 systemd\[1\]: teamspeak.service: Deactivated successfully.
Jul 06 18:47:11 TG-38314 systemd\[1\]: Stopped TeamSpeak 3 Server.
Jul 06 18:47:11 TG-38314 systemd\[1\]: teamspeak.service: Consumed 2h 2min 11.341s CPU time.
Jul 06 18:47:15 TG-38314 systemd\[1\]: Starting TeamSpeak 3 Server…
Jul 06 18:47:15 TG-38314 ts3server_startscript.sh\[3552585\]: Starting the TeamSpeak 3 server
Jul 06 18:47:15 TG-38314 ts3server_startscript.sh\[3552585\]: TeamSpeak 3 server started, for details please view the log file
Jul 06 18:47:15 TG-38314 systemd\[1\]: Started TeamSpeak 3 Server.
Jul 06 22:54:14 TG-38314 systemd\[1\]: teamspeak.service: Main process exited, code=killed, status=6/ABRT
Jul 06 22:54:14 TG-38314 systemd\[1\]: teamspeak.service: Failed with result ‘signal’.
Jul 06 22:54:14 TG-38314 systemd\[1\]: teamspeak.service: Consumed 4h 35min 54.156s CPU time.
Jul 06 22:54:29 TG-38314 systemd\[1\]: teamspeak.service: Scheduled restart job, restart counter is at 1.
Jul 06 22:54:29 TG-38314 systemd\[1\]: Stopped TeamSpeak 3 Server.
Jul 06 22:54:29 TG-38314 systemd\[1\]: teamspeak.service: Consumed 4h 35min 54.156s CPU time.
Jul 06 22:54:29 TG-38314 systemd\[1\]: Starting TeamSpeak 3 Server…
Jul 06 22:54:29 TG-38314 ts3server_startscript.sh\[3556954\]: Starting the TeamSpeak 3 server
Jul 06 22:54:29 TG-38314 ts3server_startscript.sh\[3556954\]: TeamSpeak 3 server started, for details please view the log file
Jul 06 22:54:29 TG-38314 systemd\[1\]: Started TeamSpeak 3 Server.
Jul 06 23:07:01 TG-38314 systemd\[1\]: Stopping TeamSpeak 3 Server…
Jul 06 23:08:31 TG-38314 systemd\[1\]: teamspeak.service: Stopping timed out. Terminating.
Jul 06 23:08:31 TG-38314 systemd\[1\]: teamspeak.service: Control process exited, code=killed, status=15/TERM
Jul 06 23:08:31 TG-38314 ts3server_startscript.sh\[3557286\]: Stopping the TeamSpeak 3 server …
Jul 06 23:08:31 TG-38314 systemd\[1\]: teamspeak.service: Failed with result ‘timeout’.
Jul 06 23:08:31 TG-38314 systemd\[1\]: Stopped TeamSpeak 3 Server.
Jul 06 23:08:31 TG-38314 systemd\[1\]: teamspeak.service: Consumed 9min 49.716s CPU time.
Jul 06 23:08:31 TG-38314 systemd\[1\]: Starting TeamSpeak 3 Server…
Jul 06 23:08:31 TG-38314 ts3server_startscript.sh\[3557477\]: Starting the TeamSpeak 3 server
Jul 06 23:08:31 TG-38314 ts3server_startscript.sh\[3557477\]: TeamSpeak 3 server started, for details please view the log file
Jul 06 23:08:31 TG-38314 systemd\[1\]: Started TeamSpeak 3 Server.
Based on the logs you provided, the TeamSpeak server process is crashing and being automatically restarted by systemd. This explains why the server becomes temporarily unreachable and why the uptime is reset.
The entries status=7/BUS and status=6/ABRT indicate that the server process terminated unexpectedly. However, the journal output alone does not provide enough information to determine the underlying cause, nor does it confirm that this is related to the packet cache warning.
To investigate this further, we would need to see the TeamSpeak server logs from immediately before the crashes. If your system uses systemd-coredump, please run coredumpctl list and coredumpctl info on the machine hosting your TeamSpeak server and share the output. If coredumpctl is not available or does not list any entries, please let us know.
Additionally, please share the output of systemctl cat TeamSpeak.
With the TeamSpeak logs and any available core dump information, we should be able to narrow down the cause of the crashes.
Hello,
I have collected many logs to help identify the cause of the issue. I have placed them all into a ZIP file, which you can download using the link below.
I believe the ZIP file size is around 400 KB.
Please review the logs. The most important one is the TS-log, so please make sure to check that file carefully.
I have also included the other information you requested in the ZIP file, which you can review as well.
Thank you for your help.
root@TG-38314:~# coredumpctl list
No coredumps found.
root@TG-38314:~# coredumpctl info
No match found.
root@TG-38314:~# systemctl cat TeamSpeak
[Unit]
Description=TeamSpeak 3 Server
After=network.target
[Service]
WorkingDirectory=/home/TeamSpeak/TeamSpeak 3-server_linux_amd64
User=TeamSpeak
Group=TeamSpeak
Type=forking
ExecStart=/home/TeamSpeak/TeamSpeak 3-server_linux_amd64/ts3server_startscript.sh start inifile=ts3server.ini
ExecStop=/home/TeamSpeak/TeamSpeak 3-server_linux_amd64/ts3server_startscript.sh stop
PIDFile=/home/TeamSpeak/TeamSpeak 3-server_linux_amd64/ts3server.pid
RestartSec=15
Restart=always
[Install]
WantedBy=multi-user.target
Link all Log : Gofile - Cloud Storage Made Simple
Thank you for providing the logs.
After reviewing them, I could not find a clear indication of what is causing the TeamSpeak server process to terminate unexpectedly.
The service configuration appears to be normal, and there are no obvious signs of memory or storage exhaustion. Additionally, no core dumps were generated, so unfortunately there is no additional information available regarding the SIGBUS and SIGABRT events.
One thing I noticed is the large number of resend timeout and ping timeout entries throughout the TeamSpeak logs. These indicate that many client connections are experiencing packet loss or network interruptions. However, this doesn’t explain the server crashes themselves, so I cannot confirm that the two issues are related.
Could you also let us know which Linux distribution and version you are running, and whether the server is hosted on a VPS or a dedicated machine?
Additionally, have you observed any kernel messages or hardware-related errors around the time of the crashes (e.g. in dmesg or journalctl -k)?
Hello,
I have collected and included all the information that could help us identify the cause of the issue in the ZIP file.
I have added the items you requested, along with other relevant logs and system information that may help with further investigation.
Please download the ZIP file from the link below and review it again.
Thank you very much for your time and support.
Thank you for providing the additional logs.
After reviewing them, I found one important detail that was not visible in the previous logs. The kernel log contains a segmentation fault (segfault) for the ts3server process, confirming that the TeamSpeak server itself is crashing unexpectedly.
Unfortunately, the available logs do not provide enough information to determine what is causing the segmentation fault. As no core dump was generated, there is no stack trace available for further analysis.
I also noticed the large number of resend timeout and ping timeout entries throughout the TeamSpeak logs. These indicate that many client connections are experiencing packet loss or network interruptions. However, these messages do not explain the segmentation fault, so I cannot confirm that the two issues are related.
I also noticed that you are currently running TeamSpeak Server v3.13.7. Before investigating this any further, I recommend updating to the latest available TeamSpeak 3 server version, v3.13.8, as it includes bug fixes and security updates.
If the crashes persist after updating, please let us know. At this point, the logs confirm that the TeamSpeak server process is crashing, but they do not provide enough information to determine the root cause of the segmentation fault.
I have decided to install the new TeamSpeak Server version 3.13.8 on my server, but I have a question.
I want to make sure that all of my current server data is backed up and transferred to the new version, including:
All channels on my server
Ban list
Server groups and ranks
Rank icons
Server Group IDs (SGIDs)
All other important server settings and configurations
Could you please tell me exactly which files from my current TeamSpeak Server version 3.13.7 I need to back up and move to the new 3.13.8 installation?
Also, please explain the correct migration procedure step by step so I can transfer everything safely without losing any data.
Thank you very much.
Since you are only updating from TeamSpeak Server v3.13.7 to v3.13.8, there is no special migration procedure required.
Before updating, I recommend creating a complete backup of your current TeamSpeak server directory. This will ensure that your database (ts3server.sqlitedb), uploaded files, icons, configuration files, and any other custom data are preserved.
As long as you keep your existing ts3server.sqlitedb, your channels, ban list, server groups, permissions, server group IDs, rank icons, and other server settings will remain intact after the update.
For the update procedure itself, I would like to refer you to the following guide:
The guide describes the recommended update procedure step by step, including how to properly stop the server, create a backup, replace the server files, and start the updated server again.
If you follow these steps, you should be able to update to v3.13.8 without losing your existing server data.
Hello,
I installed the latest TeamSpeak Server version 3.13.8, and most of the previous issues have been resolved.
However, I am now seeing a new warning message repeatedly in the TeamSpeak server logs:
2026-07-15 16:23:27.976844|WARNING |Connection | |Resending packet missed arrival window
2026-07-15 16:23:28.003669|WARNING |Connection | |Resending packet missed arrival window
Could you please clarify what exactly causes this issue?
My main problem is that many users are frequently getting disconnected from the server. I would like to know whether this is related to:
Could you please help me identify the exact cause and suggest what I should check or change?
Thank you.
This warning indicates that a packet had to be retransmitted, but its expected arrival window had already passed. In most cases, this is caused by network-related issues such as packet loss, unstable connections, or high latency. By itself, however, the warning does not provide enough information to determine the exact cause.
Since you also mentioned that users are frequently disconnecting, the warning may be related to the connection issues. However, we would need to review the complete TeamSpeak server log from the time the disconnects occur to investigate this further.
Could you please provide the complete TeamSpeak server log covering the period in which these warnings and the client disconnects occur?
Additionally, please let us know whether all users disconnect at the same time or whether the issue only affects individual users. This will help determine whether the problem is more likely to be related to the server’s network connection or to individual client connections.