[Announcer] Failed to read announce response from master.vc-mp.org

Started by DizzasTeR, Oct 21, 2016, 09:14 AM

Previous topic - Next topic

DizzasTeR

So apparently I'm getting this on the console:

Failed to read announce response from master.vc-mp.org (11)
when the server is up for a few hours and then it is unreachable by players i.e no more on masterlist. Anyone knows why this is happening because I didn't have this problem before.

Here's the machine:

uname -a
Linux vps 2.6.32-042stab116.2 #1 SMP Fri Jun 24 15:33:57 MSK 2016 x86_64 GNU/Linux

Restarting the server gets it on masterlist but again after few hours of uptime that shows up on console and server is no longer reachable.

KAKAN

http://forum.vc-mp.org/?topic=2337.0
Maybe try that one, I think the problem is with the plugin itself, or try using a local masterlist and see if the error still exists.
oh no

DizzasTeR

I was using the same plugin before though but I'll see if it happens with SLC's plugin.

Thijn

Try adding announce_verbose to your server.cfg and post the console output when it fails.

Anik

Same here! The message shows and players are unable to join the server.

DizzasTeR

@Thijn, After launching server it said successfully announced on masterlist, afterwards when I waited until I couldn't reach server again, I checked the console and all there was, was spam of this:

announcer: Ready to announce to masterlist(s).
announcer: Candidate for hostname found, trying to connect...
announcer: Sent 194/194 bytes to master.vc-mp.org
--> 263 bytes in
--> 0 bytes in
announcer: Received 263/511 bytes from master.vc-mp.org
announcer: HTTP/1.1 200 OK
Server: nginx/1.2.1
Date: Sat, 22 Oct 2016 11:21:04 GMT
Content-Type: text/html
X-Powered-By: PHP/5.4.45-0+deb7u4
X-Cache: MISS from localhost
X-Cache-Lookup: MISS from localhost:3128
Via: 1.1 localhost (squid/3.5.19)
Connection: close


announcer: Successfully announced to master.vc-mp.org
announcer: Candidate for hostname found, trying to connect...
announcer: Sent 194/194 bytes to master.vc-mp.org
--> 263 bytes in
--> 0 bytes in
announcer: Received 263/511 bytes from master.vc-mp.org
announcer: HTTP/1.1 200 OK
Server: nginx/1.2.1
Date: Sat, 22 Oct 2016 11:22:04 GMT
Content-Type: text/html
X-Powered-By: PHP/5.4.45-0+deb7u4
X-Cache: MISS from localhost
X-Cache-Lookup: MISS from localhost:3128
Via: 1.1 localhost (squid/3.5.19)
Connection: close

It was spammed quite numerous times.

Also I noticed that if the server is unreachable and I'd connect to the SSH i.e not even logged in yet, just connected to SSH where it asks for the user, I noticed the server started to show up. I hope you got what I'm trying to say.

Thijn

So you're basically saying your host is shit, and the announcer is working fine?

DizzasTeR

Quote from: Thijn on Oct 22, 2016, 01:18 PMSo you're basically saying your host is shit, and the announcer is working fine?

Hm, I never blamed the announcer and I've mentioned that it was working before. So how does a shitty host do such type of a thing. Isn't there a way to solve it

Thijn

Quote from: Doom_Kill3R on Oct 22, 2016, 01:33 PM
Quote from: Thijn on Oct 22, 2016, 01:18 PMSo you're basically saying your host is shit, and the announcer is working fine?

Hm, I never blamed the announcer and I've mentioned that it was working before. So how does a shitty host do such type of a thing. Isn't there a way to solve it
Your topic literally has [Announcer] as tag :P

What kind of host do you use?

DizzasTeR

Quote from: Thijn on Oct 22, 2016, 10:49 PMWhat kind of host do you use?

Not really sure what you mean by this but I have a VPS provided to me by a friend whose company provides VPSs. If this is not the answer to your question then can you elaborate what you mean by kind of host.

Thijn

Yeah that's what I meant.

I've not heard of VPSes that disable their network when they're being idle for too long. I think it's time to ask the providers' support instead of here, this isn't a VC:MP problem.

DizzasTeR

In that case, I'll get to the provider for assistance. Thanks.