Hi @htttito, I had the same issue, indeed caused by the zulu11-jdk update to 11.0.20. First thing I noticed was that standard addons are not visible, only community / marketplace. My system was still somewhat running, that’s why the forum is not yet flooded by users with the same problem I think. After a “clear-cache” you end up with a system that does not even start.
Problem is caused by the “Improved ZIP64 Extra Field Validation” in the latest java11 (see Consolidated JDK 11 Release Notes) and required valid headers for ZIP64 files.
I downgraded to the previous version of zulu11-jdk as a solution, however an alternative route reported is to add the following to your /etc/default/openhab (in case of debian based systems such as openhabian):
EXTRA_JAVA_OPTS="-Djdk.util.zip.disableZip64ExtraFieldValidation=true"
See also Openhab not working with zulu11.0.20 - #8 by RoRo
One-liner to downgrade (from: Openhab not working with zulu11.0.20 - #7 by RoRo)
apt install `dpkg -l zulu\* | grep ^i | awk '{print $2}' | sed 's/$/=11.0.19-1/'`