FreeBSD guide to TeamSpeak2_RC2

[Killing]

what does sockstat say?

[dewhead]

Oh yeah, guess I should include something like that too huh?

Ok here's what I get for the server:
nobody server_lin 98940 19 udp4 *:8767 *:*
nobody server_lin 98939 19 udp4 *:8767 *:*
nobody server_lin 98938 19 udp4 *:8767 *:*
nobody server_lin 98937 19 udp4 *:8767 *:*
nobody server_lin 98936 19 udp4 *:8767 *:*
nobody server_lin 98935 19 udp4 *:8767 *:*

I've also scanned my machine from another BSD machine using nmap and get pretty much the same. Nothing on the 14534 port or 51234 for TCPquery. It's like they just don't get started. Of course the log file is totally clean and happy. According to it all is well with the world.

Are there any switches or options that I can run in the command line when starting that will turn on verbose logging or what would be really nice is some debugging!

[CrtxReavr]

Dewhead,

I've heard of others having problems with v5.1-RELEASE. Why don't you try cvsup'ing to v5.1-CURRENT.

The CURRENT snapshot hasn't built the past three days, but it had a pretty good run before that. You can specify a specific date/time in your supfile with the syntax:

date=yyyy.mm.dd.hh.mm.ss

You can look here to see when the snapshot builds fail and succeed:

ftp://snapshots.jp.freebsd.org/pub/F...napshots/i386/

and you can, of course, track the freebsd-current E-mail list.

-CR

[Sprottlefreak]

used to run 5.0-RELEASE, TS2 RC2 (.40), two instances (on UDP 8767 & 8768), admin interface worked. Basically everything a-ok.

recently upgraded to 5.1-RELEASE, with a full portsupdate, and the effect I'm seeing is that only the second instance (on UDP 8768) gets started, the first one isn't started, neither is the admin or tcpquery interface. Unfortunately, 5.1-CURRENT is not an option for this box :|

the latest TS2 server devel build (pre_b46) segfaults & coredumps on launch, even when trying to just get the help using -h/--help



--sprot

[Sprottlefreak]

Dug a bit deeper, the problem seems to lie in the forking:

0.218439324 linux_open("/usr/local/teamspeak/tss2_rc2/server.ini",0x242,0666) = 6 (0x6)
0.219229731 write(6,0x8228560,318)               = 318 (0x13e)
0.219833980 close(6)                             = 0 (0x0)
0.220741388 linux_open("/usr/local/teamspeak/tss2_rc2/server.log",0x402,0666) = 6 (0x6)
0.221387083 gettimeofday(0xbfbff8fc,0x0)         = 0 (0x0)
0.222320669 linux_open("/etc/localtime",0x0,0666) = 7 (0x7)
0.222883302 linux_fstat64(0x7,0xbfbff63c,0x2839bd30) = 0 (0x0)
0.223425453 linux_mmap(0xbfbff61c)               = 677015552 (0x285a7000)
0.224068521 read(0x7,0x285a7000,0x4000)          = 837 (0x345)
0.224787358 close(7)                             = 0 (0x0)
0.225456889 munmap(0x285a7000,0x4000)            = 0 (0x0)
0.226302923 write(6,0x8228110,128)               = 128 (0x80)
0.226866064 linux_rt_sigprocmask(0x0,0x82226a8,0x0,0x8) = 0 (0x0)
0.227442299 linux_rt_sigaction(0xf,0xbfbff840,0xbfbff7b0,0x8) = 0 (0x0)
0.228503437 linux_rt_sigaction(0x1,0xbfbff840,0xbfbff7b0,0x8) = 0 (0x0)
0.229179124 linux_rt_sigaction(0xa,0xbfbff840,0xbfbff7b0,0x8) = 0 (0x0)
0.229745205 linux_rt_sigaction(0xc,0xbfbff840,0xbfbff7b0,0x8) = 0 (0x0)
0.238051915 linux_fork()                         = 3161 (0xc59)
0.347997365 nanosleep(0xbfbff9a4,0x0)            = 0 (0x0)
0.467985509 nanosleep(0xbfbff9a4,0x0)            = 0 (0x0)


[...] ~100 nanosleep calls


11.198110876 nanosleep(0xbfbff9a4,0x0)           = 0 (0x0)
11.308105214 nanosleep(0xbfbff9a4,0x0)           = 0 (0x0)
Error starting daemon. Aborted
11.308795069 write(1,0x8221434,31)               = 31 (0x1f)
11.309468457 gettimeofday(0xbfbff964,0x0)        = 0 (0x0)
11.310186258 write(6,0x8228110,128)              = 128 (0x80)
11.310781466 write(6,0x8228110,118)              = 118 (0x76)
11.311424141 close(6)                            = 0 (0x0)
11.312874127 close(4)                            = 0 (0x0)
11.313455898 close(5)                            = 0 (0x0)
11.313995373 linux_rt_sigaction(0x2,0x0,0xbfbff6b4,0x8) = 0 (0x0)
11.314614546 linux_rt_sigaction(0x2,0xbfbff7dc,0x0,0x8) = 0 (0x0)
11.315174033 linux_rt_sigaction(0x8,0x0,0xbfbff6b4,0x8) = 0 (0x0)
11.315807050 linux_rt_sigaction(0x8,0xbfbff7dc,0x0,0x8) = 0 (0x0)
11.316368004 linux_rt_sigaction(0xb,0x0,0xbfbff6b4,0x8) = 0 (0x0)
11.316992231 linux_rt_sigaction(0xb,0xbfbff7dc,0x0,0x8) = 0 (0x0)
11.317568764 linux_rt_sigaction(0x4,0x0,0xbfbff6b4,0x8) = 0 (0x0)
11.318133788 linux_rt_sigaction(0x4,0xbfbff7dc,0x0,0x8) = 0 (0x0)
11.318765715 linux_rt_sigaction(0x7,0x0,0xbfbff6b4,0x8) = 0 (0x0)
11.319389227 linux_rt_sigaction(0x7,0xbfbff7dc,0x0,0x8) = 0 (0x0)
11.319953667 linux_rt_sigaction(0x3,0x0,0xbfbff6b4,0x8) = 0 (0x0)
11.320576794 linux_rt_sigaction(0x3,0xbfbff7dc,0x0,0x8) = 0 (0x0)
11.321260104 munmap(0x0,0xefff)                  = 0 (0x0)
11.322234477 munmap(0x2821e000,0x1000)           = 0 (0x0)
11.322727954 exit(0x2)                          
process exit, rval = 512

right after the fork() call it appears to wait for ~10 seconds, then aborts startup (it doesn't clear up already started instances though, which is why the "normal" server functions work even after the message) due to an internal timeout presumably. Wild guess is that the way forks are reported changed in 5.1 ? I'm not a developer though.

--sprot

[CrtxReavr]

I modded that port and run my production TeamSpeak server on a v4.8 box and it runs perfectly.

Today I tried it on a v5.1-RELEASE box and encountered the same problem. I'm gonna CVSUP to today's -CURRENT and see if it behaves any differently. If it doesn't, I'll start harrassing the FreeBSD devs I know.

It would be nice, however, if the TeamSpeak folks could do a native FreeBSD port. Hint. Hint. Hint.

-CR

[dewhead]

Well CVS'upping will probably work.

I'm now current as of yesterday, with new kernel and all.
Everything is fine on the box, and TeamSpeak now starts, and I got into the admin interface for alittle bit. Wasn't able to change any info though. Then it just hung. Can't get it to do jack now, just times out.

Athough the TCPquery is working it seems and I'm happy enough with that for the time being. Would be nice to see the same options available that are in the web interface. Can't see to change the name of the server or other things....although I'm still looking around at it from work, so I still have some things to find.

This is using the TeamSpeak tarball from this site. I haven't tried using the port that was made. I'm afraid to stop TS right now for fear of not getting back into it again!

I'll re=install the port version of TS and see if that works better now.

Also the startup script for it always seems to give me problems. It would give me the error of: Ambigous redirect something or other....can't remember now. I searched around, and seems to be a shell scripting problem. I'm using ZSH, should I use some other shell to run the script from? I think I tried it from BASH, with same result.

[Sprottlefreak]

cvsup'd today to -CURRENT, new kernel & all, exactly the same behaviour as under 5.1-RELEASE - starts, forks, sleeps for 10 seconds, aborts startup. No admin or tcpquery interface running.

--sprot

[CrtxReavr]

Originally posted by Sprottlefreak
cvsup'd today to -CURRENT, new kernel & all, exactly the same behaviour as under 5.1-RELEASE - starts, forks, sleeps for 10 seconds, aborts startup. No admin or tcpquery interface running.

--sprot

In my test updating to today's -CURRENT I had sporatic behavior. At one point the web console seemed to be working, but in that I could connect and get the login screen, but the initial admin passwords were not listed in the server.log file, so I had nothing to attempt to login with. Upon killing the server, deleting the server.* files and re-running it, I was back to the behavior where only the chat server port was listening. Most preplexing.

Continues to run great on -STABLE though.

How about a native FreeBSD port?!?!?!

-CR

[StarKilLer]

No word on anyone getting it to work with openbsd with the webadmin fuctional aye?

[DeltaDK]

Dos freebsd stable 4.9 work?? anyone tried??

[TZapper]

Hello all,

I am running FreeBSD 5.1-RELEASE-p10 with linux_base-7.1_2. I installed TeamSpeak from /usr/ports/audio and it successfully started without any errors in the logfile. Server version: 2.0.19.40 Linux.

I can successfully connect to TS with my client, but I cannot connect to webinterface to initially cnfigure it, sockstat doesnt report any open sockets other than 8767 (udp4).

What am I doing wrong or is there a bug?

P.S. The behavior is very sporadic, sometimes the webinterface works sometimes not, but I cant seem to get the admin password generated in the server.log, any ideas?

With best regards,
Alex

[Dummer Sack]

Try to delete server.ini, server.log, server.dbs and start the server. Then it should generate the passwords and write them to the server.log.
All config data will be lost of cause.

[dewhead]

haven't had alot of time to work on this as of late. I setup a new box with 4.8R.

It didn't work right out of the tar, so I messed with stuff for a bit. I finally got it working perfect when i tried using the linux_base-debian-3.0.23 package. Installed that instead of the default linux_base which is redhat 7 something I think. Once I ran it under that, it started up, and I'm running happy now.

The biggest differance that I can see is the libgcc version. This seems to be a factor in getting BattleField 1942 running as well, although I think I need some pathces for the linux kernel module as it keeps core dumping on map changes. Apparently there are some syscals that are missing from the linux module for the FreeBSD kernel which were never put in place...cause they were either thought of as stupid and/or not needed. I'm trying some pathces out that I got that takes care of that. maybe that will help in this as well?

Someone with 5.x try and use the 3.0.23 debian base for FreeBSD linux emulation and see if that fixes your problems. There is also a linux_base-8 which is a RH 8 base install....that might be better as well?

[Killing]

Never been able to get TS working on 5.0 series just doesnt like it dont know why something to do with some kernel changes never did get round to finding out why.