Flashphoner service stops

SLM

Member
Yesterday the Flashphoner service (5.3.291 on an Amazon instance) suddenly stopped without explicitly using webcallserver stop. In the console when I used restart it said the Flashphoner wasn't running.

Today this happened again. I collected the logs and will send you these via email. I've updated to the latest version (5.3.298) before restarting.

Can you tell me what causes this behaviour?
 

Max

Administrator
Staff member
Good day.
We checked the report.
If you're using a custom AWS image, please use Amazon Linux 2023 or Ubuntu 22.04 or 24.04 as base OS with OpenJDK 21. If you're using Flashphoner image from AWS marketplace, please update to latest one.
We also recommend to use OpenJDK, not Correto JDK.
In 5.3 branch, websocket messages logging between clients and server is added. If you're updating from 5.2, please add the following lines to log4j.properites file:
Code:
log4j.logger.WsInLogger=info, wsInAppender
log4j.additivity.WsInLogger=false
log4j.logger.WsOutLogger=info, wsOutAppender
log4j.additivity.WsOutLogger=false
log4j.appender.wsInAppender=org.apache.log4j.DailyRollingFileAppender
log4j.appender.wsInAppender.DatePattern='.'yyyy-MM-dd-HH
log4j.appender.wsInAppender.layout=org.apache.log4j.PatternLayout
log4j.appender.wsInAppender.layout.ConversionPattern=%d{HH:mm:ss,SSS} IN %m%n
log4j.appender.wsInAppender.File=${com.flashphoner.fms.AppHome}/logs/websocket.log
log4j.appender.wsOutAppender=org.apache.log4j.DailyRollingFileAppender
log4j.appender.wsOutAppender.DatePattern='.'yyyy-MM-dd-HH
log4j.appender.wsOutAppender.layout=org.apache.log4j.PatternLayout
log4j.appender.wsOutAppender.layout.ConversionPattern=%d{HH:mm:ss,SSS} OUT %m%n
log4j.appender.wsOutAppender.File=${com.flashphoner.fms.AppHome}/logs/websocket.log
It may also be useful to enable jemalloc memory allocator to prevent excessive system memory consumption:
Code:
sudo ./webcallserver use-jemalloc enable
 
Top