![]() Table of Contents
|
Restarting The server uses a process which runs for a long time, sometimes months, while modules are installed and reloaded. Challenger is designed for this, but during months of operation many things can happen. If the server suddenly starts using more resources than normal, or responses are slower, it might be a good idea to restart it. Restarting can be done either with the Shutdown/Shut down Roxen action or by killing its pike process. The start script will ensure that the server is restarted. Restarting the server takes from about 10 seconds up to a few minutes depending on server configuration. This is intentional, as Challenger still needs to finish serving the requests which were active when the shutdown procedure was initiated. The only noticeable effect when restarting should be that the server will not respond during startup.
Automatically restarting Challenger
Anti Block System
| ||
![]() |
You can set the timeout the ABS will use before checking if the server
is still up, by changing the Global Variables/Anti-Block-System/Timeout
variable. If this timeout is too fast the ABS may assume that your
server is hanged while it just slow to respond. By examining old debug
logs it is possible to see if the ABS has unnecissarily restarted the
server.
PID file
|