FAQ

Frequently Asked Questions

The purpose of this page is to share issues other developers have run into either with the platform or the specifics of their deployment. It is meant to supplement the issue tracking in github.

• Problem installing VOLTTRON on BeagleBone Black
• Bad magic number in site.pyo when building in Angstrom Linux
• Can VOLTTRON be made to build any faster?

---

Problem installing VOLTTRON on BeagleBone Black

The following error message (or similar) is generated when I run the python2.7 bootstrap.py command to install VOLTTRON on a BeagleBone Black

Searching for BACpypes>=0.10,<0.11
Reading https://pypi.python.org/simple/BACpypes/
Download error on https://pypi.python.org/simple/BACpypes/: [Errno 1] _ssl.c:504:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed -- Some
packages may not be found!
Couldn't find index page for 'BACpypes' (maybe misspelled?)

Note: This error will be generated for every package that tries to be installed from pypi.python.org/simple. BACpypes was just the first one it encountered. The full error message is attached if that is more helpful.

Solution

It is very possible that the SSL certificate is failing because the hardware clock on your BeagleBone is not set to the current time. You may check this by typing date in a terminal. If the correct time and date do not appear, there are two methods to update it to the current time. The first (easiest) requires you to perform a command every time the BeagleBone Black is powered on. The second (more difficult) is a one-time fix.

1. Enter the command below in a terminal as a root user. (Note: This requires a network connection and might not work on networks with restrictive policies.)

root@beaglebone:~# ntpdate -b -s -u pool.ntp.org

If you are still having trouble, consult Derek Molloy's instructions.

or

2. Follow Derek Molloy's instructions to make the BeagleBone Black update its clock automatically when it is powered on.

Bad magic number in site.pyo when building in Angstrom Linux

The problem is twofold: Angstrom only includes optimized .pyo bytecode files and not standard .pyc files in its Python package and virtualenv doesn't properly detect this issue. The former can be fixed following the solution below. A patch has been submitted to the virtualenv team which, once released, will prevent the issue in the first place.

Solution 1

Use the version of virtualenv included with the distribution to initialize the environment and then run bootstrap:

volttron@beaglebone:~/volttron$ virtualenv-2.7 env
New python executable in env/bin/python2
Also creating executable in env/bin/python
Installing setuptools, pip...done.
volttron@beaglebone:~/volttron$ env/bin/python bootstrap.py
...

Solution 1 will likely not work. :-(

Solution 2

Run the following commands as root (or use sudo) in a terminal to generate a site.pyc file and remove the .pyo file:

root@beaglebone:~# python -N -m py_compile /usr/lib/python2.7/site.py
root@beaglebone:~# rm /usr/lib/python2.7/site.pyo

Then remove the env directory in the volttron project and run bootstrap.py.

Can VOLTTRON be made to build any faster?

Yes. See Speeding Up VOLTTRON Builds.