/etc/hosts file issue on Ubuntu Server 10.04 x64, Teamspeak

[Jekotia]

I'm running the pre-configured installation option for Ubuntu Server 10.04 x64, and after fully updating the system (software updates, security updates, AND system updates), it seems to have messed with the hosts file, which seems to have caused Teamspeak to not work. order related of events, keeping in mind that the server was fully functional prior to the updates:

1. Updated Ubuntu
2. Noticed "unable to resolve host minerp" in SSH when using some commands, such as sudo
3. Restarted server after noticing "SYSTEM UPDATE REQUIRED" or something to that effect when connecting to SSH
4. Teamspeak 3 server inaccessable, although it IS running

Below is the dysfunctional hosts file.

Code: Select all

127.0.0.1       localhost
127.0.1.1       virtualtemplate.internap-nyc.nfoservers.com     virtualtemplate

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

Adding "127.0.0.1 minerp" DOES fix the "unable to resolve host minerp" issue, but Teamspeak 3 remains unaffected.

Aside from the updates, nothing that could possibly cause this has been done by myself, and as far as I am aware no one else with access to the server has either.

The below link was the main reference for troubleshooting this issue as it seems to be the closest match to these problems.
http://ubuntuforums.org/showthread.php?t=723361

I'm pretty sure all I need is an unmodified copy of the hosts file that is used when pre-configured Ubuntu is installed, but support was unable to supply me with such...

[Edge100x]

It sounds like some of your software expects for the hostname of the machine to be a resolvable IP, which it isn't. It's a little strange that they would have made this change recently, as I haven't seen that before. It's also possible that they just started showing it as an error, when it was silently ignored before.

That looks like a default /etc/hosts to me, though I'm not terribly familiar with Ubuntu. You may need to change the "virtualtemplate" line to read "minerp", instead, if that's your server hostname. Or, if your current workaround is working, you can just continue with that.

Re: TS3, what messages are you seeing in the TS3 window? It sounds like it might not be binding to the correct IP and/or port.

We don't support software through our direct support system; we do it here. It was correct for the support team to direct you to this forum instead of trying to help you with your software question there. This does not mean that we can't help you (unlike at most companies that offer unmanaged services).

[Jekotia]

Re: TS3, what messages are you seeing in the TS3 window? It sounds like it might not be binding to the correct IP and/or port.

I have no idea how to access a 'window' for the TS3 server, if that's what you mean. Logs are non-existent (/opt/ts3/logs/ is empty). One thing I forgot to mention: I used this tutorial to setup the TS3 server, which HAS worked after prior restarts, although this was the first since the Ubuntu update.

Would changes to the hosts file need a system restart to fully take effect? Specifying minerp as 127.0.0.1 results in immediate resolution of the "unable to resolve host minerp" messages, however the TS3 server continues to be inaccessible.

And are you sure that our assigned IP need not be specified in the hosts file? Back in January and February the server/group I'm with used NFO for the same things it does now, however at the time we were trying out MineOS, a linux distro aimed specifically at running Minecraft servers. At the time, the server owner had to work with support to properly configure our hosts file so that the server could properly communicate with the network, he even "broke many many things" by accidentally specifying the wrong IP at one point in that process. If the VPS' have changed since then so that what is mentioned above is no longer necessary, it's irrelevant, I just thought it worth including as it seems to have relevance.

[Edge100x]

Re: TS3, what messages are you seeing in the TS3 window? It sounds like it might not be binding to the correct IP and/or port.

I have no idea how to access a 'window' for the TS3 server, if that's what you mean. Logs are non-existent (/opt/ts3/logs/ is empty). One thing I forgot to mention: I used this tutorial to setup the TS3 server, which HAS worked after prior restarts, although this was the first since the Ubuntu update.

I would recommend running the TS3 server in a "screen" session instead of as a system service so that you can see its console. Try stopping the server and just running the TS3 startup command by hand for now, though.

Would changes to the hosts file need a system restart to fully take effect? Specifying minerp as 127.0.0.1 results in immediate resolution of the "unable to resolve host minerp" messages, however the TS3 server continues to be inaccessible.

It would not require a restart. I recommend replacing "virtualtemplate" with "minerp" in the one you posted, but I don't really think that this relates to your TS3 problem.

And are you sure that our assigned IP need not be specified in the hosts file?

Yes.

[Jekotia]

I would recommend running the TS3 server in a "screen" session instead of as a system service so that you can see its console. Try stopping the server and just running the TS3 startup command by hand for now, though.

How would you recommend auto-starting the TS3 server with the system in that case? And would you happen to know offhand how to remove it as a system service? I'm going to run it manually and see what happens.

[Jekotia]

It seems our server owner broke it by changing Teamspeak's config and not telling anyone... Wonderful...

Code: Select all

2011-12-04 20:59:46.022709|INFO    |ServerLibPriv |   | Server Version: 3.0.0 [Build: 14957], Linux
2011-12-04 20:59:46.022931|INFO    |DatabaseQuery |   | dbPlugin name:    SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH
2011-12-04 20:59:46.022964|INFO    |DatabaseQuery |   | dbPlugin version: 3.7.3
2011-12-04 20:59:46.023158|INFO    |DatabaseQuery |   | checking database integrity (may take a while)
2011-12-04 20:59:46.054176|INFO    |SQL           |   | pruning old database log entries where timestamp is older than 90 days
2011-12-04 20:59:46.708593|INFO    |Accounting    |   | Licensing Information
2011-12-04 20:59:46.708668|INFO    |Accounting    |   | licensed to       : Mine-RP.net
2011-12-04 20:59:46.708699|INFO    |Accounting    |   | type              : Hoster
2011-12-04 20:59:46.708762|INFO    |Accounting    |   | starting date     : Wed Aug 17 00:00:00 2011
2011-12-04 20:59:46.708795|INFO    |Accounting    |   | ending date       : Fri Aug 17 00:00:00 2012
2011-12-04 20:59:46.708822|INFO    |Accounting    |   | max virtualservers: 5
2011-12-04 20:59:46.708846|INFO    |Accounting    |   | max slots         : 100
2011-12-04 20:59:46.723210|INFO    |FileManager   |   | listening on 0.0.0.0:30033
2011-12-04 20:59:46.875913|INFO    |VirtualServer |  1| listening on 0.0.0.0:9987
2011-12-04 20:59:46.876084|INFO    |CIDRManager   |   | updated query_ip_whitelist ips: 127.0.0.1,
2011-12-04 20:59:46.876509|INFO    |Query         |   | listening on 0.0.0.0:10011
2011-12-04 20:59:47.553977|ERROR   |Accounting    |   | too many slots hosted, shutting down!
2011-12-04 20:59:47.657726|INFO    |VirtualServer |  1| stopped
^C2011-12-04 21:01:37.244426|INFO    |ServerMain    |   | Received signal SIGINT, shutting down.

No idea what he set our max users to or when, but that seems to have broken it.

Multiple hours wonderfully wasted... Excuse me, I have someone to slap profusely.

[Jekotia]

Ok, I was wrong, something else is screwing this up...

Opened the TS3 configuration database in Navicat, our max clients is set below the 100 cap. Going to try a fresh 'install' of TS3 so I can at least verify if it's a configuration issue.

[Jekotia]

Fixed. I think our old owner (who left the server) had his Teamspeak license cancelled. Removing the license file fixed everything.

[Edge100x]

I'm glad it was something simple to fix, at least (once it was clear what was going on).