Updated to the latest version and now when I start the streaming engine service, it crashes with no helpful logged error. Thoughts?
Hi @Dave_Nichols , what version did you upgrade from?
It may be related to your Java version or to custom modules that are not compatible. There are some breaking changes when upgrading from 4.8 or earlier to 4.9; see Wowza Streaming Engine 4.9.0 Release Notes and there are some known issues here: Known issues with Wowza Streaming Engine
Try to enable debug logging in the log4j2-config.xml and start Wowza manually instead of via the service (run /bin/start.sh or start.bat from the console)
Upgrading from: Wowza Streaming Engine 4 Subscription Edition 4.8.27+5 build20240402153452
I did update the JRE folder with version 21.
Attempting your other suggestions here momentairly.
How do I enable debug logging? Starting manually did seem to possibly help:
startup
Error starting: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at com.wowza.wms.bootstrap.Bootstrap.startServer(Bootstrap.java:656)
at com.wowza.wms.bootstrap.Bootstrap.main(Bootstrap.java:73)
Caused by: java.lang.NoSuchMethodError: ‘java.lang.String org.apache.logging.log4j.util.Strings.toRootLowerCase(java.lang.String)’
at org.apache.logging.log4j.core.config.plugins.util.PluginManager.collectPlugins(PluginManager.java:132)
at org.apache.logging.log4j.core.lookup.Interpolator.(Interpolator.java:81)
at org.apache.logging.log4j.core.lookup.Interpolator.(Interpolator.java:109)
at org.apache.logging.log4j.core.config.AbstractConfiguration.(AbstractConfiguration.java:136)
at org.apache.logging.log4j.core.config.NullConfiguration.(NullConfiguration.java:32)
at org.apache.logging.log4j.core.LoggerContext.(LoggerContext.java:76)
at org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.createContext(ClassLoaderContextSelector.java:263)
at org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.locateContext(ClassLoaderContextSelector.java:222)
at org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.getContext(ClassLoaderContextSelector.java:144)
at org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.getContext(ClassLoaderContextSelector.java:123)
at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:242)
at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:46)
at org.apache.logging.log4j.LogManager.getContext(LogManager.java:176)
at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:666)
at com.wowza.wms.logging.WMSLogger.create(Unknown Source)
at com.wowza.wms.logging.WMSLoggerFactory.getLoggerObj(Unknown Source)
at com.wowza.wms.logging.WMSLoggerFactory.getLogger(Unknown Source)
at com.wowza.wms.logging.WMSLoggerFactory.initializeLogging(Unknown Source)
at com.wowza.wms.logging.WMSLoggerFactory.initializeLogging(Unknown Source)
at com.wowza.wms.server.Server.b(Unknown Source)
at com.wowza.wms.server.Server.start(Unknown Source)
… 4 more
Hi Dave,
By any chance do you have a custom module? Did you recompile it with Java17?
The above error could be a red herring:
Caused by: java.lang.NoSuchMethodError: ‘java.lang.String org.apache.logging.log4j.util.Strings.toRootLowerCase(java.lang.String)’
This method is part of log4j API and that dependency is included in the Engine. (log4j-api-2.17.2.jar in 4.8.27 and log4j-api-2.23.1.jar in Engine 4.9.1)
Just to rule out this possibility, can you check which “log4j-api” jar is present in “Wowza Streaming Engine 4.9.1+2\lib” folder?
Please let us know.
Thanks!
We don’t have custom modules. Seems Wowza is having issues with version 4.9.1+2 with multiple clients and is investigating the issue internally.
Got it. Thank you!
I think there may have been some confusion. So far we have around 2K+ install/updates for this version (4.9.1+2) and there are only 2 incidents reported. So doesn’t seem like a widespread issue.
Can you please provide the value for this WMSJAVA_HOME on the server having this issue?
You can refer to this help page to retrieve this value:
Thanks!
Thanks @Dave_Nichols for sharing that info. The value is correct.
I am assuming the stacktrace/error you posted 3 days ago is all you see on console when started engine using startup.bat, right? (If not, please try to start engine using startup.bat and share full console log).
Also was this your progression to 4.9.1?
4.7.8 —> 4.8.27+5----->4.9.1+2
Please confirm as that might help to reproduce the issue (it’s not reproducing if started with 4.8.27+5 as base version and upgraded to 4.9.1+2).
Thanks!
Our upgrade path has been a bit more than that based on the update folder.
4.7.8 → 4.8.15+3 → 4.8.18+1 → 4.8.19.4 → 4.8.27+5 → 4.9.1+2
Thanks Dave!
I received the zip file for all installed folders via support. Found a couple of issues. Since there is a support ticket, will continue to provide updates via the ticket.
Thanks