-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Support for OpenSSL3 to allow installation in Ubuntu 22.04 #4067
Comments
Can you submit your install log or your installation errors? |
This is whatappears in syslog: No other logs are created. |
You need to configure an admin account, which is clearly described in the in the logs:
|
These are my steps: go to Software app of Ubuntu and choose to install Couchdb. It installs successfully but nothing happens. I check the logs and that appears. I try to had a admin account in local.ini but i am unable (even with sudo). The files are protected (maybe because it is a snap install). So, how to proceed? Thank you. |
I just removed and try it using the terminal: sudo snap install couchdb. Again no problems, but it never asks for a admin password. |
Ok, maybe it's "used" from your previous install... |
I purged previous installations and this a fresh install of Ubuntu. I did try to add a password in sudo nano /var/snap/couchdb/current/etc/local.ini but again i cannot write in this file. |
The snap installs version 3.1.1. Using the repository to install: 1.1.1.1. Enabling the Apache CouchDB package repository¶, is unable to install because there is not version for this ubuntu version. If i try to install the couchdb for focal ubuntu version, it does not work either. |
This is an old version, and it seems the package isn't updated. I don't know about the snap release process, maybe @nickva can help? |
I sort it out. Just in case needs this information:
|
Summary
Cannot install the couchdb in Ubuntu 22.04. I suspect that is because of openssl 3 being the default now,
Desired Behaviour
Install and run immediately in http:https://127.0.0.1:5984
The text was updated successfully, but these errors were encountered: