Error: Lets wait for new config files
Posted: Sun Apr 09, 2017 12:52 pm
I rebuilt one of my rPi's today after having a corrupt /etc/rsyslog.conf file which may have been like that for some time.
I downloaded the SSD image following your instructions and changed the region, expanded to fill 16GB, set the password as it was before, etc. and all that, however I get the following message over and over again:
I have a static IP entry for this rPi so my DHCP server gave it the same IP as before.
I tried the "initial BASIC setup of rPi servers" option, but this returned "Communication with the plugin timed out." In fact it gives me this message on all of my rPi's, including the working ones.
I tried the various options of sending Config files, rebooting, etc. and even did the "sudo python installLibs.py --force". Incidentally this should read: sudo python ~/pibeacon/installLibs.py --force as you no longer install piBeacon into the home directory.
I am reasonably confident I can get this going either by deleting the original rPi device and creating a new one or by by filling in the values in the ~/pibeacon/parameters file, but was a little taken aback when finding myself in a position of having to reach for a bash editor where none of the billion other options you so splendidly provide do not work.
piBeacon is my favourite plugin
Edit: Yep, editing the ~/pibeacon/parameters file worked as expected, yet the "initial BASIC setup of rPi servers" option still fails against this now working rPi with "Communication with the plugin timed out."
I downloaded the SSD image following your instructions and changed the region, expanded to fill 16GB, set the password as it was before, etc. and all that, however I get the following message over and over again:
- Code: Select all
Master not configured yet, lets wait for new config files
I have a static IP entry for this rPi so my DHCP server gave it the same IP as before.
I tried the "initial BASIC setup of rPi servers" option, but this returned "Communication with the plugin timed out." In fact it gives me this message on all of my rPi's, including the working ones.
I tried the various options of sending Config files, rebooting, etc. and even did the "sudo python installLibs.py --force". Incidentally this should read: sudo python ~/pibeacon/installLibs.py --force as you no longer install piBeacon into the home directory.
I am reasonably confident I can get this going either by deleting the original rPi device and creating a new one or by by filling in the values in the ~/pibeacon/parameters file, but was a little taken aback when finding myself in a position of having to reach for a bash editor where none of the billion other options you so splendidly provide do not work.
piBeacon is my favourite plugin
Edit: Yep, editing the ~/pibeacon/parameters file worked as expected, yet the "initial BASIC setup of rPi servers" option still fails against this now working rPi with "Communication with the plugin timed out."