These are chat archives for nightscout/intend-to-bolus
I managed to run the “oref0-setup” script from here - http://openaps.readthedocs.io/en/dev/docs/Build%20Your%20Rig/OpenAPS-install.html - the install seemed to work fine until the rig reboots and asks you to enter a new password...during the reboot, I get the following error message during the reboot and am wondering if this is normal - [FAILED] Failed to start Hostname Service.
See 'systemctl status systemd-hostnamed.service' for details. After the reboot, I log in as root and change my password and it spits out the following...also wondering if this is normal...after I type "l" to watch the logs as it suggests in the docs, I get another error which I'll show below in my next message. - Last login: Sat Jul 22 21:39:23 ADT 2017 on ttyMFD2
Linux weenus 3.10.98-jubilinux-edison #13 SMP PREEMPT Fri Jun 23 02:24:12 EDT 2017 i686
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
-bash: plain: command not found
-bash: Usage:: command not found
Forgive my ignorance here...learning as I go with this. I just typed in "systemctl status systemd-hostnamed.service" to the command line to get more info about the failure during the reboot and here is what it says...any advice would be greatly appreciated - root@weenus:~# systemctl status systemd-hostnamed.service
● systemd-hostnamed.service - Hostname Service
Loaded: loaded (/lib/systemd/system/systemd-hostnamed.service; static)
Active: failed (Result: exit-code) since Sat 2017-07-22 21:48:27 ADT; 19min ago
Process: 410 ExecStart=/lib/systemd/systemd-hostnamed (code=exited, status=226/NAMESPACE)
Main PID: 410 (code=exited, status=226/NAMESPACE)
Jul 22 21:48:27 weenus systemd: Failed at step NAMESPACE spawning /lib...ry
Jul 22 21:48:27 weenus systemd: systemd-hostnamed.service: main process ...CE
Jul 22 21:48:27 weenus systemd: Failed to start Hostname Service.
Jul 22 21:48:27 weenus systemd: Unit systemd-hostnamed.service entered f...e.
Hint: Some lines were ellipsized, use -l to show in full.
fatal: destination path 'oref0' already existsisn't really a problem for us: it'll just
git pullinstead when
git cloneerrors out like that.
npm WARNmessages, is there any way to pre-emptively solve them … (I’m not worrying, just wondering)
wget --no-check-certificate https://raw.githubusercontent.com/openaps/docs/dev/scripts/openaps-install.sh
apt-get -f install
apt-get -f install)
apt-get update- get the list of all possible pending updates to your Edison
apt-get upgrade- install those updates that apply to your Edison - so don’t install updates to software not already installed ...
lat the command prompt
@mpets the two files you need to check are
vi /etc/hosts and
You'll probably see the old hostname in one or both of those files. Change it to the current host name and reboot. Should fix the problem quickly