Teamspeak 2 Server not starting
Posted: Wed Apr 12, 2006 10:11 pm
[Problem]
We recently had trouble with our teamspeak2 installation on our LFS (Linux from Scratch) Server. I created a user/group with NO privileges at all, 'cept for the ts2 directory. Even tho this worked a hundred times on all flavors of linux', this time i got a nasty error:
Google did not help much on the 'EInOutError: I/O error 13' - even tho there were like, two threads with similar problems, it was not the same solution. One of those threads gave the hint to solve this problem, tho 
[Solution]
In our case, the '/dev/null' access rights were not proper configured. TS2 needs this device to work, but it was set to chmod 660. A simple 'chmod 666 /dev/null' did the trick - up and running, happy voice chatting!
Another solution to this and similar errors: make sure the user who runs TS2 has appropriate rights in the teamspeak2 directory and its subdirectories. A common mistake is to chmod the teamspeak2 directory without the recursive flag, so the subdirs are not chown'ed/chmod'ed.
[Notes]
I read about this for a minute, and appearently it is not common for /dev/null to be set to 660. I could not find anything about any security risks caused by setting the device to those access rights. If someone knows better, drop a line.
We recently had trouble with our teamspeak2 installation on our LFS (Linux from Scratch) Server. I created a user/group with NO privileges at all, 'cept for the ts2 directory. Even tho this worked a hundred times on all flavors of linux', this time i got a nasty error:
Code: Select all
---------------------------------------------------------------
-------------- log started at 30-03-06 19:34 -------------
---------------------------------------------------------------
30-03-06 19:34:26,ALL,Info,server, Server init initialized
30-03-06 19:34:26,ERROR,Info,server, EInOutError: I/O error 13
----------------------------------------------------------
---------------------------------------------------------------
--------------- log ended at 30-03-06 19:34 --------------
[Solution]
In our case, the '/dev/null' access rights were not proper configured. TS2 needs this device to work, but it was set to chmod 660. A simple 'chmod 666 /dev/null' did the trick - up and running, happy voice chatting!
Another solution to this and similar errors: make sure the user who runs TS2 has appropriate rights in the teamspeak2 directory and its subdirectories. A common mistake is to chmod the teamspeak2 directory without the recursive flag, so the subdirs are not chown'ed/chmod'ed.
[Notes]
I read about this for a minute, and appearently it is not common for /dev/null to be set to 660. I could not find anything about any security risks caused by setting the device to those access rights. If someone knows better, drop a line.