Jump to content

HA on EISY, "Failed to setup" error on reboot


Recommended Posts

Posted

When I reboot EISY HA does not see EISY. A "Failed to setup" error is thrown. Selecting reload fixes the problem, until the next reboot.

The fix for me was to start VA from cron.

/etc/rc.conf -- comment out vm_list="homeassistant"

vm_enable="YES"
vm_dir="zfs:HAIO"
# vm_list="homeassistant"

crontab. -- start the homeassistant vm 3 minutes after a reboot

@reboot sleep 180 && vm start homeassistant

 

I tried adding a delay vm delay in /etc/rc.conf. Did not work.

vm_delay="300"

hopes this helps someone else with the same problem

 

  • 1 month later...
Posted

@KSaccullo01I tried this fix but I'm unable to get it to work. Does it have to go somewhere special in the file?

# /etc/crontab - root's crontab for FreeBSD
#
# $FreeBSD$
#
SHELL=/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin
#
#minute hour    mday    month   wday    who     command
#
# Save some entropy so that /dev/random can re-seed on boot.
*/11    *       *       *       *       operator /usr/libexec/save-entropy
#
# Rotate log files every hour, if necessary.
0       *       *       *       *       root    newsyslog
#
# Perform daily/weekly/monthly maintenance.
1       3       *       *       *       root    periodic daily
15      4       *       *       6       root    periodic weekly
30      5       1       *       *       root    periodic monthly
#
# Adjust the time zone if the CMOS clock keeps local time, as opposed to
# UTC time.  See adjkerntz(8) for details.
1,31    0-5     *       *       *       root    adjkerntz -a
@reboot sleep 180 && vm start homeassistant

 

Posted

Did you hand edit crontab? it look like you are in the system crontab.

to edit correctly enter: sudo crontab -e

it will bring up the vi editor so you may want to familiarize yourself with vi first.

The file will be be stored in /var/cron/tabs

As a side note. I completely deleted the admin account and all traces of it. I created a new account that uses the root folder. Eliminated the need to enter sudo for my new account and activated the root account. When I created the original cron file I did so directly as root. It should not matter. Try sudo -s then crontab -e.

 

Posted

0

16 minutes ago, KSaccullo01 said:

Did you hand edit crontab? it look like you are in the system crontab.

 

Yes I did edit it directly I guess that's why it did not work. I have it setup that after HA loads it restarts the ISY integration so I don't have to worry about it anymore but thanks for the info.

Posted

Try:

sudo -s (enter password if prompted)

crontab -e

once saved new cron file should  be in /var/cron/tabs/

Guest
This topic is now closed to further replies.

  • Recently Browsing

    • No registered users viewing this page.
  • Forum Statistics

    • Total Topics
      37.1k
    • Total Posts
      371.5k
×
×
  • Create New...