building from the ground up a new installation, trying for the first time openhabian in a debian vm.
after selecting all options from Manual/Fresh Setup (all - for 63 I selected Oracle as Zulu seems broken; for 64 I selected OpenHAB unstable), the script stop here:
$ apt -y install apt-transport-https bc sysstat avahi-daemon python python-pip
Reading package lists… Done
Building dependency tree
Reading state information… Done
apt-transport-https is already the newest version (1.4.8).
avahi-daemon is already the newest version (0.6.32-2).
bc is already the newest version (1.06.95-9+b3).
python is already the newest version (2.7.13-2).
python-pip is already the newest version (9.0.1-2).
sysstat is already the newest version (11.4.3-2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
OK
/opt/openhabian/functions/menu.sh: line 172: openhab2_unstable_setup: command not found
2018-03-16_19:05:11_CET [openHABian] Preparing openHAB folder mounts under /srv/…
$ cat /etc/fstab
/etc/fstab: static file system information.
Use ‘blkid’ to print the universally unique identifier for a
device; this may be used with UUID= as a more robust way to name devices
that works even if disks are added and removed. See fstab(5).
$ mount --all --verbose
/ : ignored
none : ignored
/media/cdrom0 : ignored
mount: special device /usr/share/openhab2 does not exist
mount: special device /etc/openhab2 does not exist
mount: special device /var/lib/openhab2 does not exist
mount: special device /var/log/openhab2 does not exist
mount: special device /usr/share/openhab2/addons does not exist
FAILED
2018-03-16_19:05:11_CET [openHABian] Applying file permissions recommendations… FAILED (please execute after openHAB was installed)
it seems some dir are missing. Do we need to create those manually?
selecting the stable release instead of unstable, it works like a charm and those dirs are created as expected.
Now trying with unstable … but I expect now it will work correctly. Mabye a mkdir missing in the script?
[edit] switch from stable to unstable works like a charm
@TomDidi just an heads-up regarding the script (the issue above): if we start from scratch trying to install the latest unstable snapshot, it seems there is a missing mkdir
I’m not sure what’s going on here if I’m honest. Just tried to install the latest snapshot on my own virtual machine and it works fine. Where does /srv/ mount to? I’d like to recreate the same scenario.
start from scratch a new debian VM (hosted on my Mac OsX server)
sudo openhabian-config
Manual / Fresh Setup (60)
4a. if you select 61-62-63b (63a Zulu is not supported any more), 64b (unstable) and 65-66-67-68-69 , we have the issue
4b if you select 61-62-63b, 64a (stable) and 65-66-67-68-69, everything’s working fine
issue in case of 4a: as you can see above, the script stop after not finding the openhab2_unstable_setup script (?). The important piece seems:
mount: special device /usr/share/openhab2 does not exist
mount: special device /etc/openhab2 does not exist
mount: special device /var/lib/openhab2 does not exist
mount: special device /var/log/openhab2 does not exist
mount: special device /usr/share/openhab2/addons does not exist
the dirs above are not present in the system, so I expect there is a missing mkdir piece.
With 4b those dirs are in the system, and the script doesn’t fail.
Absolutely clear , I seemed to have accidently installed the stable version (not snapshot) when I said I had it working earlier… Silly me!
I’ve found the issue in the openhabian scripts and will send a PR to fix, if you want to get it working straight away then edit line 170 in /opt/openhabian/functions/menu.sh from:
if [[ $choosenComponents == *"openHAB unstable"* ]]; then openhab2_unstable_setup; fi
to
if [[ $choosenComponents == *"openHAB unstable"* ]]; then openhab2_setup unstable; fi
, I seemed to have accidently installed the stable version (not snapshot) when I said I had it working earlier… Silly me!
… Silly me!