...
Since build 5.2.1537 the service type is changed from simple to forking. Also the file permissions containing the main WCS process PID are set according to systemd requirements. The service is marked as active (running), and systemd may send a signaldirectly to the main WCS process to stop it if necessary
Automatic service restart on failure
Since build 5.2.1562 the service unit webcallserver.service will be restarted automatically if the service becomes failed for some reason. Up to 5 relaunch tries will be done if no more than 2 minutes passed between them.
The service still may be stopped or started manually. If service is stopped manually, it will not be relaunched.
Automatic service restart n=may be disabled with the following command
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd /usr/local/FlashphonerWebCallServer/bin
sudo ./webcallserver set-service-restart disable |
Launch from command line
WCS can be started from command line if necessary:
...
Environment variables and parameters of the start are set in the setenv.sh script. In this script you can se use additional parameters for WCS Core and WCS Manager. Also, here you can set the parameter that prevent memory leaks on multi-CPU systems:
...
In some cases, for example, if the server won't start and does not produce any errors, you may need to start the server with direct logging to the 'stdout' console. Direct output to stdout cannot be used in production, because the server will be stopped if the console is closed or the SSH connection is lost. That is why we recommend using stdout output only for debug purposes.
To start the server in this mode, use the following command:the following command:
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd /usr/local/FlashphonerWebCallServer/bin
sudo ./webcallserver start standalone |
Starting with JVM output redirection to a log file
Since build 5.2.1562 WCS may be launched with JVM output redirected to a file like direct stdout logging
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd /usr/local/FlashphonerWebCallServer/bin sudo ./webcallserver start standalone--java-log |
In this case, all Java output will be redirected to the /usr/local/FlashphonerWebCallServer/logs/java.log file. The feature should be used for debugging purposes only but not in production, because the resulting file size may be too large.
Launching with different user permissions
...