[OH 2.4.0 M6] Testing Results

Tags: #<Tag:0x00007f3880d2e528> #<Tag:0x00007f3880d2e370> #<Tag:0x00007f3880d2e208>

oh… you are on DSM6 and using a custom script… How to update OH2 on Synology?

you need to dig into the dirs to see what is going on. Maybe some snapshot stuff were left over.

Custom … not really :wink:
I’m using the following package: https://github.com/openhab/openhab-syno-spk/releases

that package is 2.3.0.5
there is no M6 spk (yet)
this: script looks like custom made to me :slight_smile:

anyway… you need to double check your dirs for various “left-overs” from previous snapshot upgrade attempts.

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 :frowning:)

I would try to clean up as much as possible the userdata subfolders and re-deploy 2.4.0M6

backup your stuff before you go wild ! :slight_smile:

@Dim
Any suggestions where to find the link to those ‘old’ configs? in which file to look at?

@ptweety, do these types of definition still work with M6?

Color WZWL_COLOR "Wand" { channel="hue:0210:0017884f6873:1:color,hue:0210:0017884f6873:37:color" }
Switch F2WL_TOGGLE "Flur 2.OG Ein/Aus" {channel="hue:0100:0017884f6873:6:brightness", expire="10m,command=OFF"}	

In Linux (/var/lib/openhab2 = userdata) , you may find some old reference in this file: /var/lib/openhab2/config/org/apache/karaf/features.config

for example, an older 2.4.0.M5 installation which was upgraded to M6 had left behind this entry:

featuresRepositories="mvn:org.openhab.distro/distro/2.4.0.M5/xml/features,\ mvn:org.openhab.distro/openhab-addons/2.4.0.M5/xml/features,\ mvn:org.apache.karaf.features/framework/4.2.1/xml/features,\ mvn:org.apache.karaf.features/standard/4.2.1/xml/features"

I would do the following (use caution!)

  1. Backup everything wrt OH2.x on my DSM
  2. delete everything (but not the directory itself) within userdata except jsondb and persistence and zwave (if used)
  3. delete everything (but not the directory itself) within runtime dir
  4. keep conf
  5. unzip the 2.4.0.M6 contents (only need userdata and runtime)

I don’t know exactly which are the full paths on DSM of ${OH_FOLDER}/addons & ${OH_FOLDER}/userdata. It depends where is your public folder located.

Matthias,

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:

  1. Did you upgrade from another openHAB version and if so, which one?
  2. If you upgraded can you clear your cache and restart to see if this message persists.
  3. 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.

1 Like

added JVM info on the OP

fast implementation! Love it :slight_smile: (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 ? :slight_smile:

1 Like

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.

what is your java -version ?

Is this error related to a specific binding? (for example: Hue)

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)

if this is your Item config:

Switch   HueMotion1           "HueMotion1"               {http="<[http://192.168.1.118/api/***/sensors/11:750:JS(getHueMotion.js)]"}

… you are killing your system with 750 milliseconds refresh time on the http call

increase it :slight_smile:

But with 2.3 stable it runs. And i tested it with 2500ms. Nothing changes. Could it be a problem that Java is zulu linux64?

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 :slight_smile:

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?

4 possible explanations:

  1. The problem just didn’t appear yet on OH2.3. Your ulimit was not reached for the error to appear.
  2. There are bugs in the http binding that appeared in 2.4 (highly doubt it since the binding has not been modified for over 1 year now)
  3. There are bugs in the 2.4 core that affect the way that open files are treated (possible, but unlikely)
  4. JVM 64bit Zulu 192 has problems with open files (possible, but unlikely)

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

1 Like

you can try to play with the operating system and java settings to increase the max allowed open files …but… this is not a solution… most likely they will be peaked at the max again and you will get the same error.

something is happening and the open files are not being closed correctly (maybe?)
It could be an inherit bug within the http binding code (doesn’t close the connections properly or fast enough)
I am thinking that the combination of the http call with the JS transformation is opening too many files and may not be closing them correctly to free up resources.

Anyway, your plan is the best: wait for the binding to provide native sensors support :slight_smile: