Start TS from ssh - ssh hangs on exit

[Quadling]

Hi,

I've trawled the TS forums and not seen a similar problem, any advice for solving the following would be very welcome.

I have run TS for several years, my 32bit server died and was replaced with a 64bit machine, problems started soon after but it's taken me four months to work out roughly what's the cause. TeamSpeak server_linux starts OK, everyone can use it as normal but after a couple of days the server itself will fail complaining about being unable to setuid it starts to reject post and needs rebooting. Leave TeamSpeak off and the server will run indefinitely.
If I ssh to the server and start TeamSpeak and then 'exit' from ssh the window blanks and freezes. ssh-ing in from another terminal and stopping TeamSpeak releases the frozen ssh.

The server is running Fedora Core 6 x86_64 with all updates applied, I've tried vanilla kernels up to 2.6.20-rc7. Uninstalled and re-installed the 32bit libraries.
Now using the very latest TeamSpeak 2.0.23.15 BETA
I have tested it works fine on my workstation also on FC6 64bit, just not working on the machine I actually need it on...

Checking the log there are no errors from TeamSpeak at all.

Expect it's my own fauly, the problems might well have been caused by my rashly ugrading Fedora from 32bit to 64bit, a fresh install might cure it BUT I'd rather not have to!

Any ideas, insights, solutions or suggestions?

Thanks to anyone who is able to help,

Jason

[Quadling]

Thanks to anyone who took the time to read my original message.
I'm happy to say the wonderful TeamSpeak is blameless!

Whatever it is can reliably be triggered by starting TS but I can also generate the problem by stressing the server with a high load. Time for a re-install...

[Thomas]

How do you start the server?

[Quadling]

The server has been started with an init.d script.
Here's a snippit of the current version, you can see I've tried many combinations based on what I've read in the forums regarding 64bit issues.

'start')
cd /home/tss
# echo 1 > /proc/sys/vm/legacy_va_layout
# setarch `uname -m` su tss -c /home/tss/server_linux
# linux32 su tss -c /home/tss/server_linux
#setarch x86_64
su tss -c /home/tss/server_linux

I also tried teamspeak2-server_startscript, same result.

If you have any ideas I'd love to hear them but please don't spend any time unless you think it might be a problem that I can help YOU to learn something from and, hopefully, resolve. I am sure it is not a TS problem just something of my own creation so I fear I might be wasting your time on a wild goose chase.
Sometime in the next couple of days the server is going to be replaced with something older, I didn't think 64bit was still this close to the bleeding edge... I've been using it on my workstation for 18months(!) back to 32bit land for my server :-)
(The 64bit server will still be available if you'd like me to try anything out)

Thanks,
Jason