ExcecSQL Error: database is locked

[yorick]

Help!

I'm getting a ton of database locked errors. It actually looks like this:
21-03-03 19:26:45,ERROR,All,SQL, ExcecSQL Error: database is locked in query: CREATE TABLE ts2_servers

I'm running Redhat 7, kernel 2.2.16.

[tss@Styx tss2_rc2]$ ldd server_linux
/lib/libNoVersion.so.1 => /lib/libNoVersion.so.1 (0x40018000)
libpthread.so.0 => /lib/libpthread.so.0 (0x40020000)
libdl.so.2 => /lib/libdl.so.2 (0x40036000)
libc.so.6 => /lib/libc.so.6 (0x40039000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

The teamspeak server actually starts and I can join it from a windows machine but administration is impossible because the html interface hangs indefinately and I can't pull a password out of the mangled log file.

I've tried several things including chmod'ing everything to 777 and loading the rpm for sqlite; no joy. I've read the forums and a few other people have had similar problems but I've not found a solution. Any tips would be appreciated.

Thanks!

Paul

[N. Werensteijn]

bugreports in http://mantis.teamspeak.org plz

[Lethe]

I have noticed that ./tss_server_minimal stop (or whatever you have renamed the script too) doesn't actually stop all TS servers... usually 2 instances are still in existance. You have to killall <name> or kill -9 <pid> to stop these two.

So I am wondering if you have started TS, then stopped it, then started it again WITH the two rogue servers still up... this would then produce symptoms of what you are getting.

So stop TS, then do a:

ps -ax | grep server_l

and use

killall server_linux

or

kill -9 <pid>

To stop all instances.

Then start TS again and try again.

Nick

[yorick]

N. Werensteijn:
Thanks for the suggestion. After getting a login to the bug tracker I found that my problem has been logged as bug #0000123.


Lethe:
Also, thanks for the reply. I've killed and restarted the server several times. The problem seems quite repeatable. AFter killing all instances of linux_server I run the minimal start and here's what happens:

[tss@Styx tss2_rc2]$ ./tss.minimal_startscript start
Error starting daemon. Aborted
[tss@Styx tss2_rc2]$ ps -aux | grep tss
tss 10416 0.0 0.5 2344 1352 pts/5 S 20:35 0:00 bash
tss 10470 1.8 0.5 8776 1448 pts/5 S 20:37 0:00 ./server_linux -P
tss 10471 0.0 0.5 8776 1448 pts/5 S 20:37 0:00 ./server_linux -P
tss 10472 0.0 0.5 8776 1448 pts/5 S 20:37 0:00 ./server_linux -P
tss 10473 0.0 0.5 8776 1448 pts/5 S 20:37 0:00 ./server_linux -P
tss 10479 0.0 0.3 2744 872 pts/5 R 20:38 0:00 ps -aux
tss 10480 0.0 0.2 1516 588 pts/5 S 20:38 0:00 grep tss
[tss@Styx tss2_rc2]$

The server is always running fine but I can't configure it.

I'll also go stick the info in the bug tracker. Thanks.

Paul

[Lethe]

Well this definately looks like a lock/permissions error - as if a rogue service stills exists with it fingers in.

As it is really a small download, it may be worth getting again, trashing the existing one, and reinstalling - it could also be a corrupt d/l?

Then run thru' all the steps again.

Nick