Linux GURU needed.... UDP issue

Sheir,
You definitely know your game servers... . I tried that too. In fact I have one that is set for port 27961 all the time and that one, strangely enough, will never show up in the ID master list. It seems that when I start a new server, on a different port, it will sometimes show. So what I end up doing is once a server stops showing up, I start a new one and the Q3 game will default to the next available port higher than the most active over 27960. So when the game on port 27960 stops showing up, Ill start up another server and it will default to 27961 and may or may not show up on ID Master for a short period, in the meantime I'll shut down the one on port 27960 since noone is connecting.....and so on....but thats a good idea, but been there/done that.....[]

DwArFlOrD

 

Did you trying putting up a server with no mod? Might be something in the mod causing a problem.

 

Ya, I tried that too, no luck. I may downgrade my version of the linux point release and try that. I hope that works. If you have anymore ideas let me know. Im also going to try and find some servers that are linux and showing up on the ID Master and email the admins and see what they do to make it work, maybe its a trick or something......
Thx,

DwArFlOrD

 

Ok, I just found my problem yesterday and confirmed it last night and today. It was never a UDP problem as I had originally thought (based on the info I had seen out there), so sorry to steer you guys in that direction. The tests you had me do also illustrates that UDP was not the culprit as well.
The problem is that when I start my game server, I am using the command shell in webmin to execute (cant SSH from work).....i.e. ./q3ded +set something... & and then entering that. When I do this the server "heartbeat" is sent out 1 time and then no more (which is why it sometimes initially shows up in the master servers and then disappears later). In addition, no more data is added to the game console log, which it should be because the application is running.....very strange. Well, if I open up an SSH window and start my server there, it runs perfectly! In any case, the problem (I suspect) is the way I fork off the daemon. This causes the problem for whatever reason. Probably something to do with the ttycon....? and how it handles the game server.
Is there a way to start a game server in an SSH window and run it, without having to keep the window open? Right now I can not achieve that goal. I currently run it like this:
./ctf & "or" ./ctf >/dev/null 2>&1 &
where ./ctf = (./q3ded +set fs_game IU1.2Beta +set net_ip 64.251.25.11 +set net_port 27960 +set com_hunkmegs 60 +set dedicated 2 +exec ctf1.cfg)
Now, eventhough I start it like ./ctf & "or" ./ctf >/dev/null 2>&1 & in the SSH window and I can still use that window for other work, but as soon as I close that window, the server will die and stop. Im looking for a way where I can close the SSH window and the server will continue to run. Im sure it is simple and has to do with a ttycon command or something, just looking for a way.
Thanks, and I hope not to steer you guys in the wrong direction again....[B)]
(This is the most success Ive had in about 6 months, feels good)
BTW, when is the Mandrake 10 Official ISO images coming out?

DwArFlOrD

 

Can you create a shell script similar to this, it will restart a crashed server:

#!/bin/bash

while true
do
/path/to/q3ded +set fs_game q3ut3 +set dedicated 2 +set net_port 27960 +set com_hunkmegs 56 +set sv_maxclients 16 +exec server.cfg
echo "server crashed on `date`" > last_crash.txt
done

Save this in a file called "startq3ut.sh", and place it your home directory. Assuming screen is installed (it usually is on Linux systems), you can run the script and start your server with:

$ screen -m -d sh startq3ut.sh

which would start your Urban Terror server already detached from the current client. You could then log out of your machine, and come back later on to get back into the console. To do so, run:

$ screen -r

If you've only got one screened process running. If you have more than one, run:

$ screen -list

to see all of them, and then choose the one you want to get back into by using:

$ screen -r pid.host

where pid.host is the line from the "screen -list" command.


I'm not exactly sure how this works, I'm playing around with it trying to get it to work for me. Now if only I could figure out why all seeing eye doesn't want to connect to my server.

 

sorry first post was balls up

In realation to the script startut3.sh I have found it functions better with thease ammendments

#!/bin/sh
while true
do
cd /home/kaos/quake3
./q3ded +set fs_game q3ut3 +set fs_base ./ +set dedicated 1 +set net_port 27960 +set com_hunkmegs 64 +set sv_maxclients 10 +exec q3ut3_server.cfg
echo "server crashed on `date`" > last_crash.txt
done

after some tesating I found with out the cd q3ded couldn't find the base dir hense fs_base ./ meening home dir of user starting script
I place the screen line in /etc/rc.d/rc.local which may be in a different palce but will give you launch on boot up hope this is usefull for ssh remote prob I presume you can reboot as required for kernel updates this would make it clear for you to do other things
theentity

 

I am not familiar with linux, but have you tried to run the shell/cmd using nohup

nohup ./ctf &
?


Robert Glass