Wowza Core dumped after changes with log4j

Dan_Donald
Tue, 14 Dec 2021 14:23:36 +0000
Wowza Streaming Engine

Hi,
i have every 10-60 Minute Core dumps:

Dec 14 13:01:46 hostname systemd.sh[12345678]: /usr/local/WowzaStreamingEngine/bin/wms.sh: line 42: 786575 Aborted                 (core dumped) $_EXECJAVA $WMSTUNE_OPTS $JMXOPTIONS -Dcom.wowza.wms.runmode="service" -Dcom.wowza.wms.native.base="linux" -Dlog4j.configurationFile="$WMSCONFIG_HOME/conf/l>
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

and

Livestreaming will be aborted if not restart the WowzaStreamingEngine Service.

Wowza Version since yesterday is 4.8.16+1
Linux CentOS 8
Maybe we did not need to update the log4j patch?

Edit: I think we found out, that if customer connects his Encoder, then wowza engine crashes. But only today, before updates & applying fixes for log4j

2 posts - 1 participant