# Updated to 4.9.1+2 and now it won't start up

**URL:** <https://community.wowza.com/t/updated-to-4-9-1-2-and-now-it-wont-start-up/102529>\
**Category:** Wowza Streaming Engine\
**Created:** [January 15, 2025, 3:23pm UTC](https://community.wowza.com/t/updated-to-4-9-1-2-and-now-it-wont-start-up/102529 "2025-01-15T15:23:28Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dave\_Nichols](https://avatars.discourse-cdn.com/v4/letter/d/898d66/32.png) [@Dave\_Nichols](https://community.wowza.com/u/Dave_Nichols)\
**Post date:** [January 15, 2025, 3:23pm UTC](https://community.wowza.com/t/updated-to-4-9-1-2-and-now-it-wont-start-up/102529/1 "2025-01-15T15:23:28Z")

</div>

Updated to the latest version and now when I start the streaming engine service, it crashes with no helpful logged error. Thoughts?

---

<div class="post-metadata">

**Author:** ![Karel\_Boek](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/karel_boek/32/454_2.png) [@Karel\_Boek](https://community.wowza.com/u/Karel_Boek)\
**Post date:** [January 19, 2025, 4:17pm UTC](https://community.wowza.com/t/updated-to-4-9-1-2-and-now-it-wont-start-up/102529/2 "2025-01-19T16:17:04Z")

</div>

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](https://www.wowza.com/docs/wowza-streaming-engine-4-9-0-release-notes#breaking-changes-in-wowza-streaming-engine-4-9-05) and there are some known issues here: [Known issues with Wowza Streaming Engine](https://www.wowza.com/docs/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)

---

<div class="post-metadata">

**Author:** ![Dave\_Nichols](https://avatars.discourse-cdn.com/v4/letter/d/898d66/32.png) [@Dave\_Nichols](https://community.wowza.com/u/Dave_Nichols)\
**Post date:** [January 21, 2025, 5:56pm UTC](https://community.wowza.com/t/updated-to-4-9-1-2-and-now-it-wont-start-up/102529/3 "2025-01-21T17:56:32Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Dave\_Nichols](https://avatars.discourse-cdn.com/v4/letter/d/898d66/32.png) [@Dave\_Nichols](https://community.wowza.com/u/Dave_Nichols)\
**Post date:** [January 21, 2025, 6:02pm UTC](https://community.wowza.com/t/updated-to-4-9-1-2-and-now-it-wont-start-up/102529/4 "2025-01-21T18:02:02Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Manoj.Gundawar](https://avatars.discourse-cdn.com/v4/letter/m/ba9def/32.png) [@Manoj.Gundawar](https://community.wowza.com/u/Manoj.Gundawar)\
**Post date:** [January 23, 2025, 9:11pm UTC](https://community.wowza.com/t/updated-to-4-9-1-2-and-now-it-wont-start-up/102529/5 "2025-01-23T21:11:15Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![Dave\_Nichols](https://avatars.discourse-cdn.com/v4/letter/d/898d66/32.png) [@Dave\_Nichols](https://community.wowza.com/u/Dave_Nichols)\
**Post date:** [January 23, 2025, 9:27pm UTC](https://community.wowza.com/t/updated-to-4-9-1-2-and-now-it-wont-start-up/102529/6 "2025-01-23T21:27:57Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Manoj.Gundawar](https://avatars.discourse-cdn.com/v4/letter/m/ba9def/32.png) [@Manoj.Gundawar](https://community.wowza.com/u/Manoj.Gundawar)\
**Post date:** [January 24, 2025, 3:21pm UTC](https://community.wowza.com/t/updated-to-4-9-1-2-and-now-it-wont-start-up/102529/7 "2025-01-24T15:21:56Z")

</div>

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:

> **[Install and troubleshoot Java on Wowza Streaming Engin](https://www.wowza.com/docs/manually-install-and-troubleshoot-java-on-wowza-streaming-engine#troubleshooting6)**
>
> Install a different version of Java and determine and control which version of Java is being used by Wowza Streaming Engine.

Thanks!

---

<div class="post-metadata">

**Author:** ![Dave\_Nichols](https://avatars.discourse-cdn.com/v4/letter/d/898d66/32.png) [@Dave\_Nichols](https://community.wowza.com/u/Dave_Nichols)\
**Post date:** [January 24, 2025, 4:21pm UTC](https://community.wowza.com/t/updated-to-4-9-1-2-and-now-it-wont-start-up/102529/8 "2025-01-24T16:21:25Z")

</div>

New version (after upgrade)

 ![newversion](https://us1.discourse-cdn.com/flex002/uploads/wowza1/original/2X/7/79a07a11c91749aac0d6f3b31d60fe285f009b04.jpeg)

Old version (before upgrade)

 ![oldversion](https://us1.discourse-cdn.com/flex002/uploads/wowza1/original/2X/f/f3b7b4f06d18704c31dbf98caaf482f052d3d69a.jpeg)

---

<div class="post-metadata">

**Author:** ![Manoj.Gundawar](https://avatars.discourse-cdn.com/v4/letter/m/ba9def/32.png) [@Manoj.Gundawar](https://community.wowza.com/u/Manoj.Gundawar)\
**Post date:** [January 24, 2025, 6:09pm UTC](https://community.wowza.com/t/updated-to-4-9-1-2-and-now-it-wont-start-up/102529/9 "2025-01-24T18:09:27Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![Dave\_Nichols](https://avatars.discourse-cdn.com/v4/letter/d/898d66/32.png) [@Dave\_Nichols](https://community.wowza.com/u/Dave_Nichols)\
**Post date:** [January 28, 2025, 3:31am UTC](https://community.wowza.com/t/updated-to-4-9-1-2-and-now-it-wont-start-up/102529/10 "2025-01-28T03:31:59Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Manoj.Gundawar](https://avatars.discourse-cdn.com/v4/letter/m/ba9def/32.png) [@Manoj.Gundawar](https://community.wowza.com/u/Manoj.Gundawar)\
**Post date:** [January 30, 2025, 1:55pm UTC](https://community.wowza.com/t/updated-to-4-9-1-2-and-now-it-wont-start-up/102529/11 "2025-01-30T13:55:20Z")

</div>

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
