kanzure
01-06-2005, 16:02
Hello,
First, some specs on my server:
Linux server 2.6.8-2-386 #1 Mon Jan 24 03:01:58 EST 2005 i686 GNU/Linux
The system is Debian. (Ignore the date error.) Edit - the server binary version is 2.0.20.1, apparently rc2. (This is according to the provided README file.)
user@host$ ./teamspeak2-server_startscript stop
stopping the teamspeak2 server...done
That seems slightly normal.
user@host$ ./teamspeak2-server_startscript start
starting the teamspeak2 server
Error starting daemon. Aborted
I really like this error message. It doesn't tell me anything about what's actually going on. This is a great way for developers to NOT be able to know how to fix their mistakes. Heh, sarcasm aside, I'd like to know how to fix this.
Oddly enough, after doing a "ps -A", I see a couple instances of "server_linux" already running. It did say that there was an error. So, I'll try to "killall -9 server_linux" and retry the start command. Asks me to delete the PID file, that's fair enough... And then it happens again:
user@host$ ./teamspeak2-server_startscript start
starting the teamspeak2 server
Error starting daemon. Aborted
After this, "server_linux" is back into the process list.
There are no important error messages in the log file. Normally, I wouldn't care about the error message since the server seems to be running fine. And as an added bonus, I don't even connect to this server, I'm running it for a friend. So when I'm trying to start it I have to continously ask him if it's working. I've been wondering, can I just use telnet to check if the server is running on the specified port? Because running the "status" subcommand (on the script) seems to be bologna if when it says the daemon is running people can't connect.
As for the developers: Since the source isn't included, maybe a detailed debug mode can be added? Alternatively, a quick email to the root account or the owner of the process would also prove helpful.
Thanks for your time, and may the Source be with you.
First, some specs on my server:
Linux server 2.6.8-2-386 #1 Mon Jan 24 03:01:58 EST 2005 i686 GNU/Linux
The system is Debian. (Ignore the date error.) Edit - the server binary version is 2.0.20.1, apparently rc2. (This is according to the provided README file.)
user@host$ ./teamspeak2-server_startscript stop
stopping the teamspeak2 server...done
That seems slightly normal.
user@host$ ./teamspeak2-server_startscript start
starting the teamspeak2 server
Error starting daemon. Aborted
I really like this error message. It doesn't tell me anything about what's actually going on. This is a great way for developers to NOT be able to know how to fix their mistakes. Heh, sarcasm aside, I'd like to know how to fix this.
Oddly enough, after doing a "ps -A", I see a couple instances of "server_linux" already running. It did say that there was an error. So, I'll try to "killall -9 server_linux" and retry the start command. Asks me to delete the PID file, that's fair enough... And then it happens again:
user@host$ ./teamspeak2-server_startscript start
starting the teamspeak2 server
Error starting daemon. Aborted
After this, "server_linux" is back into the process list.
There are no important error messages in the log file. Normally, I wouldn't care about the error message since the server seems to be running fine. And as an added bonus, I don't even connect to this server, I'm running it for a friend. So when I'm trying to start it I have to continously ask him if it's working. I've been wondering, can I just use telnet to check if the server is running on the specified port? Because running the "status" subcommand (on the script) seems to be bologna if when it says the daemon is running people can't connect.
As for the developers: Since the source isn't included, maybe a detailed debug mode can be added? Alternatively, a quick email to the root account or the owner of the process would also prove helpful.
Thanks for your time, and may the Source be with you.