If you experience troubles with missing, or wrong pax logging version being used have a look on workaround I mentioned there: Log4j vulnerability - #49 by splatch. Mount files which are missing from host system or other container if you prefer, but mount ones which are free of vulnerabilities.
You can also use the /openhab/runtime/bin/client script. That one does work.
/srv/openhab$ docker exec -it openhab_openhab_1 /openhab/runtime/bin/client
Logging in as openhab
Failed to get the session.
Somehow does not work for me. But I don’t know where to look for the errors, /userdata/logs/openhab.log is empty, and docker logs just look normal.
I don’t know how much patience you have… but when openHAB isn’t fully started, it is normal to see this “Failed to get the session.” and empty logs.
Well, I waited for 2h now… And this is a NUC with 16GB RAM, SSD and i5-8259U where it normally starts in a second or so.
dd6b99cffb24 openhab/openhab:milestone "/entrypoint gosu op…" 2 hours ago Up About an hour (unhealthy)
The file org.apache.karaf.features.xml was functionally empty:
’
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- you can eventually blacklist features repositories, features, or even bundle here, to exclude from resolution -->
<!-- <blacklistRepositories/> -->
’
I replaced it with
’
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- you can eventually blacklist features repositories, features, or even bundle here, to exclude from resolution -->
<!-- <blacklistRepositories/> -->
<bundleReplacements>
<bundle originalUri="mvn:org.ops4j.pax.logging/pax-logging-api/[0,2.0.13)" replacement="mvn:org.ops4j.pax.logging/pax-logging-api/2.0.13" mode="maven" />
<bundle originalUri="mvn:org.ops4j.pax.logging/pax-logging-log4j2/[0,2.0.13)" replacement="mvn:org.ops4j.pax.logging/pax-logging-log4j2/2.0.13" mode="maven" />
<bundle originalUri="mvn:org.ops4j.pax.logging/pax-logging-logback/[0,2.0.13)" replacement="mvn:org.ops4j.pax.logging/pax-logging-logback/2.0.13" mode="maven" />
</bundleReplacements>
’
openhabian works on 3.2.0 again!
I found the culprit:
restore
replaces the file
3 Likes
I can see the 2.0.13 version being in there
/srv/openhab$ docker exec -it openhab_openhab_1 ls /openhab/runtime/system/org/ops4j/pax/logging/pax-logging-log4j2
2.0.13
which seem to be the latest ones (Maven Central Repository Search).
interesting, when starting with:
/srv/openhab$ docker-compose run --entrypoint /openhab/start_debug.sh openhab
Launching the openHAB runtime...
Listening for transport dt_socket at address: 5005
I can attach the debugger, so it is running, but no services are running (eg, nothing on 8080) and no logs are written.
Does it work for anyone with docker?
Was not able to fix it for now, reverted back to M4
I can confirm, that at least the RC1 version works fine with Docker.
Just as a data point, I upgraded docker from 3.2.M3 to M5 to RC1 to 3.2.0 release, over time as they were released, without any significant issues. Needed the multiple restarts to get everything synced, but that has been standard practice sin 2.5.x. Everything working as expected at this point.
1 Like
Thanks for your efforts to get 3.2 out!
After the upgrade from a snapshot version to 3.2 final I get the following:
2021-12-20 20:48:13.157 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-binding-heliosventilation, openhab-binding-modbus, openhab-binding-tr064, openhab-binding-fronius, openhab-binding-dwdunwetter, openhab-persistence-jdbc-mysql, openhab-binding-xmppclient, openhab-binding-avmfritz, openhab-transformation-javascript, openhab-ui-habpanel, openhab-transformation-jsonpath, openhab-binding-shelly, openhab-binding-mqtt, openhab-transformation-map, openhab-ui-basic, openhab-binding-astro, openhab-binding-dwdpollenflug, openhab-binding-resol, openhab-binding-snmp': Error:
Error downloading mvn:org.igniterealtime.smack/smack-experimental/4.3.3
And most of the bindings I use are not working… Anyone else seeing this?
1 Like
Mh, blindly removing the line
<bundle dependency="true">mvn:org.igniterealtime.smack/smack-extensions/4.3.3</bundle>
from the openhab-binding-xmppclient section in file /var/lib/openhab/tmp/kar/openhab-addons-3.2.0/org/openhab/distro/openhab-addons/3.2.0/openhab-addons-3.2.0-features.xml magicly improves the situation…
1 Like
Yes this is openhab-addons#11560. Now that these changes are also in the release it might be a good idea to upload the artifacts to the online repo @Kai.
1 Like
Interesting ist, that a lot of unrelated bindings were affected and that might be worth a look for the future to make the loading of bindings more independent…
Thanks! I guess I will test with a more linear upgrade path.
Thank you to all those that made version 3.2 possible.
Just to double check. Do the upgrade issues affect docker installation only?
Are there any issues reported with non-docker installations?
Anyone else having a problem with their Mail binding after the upgrade? I’m getting:
14:49:46.473 [WARN ] [hab.binding.mail.internal.SMTPHandler] - Sending the email to the following server failed : redacted.redacted.net:25
14:49:46.476 [WARN ] [hab.binding.mail.internal.SMTPHandler] - javax.mail.MessagingException: IOException while sending message;
nested exception is:
javax.activation.UnsupportedDataTypeException: text/plain; charset=UTF-8
Thing configuration:
Thing mail:smtp:redacted [ hostname="redacted.redacted.net", sender="redacted@redacted.com" ]
JavaScript code:
actions.get("mail", "mail:smtp:redacted").sendMail("redacted@redacted.com", "Test", "Test")
Actual addresses / IDs redacted. This was working in 3.1 on a manual install at /opt/openhab. It broke after running the upgrade script. I tried a fresh install to see if that made a difference but same problem on a fresh install too.
Yes and I opened a new thread at Mail binding errors sending mail UnsupportedDataTypeException: text/plaijn; charset=UTF=8.
Are you by chance running with JSScripting or using a different rules language?
It’s probably prudent to have most of the discussion over on the thread I started though.
Circling back, I’ve opened an issue for this: [Mail] sendMail and sendHtmlFail errors for UI rules · Issue #11838 · openhab/openhab-addons · GitHub It seems to impact all UI based rules regardless of language.