edl-johncogay
New Member
Last edited:
Reason for Flasphoner to crash or (code=exited, status=1/FAILURE)
- Thread starter edl-johncogay
- Start date
Good day.
First, if WCS does not start at all, please check if JDK is installed, check the file
Then, please check
If JDK is installed, and server still does not start, please provide us SSH access to the server using this form, we will check. If you cannot provide SSH access, provide us full content of the following folders
using this form
However, if server started after this error, collect a report as described here and send us using this form.
First, if WCS does not start at all, please check if JDK is installed, check the file
/usr/local/FlashphonerWebCallServer/logs/startup.log for Java startup errors.Then, please check
/usr/local/FlashphonerWebCallServer/logs/server_logs/flashphoner.log for errors.If JDK is installed, and server still does not start, please provide us SSH access to the server using this form, we will check. If you cannot provide SSH access, provide us full content of the following folders
Code:
/usr/local/FlashphonerWebCallServer/conf
/usr/local/FlashphonerWebCallServer/logsHowever, if server started after this error, collect a report as described here and send us using this form.
edl-johncogay
New Member
Actually the problem I mention is an intermittent error. It doesn't always occur.
Seems like you have not enough RAM on your server, all the crashes occur due to out of physical memory. Please read this common recommendations for server configuration depending on case.
Also, you should allocate more Java heap memory (2 Gb seems not enough for your case, garbage collector works every 2 seconds).
In this post, we also recommend you to update WCS to newer build.
Also, you should allocate more Java heap memory (2 Gb seems not enough for your case, garbage collector works every 2 seconds).
In this post, we also recommend you to update WCS to newer build.