I25 Server Maintenance: Difference between revisions
From OuroDev
Plutocracy (talk | contribs) Created page with "todo love, Pluto" |
Plutocracy (talk | contribs) fleshed out the servermonitor section, but jagnew's guide isn't public so I'm reaching out to him about that |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Monitoring and Proper Shutdown == | |||
The Server Monitor provides useful information for server administration and also allows you to properly shut down your server. | |||
=== Running ServerMonitor === | |||
: Adding the following lines to [[I25 loadBalanceShardSpecific.cfg|loadBalanceShardSpecific.cfg]] under a {{Ms|ServerRole}} will automatically launch the Server Monitor when you start up your server. | |||
: {| | |||
<syntaxhighlight>Server | |||
Command "servermonitor.exe -connect" | |||
End</syntaxhighlight> | |||
|} | |||
:* Additionally you can run it from the bin directory; it can be run with the {{Ms|-connect}} parameter to automatically connect to a dbserver running on the same machine. | |||
=== Monitoring Server Performance === | |||
[[File:i25_Server_Monitor.png|thumb]] | |||
==== Launchers ==== | |||
: Provides information regarding your Launchers, their CPU usage, as well as other statistics | |||
:* Each line corresponds to a running Launcher instance; for most smaller and solo servers there will be only one Launcher | |||
==== Mapservers ==== | |||
: Provides detailed information for each individual running Mapserver instance, including memory usage and player population | |||
:* Each individual mapserver instance corresponds to a zone in the game world | |||
:* Memory usage for any individual mapserver instance cannot exceed 2GB, as it is a 32-bit executable | |||
==== Stuck/Crash Mapservers ==== | |||
: Lists mapserver instances that have stopped responding or crashed entirely | |||
:* Mapservers can become stuck or crash from time to time; selecting one and clicking the Kill Process button will end the associated process | |||
:* If several mapservers are stuck or crashed, or frequently become so, this is indicative of an issue with your server that you will need to address | |||
==== Server Applications ==== | |||
: Details the status of other running server processes | |||
:* Also details individual CPU and Memory usage for each process | |||
:* The Kill Process button can be used to end the currently selected service | |||
=== Shutting Down Your Server === | |||
; The Server Monitor should be used wherever possible to shut your server down, to prevent database issues. | |||
: Clicking ''Shutdown DbServer'' in the upper right hand corner of the window will prompt you if you want to shut down the server | |||
:* You will also be prompted to enter a shutdown message which will appear to all connected players | |||
== SQL Database Backup and Maintenance == | |||
: link /u/jagnew78's Doc | |||
: summary of points | |||
Latest revision as of 17:59, 29 May 2019
Monitoring and Proper Shutdown
The Server Monitor provides useful information for server administration and also allows you to properly shut down your server.
Running ServerMonitor
- Adding the following lines to loadBalanceShardSpecific.cfg under a
ServerRolewill automatically launch the Server Monitor when you start up your server.
Server Command "servermonitor.exe -connect" End
- Additionally you can run it from the bin directory; it can be run with the
-connectparameter to automatically connect to a dbserver running on the same machine.
- Additionally you can run it from the bin directory; it can be run with the
Monitoring Server Performance
Launchers
- Provides information regarding your Launchers, their CPU usage, as well as other statistics
- Each line corresponds to a running Launcher instance; for most smaller and solo servers there will be only one Launcher
Mapservers
- Provides detailed information for each individual running Mapserver instance, including memory usage and player population
- Each individual mapserver instance corresponds to a zone in the game world
- Memory usage for any individual mapserver instance cannot exceed 2GB, as it is a 32-bit executable
Stuck/Crash Mapservers
- Lists mapserver instances that have stopped responding or crashed entirely
- Mapservers can become stuck or crash from time to time; selecting one and clicking the Kill Process button will end the associated process
- If several mapservers are stuck or crashed, or frequently become so, this is indicative of an issue with your server that you will need to address
Server Applications
- Details the status of other running server processes
- Also details individual CPU and Memory usage for each process
- The Kill Process button can be used to end the currently selected service
Shutting Down Your Server
- The Server Monitor should be used wherever possible to shut your server down, to prevent database issues.
- Clicking Shutdown DbServer in the upper right hand corner of the window will prompt you if you want to shut down the server
- You will also be prompted to enter a shutdown message which will appear to all connected players
SQL Database Backup and Maintenance
- link /u/jagnew78's Doc
- summary of points