I’m having the same issue here…
using master of openHABian config tool and tried with option 40-41 | openHAB testing and 40-42 | Upgrade to openHAB 3
There is another process running as user openhab, @Erling screenshot shows it as 413.
Identify this process, stop it and upgrade again.
@Benjy What does the usermod do here? Is it really needed for updates ?
If your logs are full of warnings like these
Field 'firmwareStatus' could not be eliminated: Can not set final org.openhab.core.thing.firmware.dto.FirmwareStatusDTO field org.openhab.core.io.rest.core.thing.EnrichedThingDTO.firmwareStatus to null value
when you go to the settings in the UI, that’s my fault and a fix is on the way: https://github.com/openhab/openhab-core/pull/1932
If you’re so annoyed and can’t wait to get rid of these messages, do a
bundle:update org.openhab.core.io.rest.core https://github.com/ghys/openhab-core/releases/download/rc1-rest-fix/org.openhab.core.io.rest.core-3.0.0-SNAPSHOT.jar
(disclaimer: in theory you shouldn’t update untested bundles like this 
)
8 Likes
After migration from MR5 -> RC1 my rules triggered on Item-State-Changes did not fire. Manual execution of the rules worked fine.
After an additional reboot, the problem went away without doing other changes.
Thanks, in my case it’s PID 553:
openhab 553 0.8 1.2 144004 49088 ? Ssl 21:33 0:11 node /usr/bin/frontail --ui-highlight --ui-highlight-preset /usr/lib/node_modules/frontail/preset/openhab.json -t openhab -l 2000 -n 200 /var/log/openhab/openhab.log /var/log/openhab/events.log
when I kill this process it starts again with another PID and then I get the same message but with the new PID.
Upgrade errors out with the same message.
Don‘t kill the process, do a clean
sudo service frontail stop
or whatever command it takes on your system.
I normaly stop frontail before upgrading, as I also delete the logs.
2 Likes
ah perfect, thanks!
After stopping the frontail service the upgrade passed fine.
Weird as it’s the first time I needed to do this.
Hi All!
Tried to upgrade from M5 to RC1 in docker by replacing with new image. It got stuck in endless loop as it says “You are already on Openhab 3.0.0.M5” and restarts up upgrade process. If I put M5 image back it boots properly.
When the upgrade detects that the home directory is still /var/lib/openhab2 it changes it to the correct path. I hadn’t realised that openHABian still uses the openhab user for frontail (it shouldn’t do (cc @mstormi)). I’ll release a workaround.
1 Like
It’s probably the Portainer issue described in the README:
1 Like
@Wolfy
Yes, when using portainer you have to delete the ‘OPENHAB_VERSION’-Environmentvariable of your OpenHAB-Instance before doing the upgrade.
1 Like
Right it shouldn’t and I’d think it doesn’t on fresh installs in quite a long time. If you have installed openHABian/frontail before this got fixed though you’ll still have the old user. Re-installing frontail via menu might help there.
3 Likes
The ‘RC1-2’ might be the version with the fix, that @ysc mentioned above, already applied (but I’m not 100% sure)
In that case your commands would be:
wget https://openhab.jfrog.io/openhab/list/openhab-linuxpkg/pool/main/3.0.0~RC1/openhab_3.0.0~RC1-2_all.deb
sudo apt install ./openhab_3.0.0~RC1-2_all.deb
If you do a fresh install anyway, I would try it out and having a look in the logs after install - if anything looks good, you’re probably good to go. 
The ‘-2’ at the end is just for the .deb packaging, it fixes the following install error.
The content after the install is identical and is now given to anyone who uses the milestone/testing repository. Unfortunately that does mean the same issues are present.
1 Like
Thanks for the clarification!
I got the same problem again as I had when upgrading to M5 (from M3): For some reason the Ephemeris bundle didn’t start. So there was loads of errors relating to that in the log. Simply restarting the bundle makes everything work as intented. Anyone else seen this?
On my upgrade the log4j2.xml was replaced automatically (upgraded using apt on a Debian server), so no smarthome.event there to replace. However, I seem to have the same problem anyway. Nothing in events.log and when doing a log:tail in Karaf I see no status changes. Anyone has a workaround?
Just noticed another huge problem. OH doesn’t read my .rules files anymore. The rules in the GUI works fine, but the rules I still have in files are nowhere to be found. Anyone else?
Beginning to feel I shouldn’t have upgraded to this RC 
edit: When editing the rules files my openhab.log says it’s loading them. But it doesn’t…
There seems to be something wrong in your installation, as rule files are working here without any issue.