I’ve tried installing Cayenne on a headless B+ running Jesse via the web site and I received notification that the installation was progressing up to the reboot stage. There were no further notifications and it appeared that I lost access to the Pi as I was unable to use ssh or vnc to connect. I waited about an hour in case the install was still slowly running then powered off the device and reimaged the sd card (16gb).
I tried again this time expanding the filesystem as I read that this may be necessary. I connected the Pi to a monitor & used the android app to run the install but after the install rebooted the device I noticed that wlan0 network connectivity was now lost. A display of network settings showed that the config was missing. The Pi was still quite busy as CPU usage remained around 100% and I left it for about thirty minutes then powered it down as the app still showed no devices present.
I expected this to be a quick and easy install so would anyone have any ideas what is going wrong?
Thanks…
adam
March 19, 2017, 5:23pm
2
It should be fairly quick and painless, but we’ll get this fixed for you. Can you post the output of commands below for us?
df -h
Also would be helpful to see the output of the installer. Run “sudo rpi_xxxxxxxxxx.sh -v” to get any errors that come up during install.
Adam thanks for the reply. Third time lucky as I managed to get the overview web page up after another install however I was no longer able to access the device using RealVNC. SSH access was possible.
I tried using remote access from the overview screen however I was prompted to allow device sharing on the pi but this wasn’t possible as it was headless. After a reboot the pi was totally inaccessible. I managed to access it via an ethernet cable and found that the wlan0 config was cleared again.
I captured the install logs and I can post these if they would help.
I’ve used webiopi in the past and I was hoping cayenne would be an easier and quicker solution for my current project. I may give it one more go with a fresh Jesse install.
pi@RPi2:~ $ df -hhttp://www.raspbian.org/ ”RaspbianForums - Raspbian ”RaspbianBugs - Raspbian ”
Thanks
Hi @douvers , welcome to the Cayenne Community.
Sorry for the trouble you’ve had installing on this Pi, it indeed should be quick and easy. If you have the output from running the command line install, that will offer a big hint of what is up here.
Also, regarding the Remote Desktop feature in Cayenne, it’s currently broken with the latest Raspbian, although we should have a fix for it out very shortly. In the meantime if you want graphical remote access to your Pi, I’d suggest to setup VNC per the instructions on the official Raspberry Pi site: Raspberry Pi Documentation - Remote Access
Hi rsiegel, I always use RealVNC - but as I’ve mentioned previously it get’s broken on the pi everytime I install Cayenne.
Would your install of tightvncserver have anything to do with this?
Here’s the install log as requested…
Many thanks.
pi@RPi2:~ $ wget https://cayenne.mydevices.com/dl/rpi_8xpxp2irvy.sh https://cayenne.mydevices.com/dl/rpi_8xpxp2irvy.sh cayenne.mydevices.com (cayenne.mydevices.com )… 52.202.24.38cayenne.mydevices.com (cayenne.mydevices.com )|52.202.24.38|:443… connected.
rpi_8xpxp2irvy.sh 100%[=====================>] 1.26K --.-KB/s in 0.001s
2017-03-20 10:56:45 (1.56 MB/s) - ‘rpi_8xpxp2irvy.sh’ saved [1294/1294]
pi@RPi2:~ $ sudo bash rpi_8xpxp2irvy.sh -vhttp://updates.mydevices.com/raspberry/myDevices-1.0.tar.gz updates.mydevices.com (updates.mydevices.com )… 54.148.225.117updates.mydevices.com (updates.mydevices.com )|54.148.225.117|:80… connected.
/home/pi/myDevices-1.0.t 100%[====================================>] 8.81M 40.6KB/s in 4m 38s
2017-03-20 11:04:26 (32.5 KB/s) - ‘/home/pi/myDevices-1.0.tar.gz’ saved [9234417/9234417]
./myDevices-1.0/init .pymain .pyinit .pyinit .pyinit .pyinit .pyinit .pyinit .pyinit .pyinit .pyinit .py
set -x
exec
Monday 20 March 11:14:32 AEDT 2017 Installing software componentsmain .py → build/lib/myDevicesinit .py → build/lib/myDevicesinit .py → build/lib/myDevices/ipgetterinit .py → build/lib/myDevices/cloudinit .py → build/lib/myDevices/utilsinit .py → build/lib/myDevices/remoteaccessinit .py → build/lib/myDevices/osinit .py → build/lib/myDevices/sensorsinit .py → build/lib/myDevices/wifiinit .py → build/lib/myDevices/scheduleinit .py → build/lib/myDevices/requests_futuresinit .py → build/bdist.linux-armv6l/egg/myDevices/osmain .py → build/bdist.linux-armv6l/egg/myDevicesinit .py → build/bdist.linux-armv6l/egg/myDevices/wifiinit .py → build/bdist.linux-armv6l/egg/myDevices/cloudinit .py → build/bdist.linux-armv6l/egg/myDevices/ipgetterinit .py → build/bdist.linux-armv6l/egg/myDevices/remoteaccessinit .py → build/bdist.linux-armv6l/egg/myDevices/utilsinit .py → build/bdist.linux-armv6l/egg/myDevices/requests_futuresinit .py → build/bdist.linux-armv6l/egg/myDevices/sensorsinit .py → build/bdist.linux-armv6l/egg/myDevicesinit .py → build/bdist.linux-armv6l/egg/myDevices/scheduleinit .py to init .cpython-34.pycmain .py to main .cpython-34.pycinit .py to init .cpython-34.pycinit .py to init .cpython-34.pycinit .py to init .cpython-34.pycinit .py to init .cpython-34.pycinit .py to init .cpython-34.pycinit .py to init .cpython-34.pycinit .py to init .cpython-34.pycinit .py to init .cpython-34.pycinit .py to init .cpython-34.pyc
Installed /usr/local/lib/python3.4/dist-packages/myDevices-0.1.20818-py3.4.egg
I had misread your earlier comment regarding VNC, I do think this is related to our using TightVNC and RealVNC being added in the latest Raspbian. We’re making an update this week where we switch to RealVNC for these connections to avoid the issue entirely, so you shouldn’t have to deal with it much longer.
Regarding your Pi Agent install, really everything there looks fine, it does not look like the install failed anywhere along the way. I’m wondering if this could be an issue with ports on your network. The Cayenne Raspberry Pi agent requires port 8181 to be open to communicate with our server – I could see it installing OK but failing to advance to showing as ‘online’ in the dashboard if it can’t communicate on this port.
Use telnet to check if the port is open. For some reason this is not installed by default any more so you can install it using “sudo apt-get install telnet”
If the port is open you will see the following (your IP addresses may or may not be the same as mine):
pi@raspberrypi:~ $ telnet cloud.mydevices.com 8181
Trying 54.165.135.17...
Connected to cloud.mydevices.com.
Escape character is '^]'.
Connection closed by foreign host.
If the port is closed you will see the following (your IP addresses may or may not be the same as mine):
pi@raspberrypi:~ $ telnet cloud.mydevices.com 8181
Trying 52.6.151.66...
Trying 54.165.135.17...
telnet: Unable to connect to remote host: Connection timed out