-
Notifications
You must be signed in to change notification settings - Fork 192
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
quicksetup fails without sudo #1382
Comments
Also, @yakutovicha : what would be the correct approach to create a new DB inside the jupyter software stack? I guess there one does not need sudo as the DB is run as the user? |
You are sure that sudo is not required in this case?
By fallback you mean try to use psql without sudo first? Or do you mean
trying to use `su root -c` instead?
Or just exit gracefully if su rights are required but sudo is not available?
…On Fri, Apr 6, 2018, 10:59 Giovanni Pizzi ***@***.***> wrote:
Assigned #1382 <#1382> to
@DropD <https://github.com/DropD>.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#1382 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABMqBPFjFB2xzJDwLYi5UlK5Pv3dWEjtks5tly5bgaJpZM4TJuM5>
.
|
So, I think that in the "worst" case, one would try to exit gracefully with a message. I think sudo should not be required on jupyter because the DB is installed and runs with the privileges of the current user, and the DB files live in the home. @yakutovicha might confirm, but probably it's easier if you try it directly in your jupyter.materialscloud.org account. Ideally, it would be great if quicksetup works smoothly (and without user interactiveness) also in dev-jupyter; I imagine is possible. |
Also, as a note, running the tests in a ubuntu environment without sudo fails with:
|
Moreover, note that some of the errors are due to the fact that |
Looked at this issue on On
I.e. quicksetup should determine that it can connect via psycopg. The reason it failed to connect via psycopg is, very likely, that the host was not set to localhost by default:
This is already fixed in But not in 0.12 I.e. one should simply backport the postgres improvements to |
Fixed for |
On dev-jupyter.materialscloud.org, when running the import-export demo from the aiida_demos repository (AiiDA tutorials app), I get this error:
I think that there should be some fallback and not a "crash".
This is also needed for the demos. @DropD do you think it's something easy/quick to fix?
The text was updated successfully, but these errors were encountered: