ID:1803588
 
Resolved
BYOND Version:507
Operating System:Linux
Web Browser:Firefox 35.0
Applies to:Dream Daemon
Status: Resolved

This issue has been resolved.
The Linux Distro of BYOND v507.1273 does not seem to be reporting live games to the hub, yet people can still connect to the server and everything is configured properly. I'm having issues while running under Debian 7.

HUB: http://www.byond.com/games/Lavitiz/HarmonyOnline

Live Server: byond://immortal-phoenix.com:2026
This might be something on the individual system, not necessarily anything related to that build. Still a bug of course, but other Linux users have had games report to the hub.
In response to Lummox JR
Lummox JR wrote:
This might be something on the individual system, not necessarily anything related to that build. Still a bug of course, but other Linux users have had games report to the hub.

Do you have any idea on where I should start looking to have this issue fixed?
In response to Lavitiz
Which version does it work in?
In response to Murrawhip
Murrawhip wrote:
Which version does it work in?

I've tried both stable and beta and none seem to report. I've yet to find a version that reports properly. This makes me believe it has to do with something on my end, however being new to using linux I'm not quite sure where I'd need to look to find a solution.
The FreeBSD versions have always been flaky as hell with appearing on the hub and randomly disappearing.
Any idea on how to resolve this?
I don't think this issue is necessarily specific to Linux, but probably is an issue with hub communication. I'll look into it when I can, but I don't have any immediate suggestions.

Maybe you could try tracert to see if your connection to hub.byond.com is losing packets. That would at least give you some baseline information.
Thanks, it's much appreciated.

I did as you asked and here was the output:
root@167:~# traceroute hub.byond.com
traceroute to hub.byond.com (50.22.142.19), 30 hops max, 60 byte packets
1 214.ip-192-99-168.net (192.99.168.214) 0.166 ms 0.036 ms 0.082 ms
2 bhs-g2-6k.qc.ca (178.32.135.51) 2.404 ms 3.864 ms 3.816 ms
3 * mtl-2-6k.qc.ca (198.27.73.6) 2.041 ms 2.078 ms
4 chi-2-6k.il.us (198.27.73.172) 19.685 ms * *
5 te1-7.bbr01.eq01.chi01.networklayer.com (206.223.119.63) 19.340 ms 19.333 ms 19.211 ms
6 ae7.bbr02.eq01.chi01.networklayer.com (173.192.18.171) 19.124 ms 22.638 ms 22.464 ms
7 ae1.bbr02.cs01.den01.networklayer.com (173.192.18.131) 174.157 ms 47.435 m s 47.600 ms
8 ae7.bbr01.cs01.den01.networklayer.com (173.192.18.168) 49.741 ms 49.634 ms 49.527 ms
9 ae0.bbr01.wb01.sea02.networklayer.com (173.192.18.144) 81.057 ms 81.072 ms 81.142 ms
10 ae0.dar01.sr01.sea01.networklayer.com (173.192.18.199) 80.991 ms ae0.dar02. sr01.sea01.networklayer.com (173.192.18.159) 81.336 ms ae0.dar01.sr01.sea01.net worklayer.com (173.192.18.199) 81.083 ms
11 po2.fcr02.sr03.sea01.networklayer.com (67.228.118.227) 81.670 ms po1.fcr02. sr03.sea01.networklayer.com (67.228.118.225) 81.772 ms po2.fcr02.sr03.sea01.net worklayer.com (67.228.118.227) 81.525 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


root@167:~# traceroute -T hub.byond.com
traceroute to hub.byond.com (50.22.142.19), 30 hops max, 60 byte packets
1 214.ip-192-99-168.net (192.99.168.214) 0.053 ms 0.040 ms 0.024 ms
2 * * *
3 mtl-2-6k.qc.ca (198.27.73.6) 39.855 ms 40.011 ms *
4 * * *
5 te1-7.bbr01.eq01.chi01.networklayer.com (206.223.119.63) 17.856 ms 17.965 ms 17.836 ms
6 ae7.bbr02.eq01.chi01.networklayer.com (173.192.18.171) 18.012 ms 17.954 ms 17.878 ms
7 ae1.bbr02.wb01.sea02.networklayer.com (50.97.19.18) 87.392 ms 177.519 ms 173.901 ms
8 ae1.dar01.sr01.sea01.networklayer.com (173.192.18.143) 172.988 ms ae1.dar02.sr01.sea01.networklayer.com (173.192.18.185) 173.329 ms 172.638 ms
9 po2.fcr02.sr03.sea01.networklayer.com (67.228.118.227) 172.527 ms 155.417 ms 155.326 ms
10 tesla.byond.com (50.22.142.19) 81.133 ms 77.618 ms 77.960 ms

I'm going to assume those stars mean packets started dropping and not reaching their destination.
I believe that does look like dropped packets. I'm no network expert though.
The first traceroute didn't make it to the destination and has dropped completely as Lum said.

Second one looks ok ish I would open a ticket with your provider.
I found the host files of some game that was compiled many, many years ago and it reported to the hub just fine. In fact, it reported immediately. This project was hosted with the latest beta but the server was compiled with a version that was released years ago.

Anything compiled with the latest Beta or Stable do not seem to report to the hub.

Although something does look wrong with those traceroutes, pinging hub.byond.com always seems to work- Although with varying results(80-200ms).

Seeing as this other project reports immediately makes me assume it might have something to do with BYOND. I'm not sure though, I'm just a little guy. :(
If you have ddos filtering that could be playing a part too, it really depends how touchy it is I believe games ping back to hub every 5 minutes?
In response to A.T.H.K
A.T.H.K wrote:
If you have ddos filtering that could be playing a part too, it really depends how touchy it is I believe games ping back to hub every 5 minutes?

I do, but it's never activated so I'd imagine that's not a role. Once the system detects an attack it'll mitigate it and inform me.
Bump. Updated again and still nothing shows up on the hub. Pinging hub.byond.com with no packet loss. Ports are forwarded and reachable.
The Linux distro really isn't any different from the Windows version in terms of hub behavior. I'm confused as to why this would only show up in Linux; it's far likelier that the machine itself plays a role here.
In response to Lummox JR
Do you know where I should be looking then? I have no idea where to even look to try and solve this problem. :(
In response to Lummox JR
Lummox JR wrote:
The Linux distro really isn't any different from the Windows version in terms of hub behavior. I'm confused as to why this would only show up in Linux; it's far likelier that the machine itself plays a role here.

http://www.byond.com/forum/?post=1494956

There's somewhere to start. I believe about 2 days after it was fixed the problem popped up momentarily again. But, I haven't seen it ever since. I also haven't allowed threads ever since either. I'm not sure threads are stable enough to be used by multiple games for public hosting just yet. I really wouldn't know since I haven't had any time to test anything.

Hopefully this helps, Lum & Lav.

One thing I can say to add on to this is if things still don't work is:
iptables -F
This will flush your iptables. Thus, deleting all entries.

If it still doesn't work, ping byond.com, hub.byond.com, tesla.byond.com, and games.byond.com and add the respective IPs to your iptables as allow. I believe they use TCP only?
In response to Xirre
The issue in that thread was tied to randomization not initializing properly, which impacted a world ID that really shouldn't ever see conflicts--so that it often did. That should no longer be the case.
Lavitz, can you upload the files somewhere please?
Page: 1 2