Closed jffz closed 6 years ago
we have the same bug/error using following startup-parameters for csgo with duels:
./srcds_run -game csgo +hostname SERVERNAME +host_workshop_map 125438255 +workshop_start_map 125438255 +host_workshop_collection 76561198082857351 -maxplayers_override 12 -port 27015 -ip 0.0.0.0 -tickrate 128 -usercon -retry +game_type 0 +game_mode 1 +mapgroup mg_bomb +bot_quota 0 +sv_hibernate_when_empty 0 -strictportbind +sv_setsteamaccount XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -authkey YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY -steam_dir /home/container/steamcmd/ -steamcmd_script script_autoupdate.txt -autoupdate -norestart
if we use the parameters for csgo with retake, its working:
./srcds_run -game csgo +hostname SERVERNAME +map de_dust2 -maxplayers_override 7 -port 27017 -ip 0.0.0.0 -tickrate 128 -usercon -retry +game_type 0 +game_mode 1 +mapgroup mg_bomb +bot_quota 0 +sv_hibernate_when_empty 0 -strictportbind +sv_setsteamaccount XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -autoupdate -steam_dir /home/container/steamcmd/ -steamcmd_script script_autoupdate.txt -autoupdate -norestart
latest console output after starting the server:
Connection to Steam servers successful. Public IP is A.B.C.D. Assigned persistent gameserver Steam ID [G:1:1393818]. VAC secure mode is activated. GC Connection established for server version 577, instance idx 1
also we can't send commands via the console to the server. input and enter-button working, but no output will be showed/refreshed.
@danrokzz Does this still happen with the latest stable or beta versions?
@lancepioch Currently i have no panel runnig. But I think it was already fixed.
At the end of march we will run a large part of our lanparty servers with Pterodactyl-Panel where I can check this and would report if there is still an issue.
Thanks @danrokzz comment or reopen the issue if it's still happening.
Using srcds with workshop maps seems to break ptero's status.
Launch Options i used
I already checked
/srv/daemon/src/services/srcds/main.json
and the startup sequence is ok.There is a 'known bug' about the -norestart option that has been discussed in #270 so maybe it's related, not sure.
I'll try to dig more about this but wasn't able to find any useful info atm.