Troubleshooting

Discussion in 'Web Call Server 5' started by Max, Jan 30, 2017.

  1. Max

    Max Administrator Staff Member

    Can't open page https://ip:8888
    Make sure WCS server is up, running and listening port 8888
    Code:
    ps aux | grep java
    Should display two processes
    Example:
    Code:
    [root@wcs4-us conf]# ps aux | grep WebCall
    root      7772 11.2 38.2 2697780 390372 pts/0  Sl   22:08   1:39 java -Dloader.path=/usr/local/FlashphonerWebCallServer-5.0.2047/lib/tbs-commons.jar,/usr/local/FlashphonerWebCallServer-5.0.2047/lib/wcs_manager-1.0.jar -Dcom.flashphoner.fms.AppHome=/usr/local/FlashphonerWebCallServer -Xmx512M -Xloggc:/usr/local/FlashphonerWebCallServer/logs/gc-manager.log -Dnode.enable_stdout=false -Djava.net.preferIPv4Stack=true -DstartWithDemoUser=true -jar /usr/local/FlashphonerWebCallServer-5.0.2047/lib/wcs_manager-1.0.jar -Xmx1024M -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=localhost -XX:ErrorFile=/usr/local/FlashphonerWebCallServer/logs/error%p.log -Xloggc:/usr/local/FlashphonerWebCallServer/logs/gc-core.log -Dcom.flashphoner.fms.AppHome=/usr/local/FlashphonerWebCallServer -Djava.library.path=/usr/local/FlashphonerWebCallServer/lib/so:/usr/local/FlashphonerWebCallServer/lib -DWCS_NON_ROOT=false -cp /usr/local/FlashphonerWebCallServer/lib/* com.flashphoner.server.Server
    root      7820  3.2 15.9 3199516 162804 pts/0  Sl   22:09   0:26 java -Xmx1024M -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=localhost -XX:ErrorFile=/usr/local/FlashphonerWebCallServer/logs/error%p.log -Xloggc:/usr/local/FlashphonerWebCallServer/logs/gc-core.log -Dcom.flashphoner.fms.AppHome=/usr/local/FlashphonerWebCallServer -Djava.library.path=/usr/local/FlashphonerWebCallServer/lib/so:/usr/local/FlashphonerWebCallServer/lib -DWCS_NON_ROOT=false -cp /usr/local/FlashphonerWebCallServer/lib/* com.flashphoner.server.Server
    As you can see, we have two server processes: 7772 (manager process, 512M max heap by default) and 7820 (core process, 1024M max heap by default).
    If you have one process, this means:
    a) Server is still starting (the startup may take about 1 minute).
    b) Server core process is down (was not started or crashed)
    If your server is being started, you will see activity in this log.
    Code:
    tail -f /usr/local/FlashphonerWebCallServer/logs/flashphoner_manager.log
    If your server has successfully started, you will see started message in the same log:
    Code:
    main Started Manager in 66.708 seconds (JVM running for 71.382)
    If you see activity in the log but the log is suspended, perhaps you have to install haveged
    Code:
    netstat -nlp | grep java
    If server is up an running, it binds necessary ports.
    Example:
    [root@wcs4-us conf]# netstat -nlp | grep java
    Code:
    tcp        0      0 0.0.0.0:8081                0.0.0.0:*                   LISTEN      7820/java
    tcp        0      0 0.0.0.0:8082                0.0.0.0:*                   LISTEN      7820/java
    tcp        0      0 0.0.0.0:50999               0.0.0.0:*                   LISTEN      7820/java
    tcp        0      0 0.0.0.0:8888                0.0.0.0:*                   LISTEN      7772/java
    tcp        0      0 0.0.0.0:8443                0.0.0.0:*                   LISTEN      7820/java
    tcp        0      0 0.0.0.0:8444                0.0.0.0:*                   LISTEN      7820/java
    tcp        0      0 0.0.0.0:52094               0.0.0.0:*                   LISTEN      7820/java
    tcp        0      0 0.0.0.0:9091                0.0.0.0:*                   LISTEN      7772/java
    tcp        0      0 0.0.0.0:554                 0.0.0.0:*                   LISTEN      7820/java
    tcp        0      0 0.0.0.0:1098                0.0.0.0:*                   LISTEN      7820/java
    tcp        0      0 0.0.0.0:843                 0.0.0.0:*                   LISTEN      7820/java
    tcp        0      0 0.0.0.0:1099                0.0.0.0:*                   LISTEN      7772/java
    tcp        0      0 0.0.0.0:1935                0.0.0.0:*                   LISTEN      7820/java
    tcp        0      0 0.0.0.0:8080                0.0.0.0:*                   LISTEN      7820/java
    tcp        0      0 0.0.0.0:2000                0.0.0.0:*                   LISTEN      7772/java
    udp        0      0 0.0.0.0:1935                0.0.0.0:*                               7820/java
    Here port 8888 belongs to the manager process (pid 7772)
    port 8443 belongs to the core process (pid 7820)
    If you have these two ports listening, server is started properly.
    Code:
    telnet host 8888
    Make sure that TCP port 8888 is available and open for connection from your desktop

    That is all.
    If you have listening ports 8888 and 8443 and if your ports are open for TCP connections, you should be able to open page https://host:8888
    This page uses self-signed SSL certificates. Please use this manual to test with self-signed SSL certs.
    Last edited: Feb 6, 2017
  2. Max

    Max Administrator Staff Member

    Can't activate or deactivate my license
    Try to stop WCS server, make sure it is stopped completely and try to activate / deactivate your license from the command line over SSH.
    1. Stop server.
    Code:
    service webcallserver stop
    2. Make sure it is stopped.
    Code:
    ps aux | grep WebCall
    3. Kill server process if it is not stopped
    Example:
    Code:
    kill -p 89123
    here 89123 is an example of process ID
    4. Deactivation
    Code:
    cd /usr/local/FlashphonerWebCallServer/bin
    ./deactivation.sh
    5. Activation
    Code:
    cd /usr/local/FlashphonerWebCallServer/bin
    ./activation.sh
    Possible troubles
    1. Activation or deactivation has failed for a network reason.
    Solution: Make sure you have connection to Flashphoner licensing server: https://my.flashphoner.com:443 and this connection is not affected by a system firewall.
    2. Activation has failed due a permission error.
    Solution: Make sure you start activation process as sudo or root user. It should have sufficient permissions to write licensing hash-files.
    3. Activation has failed because license is already activated.
    Solution: Most likely your license was activated on another server. Deactivate your license on those server to unlock the license for use on current server.

    If you have any unresolved licensing issues, please contact support@flashphoner.com
  3. Max

    Max Administrator Staff Member

    WCS server is starting too long time
    Normal startup time is around 30-70 seconds depending on server CPU resources.
    Startup point is command:
    Code:
    service webcallserver start
    Next you see activity in the log:
    Code:
    tail -f /usr/local/FlashphonerWebCallServer/logs/flashphoner_manager.log
    And finally you see such message:
    Code:
    18:27:13,736 INFO Manager - main Started Manager in 63.543 seconds (JVM running for 65.847)
    This means server startup took 65 seconds.

    Possible troubles
    Startup time is more than 2 minutes on a good CPU (at least two cores).
    Solution:
    Please read this article related haveged
    Long story short, you have to install haveged and run
    Example:
    Install EPEL
    Code:
    sudo yum install epel-release
    Install haveged
    Code:
    yum install haveged
    Add haveged to auto-start
    Code:
    chkconfig haveged on
    Check entropy
    Code:
    cat /proc/sys/kernel/random/entropy_avail
    Restart WCS
    Code:
    service webcallserver restart
    Alex Vorona likes this.

Share This Page