Server Crash with bad file descriptor

Hello,
I have the problem that one of the my server crashes after a while. My other Servers are running without any problems. I think this has something to do with the error in the last line, but I am not sure.
This is the Log: 2020-02-03 17:12:32.407135|INFO |ServerLibPriv | |TeamSpeak 3 Server 3.11.0 - Pastebin.com (Sorry I can’t get the text correctly formatted in the forum.)
And I did a post in the old forum: TeamSpeak - Official TeamSpeak Community Forum

XLS202

Please ensure that /dev/shm is properly mounted

1 Like

The output from “df -h” is:

Filesystem      Size  Used Avail Use% Mounted on
udev             32G     0   32G   0% /dev
tmpfs           6.3G   25M  6.3G   1% /run
/dev/md2        438G  258G  158G  63% /
tmpfs            32G  4.0K   32G   1% /dev/shm
tmpfs           5.0M   20K  5.0M   1% /run/lock
tmpfs            32G     0   32G   0% /sys/fs/cgroup
/dev/md1        488M   70M  392M  16% /boot
/dev/sda1       3.6T  1.7T  1.8T  50% /mnt/4TB
tmpfs           6.3G     0  6.3G   0% /run/user/1000

so I think its properly mounted. And 3 other Servers don´t have a problem.

Maybe you updated the server incompletely.
Make sure to overwrite all server files in order to update the server.

1 Like

A week ago I completely deleted and reinstalled the server. So this should not be the problem.

moved by moderator. Forum got a search function. Please consider to use it before posting.

2023-05-18 20:46:03.302381|WARNING |Accounting    |   |Unable to open licensekey.dat, falling back to limited functionality

2023-05-18 20:46:02.686424|ERROR   |Accounting    |   |failed to register local accounting service: Bad file descriptor

recently our license expired and since my colleague had removed the license key file, so my question what must go instead?

& where do we get the “standard” licenses from?

We are using: DOCKER-COMPOSE

So, still there is the problem that the server crashes, with the same message.

My technician gave me the following to post here on the forum:

services:
  teamspeak:
    image: teamspeak
    restart: unless-stopped
    network_mode: "host" 
    ports:
      - 9987:9987/udp
      - 10011:10011
      - 30033:30033
    volumes:
      - /root/docker/container/teamspeak:/var/ts3server

    environment:
      TS3SERVER_DB_PLUGIN: ts3db_mariadb
      TS3SERVER_DB_SQLCREATEPATH: create_mariadb
      TS3SERVER_DB_HOST: XXXXXX
      TS3SERVER_DB_USER: XXXX
      TS3SERVER_DB_PASSWORD: XXXXX
      TS3SERVER_DB_NAME: XXXXXX
      TS3SERVER_LICENSE: accept
      TS3SERVER_QUERY_PROTOCOLS: raw, ssh

any infos to this problem?

→ my technician use the following website: Docker

everything done/ available (according to technician)

our mounts:

image

Hey,

I don’t think our problems are related. But maybe they are, so I share what I did to solve the problem: I had 4 different instances of the TeamSpeak Server running. 3 of them with the same License and one without a License. Then the Server without License started to crash.

I then requested an expansion of my License to 4 Servers and gave this Server also a license.
At the same time, I moved all of them in one Server instance with multiple VServers (or how ever it is called)

Maybe it will help you… or give you an idea for what to look :smiley:

we found this issue from 2019…

related to this solution: low memory ??

issue is still present… looks like not interested in fixing this…

All answers and information are given in the GitHub issue you did link.

Memory must be available and /dev/shm must be available all the time.

Not a Linux pro answering:
Not having any space on swap may cause issues. Doesn’t have to, but it can happen.

2 Likes