Logfile not updating anymore, after upgrade from old version

xsherlock · September 9, 2017, 3:44pm

I see quite strange behavior after the upgrade from a year old install #771 that was running fine but I need new zwave devices that are only in the 2.1.

After upgrade the system seems to run fine, BUT…

The log file is not updating any more.

tail -f /var/log/openhab2/openhab.log

does display old log up to the moment old service was stopped, and not restarted.
Did the log change location? I guess not.

If I run

sudo /bin/systemctl status openhab2.service -l

I can see a part of the new log, but where it is?

[17:38:19] pi@rpi-openhab2:~$ sudo /bin/systemctl status openhab2.service -l
● openhab2.service - openHAB 2 - empowering the smart home
   Loaded: loaded (/usr/lib/systemd/system/openhab2.service; enabled)
   Active: active (running) since Sat 2017-09-09 17:33:08 CEST; 5min ago
     Docs: http://docs.openhab.org
           https://community.openhab.org
  Process: 13620 ExecStop=/usr/share/openhab2/runtime/bin/karaf stop (code=exited, status=0/SUCCESS)
 Main PID: 13864 (java)
   CGroup: /system.slice/openhab2.service
           └─13864 /usr/bin/java -Dopenhab.home=/usr/share/openhab2 -Dopenhab.conf=/etc/openhab2 -Dopenhab.runtime=/usr/share/openhab2/runtime -Dopenhab.userdata=/var/lib/openhab2 -Dopenhab.logdir=/var/log/openhab2 -Dfelix.cm.dir=/var/lib/openhab2/config -Djetty.host=0.0.0.0 -Dorg.ops4j.pax.web.listening.addresses=0.0.0.0 -Dorg.osgi.service.http.port=8080 -Dorg.osgi.service.http.port.secure=8443 -Djava.awt.headless=true -Djava.endorsed.dirs=/usr/lib/jvm/java-8-oracle/jre/jre/lib/endorsed:/usr/lib/jvm/java-8-oracle/jre/lib/endorsed:/usr/share/openhab2/runtime/lib/endorsed -Djava.ext.dirs=/usr/lib/jvm/java-8-oracle/jre/jre/lib/ext:/usr/lib/jvm/java-8-oracle/jre/lib/ext:/usr/share/openhab2/runtime/lib/ext -Dkaraf.instances=/var/lib/openhab2/tmp/instances -Dkaraf.home=/usr/share/openhab2/runtime -Dkaraf.base=/var/lib/openhab2 -Dkaraf.data=/var/lib/openhab2 -Dkaraf.etc=/var/lib/openhab2/etc -Dkaraf.logs=/var/log/openhab2 -Dkaraf.restart.jvm.supported=true -Djava.io.tmpdir=/var/lib/openhab2/tmp -Djava.util.logging.config.file=/var/lib/openhab2/etc/java.util.logging.properties -Dkaraf.startLocalConsole=false -Dkaraf.startRemoteShell=true -classpath /usr/share/openhab2/runtime/lib/boot/org.apache.karaf.diagnostic.boot-4.1.2.jar:/usr/share/openhab2/runtime/lib/boot/org.apache.karaf.jaas.boot-4.1.2.jar:/usr/share/openhab2/runtime/lib/boot/org.apache.karaf.main-4.1.2.jar:/usr/share/openhab2/runtime/lib/boot/org.osgi.core-6.0.0.jar org.apache.karaf.main.Main

Sep 09 17:33:46 rpi-openhab2 karaf[13864]: 17:33:46.242 [Start Level: Equinox Container: c5dd0013-e7a2-4780-9693-515411362d4d] ERROR org.eclipse.smarthome.core.items.GenericItem - Tried to set invalid state 0.0 (StringType) on item Heating_Required of type SwitchItem, ignoring it
Sep 09 17:33:46 rpi-openhab2 karaf[13864]: 17:33:46.549 [Start Level: Equinox Container: c5dd0013-e7a2-4780-9693-515411362d4d] ERROR org.eclipse.smarthome.core.items.GenericItem - Tried to set invalid state 224.0 (StringType) on item B_Power_Battery_Current_Discharge of type NumberItem, ignoring it
Sep 09 17:33:46 rpi-openhab2 karaf[13864]: 17:33:46.608 [Start Level: Equinox Container: c5dd0013-e7a2-4780-9693-515411362d4d] ERROR org.eclipse.smarthome.core.items.GenericItem - Tried to set invalid state 19.0 (StringType) on item GF_Temp_Setpoint_Living of type NumberItem, ignoring it
Sep 09 17:33:46 rpi-openhab2 karaf[13864]: 17:33:46.663 [Start Level: Equinox Container: c5dd0013-e7a2-4780-9693-515411362d4d] ERROR org.eclipse.smarthome.core.items.GenericItem - Tried to set invalid state 19.0 (StringType) on item B_Temp_Setpoint_Office of type NumberItem, ignoring it
Sep 09 17:33:46 rpi-openhab2 karaf[13864]: 17:33:46.747 [Start Level: Equinox Container: c5dd0013-e7a2-4780-9693-515411362d4d] ERROR org.eclipse.smarthome.core.items.GenericItem - Tried to set invalid state 23.0 (StringType) on item B_Temperature_Water_Setpoint of type NumberItem, ignoring it
Sep 09 17:33:46 rpi-openhab2 karaf[13864]: 17:33:46.795 [Start Level: Equinox Container: c5dd0013-e7a2-4780-9693-515411362d4d] ERROR org.eclipse.smarthome.core.items.GenericItem - Tried to set invalid state 1.0 (StringType) on item B_Provent_bypass_active of type NumberItem, ignoring it
Sep 09 17:33:46 rpi-openhab2 karaf[13864]: 17:33:46.851 [Start Level: Equinox Container: c5dd0013-e7a2-4780-9693-515411362d4d] ERROR org.eclipse.smarthome.core.items.GenericItem - Tried to set invalid state 20.0 (StringType) on item B_Temp_Setpoint_Bedroom of type NumberItem, ignoring it
Sep 09 17:33:46 rpi-openhab2 karaf[13864]: 17:33:46.902 [Start Level: Equinox Container: c5dd0013-e7a2-4780-9693-515411362d4d] ERROR org.eclipse.smarthome.core.items.GenericItem - Tried to set invalid state 20.0 (StringType) on item B_Provent_temp_gwc of type NumberItem, ignoring it
Sep 09 17:33:46 rpi-openhab2 karaf[13864]: 17:33:46.958 [Start Level: Equinox Container: c5dd0013-e7a2-4780-9693-515411362d4d] ERROR org.eclipse.smarthome.core.items.GenericItem - Tried to set invalid state 20.0 (StringType) on item GF_Temp_Setpoint_Bedroom of type NumberItem, ignoring it
Sep 09 17:33:47 rpi-openhab2 karaf[13864]: 17:33:47.137 [Start Level: Equinox Container: c5dd0013-e7a2-4780-9693-515411362d4d] ERROR org.eclipse.smarthome.core.items.GenericItem - Tried to set invalid state 5.0 (StringType) on item B_Provent_gear_selected of type NumberItem, ignoring it

Benjy · September 9, 2017, 4:16pm

When you upgraded, dpkg would have told you that there’s a new version of /var/lib/openhab2/etc/org.ops4j.pax.logging.cfg and asked if you wanted to replace it, the default option is unfortunately “no”.

You can get the logging working with the new defaults with the following commands.

sudo mv /var/lib/openhab2/etc/org.ops4j.pax.logging.cfg /var/lib/openhab2/etc/org.ops4j.pax.logging.cfg.old
sudo mv /var/lib/openhab2/etc/org.ops4j.pax.logging.cfg.dpkg-dist /var/lib/openhab2/etc/org.ops4j.pax.logging.cfg

sudo systemctl restart openhab2.service

For more information, see this thread.

Hope that helps.

xsherlock · September 9, 2017, 11:00pm

Many thanks , got that up an running in no time, surprisingly after conforming to the new nazi rule engine checker the update over 250 builds went smooth.