Table des matières

Serveur OpenNeL Khanat - Tour d'horizon

Note préalable : notre serveur de jeu utilisant RyzomCore / OpenNeL, toute la documentation qui s'y rapporte s'applique également à notre serveur de jeu : www.ryzomcore.org.
La page d'index alphabétique de leur wiki permet de trouver bon nombre d'informations utiles, de tutoriels (en anglais exclusivement par contre) : https://ryzomcore.atlassian.net/wiki/display/RC/Reference+Guides

Quelques définition préalables 

Dans notre cas, notre premier serveur unique, une machine virtuelle dénommée « kh-dev », fonctionnait sous Debian 6 (Squeeze) et était installée sur un véritable serveur physique : « ninm.net ». Notre second serveur tourne sous debian 8 (Jessie) et notre troisième est une machine virtuelle sous debian 8 aussi.

Lancement et arrêt des services du jeu

Le lancement et l'arrêt des services du jeu se font à l'aide d'un script simple une fois connecté sur notre serveur de jeu

Lancement des services du jeu « Khanat » :

$ shard start

Arrêt des services du jeu « Khanat » :

$ shard stop

Les services

Il y a 23 services comme le montre l'affichage du dossier des binaires de ryzom core. Cependant, ils ne sont pas tous utiles pour faire tourner un jeu :

khanat@kh-dev:~$ ls ryzomcore/code/build/bin/ryzom_*
ryzomcore/code/build/bin/ryzom_admin_service
ryzomcore/code/build/bin/ryzom_ai_service
ryzomcore/code/build/bin/ryzom_backup_service
ryzomcore/code/build/bin/ryzom_dynamic_scenario_service
ryzomcore/code/build/bin/ryzom_entities_game_service
ryzomcore/code/build/bin/ryzom_frontend_service
ryzomcore/code/build/bin/ryzom_general_utilities_service
ryzomcore/code/build/bin/ryzom_gpm_service
ryzomcore/code/build/bin/ryzom_ios_service
ryzomcore/code/build/bin/ryzom_log_analyser_service
ryzomcore/code/build/bin/ryzom_logger_service
ryzomcore/code/build/bin/ryzom_mail_forum_service
ryzomcore/code/build/bin/ryzom_mirror_service
ryzomcore/code/build/bin/ryzom_mission_compiler
ryzomcore/code/build/bin/ryzom_monitor_service
ryzomcore/code/build/bin/ryzom_naming_service
ryzomcore/code/build/bin/ryzom_patchman_service
ryzomcore/code/build/bin/ryzom_pd_support_service
ryzomcore/code/build/bin/ryzom_persistant_data_service
ryzomcore/code/build/bin/ryzom_reference_builder_service
ryzomcore/code/build/bin/ryzom_session_browser_service
ryzomcore/code/build/bin/ryzom_shard_unifier_service
ryzomcore/code/build/bin/ryzom_tick_service
ryzomcore/code/build/bin/ryzom_welcome_service

Détail des services :

Liste des ports

Cliquez pour afficher ⇲

Cliquez pour masquer ⇱

jeanluc@tomate:~/ryzomcore$ rgrep Port code/*/*/*.cfg code/nelns/admin_service/admin_service.cfg:WebPort = 49995; code/nelns/login_service/login_service.cfg:WSPort = 49999; port for the welcome service connection (default is 49999) code/nelns/login_service/login_service.cfg:WebPort = 49998; port for the web server (default 49998) code/nelns/login_service/login_service.cfg:ClientsPort = 49997; port for the clients connection (default 49997) code/ryzom/server/admin_executor_service.cfg:ASPort=“46701”; code/ryzom/server/admin_executor_service.cfg: “gw_aes.transportCmd aes_l3c(connect addr=”+AESHost+“:”+AESPort+“)”, code/ryzom/server/admin_executor_service.cfg: “asc_gw.transportCmd l3c(connect addr=”+ASHost+“:”+ASPort+“)”, code/ryzom/server/admin_executor_service.cfg: “aes_gw.transportCmd l3s(open port=”+AESPort+“)”, 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/admin_service_default.cfg: “moduleManager.createModule AdminService as webPort=”+ASWebPort, code/ryzom/server/admin_service_default.cfg: “as_gw.transportCmd l3s(open port=”+ASPort+“)”, code/ryzom/server/ai_service.cfg:SUPort = 50505; code/ryzom/server/ai_service.cfg:SUAddress = SUHost+“:”+SUPort; code/ryzom/server/backup_service.cfg:WebPort = 49970; code/ryzom/server/backup_service_default.cfg:ListeningPort = 49990; code/ryzom/server/backup_service_default.cfg:WebPort = 49898; code/ryzom/server/backup_service_default.cfg: Port for the Layer 3 interface of the backup service code/ryzom/server/backup_service_default.cfg:L3ListeningPort = 49950; code/ryzom/server/backup_service_interface.cfg:L3BSPort = “49950”; code/ryzom/server/common.cfg:AESPort=“46702”; code/ryzom/server/common.cfg: “gw_aes.transportCmd aes_l3c(connect addr=”+AESHost+“:”+AESPort+“)”, 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/dynamic_scenario_service.cfg:SUPort = 50505; code/ryzom/server/dynamic_scenario_service.cfg:SUGlobalPort = 50503; code/ryzom/server/dynamic_scenario_service.cfg:L3BSPort = “49950”; code/ryzom/server/dynamic_scenario_service.cfg:L3SlaveBSPort = “49951”; code/ryzom/server/dynamic_scenario_service.cfg:L3MasterLGSPort = 49992; code/ryzom/server/dynamic_scenario_service.cfg:LGSBSPort = 49994; code/ryzom/server/dynamic_scenario_service.cfg:L3LGSBSPort = 49995; code/ryzom/server/dynamic_scenario_service.cfg:“gw_aes.transportCmd aes_l3c(connect addr=localhost:”+AESPort+“)”, code/ryzom/server/dynamic_scenario_service.cfg:SUAddress = SUHost+“:”+SUPort; code/ryzom/server/dynamic_scenario_service.cfg:BasePort = 51400; code/ryzom/server/entities_game_service.cfg:AESPort=“46702”; code/ryzom/server/entities_game_service.cfg:SUPort = 50505; code/ryzom/server/entities_game_service.cfg:SUGlobalPort = 50503; code/ryzom/server/entities_game_service.cfg:L3MasterLGSPort = 41292; code/ryzom/server/entities_game_service.cfg:L3SlaveLGSPort = 49993; code/ryzom/server/entities_game_service.cfg:SUAddress = SUHost+“:”+SUPort; code/ryzom/server/entities_game_service_default.cfg: “glob_gw.transportCmd l3c(connect addr=”+SUHost+“:”+SUGlobalPort+“)”, code/ryzom/server/entities_game_service_default.cfg: “lgs_gw.transportCmd masterL3c(connect addr=”+MasterLGSHost+“:”+L3MasterLGSPort+“)”, code/ryzom/server/entities_game_service_default.cfg: “lgs_gw.transportCmd slaveL3c(connect addr=”+SlaveLGSHost+“:”+L3SlaveLGSPort+“)”, code/ryzom/server/frontend_service.cfg:FSUDPPort = 47851; code/ryzom/server/frontend_service_default.cfg:FrontendPort = 47851; code/ryzom/server/frontend_service_default.cfg:ListenAddress = FSListenHost+“:”+FSUDPPort; code/ryzom/server/input_output_service.cfg:AESPort=“46702”; code/ryzom/server/input_output_service.cfg:SUPort = 50505; code/ryzom/server/input_output_service.cfg:SUGlobalPort = 50503; code/ryzom/server/input_output_service.cfg:L3MasterLGSPort = 41292; code/ryzom/server/input_output_service.cfg:L3SlaveLGSPort = 49993; code/ryzom/server/input_output_service.cfg:SUAddress = SUHost+“:”+SUPort; code/ryzom/server/input_output_service_default.cfg: “glob_gw.transportCmd l3c(connect addr=”+SUHost+“:”+SUGlobalPort+“)”, code/ryzom/server/input_output_service_default.cfg: “lgs_gw.transportCmd masterL3c(connect addr=”+MasterLGSHost+“:”+L3MasterLGSPort+“)”, code/ryzom/server/input_output_service_default.cfg: “lgs_gw.transportCmd slaveL3c(connect addr=”+SlaveLGSHost+“:”+L3SlaveLGSPort+“)”, code/ryzom/server/logger_service.cfg:LGSL3Port = 41292; code/ryzom/server/logger_service.cfg:“lgs_gw.transportCmd l3s(open port=”+ LGSL3Port +“)”, code/ryzom/server/naming_service.cfg:BasePort = 51000; code/ryzom/server/session_browser_server.cfg:SBSPort = 48851; code/ryzom/server/session_browser_server.cfg:“moduleManager.createModule SessionBrowserServerMod sbs suAddr=”+SUHost+“:49999 listenPort=”+SBSPort+“ ring_db(host=”+DBHost+“ user=”+DBRingUser+“ password=”+DBRingPass+“ base=”+DBRingName+“)”, code/ryzom/server/shard_unifier_service.cfg:SUGlobalPort = 50503; code/ryzom/server/shard_unifier_service_default.cfg: “glob_gw.transportCmd l3s(open port=”+SUGlobalPort+“)”, code/ryzom/server/welcome_service.cfg:SUPort = 50505; code/ryzom/server/welcome_service.cfg:SUAddress = SUHost+“:”+SUPort; </hidden>