Install error when lamsom imports Scheduler

[felmoltor]

Hello,

I'm having some troubles installing shiva in one Debian 7. Executing "./install.sh" script it get stucked after the cleanup step:

[*] Installing Lamson (receiver) and creating project:
Requirement already satisfied (use --upgrade to upgrade): lamson in ./lib/python2.7/site-packages
Requirement already satisfied (use --upgrade to upgrade): chardet in ./lib/python2.7/site-packages (from lamson)
Requirement already satisfied (use --upgrade to upgrade): jinja2 in ./lib/python2.7/site-packages (from lamson)
Requirement already satisfied (use --upgrade to upgrade): mock in ./lib/python2.7/site-packages (from lamson)
Requirement already satisfied (use --upgrade to upgrade): nose in ./lib/python2.7/site-packages (from lamson)
Requirement already satisfied (use --upgrade to upgrade): python-daemon in ./lib/python2.7/site-packages (from lamson)
Requirement already satisfied (use --upgrade to upgrade): python-modargs in ./lib/python2.7/site-packages (from lamson)
Requirement already satisfied (use --upgrade to upgrade): markupsafe in ./lib/python2.7/site-packages (from jinja2->lamson)
Requirement already satisfied (use --upgrade to upgrade): setuptools in ./lib/python2.7/site-packages/setuptools-5.4.2-py2.7.egg (from python-daemon->lamson)
Requirement already satisfied (use --upgrade to upgrade): lockfile>=0.9 in ./lib/python2.7/site-packages (from python-daemon->lamson)
Cleaning up...
Traceback (most recent call last):
  File "/home/harvester/honey/shiva/shiva/shivaReceiver/bin/lamson", line 4, in <module>
    from lamson import commands
  File "/home/harvester/honey/shiva/shiva/shivaReceiver/local/lib/python2.7/site-packages/lamson/commands.py", line 28, in <module>
    from lamson import server, utils, mail, routing, queue, encoding
  File "/home/harvester/honey/shiva/shiva/shivaReceiver/local/lib/python2.7/site-packages/lamson/server.py", line 20, in <module>
    from apscheduler.scheduler import Scheduler
ImportError: No module named apscheduler.scheduler

But the weird thing is that executing directly the files giving problems throws no error at all:

$ python /home/harvester/honey/shiva/shiva/shivaReceiver/local/lib/python2.7/site-packages/lamson/server.py
$ (No error thrown)
$ ipython
Python 2.7.3 (default, Mar 13 2014, 11:03:55)
Type "copyright", "credits" or "license" for more information.

IPython 0.13.1 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.

In [1]: from apscheduler.scheduler import Scheduler
In [2]: from lamson import server, utils, mail, routing, queue, encoding
In [3]: from lamson import commands
In [4]: exit

I'm using Python 2.7.3 and the needed libraries are present:

$ python -V
Python 2.7.3

Installed packages and versions:

• exim4-daemon-light: 4.80-7
• g++: 4.7.2-1
• python-virtualenv: 1.7.1.2-2
• python-dev: 2.7.3-4+deb7u1
• libmysqlclient-dev: 5.5.38-0+wheezy1
• mysql-client: 5.5.38-0+wheezy
• mysql-server: 5.5.38-0+wheezy

Not sure what's happening here. :sweat:

[b0nd]

Hi, What is the version of apscheduler inside virtualenv?

Running: $pip install apscheduler==2.1.2 shall resolve the issue. I need to fix that in install.sh file Thanks

[RahulBinjve-zz]

Hi @felmoltor,

To add to what @b0nd already mentioned, I shall ask you to follow the below steps to reproduce the error message -

$ cd shiva/shivaReceiver
$ source bin/activate
(shivaReceiver) $ python -c 'from apscheduler.scheduler import Scheduler'

If the above steps show the same error, it will ensure that the error indeed is with apscheduler, which I believe is true. To fix this, for the time being, please follow these instructions

(shivaReceiver) $ pip uninstall apscheduler
(shivaReceiver) $ pip install apscheduler==2.1.2

Just make sure that the virtualenv is activated. And, follow the same steps in analyzer too. This is a temporary fix until we update the installer.

Thanks.

[felmoltor]

Thanks to both of you, I've done the installation of apscheduler 2.1.2 inside the shivaReceiver virtualenv and now the install.sh doees not throw the error with apscheduler library, but now it complains about the existence of the Project receiver:

[*] Installing Lamson (receiver) and creating project:
Requirement already satisfied (use --upgrade to upgrade): lamson in ./lib/python2.7/site-packages
Requirement already satisfied (use --upgrade to upgrade): chardet in ./lib/python2.7/site-packages (from lamson)
Requirement already satisfied (use --upgrade to upgrade): jinja2 in ./lib/python2.7/site-packages (from lamson)
Requirement already satisfied (use --upgrade to upgrade): mock in ./lib/python2.7/site-packages (from lamson)
Requirement already satisfied (use --upgrade to upgrade): nose in ./lib/python2.7/site-packages (from lamson)
Requirement already satisfied (use --upgrade to upgrade): python-daemon in ./lib/python2.7/site-packages (from lamson)
Requirement already satisfied (use --upgrade to upgrade): python-modargs in ./lib/python2.7/site-packages (from lamson)
Requirement already satisfied (use --upgrade to upgrade): markupsafe in ./lib/python2.7/site-packages (from jinja2->lamson)
Requirement already satisfied (use --upgrade to upgrade): setuptools in ./lib/python2.7/site-packages/setuptools-5.4.2-py2.7.egg (from python-daemon->lamson)
Requirement already satisfied (use --upgrade to upgrade): lockfile>=0.9 in ./lib/python2.7/site-packages (from python-daemon->lamson)
Cleaning up...
Project receiver exists, delete it first.

Does it means I have to delete the whole folder "receiver"?

Thanks.

[RahulBinjve-zz]

Hi @felmoltor,

Yes, actually when you run install.sh, it starts from the scratch, which you don't want. The script is trying to do a fresh install of SHIVA, which already exists.

Can you confirm that if you can run SHIVA or not? And this was the reason why I suggested you to install 'apscheduler' in receiver and analyzer, manually. After that, running 'install.sh' is not required.

Sorry, for the inconvenience caused. Hope this helps. :)

[felmoltor]

Cool, now everything it's running well :smile: Thank you for your support @b0nd and @RahulBinjve

[RahulBinjve-zz]

Glad we could help @felmoltor. And btw, the code has been updated to install right version of libraries. Thanks for reporting the issue to us.

Cheers. :)