Forum


Notice to all users

We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020

Results 1 to 11 of 11

Thread: A New Problem

  1. #1
    Join Date
    August 2014
    Posts
    8

    Angry A New Problem

    I've been using Teamspeak for a long time now. Have no issues until this one really confused me.
    I have googled around and not found anything relating to this issue.


    I'm trying to setup a new Teamspeak server on my dedicated server running Ubuntu.

    When I start the server with ."/ts3server_startscript.sh" it says:

    [email protected]:~/Main$ ./ts3server_startscript.sh start
    Starting the TeamSpeak 3 server
    TeamSpeak 3 server started, for details please view the log file
    But that's it. It doesn't give me the serveradmin credentials or even the token.

    Worst of all, it doesn't even create the log file.

    I double-checked the Linux requirements and I'm pretty sure my server meets them. Any way to check?

    Help, please? Any details needed I can provide.

  2. #2
    Join Date
    April 2014
    Location
    Seattle, WA, USA
    Posts
    141
    Hello, you can check your full system log (usually) in /var/log/messages

    This will show the last 100 lines of the log.
    Code:
    # tail -n100 /var/log/messages

    Add scrolling (arrow keys):
    Code:
    # tail -n100 /var/log/messages | less
    You can also check if the pid is up:

    Result should look like screenshot:
    Click image for larger version. 

Name:	90r8oc3.png 
Views:	59 
Size:	5.8 KB 
ID:	11102

  3. #3
    Join Date
    August 2014
    Posts
    8
    Quote Originally Posted by Ronin Design View Post
    Hello, you can check your full system log (usually) in /var/log/messages

    This will show the last 100 lines of the log.
    Code:
    # tail -n100 /var/log/messages

    Add scrolling (arrow keys):
    Code:
    # tail -n100 /var/log/messages | less
    Thanks for your reply! Using:

    Code:
    tail -n100 /var/log/messages
    It comes up with this:

    tail: cannot open `/var/log/messages' for reading: No such file or directory

  4. #4
    Join Date
    April 2014
    Location
    Seattle, WA, USA
    Posts
    141
    Could you give me the results of:

    Click image for larger version. 

Name:	cSQc2MH.png 
Views:	46 
Size:	1.4 KB 
ID:	11103

    This will tell me what system you're on.

    btw: Wow, this CloudFlare ban thing is rough when trying to paste cmds....

  5. #5
    Join Date
    August 2014
    Posts
    8
    Quote Originally Posted by Ronin Design View Post
    Could you give me the results of:

    Click image for larger version. 

Name:	cSQc2MH.png 
Views:	46 
Size:	1.4 KB 
ID:	11103

    This will tell me what system you're on.

    btw: Wow, this CloudFlare ban thing is rough when trying to paste cmds....
    Here you go:

    Linux server217-174-249-119.live-servers.net 3.2.0-67-generic #101-Ubuntu SMP Tue Jul 15 17:46:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

  6. #6
    Join Date
    April 2014
    Location
    Seattle, WA, USA
    Posts
    141
    Ubuntu! Good stuff

    Here is the correct location of your logs should be: /var/log/syslog

    Please adjust above commands to match, and try running them again. Hopefully you'll see some clue as to why the server is choking!

    Screenshot of commands:
    Click image for larger version. 

Name:	MxsvErQ.png 
Views:	58 
Size:	1.8 KB 
ID:	11107

  7. #7
    Join Date
    August 2014
    Posts
    8
    Quote Originally Posted by Ronin Design View Post
    Ubuntu! Good stuff

    Here is the correct location of your logs should be: /var/log/syslog

    Please adjust above commands to match, and try running them again. Hopefully you'll see some clue as to why the server is choking!

    Screenshot of commands:
    Click image for larger version. 

Name:	MxsvErQ.png 
Views:	58 
Size:	1.8 KB 
ID:	11107
    I ran the command and looked through the logs.

    I believe this is the error that the server has:

    kernel: [55811.485288] ts3server_linux[24934]: segfault at 8 ip 00007f90d9ef6be2 sp 00007fff5bd44860 error 4 in ld-2.15.so[7f90d9eeb000+22000]
    I hope that means something?

  8. #8
    Join Date
    April 2014
    Location
    Seattle, WA, USA
    Posts
    141
    Looks like others have seen similar stuff, give me a sec to research a bit more:

    http://forum.teamspeak.com/showthrea...entation-fault

  9. #9
    Join Date
    August 2014
    Posts
    8
    2011 D:


    No problem, I'll surf the webs too.

  10. #10
    Join Date
    April 2014
    Location
    Seattle, WA, USA
    Posts
    141
    Getting warmer?

    EDIT: Actually, found a thread from 2014:

    http://forum.teamspeak.com/showthrea...-down-randomly

    EDIT 2: Also, more helpful info on getting good crash reports:

    Quote Originally Posted by Peter
    Hello,

    here I will explain which information you should post when your ts3server crashed or hangs up. You can create a new thread with your problem then.

    (1) Make sure your system is configured to write core dumps when applications crash. You can enable this by running something like
    Code:
    ulimit -c 500000
    You can put this in your ts3 server startscript to make sure it is set on every startup

    (2) When the server crashes it will now write a file called "core" or "core.NUMBER"
    If the server is in a hung up state (it is not reacting to serverquery or normal client connections anymore) you can force the server to write a core by running "killall -SIGQUIT ts3server_linux_amd64" (use _x86 for x86 servers)

    (3) The core alone is no use, what is also needed is a few libraries from your system, a script I wrote will gather them and put them in an archive. The script is attached [1], running it will look something like this:
    Code:
    [email protected]:~$ ./make_core_environment.sh ts3/
    core_environment/
    core_environment/usr/
    core_environment/usr/lib/
    core_environment/usr/lib/libstdc++.so.6
    core_environment/lib/
    core_environment/lib/libdl.so.2
    core_environment/lib/libgcc_s.so.1
    core_environment/lib/libc.so.6
    core_environment/lib/libm.so.6
    core_environment/lib/librt.so.1
    core_environment/lib/libpthread.so.0
    core_environment/lib64/
    core_environment/lib64/ld-linux-x86-64.so.2
    [email protected]:~$
    The file "core_environment.tar.gz" is created by the script. It contains the needed libraries.

    (4) Provide the log file of the incident, provide any other information you know (what was being done with the server etc.). Can you reproduce the problem? If so, tell us the steps.

    (5) Bundle the core file(s), the core_environment.tar.gz in an archive an upload it to somewhere. Post a link in your report.


    [1] http://dl.4players.de/ts/releases/de...environment.sh
    ^^ Good stuff, never seen this before. Definitely one for the scrap book.

    Here's some sketchy stuff about unlinking the linux library: ld-2.15.so

    https://kc.mcafee.com/corporate/inde...8860&pmv=print

    Definitely tread lightly and carry a big backup... if you aren't familiar with the nix commands.
    Last edited by Chris; August 13th, 2014 at 12:17 PM. Reason: merged double post

  11. #11
    Join Date
    August 2014
    Posts
    8
    Quote Originally Posted by Ronin Design View Post
    Here's some sketchy stuff about unlinking the linux library: ld-2.15.so

    https://kc.mcafee.com/corporate/inde...8860&pmv=print

    Definitely tread lightly and carry a big backup... if you aren't familiar with the nix commands.
    Here is a link to the Core file and the libraries: https://www.mediafire.com/?4ge1f92g98otyv0

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Serveredit problem, and Admin user problem.
    By 0wn3r in forum Linux / FreeBSD
    Replies: 1
    Last Post: December 23rd, 2018, 12:09 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •