...
Code Block | ||||
---|---|---|---|---|
| ||||
service webcallserver stop |
ATTENTION, server start can take up to 1 minute.
Here are a few ways to make sure the server has started and is ready to work:
Make 1. Make sure the server process is running.
...
The console should display two processes: WCS Core (20850 on the example below) and WCS Manager (20806 on process (11114 on the example below):
Code Block | ||||
---|---|---|---|---|
| ||||
[root@localhost tmp]# ps aux | grep WebCallServer root 2080611114 01.45 4557.1 3014240 1076652 522148? 236512 pts/0 Sl Jan18 10124:5645 java -Xmx1024M 0:59 java -Dloader.path=/usr/local/FlashphonerWebCallServer-5.0.2993/lib/tbs-commons.jar,/usr/local/FlashphonerWebCallServer-5.0.2993/lib/wcs_manager-1.0.jar -Dcom.flashphoner.fms.AppHome=/usr/local/FlashphonerWebCallServer -jar /usr/local/FlashphonerWebCallServer-5.0.2993/lib/wcs_manager-1.0.jar -Xmx1200M -Djava.net.preferIPv4Stack=true-XX:+UseConcMarkSweepGC -XX:NewSize=1024m -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=70 -Djava.net.preferIPv4Stack=true -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=50999 -Djava.rmi.server.hostname=p11.flashphoner.com -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 XX:+PrintGCDateStamps -XX:+PrintGCDetails -Xloggc:/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 -logs/gc-core-2019-01-18_18-19.log -XX:+ExplicitGCInvokesConcurrent -Dsun.rmi.dgc.client.gcInterval=36000000000 -Dsun.rmi.dgc.server.gcInterval=36000000000 -Dcom.flashphoner.fms.AppHome=/usr/local/FlashphonerWebCallServer -Djava.library.path=/usr/local/FlashphonerWebCallServer/lib/so:/usr/local/FlashphonerWebCallServer/lib -DWCS_NON_ROOT=false -DsessionDebugEnabled=false -Djdk.tls.client.protocols="TLSv1,TLSv1.1,TLSv1.2" -cp /usr/local/FlashphonerWebCallServer/lib/* com.flashphoner.server.Server root 2205317709 0.0 0.10 112704 61152 976 732 pts/0 RS+ 1412:5142 0:00 grep --color=auto WebCallServer [root@localhost tmp]# |
...
Code Block | ||||
---|---|---|---|---|
| ||||
netstat -nlp | grep java [root@localhost tmp]# netstat -nlp | grep java tcp 0 0 0.0.0.0:1098554 0.0.0.0:* LISTEN 2085011114/java tcp 0 0 0.0.0.0:80801098 0.0.0.0:* LISTEN 20850 11114/java tcp 0 0 0.0.0.0:8081843 0.0.0.0:* LISTEN 20850 11114/java tcp 0 0 0.0.0.0:509991935 0.0.0.0:* LISTEN 20850 11114/java tcp 0 0 0.0.0.0:84438080 0.0.0.0:* LISTEN 20850 11114/java tcp 0 0 0.0.0.0:2001 0.0.0.0::9091* LISTEN 11114/java tcp 0 0 0.0.0.0:8081 0.0.0.0:* LISTEN 11114/java tcp 0 0 0.0.0.0:8082 0.0.0.0:* LISTEN 20806 11114/java tcp 0 0 0.0.0.0:8888 0.0.0.0::1099* LISTEN 11114/java tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 11114/java tcp 0 0 0.0.0.0:8444 0.0.0.0:* LISTEN 20806 11114/java tcp 0 0 0.0.0.0:8445 0.0.0.0::2000* LISTEN 11114/java tcp 0 0 0.0.0.0:9091 :::*0.0.0.0:* LISTEN 20806 11114/java udp 0 0 0.0.0.0:1935 0.0.0.0:* 20850 11114/java |
If you used a standard number of ports, you should see ports 8080 (Websockets) and 1935 (RTMP) as well as other port you configured for the WCS5 WCS server in the netstat listened ports output.
3. Make sure the WCS5 WCS server writes the main server log of the Core.
Code Block | ||||
---|---|---|---|---|
| ||||
tail -f /usr/local/FlashphonerWebCallServer/logs/server_logs/flashphoner.log |
...
Code Block | ||||
---|---|---|---|---|
| ||||
1518:5929:3751,378945 INFO Config - main LOAD_BALANCING_SERVERS: null 15:59:37,378 INFO Config SettingsLoader - main Override setting STREAMallow_MODEoutside_UDPcodecs: from true to false 1518:5929:3751,379974 INFO Config SettingsLoader - 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 should react on connection of web clients. If that does not happen during testing, make sure the server process is running and the web client is configured properly to connect this particular server. See the Troubleshooting section for additional information.
...
Code Block | ||||
---|---|---|---|---|
| ||||
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)Override setting codecs: from null to opus,alaw,ulaw,g729,speex16,g722,mpeg4-generic,telephone-event,h264,vp8,flv,mpv 18:29:51,975 INFO SettingsLoader - main Override setting media_port_from: from 31001 to 31001 18:29:51,978 INFO SettingsLoader - main Override setting keep_alive.enabled: from websocket,rtmp,rtmfp to websocket,rtmfp 18:29:51,978 INFO SettingsLoader - main Override setting webrtc_cc_min_bitrate: from 30000 to 3000000 18:29:51,979 INFO SettingsLoader - main Override setting codecs_exclude_sip: from null to mpeg4-generic,flv,mpv,opus,ulaw,h264,g722,g729 18:29:51,979 INFO SettingsLoader - main Override setting wss.port: from 8443 to 8443 18:29:51,980 INFO SettingsLoader - main Override setting codecs_exclude_sip_rtmp: from null to opus,g729,g722,mpeg4-generic,vp8,mpv 18:29:51,980 INFO SettingsLoader - main Override setting codecs_exclude_streaming: from null to telephone-event 18:29:51,980 INFO SettingsLoader - main Override setting webrtc_cc_max_bitrate: from 10000000 to 7000000 18:29:51,980 INFO SettingsLoader - main Override setting ip: from 0.0.0.0 to 192.168.1.5 18:29:51,980 INFO SettingsLoader - main Override setting client_log_level: from INFO to DEBUG 18:29:51,980 INFO SettingsLoader - main Override setting ip_local: from 0.0.0.0 to 192.168.1.5 18:29:51,980 INFO SettingsLoader - main Override setting media_port_to: from 32000 to 32000 18:29:51,981 INFO SettingsLoader - main Override setting ws.port: from 8080 to 8080 |
Logs should react on connection of web clients. If that does not happen during testing, make sure the server process is running and the web client is configured properly to connect this particular server. See the Troubleshooting section for additional information.
If the server process is running and logs have no error, this means the WCS server is ready to work and you can start testing it.
...
Code Block | ||||
---|---|---|---|---|
| ||||
MALLOC_ARENA_MAX=4 |
Technically, starting goes as follows: first, the WCS Manager process starts, then that process launches the child process, WCS Core.
Starting with stdout output
...
Code Block | ||||
---|---|---|---|---|
| ||||
cd /usr/local/FlashphonerWebCallServer/bin ./webcallserver start standalone |
In this case, logs of the root process, WCS Manager, are printed directly to the console, and the server will be stopped if you press Ctrl+C.
To configure output of logs of the child process, WCS Core, use the node.enable_stdout=true setting.
JVM parameters
Parameters are set in the setenv.sh file.
...
WCS_JAVA_OPTS - the list of options for WCS Core
WCS_MANAGER_OPTS - the list of options for WCS Manager
Even though, one process is a parent of the other one, these processes are completely independent, and options set for the parent do not influence the child process. For example, if both for the parent and the child processes the -Xmx512M option is set, each of the processes will be executed isolated and have 512 megabytes of heap memory.