Need help with 2 linux servers on same box

[AnnoyU]

Well I have spent the last 2 days banging my head against the wall searching for a solution for my problem so now I will finally just ask to see if anyone out there has an answer. Our clan recently purchased a second server for CoD which is running on the same box as our other server. I have full ftp access and ssh access and the ability to do about anything I need to to run the server. The problem i'm having is that currently both servers are sharing the hidden CoD directory /.callofduty which has the config_mp_server.cfg file, games_mp.log, and then the punkbuster folder also. I have tryed creating separate accounts of this directory and then directing each server using fs_homepath in the command line, but when I do this neither server will start correctly.

Each server is running in a seperate directory with specified names to distinguish them by. However, when i try to direct a server to a specific directory using fs_homepath, the actual server will start but punkbuster will not. Also i get errors saying it could not write to config_mp_server.cfg or unable to load games_mp.log. Of course, I'm a newbie with linux so that is not helping the case either. So basically I need to know how to run seperate accounts of punkbuster for each of my servers on the box, because i'm running out of ideas to try and need further imput. Do i need to be using fs_basepath instead?

[jdwright]

Check that you're using fs_basepath and fs_homepath correctly.

This post explains it pretty well.

http://www.codadmin.com/nuke/modules.php?name=Forums&file=viewtopic&p=7824#7824

[AnnoyU]

Thanks for the response and the link to that post. However, I'm still having problems and haven't the slightest clue what i'm doing wrong. I did exactly step by step what the post said to do and still no luck. The main error I keep getting is couldn't find default_mp.cfg, make sure call of duty installation is in the same folder.

[Kill_Control]

when i first started running multiple servers on our machine, i had a similar problem. i figgured it out when i cycled rcon passwords, but found that the server kept accepting the old password and not the new one. it drove me nuts until i discovered the hidden directory, and a config in there with the old rcon password.

fs_homepath is a godsent!
using fs_basepath actually hinders pb on our servers when used with fs_game for some reason, and since you are executing the binary in it's expected path, it picks it up automagically anyways.

here is a really ugly startup script that i use for our primary public server:

echo "--- Starting PRM Server ---";sleep 3s;cd cod;./cod_lnxded +PRM +set net_port 28960 +dedicated 2 +set fs_game prm +set fs_homepath ~/.prm +exec prm.default_mp.cfg&sleep 12s;cd ;echo "--- Making sure server is running --";sleep 2s;ps aux|grep cod_lnxded

i know, i should use screen, but i've never had it crash, and i like having full control. i have a script that will pick up the pid from ps and kill whatever server i want. if anybody wants it, i'll post it. it's actually quite simple and usable across a wide range, from killing specific users bash shells, ect ect .. i added the +PRM to the startup so the kill script can differenciate between the 4 servers we run (another would be +TWL for the match server, +TRT for rifles only.. you get the idea)

as far as the servers starting but not pb, search for 'sv_punkbuster is read only' and follow my fix there. it might help. i'd also recommend moving your .callofduty dir and starting over fresh and simple, one server at a time.

mv .callofduty .callofduty.org

there is no need to create the actual .callofduty folder again or whatever fs_homepath you specify, the game will do it for you.

good luck

[TS]

Why are you running 2 or more servers with the same base file?

This is nutz to do so as many more problems will arise !!

You always set each instance with it's own base and files...nerver share...bad juju !!

[imported_Sac]

Why are you running 2 or more servers with the same base file?

This is nutz to do so as many more problems will arise !!

You always set each instance with it's own base and files...nerver share...bad juju !!
Sorry but that's just plain wrong, this is what basepath and homepath are for and they work fine. The only potential problems are ones you create yourself if you don't understand the principles.

11 servers here on one box and one basepath. No way I'd do that with 11 copies of the same install. :!:

Now if you were talking about different customers' servers sharing a single basepath it would be different. :wink:

[Kill_Control]

wow,11??

must be a nice server!

once 2 servers get full, my cpu starts laggin..