Wowza Community

Wowza Streaming Engine 4.8.21+6 Updater extracts to folder "WowzaStreamingEngine-Update-4-3"

Looking to update and I notice that when I unzip the updater for 4.8.21+6 it extracts to a folder called “WowzaStreamingEngine-Update-4-3” which seems wrong - I am inclined to change this folder name to match the zip “WowzaStreamingEngine-Update-4-8-21” but not sure if this will cause problems. Also, maybe related, I notice the syntax changed slightly - all previous updates have had dots not dashes in the version #: “WowzaStreamingEngine-Update-4.8.20+1.zip” “WowzaStreamingEngine-Update-4.8.15+3.zip”

2 Likes

I will wait before updating !

An interesting question.
I am also confused by the naming of the folder.
Why is it necessary to unsettle users who are not so technically aware in this way?
An update should not actually be anything complicated.
Or have I missed some change in this regard?

This is a recently discovered issue when updating with OSX. If not already, please create a support ticket with Wowza:
https://www.wowza.com/portal/help

Actually, it’s not only OSX, the ZIP has a different folder name scheme than the previous patch files.
I updated some Linux machines by renaming the extracted folder and moving the contents to updates/WowzaStreamingEngine-Update-4.8.21/. The updater ran just fine…it’s strange nonetheless…

Got the exact same behavior also it refuses to accept my openjdk 11.0.2 even though it have been used for several updates the past year or so.

I have opened a support ticket and I will await their response, before manually renaming files etc, wonder what else they messed up in this version…

4-3 that is really a looooong time ago, imagine if it rolled back to that version

Holy smokes
Wowza support came back with an answer stating that they knew it and basicly suggests that the folder named 4-3 is moved up one level and manually renamed… to ~/updates/…

That is really a no no. I dont doubt it will work, but having to manually intervene, leaves to much room for typos, which could result in unpredicted/unwanted behavior later on (at least in terms of investigation)

Should be quite simple for them if it is only the naming that is faulty to release a new zip file, named similar to previous versions.
I think we’ll skip this version and await 4.8.22’ish