SRCDS Steam group


Server wont start after rcon killserver
#1
i use this command to start my server

./srcds_run -game cstrike -autoupdate +map surf_greatest_river +maxplayers 40 +ip 95.154.192.34 +port 27015 -tickrate 120 > srcds.log 2>&1 &

but when i do rcon killserver or it crashes it starts(as shown) up but wont show on the server search or connect by consol it fails after 4 trys but if i take > srcds.log 2>&1 & off the end it shows this proof that it is up


****** Executing mani_server.cfg ******
couldn't exec mani_quake_sounds.cfg
****** Finished executing mani_server.cfg ******
Adding master server 72.165.61.189:27011
Adding master server 68.142.72.250:27011
hooked mp_restartgame 0
Connection to Steam servers successful.
VAC secure mode is activated.
Adding master server 72.165.61.189:27011
Adding master server 68.142.72.250:27011
hooked mp_restartgame 0
Connection to Steam servers successful.
VAC secure mode is activated.

can you help me please!

currant ports unblocked

iptables -A INPUT -p tcp --dport 27030 -j ACCEPT
iptables -A INPUT -p tcp --dport 27031 -j ACCEPT
iptables -A INPUT -p tcp --dport 27032 -j ACCEPT
iptables -A INPUT -p tcp --dport 27033 -j ACCEPT
iptables -A INPUT -p tcp --dport 27034 -j ACCEPT
iptables -A INPUT -p tcp --dport 27035 -j ACCEPT
iptables -A INPUT -p tcp --dport 27036 -j ACCEPT
iptables -A INPUT -p tcp --dport 27037 -j ACCEPT
iptables -A INPUT -p tcp --dport 27038 -j ACCEPT
iptables -A INPUT -p tcp --dport 27039 -j ACCEPT
iptables -A INPUT -p udp --dport 1200 -j ACCEPT
iptables -A INPUT -p udp --dport 27015 -j ACCEPT
iptables -A INPUT -p udp --dport 27016 -j ACCEPT
iptables -A INPUT -p udp --dport 27017 -j ACCEPT
iptables -A INPUT -p udp --dport 27018 -j ACCEPT
iptables -A INPUT -p udp --dport 27019 -j ACCEPT
iptables -A INPUT -p udp --dport 27020 -j ACCEPT
iptables -A INPUT -p tcp --dport 27015 -j ACCEPT
iptables -A INPUT -p udp --dport 27000 -j ACCEPT
iptables -A INPUT -p udp --dport 27001 -j ACCEPT
iptables -A INPUT -p udp --dport 27002 -j ACCEPT
iptables -A INPUT -p udp --dport 27003 -j ACCEPT
iptables -A INPUT -p udp --dport 27004 -j ACCEPT
iptables -A INPUT -p udp --dport 27005 -j ACCEPT
iptables -A INPUT -p udp --dport 27006 -j ACCEPT
iptables -A INPUT -p udp --dport 27007 -j ACCEPT
iptables -A INPUT -p udp --dport 27008 -j ACCEPT
iptables -A INPUT -p udp --dport 27009 -j ACCEPT
iptables -A INPUT -p udp --dport 27010 -j ACCEPT
iptables -A INPUT -p udp --dport 27011 -j ACCEPT
iptables -A INPUT -p udp --dport 27012 -j ACCEPT
iptables -A INPUT -p udp --dport 27013 -j ACCEPT
iptables -A INPUT -p udp --dport 27014 -j ACCEPT
iptables -A INPUT -p udp --dport 27015 -j ACCEPT
Reply
#2
try rcon quit instead
Reply
#3
HBS|Ryan Wrote:try rcon quit instead

no becouse i need the server to go down so i can change the default map rcon quit restarst the server now allowing me to change the default map and when i do rcon killserver the server starts but no 1 can join it evan tho the ports are unblocked
Reply
#4
[Image: b_560x95.png]
Reply
#5
iptables -A INPUT --dport 27000:27020 -j ACCEPT
Use that instead of all of your code, its easier. That forwards tcp and udp traffic, tcp traffic is for rcon. add -autoupdate to your startup line.
[Image: b_350x20_C002748-004880-FFFFFF-000000.png]
Reply
#6
pengy Wrote:iptables -A INPUT --dport 27000:27020 -j ACCEPT
Use that instead of all of your code, its easier. That forwards tcp and udp traffic, tcp traffic is for rcon. add -autoupdate to your startup line.

i you didn't notice -autoupdate is already in my start up command
Reply
#7
Sorry, I didn't see it at the very beginning, did you try an rcon quit command?
[Image: b_350x20_C002748-004880-FFFFFF-000000.png]
Reply
#8
pengy Wrote:Sorry, I didn't see it at the very beginning, did you try an rcon quit command?

no i need the server to shut down so i can restart it and change the default map but the only way i can do taht is by reinstall my linux server to reinstall my CSS server
Reply
#9
You can kill the server process by typing ps aux and grabbing the process id, and typing kill pid
[Image: b_350x20_C002748-004880-FFFFFF-000000.png]
Reply
#10
pengy Wrote:You can kill the server process by typing ps aux and grabbing the process id, and typing kill pid

? you meen in the command? i use putty to start the server and leave it running 24/7 but i close putty becouse ofc i can't leave my pc running 24/7 but my linux servr which runs my CSS server if 24/7
Reply
#11
start the server inside a screen session (i.e. run the "screen" command before running the server). then you can detach by pressing "ctrl+a d" and reattach to the server console by running "screen -R". this way you can easily stop and restart your server and also change maps etc. directly at the server console.
http://www.fpsmeter.org
http://wiki.fragaholics.de/index.php/EN:Linux_Optimization_Guide (Linux Kernel HOWTO!)
Do not ask technical questions via PM!
Reply
#12
BehaartesEtwas Wrote:start the server inside a screen session (i.e. run the "screen" command before running the server). then you can detach by pressing "ctrl+a d" and reattach to the server console by running "screen -R". this way you can easily stop and restart your server and also change maps etc. directly at the server console.

i've been trying to do that i don't understadn how i start a screen becouse i've got to log onto my server and then when i enter screen command it's sending that to ym server not putty
Reply
#13
russ939 Wrote:
BehaartesEtwas Wrote:start the server inside a screen session (i.e. run the "screen" command before running the server). then you can detach by pressing "ctrl+a d" and reattach to the server console by running "screen -R". this way you can easily stop and restart your server and also change maps etc. directly at the server console.

i've been trying to do that i don't understadn how i start a screen becouse i've got to log onto my server and then when i enter screen command it's sending that to ym server not putty

i can screen but i can't log back into it
Reply


Forum Jump:


Users browsing this thread: 4 Guest(s)