-
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/Configuration on fresh install of Debian 10 fails. #22
Comments
Dear @Dewieinns, thanks for your persistence! I recognize the full list of suggested dependencies of Kotori is pretty huge. However, you should be able to run it with a minimal set of dependencies without using
as both will/should be available from the same package repository. Thanks for figuring out the requirement of GnuPG. I can't tell anything about any VM weirdness you might be observing.
Sure, just drop me an email at With kind regards, |
Just wanted to give you a heads-up that I've sent 2 email messages now; just in the even your SPAM filter nabbed them. |
Dear @Dewieinns, we updated the packages for Debian "buster" 10, so Kotori 0.24.5 should now install without pulling in such a large number of dependencies you have been observing at #7 (comment). We tested the new release on a VirtualBox virtual machine through Vagrant and it worked flawlessly using the updated documentation [1]. With kind regards, |
Hey @amotl I am starting a new thread to follow up with a post I made where similar was happening as I'm experiencing slightly different variations now.
After my reply last evening I set about working with a new VM. I didn't properly document everything I had done so this morning I started over COMPLETELY fresh. I was seeing weird issues where systemctl didn't seem to be running and the VM I was using had only one cpu/core. I assumed this was the reason for performance issues I was seeing so I wiped it, made a new VM (on a different drive in my server even) and set about installing Debian (debian-10.3.0-amd64-netinst.iso)
I opted not to install the GUI and enabled the SSH server.
With Debian successfully installed I installed screen and then started following the Setup on Debian guide again.
Note: When I started following this guide initially (yesterday) it wasn't obvious to me (I'm a n00b) that I needed to install the package source for Debian Stretch (9) OR Debian Buster (10).
This time I added only the package source I needed (Buster) and was good to go... until:
Add GPG key for checking package signatures:
wget -qO - https://packages.elmyra.de/elmyra/foss/debian/pubkey.txt | apt-key add -
Error:
E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation
Fix:
apt-get install gnupg
All is good and I set about installing Kotori as well as recommended and suggested packages (14.9GB - takes about an hour and a half on my slow internet connection)
Next thing prompted for is "Configuring jackd2"
_Do I want to run with realtime priority? (_explains it may lead to lock-ups.) <-- Selected No
then followed:
Configuring Kerberos Authentication
Default Kerbors version 5 realm:
- Pre-populated with my domain <-- left it as is
Kerberos servers for your realm:
- Nothing pre-populated <-- left it blank
Administrative server for your Kerberos realm:
- Nothing pre-populated <-- left it blank
It then goes through and installs everything - this takes some time - until it gets to the end where there are a couple of errors displayed:
and then:
At this point I rebooted the VM using systemclt reboot
After reboot I noticed VM was SLOW again - mega slow.
I again ran apt update, all packages were up to date.
I then again ran apt install --install-recommends --install-suggests kotori and noticed the following:
I hit Y to continue and it looked like everything was successful this time.
I attempted to execute systemctl start influxdb grafana-server but received the following warning again:
It was after this that I wiped the VM last time thinking I had done something mega wrong...
I then installed open-vm-tools on the VM which allowed me to gracefully reboot the system via the VM Host console.
Upon rebooting systemctl still isn't running... at this point I'm kind of at a loss. I was farther than this trying to install it on Ubuntu yesterday.
Sorry for the wall of information but I wanted to be thorough enough you may be able to provide some insight as to what's going on (Hopefully something more than "that's really weird" haha)
If you wish me to get in touch directly I can do this also.
The text was updated successfully, but these errors were encountered: