17-10-04 14:01:58,ERROR,All,SQL, Database initialization error: SQL logic error

[superhoe]

Hi all,

All help is greatly appreciated. I've ran Teamspeak for quite some time now on our private OFP server, but ran into a quite confusing problem..

Teamspeak (latest version of Linux deddy client) ran fine on our Debian server and we had no problems. Then, a power shortage came and we had to reboot the server. After this, our otherwise working Teamspeak server gave this quite informative error upon startup:

Error starting daemon. Aborted

Fine enough. Then a quick peek at the log which says:

17-10-04 14:12:08,ALL,Info,server, Server init initialized
17-10-04 14:12:08,ALL,Info,server, Server version: 2.0.20.1 Linux
17-10-04 14:12:08,ERROR,All,SQL, Database initialization error: SQL logic error or missing database
17-10-04 14:12:08,ERROR,All,SQL, Database initialization error: SQL logic error or missing database
17-10-04 14:12:08,ERROR,All,SERVER, Start_Server: unable to open database

Well, this is getting interesting as I don't even have MySQL on the machine (we use Postgres) and the Teamspeak was therefore never even configured to use SQL.

I've scrapped the server and installed a fresh install from a tarball. Doesn't work, same error.

I've ran the server with 'out-of-box' minimal configuration. Doesn't work. Actually, I've tried pretty much everything. Checked Debian lib requirements and they're OK as supposed; the server worked for us before. But this weird SQL error is really, really, confusing me.

Can anyone help? And yes, I am extremely sure that my server.ini does not contain anything related to SQL. I've tried with out-of-tarball server.ini which has 3 lines or so, and it still gives the same error.

[SatanClaus]

ts uses SQLite by default for the server.dbs file (in which server-infos and user-infos get saved). Normally such a database shouldn't be corrupted by a powerdown, but it seems to happen from time to time (most probably power was interrupted while writing to the file).

Easiest solution should be: stop the ts-server, delete (or move if you like) the server.dbs file out of the ts-server's directory and start the ts-server again.
It should work as if never started before, meaning: all settings are lost (except for those in the server.ini) + defaults will be restored (passwords in server.log)

cu
SatanClaus

[superhoe]

Well, simple and clear:

Problem solved with your suggestion.

Thanks a million!