Starting openHAB fails sometimes

[GoogleCodeExporter]

See http://knx-user-forum.de/openhab/26967-webinterface-nicht-erreichbar.html

When started with the shell script the start up process stops somewhere in the 
middle (checked by watching the log messages). In these cases the webinterface 
can not be reached, but the openHAB process is still active. In these cases a 
second attempt will fail with a very high likelihood as well.

Some tests sugests, that this issue might by related to the db4o persistence 
service, as openHAB started correctly after deleting the db4o data store. But 
this is only an assumption and not proven.

I tried this an OS X Mountain lion server with "Java(TM) SE Runtime Environment 
(build 1.7.0_17-b02)" and obenHAb stabele 1.2.0 (Bindings 1.2.1). With former 
versions of openHAB (including the nightly build from 2013-01-16) this issue 
did not occure.

What might also be related: When stopping openhab (on the console or by 
unloading the OS X launch daemon) the process keeps active, but the logs say. 
It can only be stopped by sending the signal SIGKILL, other signals have no 
effect.

It was dicussed if this is related to some bindings, I am using the following: 
ecec, fritzbox, http, hue (installed but currently unused), knx, networkhealth, 
snmp (installed but currently unused), tcp, wol, db4o, logging (installed but 
currently unused), rrd4j

One user has reported this problem without using the knx binding, He uses the 
following ones: homematic, fritzbox, vdr, wol, networkhealth, http, ntp. exec 
and dropbox are installed but not used.

Original issue reported on code.google.com by estan...@gmx.de on 25 May 2013 at 12:01

[GoogleCodeExporter]

The log message when stopping openHAB fails is missing. It should read ... the 
logs say "o.o.i.r.i.RESTApplication[:174]- Stopped REST API"

The "stopping fails" issue is documented in issue #315

Original comment by estan...@gmx.de on 25 May 2013 at 12:10

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I get this message sometimes on my Raspberry Pi:

22:22:04.935 INFO  o.o.c.internal.CoreActivator[:92 - openHAB runtime has been 
started (v1.3.0).
22:22:19.898 ERROR o.o.b.k.i.c.KNXConnection[:185 - Error connecting to KNX 
bus: acknowledge error, failed to connect to control endpoint 
/192.168.178.28:3671
22:22:41.310 INFO  o.o.m.c.i.f.FolderObserver[:163 - Loaded file 'rrd4j.persist'
22:22:41.442 INFO  o.o.m.c.i.f.FolderObserver[:163 - Loaded file 'db4o.persist'
22:26:23.204 WARN  OSGi[:97 - [SCR - WorkThread] Timeout occurred! Thread was 
blocked on processing [QueuedJob] WorkPerformer: 
org.eclipse.equinox.internal.ds.SCRManager@760f68; actionType 1
22:26:23.210 WARN  OSGi[:97 - [SCR - WorkThread] Timeout occurred! Thread was 
blocked on processing [QueuedJob] WorkPerformer: 
org.eclipse.equinox.internal.ds.SCRManager@760f68; actionType 1
22:26:23.802 WARN  OSGi[:97 - [SCR] Enabling components of bundle 
org.openhab.core.persistence did not complete in 240000 ms 
22:26:23.814 WARN  OSGi[:97 - [SCR] Enabling components of bundle 
org.openhab.core.persistence did not complete in 240000 ms

For me, there seems to be a problem with the db4p persist, because when i use 
this service, the chance for a proper start seems to be lower. 

Also see here:
http://knx-user-forum.de/openhab/26967-webinterface-nicht-erreichbar.html

Original comment by N.Schnit...@gmail.com on 27 May 2013 at 4:24

[GoogleCodeExporter]

I can investigate a very similar problem:
Restarting openhab fails and the only solution is to delete the etc/db4o 
folder. I'm running openhab on raspberry pi on the latest standard raspbian 
(with Oracle Java 7).

The difference is that i do not get any "Timeout" error messges. What i can 
find are "Item Group does not exist":

07:38:26.656 DEBUG o.o.c.p.i.PersistenceManager[:166]- Initializing db4o 
persistence service.
07:38:27.102 DEBUG o.o.c.p.i.PersistenceManager[:448]- Scheduled strategy 
db4o.everyHour with cron expression 0 0 * * * ?
07:38:27.128 DEBUG o.o.c.p.i.PersistenceManager[:448]- Scheduled strategy 
db4o.everyDay with cron expression 0 0 0 * * ?
07:38:27.519 DEBUG o.o.c.p.i.PersistenceManager[:166]- Initializing rrd4j 
persistence service.
07:38:27.548 DEBUG o.o.c.p.i.PersistenceManager[:348]- Item group 
'Weather_Chart' does not exist.
07:38:27.589 DEBUG o.o.c.p.i.PersistenceManager[:448]- Scheduled strategy 
rrd4j.everyMinute with cron expression 0 * * * *
 ?

The result is the same: the UI is not accessable und the only solution is to 
delete the db4o data store.

Original comment by sepp.mar...@gmail.com on 14 Oct 2013 at 8:49

[GoogleCodeExporter]

Original comment by kai.openhab on 5 Dec 2013 at 10:19

• Added labels: To-Github

[GoogleCodeExporter]

has been migrated to https://github.com/openhab/openhab/issues/637

Original comment by teichsta on 10 Dec 2013 at 10:18

• Changed state: Invalid
• Added labels: Migrated-to-Github