Windows is the only OS I am aware of that uses backslashes \ in path names. Most all other operating systems use slashes /. That is why I assumed Windows.
You are running Raspian 8 (jessie) which, I believe is now unsupported. I do not know if that relates to your log issues though,
I use 9 (Stretch) oldstable and 10 (Buster) is now current stable,
You have eyes like an eagle. I was just to lazy to enter the path, so I made it by copy and paste out of my editor (from the windows-side via samba-share).
But the news you gave me,are shocking me . I always made my updates and upgrades via openhabian-config and never found a hint to upgrade OS and how to do it. I only know that Buster is the OS for RPi4, but not for RPi3
I’ve not read the full discussion but I can comment on this.
openhabian-config option 2 will perform a full upgrade of all the software on the system but it does not move to the next distro. So if you are on Raspbian stretch and execute that option (which runs sudo apt-get update; sudo apt-get dist-upgrade) it will upgrade to the latest versions of all software for Raspbian stretch.
Buster is not strictly for Raspberry Pi 4s. The RPi 4 will only run buster. But all previous RPi versions can also run buster. I’ve upgraded my RPi 1s, RPi 0Ws, and RPi 3s to buster.
To upgrade to a new Linux distro is a lot riskier and error prone so I suggest a fresh install and rebuild of the SD card instead of an in place upgrade. If you want to take the risk you can try an inplace upgrade. In my experience it worked three times out of five.
More or less. Sometimes, after an initial Startup (systemctl stop openhab2, shutdown) it can happen that not all bindings are loaded. But after a restart (systemctl restart openhab2) everything seems to work fine. Only the Info-Message appears.
Therefore I made a workaround with
openhab> log:set warn org.openhab.ui.paper
So I do not get the message anymore. But it’s not real answer of my question (maybe I have to live with it )
It’s the other way… RPi4 needs buster (at least). It’s very unlikely that by upgrading to the next release a computer systems stops working.
Of course you don’t need to upgrade, but as it’s jessie… there won’t be any security fixes anymore, and that’s the whole point of updating the system.
Another point is, your java version is pretty old 1.8.0_152
I’m not sure about zulu, but I’m on 1.8.221 if I remember correctly. (I’m still using oracle…)
And openHAB tends to be a bit delicate about the exact java version.
Anyway, at least I would upgrade to stretch (no risk at all), maybe wait a month or so, and then upgrade to buster.
Maybe make a clone of your SD card first (always a good idea).
I recently upgraded my home mail server from stretch to buster and damn, there is a unmet dependency, atm I can’t figure out how to get rid of it, surely I did no backup before upgrading… stupid I…
Hi guys, thx you are great. I’m just making a clone, and as you said " no risk, no fun" . Further question: How can I upgrade java/zulu ? Can you give me the commands ? And before upgrading to stretch or after ?
Thx in advance
The risk is significantly higher if you are doing the upgrade on a headless machine through ssh. In that case, a hickup in your network can kill the upgrade right in the middle of it’s operations. Depending on what it was doing when apt was cut off you may be fine or you may have a completely unusable machine and have to go back to the drawing board with a fresh install. I upgrade 5 RPis and two of them crashed mid upgrade and had to be rebuilt from scratch. That wasn’t really a big deal though as it was all scripted.