Raspbian jessie lite installation failure model A+

Install of cayenne failing on my new A+ with the following error below:

Fri 9 Dec 15:38:33 UTC 2016 Installing myDevices agent
Fri 9 Dec 15:48:11 UTC 2016 Found Python 3.4.2…
Fri 9 Dec 15:48:11 UTC 2016 Copying agent libraries
Fri 9 Dec 15:48:53 UTC 2016 Installing python utils
Fri 9 Dec 15:49:03 UTC 2016 Installing software components
Fri 9 Dec 15:49:04 UTC 2016 Trying to install myDevices for python3 version: Python 3.4.2
Fri 9 Dec 15:49:05 UTC 2016 Build for Python 3.4.2 failed\n

Hi @josh1,

We’ve had a number of users with this error on the forum in the past, and they’ve all resolved it with an update through these commands, then re-attempting the Cayenne install.

sudo apt-get -f update sudo apt-get -f upgrade sudo apt-get -f dist-upgrade sudo apt-get -f install python3.4 sudo apt-get -f install

I’ll leave this open for a bit to see how they work for you, please let us know if they resolve the error message!

I followed your instructions. Still failing with the same error. I’m running a 16GB card in my A+. Is that enough?

Yeah, it’s definitely not a disk space issue (unless your disk is 98% full, I suppose), Cayenne doesn’t take much space at all. Something to do with that python version I’m sure. Can you run cat /etc/os-release and post the output for me here?

I know you’ve said it’s Jessie Lite – we should support that but I haven’t run it in a long time, so I’ll take a moment to run it on one of my test pis to be sure. It is a fresh install of Jessie Lite? Or something that’s been running with other projects/software for a while now? Just looking to get as close to your configuration as possible so I can poke at it.

root@raspberrypi:~# cat /etc/os-release
PRETTY_NAME=“Raspbian GNU/Linux 8 (jessie)”
NAME=“Raspbian GNU/Linux”
VERSION=“8 (jessie)”
SUPPORT_URL=“RaspbianForums - Raspbian
BUG_REPORT_URL=“RaspbianBugs - Raspbian


Sorry if if you’ve already done this, but did you expand the file system after you installed the image?



no, i have not. Are you referring to expanding the image via the

Yes. Otherwise the whole flash isn’t being utilized and you will run into space constrains.

I hadn’t considered that this was a thing you had to do. I’m not sure I fully understand why they don’t do that at OS install time but I’d never had an issue with it before. Maybe because I’m using the NOOBS installer usually with full Jessie it wasn’t an issue? Or was it always a looming issue that I’ve just managed to avoid :slight_smile:

Anyway, I want to report that in my test (granted, on a Pi2 Model B) I was able to install Cayenne on a fresh image of Jessie Lite (I did not use NOOBS or expand the filesystem). The install seemed to take longer than I’m used to, but it finished within 5-10 minutes.

So if expanding the filesystem doesn’t do the trick for you Josh, I’d be interested in how old the install is/what other software you’re running, etc.

If I recall correctly, I think it asks you if you want to. If you skip over this step, well…

I trust that you’re offering good advice. I’m just curious what the use case would be for NOT doing it. Maybe multiple partitions on one SD card?

Seems to me like the user-friendly thing to do would just be to fill the card by default so your average Pi user can take advantage of their full disk capacity, and let the minority who are running 7 OS on 8 paritions on one SD card in 2016 use their technical skill to to resize it back. :innocent:

I kid, but only somewhat.

The only thing I can think of is for VMs or switching between images on the same media. You would make sure to have a persistent storage area, but the image doesn’t grow past that. Then have a bootloader to jump to the image you want.

I’m not 100% sure about Jessie lite since I haven’t used it in quite some time but the latest image of Jessie full will auto expand on first boot (can’t skip this). It has been that way sine September I believe. So…if an old image was used it’s possible that it’s not expanded.

I finally resolved the issue by using a 64GB card and NOOBS. Thanks for the input everyone!

Glad to hear the issue resolved itself. Something tells me it was probably just the wipe-and-reinstall rather than the disk space, in case anyone comes across this thread in the future.