I just updated to
openhab2 | 2.2.0~20170829225437-1 | http://openhab.jfrog.io/openhab/openhab-linuxpkg/ unstable/main amd64 Pack
ages
And now openhab won’t start up fully. Just hangs as far as I can tell. Anyone else having issues?
any log output that you can share?
In general: Yes, there are some issues with the latest snapshot but that’s expected cause the maintainers are testing new stuff out (new Karaf, new ESH core, etc) and they need our help to stabilize them (that’s the concept of the unstable branch)
For example, there are some threads and issues open already for Snapshots greater than 1025 (search).
Ps: I just issued apt-get upgrade on my system for the same snapshot build (#1027)… I will check my logs also.
update:
I see the following at the moment in my logs after upgrading from 1026 to 1027:
Several timeouts towards https://openhab.jfrog.io/openhab/online-repo-snapshot/2.2/
30-Aug-2017 08:11:21.736 [WARN ] [org.ops4j.pax.url.mvn.internal.AetherBasedResolver] - Error resolving artifact org.openhab.ui:org.openhab.ui.habmin:jar:2.2.0-SNAPSHOT: [Could not transfer artifact org.openhab.ui:org.openhab.ui.habmin:jar:2.2.0-SNAPSHOT from/to openhab (https://openhab.jfrog.io/openhab/online-repo-snapshot/2.2/): Connect to openhab.jfrog.io:443 [openhab.jfrog.io/104.196.54.40] failed: connect timed out] java.io.IOException: Error resolving artifact org.openhab.ui:org.openhab.ui.habmin:jar:2.2.0-SNAPSHOT: [Could not transfer artifact org.openhab.ui:org.openhab.ui.habmin:jar:2.2.0-SNAPSHOT from/to openhab (https://openhab.jfrog.io/openhab/online-repo-snapshot/2.2/): Connect to openhab.jfrog.io:443 [openhab.jfrog.io/104.196.54.40] failed: connect timed out]
30-Aug-2017 08:16:10.257 [WARN ] [org.ops4j.pax.url.mvn.internal.AetherBasedResolver] - Error resolving artifact org.openhab.binding:org.openhab.binding.samsungtv:jar:2.2.0-SNAPSHOT: [Could not transfer artifact org.openhab.binding:org.openhab.binding.samsungtv:jar:2.2.0-SNAPSHOT from/to openhab (https://openhab.jfrog.io/openhab/online-repo-snapshot/2.2/): Connect to openhab.jfrog.io:443 [openhab.jfrog.io/104.196.54.40] failed: connect timed out] java.io.IOException: Error resolving artifact org.openhab.binding:org.openhab.binding.samsungtv:jar:2.2.0-SNAPSHOT: [Could not transfer artifact org.openhab.binding:org.openhab.binding.samsungtv:jar:2.2.0-SNAPSHOT from/to openhab (https://openhab.jfrog.io/openhab/online-repo-snapshot/2.2/): Connect to openhab.jfrog.io:443 [openhab.jfrog.io/104.196.54.40] failed: connect timed out]
I can browse to the repo (https://openhab.jfrog.io/openhab/online-repo-snapshot/2.2/) but my OH2 log shows that my system cannot connect to the repo to download to the jars.
I cleared my cache and tmp so OH2 needs to grab again the jars (that’s normal).
Investigating more now…
Massive exception errors, I’m on iPad for the night so a little hard to grab the log, I’ll have to extract it tomorrow morning. Tried to downgrade but jfrog seems to be down or ignoring my attempt. Sounds like you see similar.
1 Like
yeah… looks like the online repo is having some hiccups at the moment…
Network stats look ok but I get timeouts while trying to connect to it.
root@homer:/var/log/openhab2# nslookup openhab.jfrog.io
Server: 172.16.13.100
Address: 172.16.13.100#53
Non-authoritative answer:
openhab.jfrog.io canonical name = jfrog-gcprod-lb.jfrog.io.
Name: jfrog-gcprod-lb.jfrog.io
Address: 104.196.54.40
root@homer:/var/log/openhab2# traceroute 104.196.54.40
traceroute to 104.196.54.40 (104.196.54.40), 30 hops max, 60 byte packets
1 ZTE-Router.itcs.lan (172.16.13.254) 0.567 ms 0.767 ms 0.961 ms
2 10.0.0.1 (10.0.0.1) 8.024 ms 7.942 ms 8.082 ms
3 * * *
4 * * *
5 213-154-130-234.rdsnet.ro (213.154.130.234) 22.745 ms 24.430 ms 24.228 ms
6 64.233.175.230 (64.233.175.230) 25.959 ms 25.032 ms 209.85.246.180 (209.85.246.180) 22.809 ms
7 216.239.41.57 (216.239.41.57) 38.704 ms 108.170.236.247 (108.170.236.247) 33.341 ms 216.239.41.57 (216.239.41.57) 32.731 ms
8 209.85.253.185 (209.85.253.185) 45.930 ms 48.687 ms 209.85.252.149 (209.85.252.149) 56.966 ms
9 216.239.62.161 (216.239.62.161) 121.197 ms 209.85.143.216 (209.85.143.216) 122.759 ms 216.239.59.83 (216.239.59.83) 121.047 ms
10 209.85.255.146 (209.85.255.146) 131.104 ms 132.259 ms 216.239.40.20 (216.239.40.20) 182.456 ms
11 74.125.37.181 (74.125.37.181) 135.229 ms 72.14.239.51 (72.14.239.51) 132.051 ms 209.85.240.214 (209.85.240.214) 132.907 ms
12 * * *
13 * 40.54.196.104.bc.googleusercontent.com (104.196.54.40) 132.850 ms 132.364 ms
root@homer:/var/log/openhab2# ping 104.196.54.40
PING 104.196.54.40 (104.196.54.40) 56(84) bytes of data.
64 bytes from 104.196.54.40: icmp_seq=1 ttl=44 time=132 ms
64 bytes from 104.196.54.40: icmp_seq=2 ttl=44 time=133 ms
64 bytes from 104.196.54.40: icmp_seq=3 ttl=44 time=133 ms
64 bytes from 104.196.54.40: icmp_seq=4 ttl=44 time=131 ms
64 bytes from 104.196.54.40: icmp_seq=5 ttl=44 time=133 ms
64 bytes from 104.196.54.40: icmp_seq=6 ttl=44 time=133 ms
64 bytes from 104.196.54.40: icmp_seq=7 ttl=44 time=133 ms
64 bytes from 104.196.54.40: icmp_seq=8 ttl=44 time=133 ms
^C
--- 104.196.54.40 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7002ms
rtt min/avg/max/mdev = 131.735/133.001/133.745/0.658 ms
not much we can do at the moment… Maybe we have to wait for the repo to “stabilize”…
I restarted OH2 several times and I always get timeouts towards the repo.
As long as OH2 is not able to grab the jars, it will fail to load…
30-Aug-2017 08:41:52.740 [WARN ] [org.ops4j.pax.url.mvn.internal.AetherBasedResolver] - Error resolving artifact org.eclipse.smarthome.binding:org.eclipse.smarthome.binding.astro:jar:0.9.0-SNAPSHOT: [Could not transfer artifact org.eclipse.smarthome.binding:org.eclipse.smarthome.binding.astro:jar:0.9.0-SNAPSHOT from/to openhab (https://openhab.jfrog.io/openhab/online-repo-snapshot/2.2/): Connect to openhab.jfrog.io:443 [openhab.jfrog.io/104.196.54.40] failed: connect timed out]
I didn’t try to revert back to an older snapshot build because I assume that I will experience the same timeouts…
So, bottom line: people should wait a bit and not upgrade their snapshots till this networking situation is resolved.
apt-get upgrade will clear out tmp & cache and trigger a re-download of the addons from the snapshot repo (which will fail), leaving users with a broken OH2.2.0 system.
(good) Update!
At 5:48 AM GMT openHAB 2.2.0 Snapshot build #1027 was able to download all jars and system came back online
So far so good.
Try restarting your OH2 service and it should be able now to download the addon jars from the snapshot repo.
Mine is working fine for now and my tmp and cache folders are properly populated
Alas I’m still getting timeouts. I’ll have to try again in the morning. Thanks for looking at this issue, I suppose i need to switch to stable releases so the wife doesn’t beat me when everything stops working…
1 Like
FYI this issue continues this morning with jfrog. Reverted to 2.1.0-1 release off bintray. Perhaps I’ll stick with stable for awhile.
Now that jfrog is supposed to be working I tried to upgrade again and things still don’t start. No exceptions, it just hangs trying to initialize zwave. 
Upon reading more error reports it appears that’s because of issue 519 - zwave added to the addons folder causes issues. Reverted to 1023 and it works fine.