Skip to content

Troubleshooting

ARIbemoss edited this page May 11, 2017 · 1 revision

[Back to Installation Guide]


Troubleshooting

Troubleshooting 1: VM error

If you see "Error relaunching VirtualBox VM process: 5", this means that you have downloaded and install the current build of VM 4.3.13. This may cause conflicts with anti-virus packages. Please download and install the old build 4.3.12.

Screen Shot 2014-08-20 at 8.51.15 PM.png


Troubleshooting 2: Eclipse error

If Eclipse cannot be installed due to Java version,

Screen Shot 2014-08-28 at 10.22.35 AM.png

Open your terminal. Type the following command to change the Java version to use version 7.

#!linux

>> sudo update-alternatives --config java

Then, type the section number for Java 7.

If Help menu is missing in Eclipse, open your terminal. Type the following command to open Eclipse.desktop file:

#!python

sudo -H gedit /usr/share/applications/eclipse.desktop

Then, replace the Exec= line with this:

#!python

Exec=env UBUNTU_MENUPROXY= eclipse

Troubleshooting 3: Mercurial error

If you encounter this error:

Screen Shot 2014-08-28 at 6.31.47 PM.png

Type this in the terminal:

#!python

hg -y debuginstall

You will be told to type:

#!python

sudo apt-get install mercurial

This should solve the problem.


Troubleshooting 4: ./bootstrap problem

  1. cryptography 0.4 is not installed

Type the following command in the terminal:

#!linux
sudo apt-get install python-pip
sudo apt-get install libffi-dev
sudo pip install cryptography
#then run 
>> ./bootstrap
#Finally 
>> bin/buildout -N
  1. cannot get pyscopg2

Type the following command in the terminal:

#!linux

sudo apt-get install libpq-dev

Troubleshooting 5: Permission problem

If you face any permission issues:

Before running a shell script file (*.sh), type the following command in the terminal to give the permission to execute the specific file.

#!linux

>> sudo chmod +x filename.sh

or, to give permission to the entire folder, please type the following command:

#!linux

>> sudo chmod 777 -R foldername



Troubleshooting 6: Running other agents manually

The following commands run thermostat agent, plug load agent and lighting load agent manually.

  • Run Thermostat Agent
#!linux

>> sudo ./runThermostatAgent.sh
  • Run Plugload Agent
#!linux

>> sudo ./runPlugloadAgent.sh
  • Run Lighting Agent
#!linux

>> sudo ./runLightingAgent.sh

Troubleshooting 7: sMAP has existing data

If sMAP has existing data (check localhost/plot), you can remove existing sMAP data by:

  • Stop sMAP - by going to the terminal that has sMAP running, hit ctrl+C

  • Go to localhost/admin, log in

  • Go to subscriptions

  • Select subscriptions to delete, click "delete" button.

  • Add new subscriptions, copy the "key" and modify "smap_driver.ini" using Step 2 described here.

  • Then re-start sMAP by typing the following commands:

#!linux

>> cd ~/workspace/bemoss_os
>> sudo twistd -n smap smap_driver.ini

Interesting articles:

http://makezine.com/magazine/how-to-choose-the-right-platform-raspberry-pi-or-beaglebone-black/


[Back to Installation Guide]

Clone this wiki locally