Ryzom

And yet those values are active in several other configs as well:

code/ryzom/server/admin_executor_service.cfg:ASPort="46701";
code/ryzom/server/admin_service.cfg:ASWebPort="46700";
code/ryzom/server/admin_service.cfg:ASPort="46701";
code/ryzom/server/admin_service_default.cfg://ASWebPort="46700";
code/ryzom/server/admin_service_default.cfg://ASPort="46701";
code/ryzom/server/common.cfg:AESPort="46702";
code/ryzom/server/dynamic_scenario_service.cfg:ASWebPort="46700";
code/ryzom/server/dynamic_scenario_service.cfg:ASPort="46701";
code/ryzom/server/dynamic_scenario_service.cfg:AESPort="46702";
code/ryzom/server/entities_game_service.cfg:AESPort="46702";
code/ryzom/server/input_output_service.cfg:AESPort="46702";

Particlularly the admin_service.cfg, which should override admin_service_default.cfg, right?

What's more:

code/ryzom/server/admin_service_default.cfg:AESHost="localhost";
code/ryzom/server/common.cfg:DontUseAES = 1;
code/ryzom/server/common.cfg:AESHost="localhost";

So If you add the AESHost="localhost"; line to admin_service.cfg that works as well.
Config bug!
[Not sure what AES does but I don't like cycling errors on my servers]

Nakarti,

First things first: please open a new thread rather than excavating 8+ month old threads.

We're going to need a bit more information than you provided - can you be explicit in what is happening? The previous poster has logs stating that the AES cannot connect to localhost:46701. This is the AES connecting to the AS, or rather failing to do so. So check your AS and find out why it is not running or why it is not listening on port 46701. Or if the AS is on a different machine then you will need to set the ASHost to be correct.

To summarize what these are - the AS (admin service) is manages all of the AES (Admin Executor Services.) There is one total AS installed, regardless of the number of shards. There is one AES per physical server. The AS acts as a management node routing commands and requests from its console and the admin web app to the various physical servers. It facilitates data collection as well as service restarts. When you request that a service (lets say IOS) shuts down and then you boot it on a different physical server what happens is the webapp forwards the request to the AS which sends a command to the AES to shut down the process. The AES is responsible for knowing what is running on its server and relaying this information back to the AS.

Technically you could bypass the whole AS/AES process by setting DontUseAES=1 and DontUseAS=1 in all of the config files - the way the default startup of Ryzom Core is (using the batch file) you essentially are bypassing it.

I'm not sure what you are running into but the admin and admin_executor configs in Hg work just fine for everyone else so it would be beneficial to get more detailed logging if there indeed is a problem.

Thank you.
sfb
/s