Setting up second server on dedi problems

[PTG_Chef_uk]

Hi guys, i'm trying to set up a second server on the dedi but to no avail.

I've created a new dedicated_cfg file and a new game_settings file (created copies of first server and changed server name) but alas when I go to launch the CMD window shuts down immediately.

Any ideas? Does the second server need to run on a separate port?

[Slig]

Any ideas? Does the second server need to run on a separate port?

Yes and no : if you keep the same then the 1st started one will use them, and the other whill use the next values (+1) because they are already occupied. Anyway a better practise is to set different value (available ones), so it will really use the values indicated in the config file.

What really need to be different is the login (you are supposed to go on the player page and create server logins, oine per server, and not to use your player login)

[PTG_Chef_uk]

Any ideas? Does the second server need to run on a separate port?

Yes and no : if you keep the same then the 1st started one will use them, and the other whill use the next values (+1) because they are already occupied. Anyway a better practise is to set different value (available ones), so it will really use the values indicated in the config file.

What really need to be different is the login (you are supposed to go on the player page and create server logins, oine per server, and not to use your player login)

Ahh, i see Thanks, will give that a go.

[PTG_Chef_uk]

Hmm, still having the same issue :/ Set up a separate port. Created another dedicated server login. What else am I missing that needs changing?

[nighthawk4571]

Suggestions:
Did you only change the <xmlrpc_port>5000</xmlrpc> setting? E.g --> 5015
Remember there are two other settings which should also be unique to each server:
<server_port>2350</server_port> E.g --> 2315
and
<server_p2p_port>3450</server_p2p_port> E.g --> 3415

If your server starts then shuts down, there may be a clue in the most recent server log file (look in the 'Logs' folder).
For example, the new server login may not have been processed fully in the MasterServer, so it is not yet recognized/ authorized.
....... 'Identifying on master server
....... OK '
Another example, the dedicated_cfg file may not have been found (you should see an error in the log). The default 'dedicated_cfg.default.txt' needs to be renamed to 'dedicated_cfg.txt' to match the entry in your .sh or .bat start script.

If you are using a controller (e.g. my favourite XAseco2), you will also need to register your server login to get a unique dedimaniacode which goes into the dedimania.xml file: http://dedimania.net/tm2stats/?do=register
This is entered along with your server login:
'<login>?PTG_Chef_uk_server_account_login_name?</login>
<dedimaniacode>blahblahblah</dedimaniacode>'
I'm not sure this will cause your problem but just a thought. Definitely look at the log file/s (one is created every time you start your server).

Cheers

[PTG_Chef_uk]

Didn't realise those ports needed changing too working now Thanks guys.

[nighthawk4571]

np - another happy ending - now you'll have twice the fun!