• Hey Guest, we're evolving the future of TeaSpeak.
    You're invited to join the discussion here!

Completed Server shutting down without issueing

Status
Not open for further replies.

razaq

Well-known member
Teaspeak log:
Code:
[2018-09-30 20:10:55] [ERROR] Timer ConnectedClient::tick needs more than 4508 microseconds. Max allowed was 2000 microseconds.
[2018-09-30 20:10:55] [ERROR]     3 | Ticking of client <ip> (<user>) needs more that 2500 microseconds! (7768 microseconds)
[2018-09-30 20:10:57] [DEBUG]     3 | [Property] Changed property in db key: client_month_online_time value: 734520
[2018-09-30 20:10:57] [DEBUG]     3 | [Property] Changed property in db key: client_total_online_time value: 734520
[2018-09-30 20:10:57] [ERROR] Timer ConnectedClient::tick needs more than 4407 microseconds. Max allowed was 2000 microseconds.
[2018-09-30 20:10:57] [ERROR]     3 | Ticking of client <ip> (<user>) needs more that 2500 microseconds! (6310 microseconds)
[2018-09-30 20:11:01] [DEBUG] Requesting server <ip>
[2018-09-30 20:11:01] [DEBUG]   GEN | Running close in a new thread
[2018-09-30 20:11:01] [DEBUG]   GEN | Executing close done
END
Syslogs:
Code:
Sep 30 20:11:02 <hostname> systemd[1]: Stopping User Manager for UID 1000...
Sep 30 20:11:02 <hostname> systemd[11843]: Stopped target Default.
Sep 30 20:11:02 <hostname> systemd[11843]: Stopped target Basic System.
Sep 30 20:11:02 <hostname> systemd[11843]: Stopped target Sockets.
Sep 30 20:11:02 <hostname> systemd[11843]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Sep 30 20:11:02 <hostname> systemd[11843]: Closed GnuPG network certificate management daemon.
Sep 30 20:11:02 <hostname> systemd[11843]: Closed GnuPG cryptographic agent (access for web browsers).
Sep 30 20:11:02 <hostname> systemd[11843]: Stopped target Paths.
Sep 30 20:11:02 <hostname> systemd[11843]: Stopped target Timers.
Sep 30 20:11:02 <hostname> systemd[11843]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Sep 30 20:11:02 <hostname> systemd[11843]: Closed GnuPG cryptographic agent and passphrase cache.
Sep 30 20:11:02 <hostname> systemd[11843]: Reached target Shutdown.
Sep 30 20:11:02 <hostname> systemd[11843]: Starting Exit the Session...
Sep 30 20:11:02 <hostname> systemd[11843]: Received SIGRTMIN+24 from PID 13950 (kill).
Sep 30 20:11:02 <hostname> systemd[1]: Stopped User Manager for UID 1000.
Sep 30 20:11:02 <hostname> systemd[1]: Removed slice User Slice of <user>.
END
Title says it. I did not run a stop command or anything. There is no crash dump.
Note that the syslogs are AFTER the server stopped.
Kernel logs show nothing, so process wasnt terminated by system.
Teaspeak is on version 1.2.19-beta-5 atm.

Some logs from a previous crash:
Code:
[2018-09-23 06:24:12] [DEBUG] Requesting server <ip>
[2018-09-23 06:24:13] [DEBUG]   GEN | Running close in a new thread
[2018-09-23 06:24:13] [DEBUG]   GEN | Executing close done
[2018-09-23 06:24:17] [INFO]    GEN | License successfully validated!
END
Is it trying to validate license and crashing there or something?
 
Last edited:

WolverinDEV

TeaSpeak Team
Staff member
Administrator
That's interesting.
I've no idea why.
Could you may dump the server output within a file to may get some none logged messages?
Is there may also a crash dump?
 

razaq

Well-known member
Here is the server log from the crash.
It seems like the server checks the license every 2 hours. Is it really needed that often?


Also notice the error, every time a query client logs in:

Code:
[2018-10-01 08:00:01] [INFO]  QUERY | Got new client from 127.0.0.1:50236
[2018-10-01 08:00:01] [ERROR] QUERY | [127.0.0.1:50236/ServerQuery#127.0.0.1/50236] Failed to read! Code: 0 errno: 0 message: Success
 

WolverinDEV

TeaSpeak Team
Staff member
Administrator
Yeah its not only a license check its more a hey here am I.
And yeah not only the log, I guess there is something in the terminal which dosnt get written into the log file.
 

WolverinDEV

TeaSpeak Team
Staff member
Administrator
No I didnt ment the log.
Could you may start the server via the minimal script an wait untill the server stopped and copy the last few lines?
 

razaq

Well-known member
No I didnt ment the log.
Could you may start the server via the minimal script an wait untill the server stopped and copy the last few lines?
okay
this can take a couple days tho untill it happens again
 
Last edited:
Status
Not open for further replies.