-
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
Snap 3.3.3 breaks previous version (3.1.1) functionality #4945
Comments
Hi,
The cookie value with this message is "monster", which isn't allowed anymore. Can you look into your |
Hey, |
The snap hook should be found here.
You can try this to see if the script is working for you
But you can also edit the file by hand and restart the snap.
|
Hey,
That might be the reason why 'sudo snap set' does not work. Manual setting:
also does not work. Here the log
Thanks for your help! |
For additional information
|
Okay, those hooks are missing. You'll need to change by hand for the moment. cd /var/snap/couchdb/current/etc edit local.ini Ensure that you have this stanza
then snap restart and check the logs again. |
That fixes the issue for me
Thank you! How will this issue continue: will there be a fix to do things automatically or should the user do things manually? |
Good. The next snap revision will include the hooks. |
Great |
Recreated and uploaded the snap packages! |
Thanks! The new snap works like a charm. |
Snap automatically pushes new versions to its users, after having run with couchdb 3.1.1 successfully; the new 3.3.3 snap that was uploaded on Jan 2nd breaks because of setcookie=monsters
Description
(I know I can revert snaps but that does not fix the issue going forward and for new installations)
Linux/Ubuntu: single node installation:
If one installed 3.1.1 couchdb via snap, the installation was "sudo snap set couchdb admin={password}". After the new 3.3.3 version was pushed to the snap server, the new versions are automatically installed on the users computers. However, with 3.3.3 a cookie is required (installation documentation: "sudo snap set couchdb admin={password} setcookie={cookie}"), since the old configuration does not have a cookie, couchdb stops with "Monster detected ohno!, aborting startup."
Even if I use the new install command "sudo snap set couchdb admin=[your-password] setcookie=[your-cookie]" the installation does not succeed, as I get
"""
error: cannot perform the following tasks:
"""
Also snap set setcookie does not succeed.
Therefore, I went into /var/snap/couchdb/current/etc/vm.args and add a random cookie there. Still no success:
as the initialize_nodelist(line 110) fails to initialize.
Steps to Reproduce
sudo snap set couchdb admin=[your-password] setcookie=[your-cookie]
Expected Behaviour
ability to load http:https://127.0.0.1:5984/_utils/ or curl http:https://127.0.0.1:5984
Your Environment
Additional Context
The text was updated successfully, but these errors were encountered: