-
Notifications
You must be signed in to change notification settings - Fork 335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update on Shinken Migration to Python 3: Any News? #2031
Comments
hi I think the project is actually stop or dead :-( I installed version 3 of Shinken in a debian 11 VM with the following procedure: apt-get install python3-pip python-six python3-bottle python3-cherrypy3 cd /home/shinken/shinken for i in arbiter poller reactionner scheduler broker receiver; do /usr/local/bin/shinken-arbiter -v -c /etc/shinken/shinken.cfg //to control good installation The 6 shinken services are started ! Well, but the following "shinken" script which apparently allows you to add modules (like webui2) does not seem to have been completely ported to Python3. In particular, there are several errors in the ConfigParser commands, and the CONFIG dictionary. best regards |
Hi @getienne53 It was I did, I installed shinken on VM rocky 8 separate of other soft to avoid incompatibility python issue. All with pip is working but you have to set alternative python to python 2. |
Thanks for your reply @garadar :-) I tried with update-alternatives --config python : Selection Path Priority Status
Selection 0, 1 or 2 give the same error --> File "/usr/local/lib/python3.9/dist-packages/Shinken-3.0.0rc1-py3.9.egg/EGG-INFO/scripts/shinken", line 428, in main "ConfigParser" is a python2 command. So, i don't understand why that dont work, with python 2.7.18 If i modify the shebang with #!/usr/bin/env python3, i have the same error with python3 that's life :-( |
Weird indeed. I a migrating my vm I will give my prodecure once completed. But I used pip to install it and I had to reinstall my-curl in a specific and old version and recompile another package with specific option.... Well I need to document clearly. I also contact the customer service of shinken Are you on rocky 8 too? |
Hi, I converted all the files via 2to3 and corrected the problems when running cli shinken. Module installation seems to be working fine. https://github.com/Guillaume001/shinken/tree/python3 On Debian 12 and Python 3.11.2. I've got all the deamons running and they seem to be taking their configuration. I'm trying to port mod-livestatus and mod-logstore-sqlite to connect a thruk but there are still quite a few problems. |
Interesting, I am using this both mod, what kind of issue do you have ? |
hello I took the shinken script writed in python3 from Guillaume001's repository. (thanks to him) Now "sudo shinken --init" works :-) I tried to install the webui or webui2 modules and I got the following error: sudo shinken install webui2 By replacing "from StringIO import StringIO" with "from io import StringIO" in /var/lib/shinken/cli/shinkenio/cli.py, we move forward but we still get the error: shinken@ct-shinken:~/shinken$ sudo shinken install webui2 Same error with "webui" module. Any idea ? |
Hi @getienne53 |
hi @getienne53 Actualy, i install module livestatus and logstore-sqlite via the following commands : Some parts may be missing for downloading modules.. |
hi @garadar I currently have the following errors : broker logs
scheduler logs
during starting up reactionner and poller daemon :
|
It's been a while, but I'm back with some exciting news, I hope. I've managed to make Shinken work without any code changes on Rocky 8. Here's the procedure I posted: #2033. Additionally, I've created a SaltStack (similar to Puppet or Ansible) Shinken installation for automatic deployment. So far, I haven't encountered any conflicts or errors. :) Let me know how it's work for you ! |
Dear @naparuba, @geektophe, and @shinken-solutions,
I am an HPC system engineer and have been using Shinken since my beginning in this vast IT world.
I used to work on RHEL/CentOS7, but ongoing administration/maintenance is pushing us to migrate to newer architectures, EL8/9, which complicates the deployment of Shinken with Python 2.
Currently, we are using a Docker container, but it has its limitations.
Do you have any updates on the migration to Python 3?
Thank you for your work and this solution !
PS: (I doubt you are not already aware, but...) The Python tool https://docs.python.org/3/library/2to3.html may be an interesting tool for automating the translation to Python 3.
PS2: If you need help maybe some tasks can be delegate to the community and pull requested. Let us know !
The text was updated successfully, but these errors were encountered: