Notice to all openHABian users: Please apply a fix asap!

The discussed problem is related to the openHABian Linux setup many are using at home on their Raspberry Pi or other dedicated systems. It is not related to openHAB itself. If you are using openHAB on Windows or the Mac, or you’ve got openHAB set up on Linux by yourself, the “Urgent Fix” is irrelevant to you.

I have made the update on my rpi and when the system reboot i no longer can make any comands, for example “sudo openhabian-config” or no other commands. What to do?

Bad luck, this might be related to openHABian stuck on ssh connection

@Magnus the issue is resolved. Please follow the link to see how to solve it for you.

I tried to update but got a error message. Sorry I didn’t saved it. It stated something about my system is not located on a SD card (I have moved my system from SD card to a USB stick).
In the terminal I got:

2017-05-08_21:03:42_CEST [openHABian] Updating myself… fatal: The remote end hung up unexpectedly
FAILED - There was a problem fetching the latest changes for the openHABian configuration tool. Please check your internet connection and try again later…

Hi, i got the following lines after applying the update and then applying the fix…

2017-05-10_21:41:16_BST [openHABian] Checking for root privileges... OK
2017-05-10_21:41:16_BST [openHABian] Loading configuration file '/etc/openhabian.conf'... OK
2017-05-10_21:41:26_BST [openHABian] Downloading and setting up FireMotD...
$ git clone https://github.com/ThomDietrich/FireMotD.git /opt/FireMotD
Cloning into '/opt/FireMotD'...
remote: Counting objects: 604, done.
remote: Compressing objects: 100% (37/37), done.
remote: Total 604 (delta 21), reused 0 (delta 0), pack-reused 567
Receiving objects: 100% (604/604), 1.73 MiB | 1.21 MiB/s, done.
Resolving deltas: 100% (352/352), done.
Checking connectivity... done.

$ /bin/bash /opt/FireMotD/FireMotD -S
W: GPG error: https://dl.bintray.com jessie Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 379CE192D401AB61
W: GPG error: https://packagecloud.io jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 37BBEE3F7AD95B3F
OK
If you wish so. Bye Bye! :)

Is the GPG error of concern?

Hi @ThomDietrich,
for me the update works fine. FireMotD also works now…hope no UpdateServer will be harmed this night :grin:
Schönes Wochenende
ChristianH

1 Like

Hello @Roscoe_Gray, yes that’s of concern but unrelated to the update.
Your apt repositories are not properly set up. Please import the respective public keys.

  1. http://docs.openhab.org/installation/linux.html#package-repository-installation
  2. Depends on where it came from. Please check your /etc/apt/sources.list.d/
1 Like

Maybe a stupid beginner question. On my RasPi console there is no openhabian-config command.

You would have it if you would have installed openhabian. Maybe you did install openhab on your on your pi which hab already an os on it. In this case you don’t have that.

To be honest, i’m not realy understood the answer.

I have installed openhab2 on raspbian operating system. There is no command openhabian-config available.

What to do?

Since you have not installed openhabian (which is a package of raspbian plus openhab) your system does not have this command and this thread does not apply to you.

1 Like

Friend I installed all now openHABian no longer sees my sitemap file despite this is existing … error … not found sitemap

This is probably unrelated. Please open a new thread and describe the problem in more detail. Thanks

same problem. the app popsup a “not acceptable” message.

everything worked fine for more than 1 month before appling this update, sound like its related

UPDATE:
after one more reboot and 10 minutes myhopenhab.org resyinced and everything works now.

Hi Tom

Today I made an update of the openhabian config tool because I wanted to upgrade to 2.1 on my PI2, and got this:

│ Attention: It was brought to our attention that the old openHABian │
│ ua-netinst based image has a problem with a lately updated Linux package. │
│ If you upgrade(d) the package ‘raspberrypi-bootloader-nokernel’ your │
│ Raspberry Pi will run into a Kernel Panic upon reboot! │
│ │
│ Do not Upgrade, do not Reboot! │
│ │
│ A preliminary solution is to not upgrade the system (via the Upgrade menu │
│ entry or ‘apt upgrade’) or to modify a configuration file. In the long run │
│ we would recommend to switch over to the new openHABian Raspbian based │
│ system image! This error message will keep reapearing even after you fixed │
│ the issue at hand. │
│ Please find all details regarding the issue and the resolution of it at: │
https://github.com/openhab/openhabian/issues/147

I read through the thread at github, but I have absolutely no idea what you guys talking about and I´m afraid, that I break my working system.

I wanted to make a backup of my openhab folders via WinSPC (cope them on my windows desktop) but it says permission denied so I don´t have a backup solution. Mayby just copy the whole SD card? But then it would have the same behaviour if I just clone it if I am right.

Thx
Daniel

No need to do that. Just check out the last answer by me: https://github.com/openhab/openhabian/issues/147#issuecomment-312449656


No need for winscp, you can access everything via samba and the “openhab-share” named share. There is also a README telling you a few things about permissions…

In general the solution is pretty simple and always similar:
Your user doesn’t have access to certain files. Makes sense because of security reasons. However at times you need access to them. Well that is why the Linux world gave us elevated rights and the sudo command. Just make them available for you.
My recommendation for a backup of various files would be to copy all of them (using sudo if needed) to one “Backup” folder, then make this folder owned by your user, then copy it.

Also check out http://docs.openhab.org/installation/linux.html#backup-and-restore

Hello Tom

THX for your reply.

So to make the update to 2.1 I first have to execute the command:
sudo apt-mark hold raspberrypi-bootloader-nokernel

After that, I can make the 2.1 upgrade and all should be fine?

I´m not very good in understandig what an why I do things in the console, that was the reason for WinSPC.

I read the backup and restore manual, but if i understnd i right, the backup is on the same SD Card as the whole system?

Yesterday I tried to clone my card with win32 but the new card doesen´t work. Maybe this was a size issue. Will check that today.

THX
Daniel