-
Notifications
You must be signed in to change notification settings - Fork 17
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
Installation from .deb package on Ubuntu 18.04 fails #7
Comments
Dear @TheOneWhoKnocks96, thanks for letting us know about this issue. We will try to look into that. With kind regards, |
We can confirm your observations for the Python virtualenv shipped with Kotori on Ubuntu 18.04.2 LTS as well. Kotori was packaged on a Debian stretch system, so there seems to be some anomaly between Python 2.7.13 and Python 2.7.15. While being designed to ship a fully self-contained Python virtualenv together with Kotori, this seems to fail here as there are things from the distribution Python being invoked. Sorry about that. Looks like the internet already knows about the very same issue you are observing. The most valuable references seem to be: |
The minimum steps to reproduce the issue is By following the recommendation at [1] to upgrade the existing virtual environment through
the command above stops yielding an error and Kotori will start after invoking [1] MDAnalysis/mdanalysis#1739 (comment) Until we can resolve the issue on the packaging process, we humbly ask you to fix the existing virtualenv on your machine by applying this workaround. |
I upgraded the existing virtual environment through
But when i restart the kotori service with
|
Sorry to hear about that. When installing the package,
we receive the following output which indicates the appropriate installation and activation of the systemd unit file:
After that, the service pretends to be installed correctly
And after fixing the dependency woes as outlined above by upgrading the existing virtual environment, it will also actually start flawlessly. Currently, I'm a bit out of ideas what might be going wrong on your machine regarding the appropriate setup of the systemd unit file. Nevertheless, we are still curious and would like to resolve the issue to make you and other users happy. |
it Worked!! Thank you very much |
Hi @TheOneWhoKnocks96, do you have an idea what actually made things work after it failed before? Was it just an arbitrary hiccup? Anyway, good to hear it is now working for you. Let's keep this issue open until we have been able to resolve the issue which still requires the workaround re. upgrading the existing virtualenv, right? Happy telemetry and with kind regards, |
The service of Kotori started and is active and running but i checked the logs of kotori.log and it gives this:
|
This is another error you are experiencing right now? Bummer! The minimal step to reproduce the issue here is:
We will try to continue to improve this situation for users on Ubuntu 18. In the meanwhile, we want to apologize for the inconvenience. |
I would have recommended to just install the
- but - Problems all the way downunfortunately, this also bails out
The minimal step to reproduce this would be
where we also can see the system Python shines through
|
We've created a gist [1] with an accompanying automated non-invasive patch-script [2] which will mitigate the problems learned throughout this conversation including the most recent one. Sorry again for the hassle. The amount of issues with Ubuntu 18.04 indicate we probably should build packages natively on that system instead of just reusing the Debian package. However, we are currently lacking the resources to do so, so workarounds is the best we can deliver at the moment. We apologize for that. [1] https://gist.github.com/amotl/31eec18126c3f86908629671ea9ecc4d
|
I started the script a it mitigated the most recent problem but it raised another problem also:
What could be a better solution? Install Kotori in a Debian stretch system? |
For now and when looking at what we have learned throughout this discussion (thanks again!), I would definitively recommend to install the current Kotori [1] https://github.com/daq-tools/kotori/blob/0.22.7/Makefile#L111-L113 |
Okay, thank you very much for the help!! |
Hi again!! (kotori.log)
|
i solved it for now!! I imported the arrow from PyPi |
Hi there, bummer. We haven't exactly been aware that the Debian package actually causes problems on Debian! I just checked and want to add that we are successfully running Kotori on a Debian 9.9 system where both the
However, installing Kotori on this system happened a while ago already. Nevertheless, I am still curious where this issue might be coming from and definitively would like to see it resolved for you and other users. In the meanwhile, we are happy that you have been able to help yourself. Do you remember what you did exactly to mitigate this installation issue on Debian? Maybe post-installing
With kind regards, |
What i did was to install the arrow package: |
Thanks for letting us know. Did you install it into the virtualenv or into the system Python? |
Dear @Ozymandias96, Kotori 0.23.0 packages are now available for Debian "buster" 10. They might well also work on Ubuntu 18.04. The package repository is at [1]:
With kind regards, [1] https://getkotori.org/docs/setup/debian-quickstart.html#register-with-package-repository |
I just wanted to chime in for others who may be trying to make this work On a fresh install of Debian 10.3 (I tried Ubuntu initially also - encountered above issues as well), following the [Quick Start] (https://getkotori.org/docs/setup/debian-quickstart.html) I still had the issue with the: I then encountered the next issue: I've been searching for a solution to this error but everything seems to point to updating libraries for Python3 and it is my understanding you're using Python 2.7? I'm no programmer but know just enough to be dangerous. It appears I maybe don't have a full-blown version of pip? |
Hi @Dewieinns, thanks for writing in.
as the package repository?
With kind regards, |
Time for another Fun filled Ubuntu update: Today I started over fresh with my Ubuntu install and tried to document as many variations as I could. First off - Register with Package Repository
Resulted in: so I discovered that if you add them first via: you can then add the repo without errors I then ran apt update and apt upgrade to be sure everything was up to date before starting. When that was done I executed apt install --install-recommends --install-suggests kotori During Install I had no idea what to enter for a few of these. Could you please provide a bit of feedback here?
Everything seemed to be ok until I got to:
so I went back and tried to upgrade the virtual environment This required me to install virtualenv. I did a bit more messing around and was still unable to get the Kotori service to start. I ended up issuing the above command again and finally, the service is up and running it says. I hop on over and have a look at the Kotori logs again and see the following in there:
so back to the error thread I go. I found where you made a bash script and I tried to execute it. Got permission errors when not using sudo and it just did nothing when I was sudo... so I downloaded it: and then ran it manually everything seems good so I restart the Kotori service annnd... ^^ That was one of the issues your script seemed to say it would fix... Restart the service again! SUCCESS!! I Think... wait... I then go back to the "Getting Started" guide and see where it says to send a sample telemetry packet, so I do and the look in the Kotori log again:
Well that's weird... what's going on with Grafana?
so I start it and it seems to start no problem. I restart Kotori again and look in the logs:
Which isn't good. As per the Guide I had logged in to Grafana as admin/admin. I was prompted to set a password; maybe that's not good? I reset it back to "admin" to test my theory: https://community.grafana.com/t/how-do-i-reset-admin-password/23 Restarted Kotori again - no warnings! no errors! So I again send a telemetry packet - again no errors! I then attempted to look at the dashboard and Watch Telemetry Data as per the Guide but the provided sample URL did not work for me (http://192.168.1.132:3000/dashboard/db/ecuador) I was able to find it by logging in to Grafana > Dashboards > Manage > Instant Dashboards > ecuador Success! Data! I am guessing this is maybe due to a newer version of Grafana? Moving forward I guess I have to determine how I can secure Grafana better (better password) and have Kotori still be able to access it. |
Dear @Dewieinns,
Thanks for sharing your walkthrough and for your patience getting Kotori up and running. It's a bit poor that it caused so much hassle for you. I should really update the documentation accordingly to make the installation work more smoothly. Apart from that, I should investigate a) why Kotori pulls in such a wrath of dependencies through the Debian package installation path which might not be required at all (don't know why it actually should need Chief, Icecast, Jack Audio, Kerberos and Postfix) by improving the documentation to install specific packages (InfluxDB and Grafana) explicitly and b) why it fails on installing the essential Python modules ( Apart from that, finally moving forward to Python 3 (#20) would do no harm either and might also improve the installation experience.
I believe the Grafana credentials may be configured within Good luck and let me know about further questions you might have. With kind regards, |
Not a problem, I provided the feedback to hopefully help others moving forward (or perhaps you to improve documentation) If there is anything I can do to help please feel free to ask. I have a feeling I will have some more questions as I go :) |
Dear Andrew, I've slightly updated the documentation [1] through dfa62db and the gist on [2]. Saying this, it should probably work out-of-the-box without needing a fixup script just by using the packages. Sorry again that it didn't do that for you and thanks for your feedback! With kind regards, [1] https://getkotori.org/docs/setup/debian-quickstart.html P.S.: The command to invoke the updated fixup script is:
|
You are welcome to join us on https://community.hiveeyes.org/.
We are mostly from Berlin, Germany. You are from Canada? Cheers! |
You are welcome to join us on https://community.hiveeyes.org/.
We will!
We are mostly from Berlin, Germany. You are from Canada? Cheers!
Indeed we are. I see now I'm replying to the github issue thread and will
stop. Thanks again!
… —
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#7?email_source=notifications&email_token=AGMJVAOODR5NZZZ6HDUUNJTRFLY2JA5CNFSM4HRYACKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENNQFYI#issuecomment-593167073>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGMJVAIMMUG6NLWMR4TCZWDRFLY2JANCNFSM4HRYACKA>
.
|
I just installed this again using the minimum set of required packages. Even after executing your script I still ended up having to run:
to get dateutil to download for some reason..
|
Dear @Dewieinns, thanks for your feedback. This is really weird. If you might have another chance, I will be happy to see the output of the fixup script. Cheers, |
While we haven't been able to build appropriate packages for Ubuntu, Kotori 0.24.5 is now available as a Docker image from Docker Hub, see also [1] and [2]. However, Debian "stretch" 9 and Debian "buster" 10 are supported natively by corresponding Debian packages on the package repository as outlined on [3]. [1] https://hub.docker.com/repository/docker/daqzilla/kotori |
Dear @RuiPinto96 and @Dewieinns, we finally added builds for Ubuntu 18 Bionic Beaver and updated the documentation at [1] accordingly. We have been able to give it a quick test on a VirtualBox machine which appeared to be successful but will also be happy to receive further feedback from you. With kind regards, [1] https://getkotori.org/docs/setup/debian-quickstart.html#register-with-package-repository |
Hi! I installed the latest kotori package (0.22.7) for amd64 in my Ubuntu 18.04 LTS machine, but the kotori service fails to start. My machine has the architecture x86_64.
If anyone could please help.
The logs from kotori are:
Regards
The text was updated successfully, but these errors were encountered: