FAQ

Alternate deployments

Can I try ERM while running Windows ?

Evectors does not provide any Windows based environment to run ERM into. However, with a good deal of patience, there's no reason why you should not be able to run ERM within a Cygwin environment. If you do succeed, tell us about your experience at foss [at] evectors.com, we'll be happy to add a specific README to the project.

Can I try ERM while running Linux ?

There is no reason why you shouldn't, provided you instal all the pre-requisites detailed in the README file. Indeed, all of Evectors production sites are deployed under a Debian distribution. Evectors provides a VMware image file at http://foss.evectors.com with everything ready to roll. You may also run ERM under Amazon EC2 by launching an instance of public AMI 'ami-1a8c7073', tagged 'Evectors ERM vs 1.0'.

Can I try ERM while running Mac OS 10.5 Leopard ?

Well, we wish you didn't, but if you must, make sure you are installing Xcode 3.1.4 (the latest Leopard compatible version) with gcc 4.0.1, and are using the bundled Python 2.5. You should also compile mod_wsgi from its source as the library referenced in the README is optimized for 10.6.

Installation

MySQLdb issue: Library not loaded: libmysqlclient.16.dylib
MySQLdb issue: Library not loaded: libmysqlclient.18.dylib

MySQL packages for Mac OS X are not very consistent in where they instal their payload. Chances are your system is looking to retrieve the library from /usr/local/lib (hardly unreasonable), while MySQL installed it in /usr/local/mysql/lib or some other specific location. Try locate libmysqlclient to find out.

Then enter export DYLD_LIBRARY_PATH=/usr/local/mysql/lib/ or whichever path was reported for libmysqlclient before running the MySQLdb installation sequence again.

MySQLdb issue: EnvironmentError: mysql_config not found

Again, a MySQL package installation issue. Python is looking for mysql_config in /usr/local/bin, while it probably hides in /usr/local/mysql/bin.

Confirm mysql_config's location by running locate mysql_config, then edit the site.cfg file in the MySQL-python-1.2.3 directory.

Uncomment #mysql_config = /usr/local/bin/mysql_config, update the path to mysql_config as needed, save, then run the MySQLdb installation process again.

Running in Amazon EC2

I can't access the instance I have just launched

So I've located the latest public AMI for Evectors ERM, and launched an instance from my AWS account, using my usual key pair and security group. The AWS EC2 console reports the instance as 'running', it displays its 'Public DNS' name, the system log reports sshd and apache2 have launched.

However, running ssh -i .my_private_key root@public_dns_name in a terminal session, as well as accessing 'http://public_dns_name/api/explorer/ from my browser just hang and eventually time out.

Most likely cause: your AWS security group is not set up to let TCP traffic through from all sources (0.0.0.0/0) on ports 22 (ssh) and 80 (http). Click on the Security Groups link in the EC2 Dashboard page, select the 'default group', then the 'Inbound' tab, and review the TCP ports list, and create missing rules for SSH or HTTP accordingly.