Server shutdown and startup

Top  Previous  Next

Launch WCS after licence activation using following instruction:

 

service webcallserver start

 

Server shutdown will be executed after instruction:

 

service webcallserver stop

 

NOTICE! Server startup will take about 1 minute.

 

There are a few methods to ensure that server has started and it is ready for operation:

 

1.Ensure that server process is operating:

 ps aux | grep WebCallServer

 

Two processes should be displayed in console: WCS Core (20850 in the example below) and WCS Manager (20806 in the example below):

 

[root@localhost tmp]# ps aux | grep WebCallServer

root     20806  0.4 45.1 522148 236512 pts/0   Sl   10:56   0:59 java -Dloader.path=/usr/local/FlashphonerWebCallServer-3.0.1007/lib/tbs-commons.jar,/usr/local/FlashphonerWebCallServer-3.0.1007/lib/wcs_manager-1.0.jar -Dcom.flashphoner.fms.AppHome=/usr/local/FlashphonerWebCallServer -jar /usr/local/FlashphonerWebCallServer-3.0.1007/lib/wcs_manager-1.0.jar -Xmx1200M -Djava.net.preferIPv4Stack=true -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=50999 -XX:ErrorFile=/usr/local/FlashphonerWebCallServer/logs/error%p.log -Dcom.flashphoner.fms.AppHome=/usr/local/FlashphonerWebCallServer -Djava.library.path=/usr/local/FlashphonerWebCallServer/lib/so:/usr/local/FlashphonerWebCallServer/lib -cp /usr/local/FlashphonerWebCallServer/lib/* com.flashphoner.server.Server

root     20850  0.0 16.5 1567800 86636 pts/0   Sl   10:57   0:06 java -Xmx1200M -Djava.net.preferIPv4Stack=true -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=50999 -XX:ErrorFile=/usr/local/FlashphonerWebCallServer/logs/error%p.log -Dcom.flashphoner.fms.AppHome=/usr/local/FlashphonerWebCallServer -Djava.library.path=/usr/local/FlashphonerWebCallServer/lib/so:/usr/local/FlashphonerWebCallServer/lib -cp /usr/local/FlashphonerWebCallServer/lib/* com.flashphoner.server.Server

root     22053  0.0  0.1  61152   732 pts/0    R+   14:51   0:00 grep WebCallServer

[root@localhost tmp]#

 

 

2.Ensure that server process listens for main ports:

 netstat -nlp | grep java

 

[root@localhost tmp]# netstat -nlp | grep java
tcp        0      0 0.0.0.0:1098  0.0.0.0:* LISTEN 20850/java
tcp        0      0 0.0.0.0:8080  0.0.0.0:* LISTEN 20850/java
tcp        0      0 0.0.0.0:8081  0.0.0.0:* LISTEN 20850/java
tcp        0      0 0.0.0.0:50999 0.0.0.0:* LISTEN 20850/java
tcp        0      0 0.0.0.0:8443  0.0.0.0:* LISTEN 20850/java
tcp        0      0 :::9091       :::*      LISTEN 20806/java
tcp        0      0 :::1099       :::*      LISTEN 20806/java
tcp        0      0 :::2000       :::*      LISTEN 20806/java
udp        0      0 0.0.0.0:1935  0.0.0.0:*        20850/java

 

 

If you took into use the standard set of ports, then in the table of ports listened after entering netstat instruction ports #8080 (Websockets) and #1935 (RTMFP) or other ports, that you have configured for WCS4 server, should appear.

 

3. Ensure that WCS4 server is writing main server log of the Core.

 

tail -f /usr/local/FlashphonerWebCallServer/logs/server_logs/flashphoner.log

 

The information about settings, with whom server started, should appear.

 

Example:

 

15:59:37,378 INFO        Config - main LOAD_BALANCING_SERVERS: null

15:59:37,378 INFO        Config - main STREAM_MODE_UDP: true

15:59:37,379 INFO        Config - main LOAD_TOOL_ENABLED: false

15:59:37,379 INFO        Config - main CLI_ENABLED: false

15:59:37,379 INFO        Config - main RMI_PORT: 1098

15:59:37,379 INFO        Server - main Starting server...

15:59:37,492 INFO        KeepAliveManager - KeepAliveManager Start keepAlive thread KeepAliveManager

15:59:37,614 INFO        Server - main Listening RTMFP on 1935 port, bufferSize: 64000

15:59:37,750 INFO        Server - main Listening WebSocket on 8080 port, bufferSize: 64000

15:59:37,759 INFO        Server - main Listening WebSocket Ssl on 8443 port, bufferSize: 64000

 

Logs must react on web-clients connections. If it doesn't happen during the testing, ensure that server process is working and web-client is configured properly to connect to this server. Refer to section Troubleshooting for additional information.

 

4. Ensure that WCS4 server is writing main server log of the Administrative Module:

 

tail -f /usr/local/FlashphonerWebCallServer/logs/flashphoner_manager.log

 

15:59:36,277 INFO  gerCommandLineRunner - main Starting server node

15:59:36,278 INFO  ServerProcess - main Starting server node

15:59:36,293 INFO  ServerProcess - main Arg: java

15:59:36,294 INFO  ServerProcess - main Arg: -Xmx1200M

15:59:36,294 INFO  ServerProcess - main Arg: -Djava.net.preferIPv4Stack=true

15:59:36,294 INFO  ServerProcess - main Arg: -Dcom.sun.management.jmxremote.ssl=false

15:59:36,294 INFO  ServerProcess - main Arg: -Dcom.sun.management.jmxremote.authenticate=false

15:59:36,294 INFO  ServerProcess - main Arg: -Dcom.sun.management.jmxremote.port=50999

15:59:36,294 INFO  ServerProcess - main Arg: -XX:ErrorFile=/usr/local/FlashphonerWebCallServer/logs/error%p.log

15:59:36,294 INFO  ServerProcess - main Arg: -Dcom.flashphoner.fms.AppHome=/usr/local/FlashphonerWebCallServer

15:59:36,294 INFO  ServerProcess - main Arg: -Djava.library.path=/usr/local/FlashphonerWebCallServer/lib/so:/usr/local/FlashphonerWebCallServer/lib

15:59:36,294 INFO  ServerProcess - main Arg: -cp

15:59:36,295 INFO  ServerProcess - main Arg: /usr/local/FlashphonerWebCallServer/lib/*

15:59:36,295 INFO  ServerProcess - main Arg: com.flashphoner.server.Server

15:59:36,313 INFO  Manager - main Started Manager in 49.416 seconds (JVM running for 51.706)

 

If server process is started and there are no errors in the logs, it means that WCS server is ready for operation and you can start testing.