Server listed as Down

[geddak]

So on Dec. 26 I checked nobody was logged into my server, then updated hotzones, stopped and restarted it, and went off on some holiday stuff. Today I wanted to play, but when I tried to login, my server was listed as down. It says it was last seen about the time I stopped and restarted it on the 26th. I tried restarting it (linux server with server_status said zones were up) but still listed as down. I asked on Discord, and checked the logs, but could find no reason for it to be down. Eventually I reinstalled the whole thing, but...still down. I am out of ideas - where else can I check what the issue is? Someone suggested the IP might be banned, but that doesn't really make any sense. Any thoughts?

[geddak]

So, someone suggested I check world - running ./world changes down status to locked (though not set in my eqemu_config.json to be locked), but then I can see the server in the login server list - when I login it shows my characters (and switches status to pending), but if I try to log a character in, it tells me that the zone is not available, and in the ./world output it says:
[World] [Info] Attempting autobootup of [poknowledge] ([202]:[0])
[World] [Info] No zoneserver available to boot up
(this is after I set server_start so 30 zones should be available to boot up).

It was suggested this might be a port issue.
Running on Ubuntu, so tried the ss -ltnp command and found that port 9000 and 9001 are open by user world:
LISTEN 129 128 0.0.0.0:9000 0.0.0.0:* users:(("world",pid=3809338,fd=14))
LISTEN 129 128 0.0.0.0:9001 0.0.0.0:* users:(("world",pid=3809338,fd=15))

But I don't see ports 7000-7400, 5998, etc.

It looks like these ports are automatically opened - but not sure using what command, or why the other ones are not.

Any thoughts? Anyone who is running a linux server?

[geddak]

I don't think it's a config thing, but I have been wrong once or twice before - if you see anything please let me know:
{
"server" : {
"chatserver" : {
"host" : "0.0.0.0",
"port" : "7778"
},
"database" : {
"db" : "**dbname**",
"host" : "127.0.0.1",
"password" : "**dbuserpw**",
"port" : "3306",
"username" : "**dbusername**"
},
"directories" : {
"opcodes" : "assets/opcodes/",
"patches" : "assets/patches/"
},
"files" : {
"mail_opcodes" : "assets/opcodes/mail_opcodes.conf",
"opcodes" : "assets/opcodes/opcodes.conf"
},
"mailserver" : {
"host" : "0.0.0.0",
"port" : "7778"
},
"qsdatabase" : {
"db" : "**dbname**",
"host" : "localhost",
"password" : "**dbuserpw**",
"port" : "3306",
"username" : "**dbusername**"
},
"world" : {
"key" : "**key**",
"loginserver1" : {
"account" : "**world server acct**",
"host" : "login.eqemulator.net",
"legacy" : "1",
"password" : "**world server pw**",
"port" : "5998"
},
"loginserver2" : {
"account" : "**world server acct**",
"host" : "127.0.0.1",
"password" : "**world server pw**",
"port" : "5998"
},
"loginserver3" : {
"account" : "**world server acct**",
"host" : "login.projecteq.net",
"password" : "**world server pw**",
"port" : "5998"
},
"longname" : "Hellefire",
"shortname" : "HEL",
"tcp" : {
"ip" : "127.0.0.1",
"port" : "9001"
},
"telnet" : {
"enabled" : "true",
"ip" : "0.0.0.0",
"port" : "9000"
}
},
"zones" : {
"defaultstatus" : "0",
"ports" : {
"high" : "7400",
"low" : "7000"
}
}
}
}

[geddak]

OK, problem fixed - it was a weird mash...adding address and local address to config (both the same as it is a cloud server), and cleaning up some db bits for launcher and launcher_zones. But we are back up!