Master Server Issue

[-=VcL.Rajinn]

I notice that Velocity servers only show up on Master servers 1 and 3. When you login, if you get another master server, a lot of servers, including velocity servers don't show up. This is not an issue on my side, as others have reported the same thing.

Regards,
Rajinn

[Z-Man]

Hmm, which other servers are affected? (With IPs, if possible, for easier log grepping)

[-=VcL.Rajinn]

I can't seem to reproduce this problem at the moment. Seems today that all of the servers are showing up on the list Weird.

Thanks,
Rajinn

[-=VcL.Rajinn]

Well, today they are acting funny again..., even for scripts it seems:

The velocity servers IP is 98.142.211.227 I don't know what other servers aren't showing up at the moment, but like I said, I noticed ours are only showing on Masters 1 and 3...

Rajinn

[kyle]

why don't you traceroute or something to the master servers, maybe there is an error?

[-=VcL.Rajinn]

Maybe this will help from my log files.

[0] Command LADDERLOG_PLAYER_RENAMED unknown.
[0]
[0] Command LADDERLOG_PLAYER_LEFT unknown.
[0]
[0] Command VOTING_TIMEOUT_PER_VOTE unknown.
[0]
[0] Bound socket to *.*.*.*:36416.
[0] Bound socket to 98.142.211.227:4538.
[0] Setting SPAM_MAXLEN (Group: Cheating) deviates from its default value; clients older than 0.2.6.0 will not be allowed in.
[0] Setting CYCLE_RUBBER_TIMEBASED (Group: Visual) deviates from its default value; clients older than 0.2.8_beta2 may experience problems.
[0] Setting CYCLE_RUBBER_MINDISTANCE (Group: Annoying) deviates from its default value; clients older than 0.2.7.1 may experience problems.
[0] Connecting to Master Server 1...
[0] Killing user 0, ping 1.25.
[0] Login information sent. Waiting for reply...
[0] Got address 98.142.211.227:4538.
[0] Login Succeeded. User Nr. 1
[0] Syncing with server...
[0] Relabeling NetObjects...
[0] Syncing again...
[0] Done!
[0] Sending my server info...
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 0.22301.
[0] Closing socket bound to 98.142.211.227:4538
[0] Bound socket to 98.142.211.227:4538.
[0] Setting SPAM_MAXLEN (Group: Cheating) deviates from its default value; clients older than 0.2.6.0 will not be allowed in.
[0] Connecting to Master Server 2...
[0] Killing user 0, ping 1.25.
[0] Login information sent. Waiting for reply...
[0] Login failed: Timeout.
[33 IP=90.227.129.58:4533] Killing user 33, ping 1.25.
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 1.25.
[0] Closing socket bound to 98.142.211.227:4538
[0] Bound socket to 98.142.211.227:4538.
[0] Setting SPAM_MAXLEN (Group: Cheating) deviates from its default value; clients older than 0.2.6.0 will not be allowed in.
[0] Connecting to Master Server 3...
[0] Killing user 0, ping 1.25.
[0] Login information sent. Waiting for reply...
[0] Login Succeeded. User Nr. 1
[0] Syncing with server...
[0] Relabeling NetObjects...
[0] Syncing again...
[0] Done!
[0] Sending my server info...
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 0.202069.
[0] Closing socket bound to 98.142.211.227:4538
[0] Bound socket to 98.142.211.227:4538.
[0] Setting SPAM_MAXLEN (Group: Cheating) deviates from its default value; clients older than 0.2.6.0 will not be allowed in.
[0] Connecting to Master Server 4...
[0] Killing user 0, ping 1.25.
[0] Login information sent. Waiting for reply...
[0] Login failed: Timeout.
[33 IP=78.105.161.85:4533] Killing user 33, ping 1.25.
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 1.25.
[0] Closing socket bound to 98.142.211.227:4538
[0] Bound socket to 98.142.211.227:4538.
[0] Setting SPAM_MAXLEN (Group: Cheating) deviates from its default value; clients older than 0.2.6.0 will not be allowed in.
[0] Ping charity changed from 0 to 500.
[0] Nobody there. Taking a nap...
[0] Timestamp: 2010/01/13 13:36:06
[0] Closing socket bound to 98.142.211.227:4538
[0] Bound socket to 98.142.211.227:4538.

I notice the "[0] Login failed: Timeout." happens in all but 1 and 3 also.

Is this an error on my side that I should try to fix?

Thanks in advance,
Rajinn

Edit: I just did a fresh rebuild and it still didn't fix the problem