TeamSpeak Issues – Feb 8 – Resolved

The majority of the users connected to TeamSpeak were dropped for an unknown reason. Attempting to reset the firewall had no effect which forced me to restart the TeamSpeak process.. Process would not restart then causing a kernel crash. Upon restarting the server the TeamSpeak Start Script failed to initialize requiring me to manually start the process instead.

If I find out anything from the logs I will update this post. Sorry for any inconvenience!

Update 1:50pm EST: There was a database crash on the server. Unsure why this happened but I do see a login from the MyExtraneous system 5 minutes before the crash – although unlikely that it would have caused this I’m not ruling it out. I will run a scan for any corrupted data.

2016-02-08 18:27:33|CRITICAL|   | Server unable to initialize database

Update 10:00pm EST: We will be restarting the TeamSpeak server on Friday Feb 12 as there were issues starting it using our start script. This restart will move the PID (Process ID) back to the correct service manager. Downtime should be 20 seconds or less. This has been successfully completed at 7:46AM EST