1
2
Well definitely leave threading off. If it was on from the beginning then it throws a lot of this report into question; threading has known issues.
|
root@ns503038:~/HOEngine# ls
HOEngine.dmb HOEngine.rsc root@ns503038:~/HOEngine# DreamDaemon HOEngine.dm b -trusted Fri Apr 24 18:27:06 2015 World opened on network port 50224. Welcome BYOND! (5.0 Beta Version 507.1273) Or this code can be embedded: The BYOND hub reports that port 50224 is reachabl e. |
In response to Lavitiz
|
|
Lavitiz wrote:
The game is reachable, it just doesn't show on the hub. =[ Just a few debugging questions -- 1) What is your output for the following two commands... DreamDaemon 2) What is the command-line you are using? e.g. DreamDaemon <game_path> <port> <params> 3) I presume that when you run this command... iptables -L 4) Download iftop, a free program for Linux distros that allows you to monitor traffic. Do you see any traffic going to tesla.byond.com or 50.22.142.19? 5) Could you screenshot the output of the following or copy and paste it? (feel free to replace or blur out any sensitive data): netstat -a |
In response to Xirre
|
|
Xirre wrote:
Lavitiz wrote: root@167:~/servers# DreamDaemon root@167:~/servers# DreamDaemon -version 2) What is the command-line you are using? e.g.Same path? Lol. DreamDaemon PathToDmb.Dmb PortHere param2turnOffThreading(Forgot) & disown disown prevents sighup from being called when disconnecting from the terminal. 3) I presume that when you run this command...iptables has the tcp ports I need forwarded setup. 4) Download iftop, a free program for Linux distros that allows you to monitor traffic. Do you see any traffic going to tesla.byond.com or 50.22.142.19?I don't have time to do this at this time, but like I said already I can reach that destination. 5) Could you screenshot the output of the following or copy and paste it? (feel free to replace or blur out any sensitive data): root@167:~/servers# netstat -a |
Issue fixed, Lavitz has a control panel install which to his knowledge didn't have a firewall (or firewall module) enabled, but it did.
Stopping the firewall has fixed the issue for now and the game is now on the hub. More investigation is needed as the port was open in the firewall but not accessible. |
Thanks, for the help man. Much appreciated. :3
Thanks to the rest of you for trying as well. |
1
2
I've only forwarded for TCP if that makes a difference.
I've also tried with threading off and nothing changed.
I might be upgrading my VPS once again in the near future, if anything I'm hoping that helps. Right now I'm using a server that uses OpenVZ for dev purposes and I plan to upgrade to one that uses VMware. I was told that's better and more stable.