shinken
shinken copied to clipboard
strange install path in ubuntu xenial
Hi, Not sure if this is a shinken or ubuntu issue but when installing it treats dist-packages as the file install root rather than systems root at /.
root@shinken-test-ubuntu:~# pip install --upgrade pip
Collecting pip
Downloading pip-9.0.1-py2.py3-none-any.whl (1.3MB)
100% |████████████████████████████████| 1.3MB 364kB/s
Installing collected packages: pip
Found existing installation: pip 8.1.1
Not uninstalling pip at /usr/lib/python2.7/dist-packages, outside environment /usr
Successfully installed pip-8.1.1
You are using pip version 8.1.1, however version 9.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
root@shinken-test-ubuntu:~# pip install --upgrade pip
Requirement already up-to-date: pip in /usr/local/lib/python2.7/dist-packages
root@shinken-test-ubuntu:~# pip install Shinken
Collecting Shinken
Installing collected packages: Shinken
Successfully installed Shinken-2.4.3
root@shinken-test-ubuntu:~# find / -name shinken-arbiter
/usr/local/lib/python2.7/dist-packages/usr/bin/shinken-arbiter
/usr/local/lib/python2.7/dist-packages/etc/init.d/shinken-arbiter
root@shinken-test-ubuntu:~#
running pip with a specific install location seems to work, so it might be a packaging issue?
root@shinken-test-ubuntu:~# pip install --install-option="--prefix=/" Shinken
/usr/local/lib/python2.7/dist-packages/pip/commands/install.py:194: UserWarning: Disabling all use of wheels due to the use of --build-options / --global-options / --install-options.
cmdoptions.check_install_build_global(options)
Collecting Shinken
Using cached Shinken-2.4.3.tar.gz
Skipping bdist_wheel for Shinken, due to binaries being disabled for it.
Installing collected packages: Shinken
Running setup.py install for Shinken ... done
Successfully installed Shinken
root@shinken-test-ubuntu:~# find / -name shinken-arbiter
/usr/bin/shinken-arbiter
/etc/init.d/shinken-arbiter
Oh thank god I thought I was going insane because nobody else on the internet seemed to have the problem. :-O
Same issue here under Debian Testing with all updates, installing Shinken 2.4.3 with the pip method.
I'have same problem with Debian 9 :(
"only" problem after this "trick" pip is unable do uninstall shinken
# pip uninstall shinken
Cannot uninstall requirement shinken, not installed
same here thanks for the trick
Same issue here, on Debian 8.
Same on Ubuntu 18.04
If I install shinken like this I am getting errors like this when trying to start the service:
FAILED: ImportError: No module named shinken (full output is in /tmp/bad_start_for_arbiter)