the third time I see this (1 time on regular Linux host, 2 times on DSM)
For the DSM users: you guys need to check the files in userdata to see why there are old configs there pointing to snapshot repos.
It seems that following 2.3.0.5 you deployed 2.4 snapshots using various methods since the spk packages were not being renewed.
Now, you are trying to use the same methods to deploy 2.4.0.M6 (understandable, since you want the latest and greatest and can’t wait for an “official” release) but I don’t know what could have gone wrong during the upgrade process… I don’t own a Synology NAS to test this stuff out )
I would try to clean up as much as possible the userdata subfolders and re-deploy 2.4.0M6
I tried to reproduce your problem But I can’t reproduce it. It might be specific to hue, but can’t test that. I suspect the context this messages are given doesn’t result in any problems. It looks like it wants to register the channel as metadata. Metadata should have an unique key, so the message seems correct. But I don’t think it should do something with channel. But I don’t know why it does. Therefor can you give some more feedback:
Did you upgrade from another openHAB version and if so, which one?
If you upgraded can you clear your cache and restart to see if this message persists.
If the message keeps showing when starting or I guess when reloading the items page, can you enable trace log level org.eclipse.smarthome.core and provide me the log.
Maybe this will give some more inside into why this happens.
fast implementation! Love it (off topic for M6 since I am running Snapshot also)
Setting up openhab2 (2.4.0~S1442-1) ...
root@homer:/var/log/openhab2# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
openhab2
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 73.5 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main openhab2 all 2.4.0~S1442-1 [73.5 MB]
Fetched 73.5 MB in 7s (9,788 kB/s)
Reading changelogs... Done
(Reading database ... 65897 files and directories currently installed.)
Preparing to unpack .../openhab2_2.4.0~S1442-1_all.deb ...
Unpacking openhab2 (2.4.0~S1442-1) over (2.4.0~S1441-1) ...
Processing triggers for systemd (215-17+deb8u8) ...
Setting up openhab2 (2.4.0~S1442-1) ...
Listing important changes for version 2.4.0:
Warning: Astro Binding: The 'kilometer' and 'miles' channels have been replaced by a new 'distance' channel
Warning: Jeelink Binding: The 'currentWatt' and 'maxWatt' channels have been replaced with 'currentPower' and 'maxPower' channels
Warning: WeatherUnderground Binding: A bridge has been added on top of the current things, you need to add a bridge containing your api-key.
Warning: ZWave Binding: Major changes have been merged to support features such as security. All things must be deleted and re-added. Refer to https://community.openhab.org/t/zwave-binding-updates/51080 for further information.
Warning: Synop Binding is now using UoM. 'wind-speed-ms' and 'wind-speed-knots' channels have been replaced by a single 'wind-speed' channel.
root@homer:/var/log/openhab2# apt-cache madison openhab2
openhab2 | 2.4.0~S1442-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.4.0~S1441-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.4.0~S1440-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.4.0~20181122162220-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.4.0~20181122141057-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.4.0~20181122121219-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.4.0~20181122105226-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.4.0~20181122034436-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.4.0~20181121231425-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.4.0~20181121003414-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.4.0~20181119183855-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.4.0~20181118113913-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.4.0~20181117214013-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.4.0~20181117181319-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.4.0~20181117002418-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.4.0~20181115123158-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.3.0-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.3.0~RC2-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.3.0~RC1-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.2.0-1 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
openhab2 | 2.1.0-2 | https://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Packages
root@homer:/var/log/openhab2#
Ps: @Benjy why keep the old stuff from 2.1, 2.2 and 2.3 RC in the unstable repo ?
Hi to all.
I hope i can ask this here.
After changing from openhab 2.3 stable to 2.4 M5, I got this error and a crash:
org.openhab.io.net.http.HttpUtil ] - Fatal transport error: java.net.SocketException: Too many open files 2018-11-04 02:08:31.717 [ERROR] [ab.binding.http.internal.HttpBinding] - No response received from:.
I am happy that i could downgrade again and 2.3 runs great. But i am very interested in some new options.
Now the question is, was there a change in the http binding or error, which is now fixed with M6?
Thanks for help and greetings,
Markus.
Hi Dim.
Yes, the first error comes from a hue bridge. This one has motion sensors.
Java version is Runtime Enviroment (zulu 8.33.0.1-linux64) (build 1.8.0_192-b01)
No, I don’t think that JVM is the problem… you have the latest Zulu
you could try the 32bit one to see if things improve
in general, this is Java +O/S issue (too many open files)
you will find several discussions around this on google
You are calling every 0,75 seconds an HTTP Call + a JS transformation sitting on a file… that’s overkill
that’s like putting Motorhead to optimize your openHAB installation
Okay. I understand. But i need this for the motion sensors. If i take a time of 5000ms, I am at the end of the room and the lights are still off. And why does it run under OH 2.3. without problems?
Okay. Thank you very much for your help. I think, I will wait until Christoph implement the sensors in the binding and i don’t need the http request.
Or i will delete this motion items and make a update again. Than it should run better i hope.
Greetings, Markus