Masterserver registration.
#1
My ver. 1.1 server keeps losing registration to the masterserver here are the log entries.

Code:
Aug 10 23:09:31 looking up assault.cubers.net...
Aug 10 23:09:42 master server registration succeeded
Aug 10 23:49:32 looking up assault.cubers.net...
Aug 10 23:49:32 master server registration succeeded
Aug 11 00:29:32 looking up assault.cubers.net...
Aug 11 00:29:32 master server registration succeeded
Aug 11 01:09:32 looking up assault.cubers.net...
Aug 11 01:09:32 master server registration succeeded
Aug 11 01:49:32 looking up assault.cubers.net...
Aug 11 01:49:32 master server registration succeeded
Aug 11 02:29:32 looking up assault.cubers.net...
Aug 11 02:29:32 master server registration succeeded

Aug 11 03:09:32 looking up assault.cubers.net...
Aug 11 03:09:32 master server registration succeeded
Aug 11 03:49:32 looking up assault.cubers.net...
Aug 11 03:53:01 WARNING: could not connect

Aug 11 04:43:43 WARNING: could not connect

Aug 11 05:23:43 WARNING: could not connect
Aug 11 06:03:43 WARNING: could not connect
Aug 11 06:43:43 WARNING: could not connect
Aug 11 07:23:43 WARNING: could not connect
Aug 11 07:39:43 Status at 11-08-2010 07:39:43: 0 remote clients, 0.0 send, 0.0 rec (K/sec); Ping: #10246|600198|26779; CSL: #161|1125|479 (bytes)
Aug 11 08:03:43 WARNING: could not connect
Aug 11 08:43:43 WARNING: could not connect
Aug 11 09:23:43 WARNING: could not connect
Aug 11 10:03:43 WARNING: could not connect

Aug 11 10:43:43 WARNING: could not connect
Aug 11 11:23:43 WARNING: could not connect

my server IP is 79.170.198.38:8500

I dont think it's a server problem as my other server IP 79.170.198.38:13013 stays registered, could it be that this port was originally used for my ver. 1.0.4 server. Any help with this would be appreciated.
Thanks given by:
#2
Most likely arbitrary rules are bringing you down. Do what the man says and you can pass.
Thanks given by:
#3
Re-forward the ports or forward different ports, it's what many of us had to do.
Thanks given by:
#4
This behaviour is totally normal, you should see the exact same sort of lines on your other server. The masterserver will drop any server from the listing after an hour (IIRC) of not getting any re-registration message - this is to avoid the list getting ever longer, since some servers just exist for a short period of time on the same IP.

Oh. wait - the interesting/important bit of your log only got apparent after scrolling down ... the initial bits are perfectly normal - the later bits aren't, it could be that your internet connection was down at the time; more information about your specific setup would be required to give any serious answer though.
I've just checked the masterserver-blacklist - you're not on that; if your other server is registering OK it's indeed mysterious - maybe you started them both so close to each other that they mess with each other in trying to claim the port for registration - try starting them about a minute (or more) apart from each other.
Thanks given by:
#5
I'm running ubuntu 8.0.4 on vds in a data center in Manchester UK. (the cheapest linux one here)

http://www.intrahost.co.uk/linux-virtual...d-servers/

Both of my servers have now lost connection but not at the same time. I can restart them and they register but after some random time one will lose the connection, then after another random period of time the other will lose connection. I have tried using different ports but it still happens. If i'm using port 13013 do i need to forward 28764 as well as 13013/13014? if so maybe that is my problem.

Also could someone explain this line in the log plz :

Aug 16 22:16:35 Status at 16-08-2010 22:16:35: 2 remote clients, 1.0 send, 1.0 rec (K/sec); Ping: #50|3708|100; CSL: #1|81|3 (bytes)
Thanks given by: