- Platform information:
- Hardware: Raspberry Pi 2
- OS: Raspbian Debian Stretch 9
- Java Runtime Environment: OpenJDK 1.8.0-152
- openHAB version: 2.3.0-1
- Issue of the topic: Easy first time setup breaks multiple times, not fixable by beginners
I decided to begin with a fresh install because of to much problems with my Z-Wave infrastructure. It should be easy with OpenHABian.
The /boot/first-boot.sh Script failed for the first time at
2018-07-27_10:39:37_UTC [openHABian] Installing additional needed packages… FAILED
2018-07-27_10:39:40_UTC [openHABian] Initial setup exiting with an error!
When restarted (the script or the whole Raspberry Pi) then it would stop everytime at
2018-07-27_10:37:14_UTC [openHABian] Cloning myself… FAILED
because “/opt/openhabian” already exists and git gives back an error code.
Workaround 1: remove or move /opt/openhabian out of the way for every other try of reinstalling.
Workaround 2: insert an if not exists “/opt/openhabian” directory condition into first-boot.sh before cloning it.
Then it got to installing Node.js. That failed.
Installing the NodeSource Node.js 8.x LTS Carbon repo…
Populating apt-get cache…
- apt-get update
Hit:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Ign:2 http://archive.raspberrypi.org/debian stretch InRelease
Err:3 http://archive.raspberrypi.org/debian stretch Release
503 Service Unavailable [IP: 2a00:1098:0:80:1000:13:0:7 80]
Ign:4 http://repos.azulsystems.com/debian stable InRelease
Hit:5 http://repos.azulsystems.com/debian stable Release
Ign:6 https://dl.bintray.com/openhab/apt-repo2 stable InRelease
Hit:7 https://dl.bintray.com/openhab/apt-repo2 stable Release
Reading package lists… Done
E: The repository ‘http://archive.raspberrypi.org/debian stretch Release’ does no longer have a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Error executing command, exiting
I don’t know if it is the best idea to install Node.js without asking at first time install, because Node.js infrastructure is volatile to say the least. I guess it’s as a dependency of the now log file viewer.
So as a Linux Pro I keep on nursing the script for hours until it comes to a successful end, because otherwise it will start over and over with every reboot.
I hope reporting these two hicups is useful to others.
Thanks for the script and the effort nethertheless.