Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Installation: first "dataverseAdmin" user and root dataverse can't be created #3894

Closed
pdurbin opened this issue Jun 13, 2017 · 3 comments
Closed

Installation: first "dataverseAdmin" user and root dataverse can't be created #3894

pdurbin opened this issue Jun 13, 2017 · 3 comments
Assignees
@kcondon
Labels
Feature: Installer Type: Bug a defect
Milestone
4.7 - Customizati...

Comments

@pdurbin
Copy link
Member

pdurbin commented Jun 13, 2017

As of 02e5545 on the develop branch, the first "dataverseAdmin" user can't be created which means that the root dataverse can't be created. This affects new installations of Dataverse.
@pdurbin pdurbin self-assigned this Jun 13, 2017
@bsilverstein95 bsilverstein95 self-assigned this Jun 13, 2017
@bsilverstein95
Copy link
Contributor

bsilverstein95 commented Jun 13, 2017 •
edited
Loading

After a reinstall and redeploy with a brand new database, I checked the authenticateduser table in postgres and I do have a dataverseAdmin user-- but when I try and run the app it can't seem to find any root dataverse.

The user exists in my database, but the root dataverse does not. Is there a way to manually create it without going through the application? I get nothing but 500 errors when I try localhost:8080.

edit: in the glassfish logs, this is the first error that sets in motion some other ones that involve trying to find the root dataverse:

Warning: A system exception occurred during an invocation on EJB DataverseServiceBean, method: public edu.harvard.iq.dataverse.Dataverse edu.harvard.iq.dataverse.DataverseServiceBean.findRootDataverse()

pdurbin added a commit that referenced this issue Jun 13, 2017
@pdurbin
don't send notification when creating dataverseAdmin user #3894
f800e2d 
The dataverseAdmin user creates the root dataverse. This user is created
by the installer.

Also included is a null check when creating a dataverse fails.
@pdurbin pdurbin mentioned this issue Jun 13, 2017
Merged
5 tasks
@pdurbin
Copy link
Member Author

pdurbin commented Jun 13, 2017

I just created pull request #3895 and am moving this to code review at https://waffle.io/IQSS/dataverse

kcondon added a commit that referenced this issue Jun 13, 2017
@kcondon
Merge pull request #3895 from IQSS/3894-setup
e28b927 
don't send notification when creating dataverseAdmin user #3894
@pdurbin
Copy link
Member Author

pdurbin commented Jun 13, 2017

@michbarsinai took a look and said the fix looked ok.

@kcondon kcondon self-assigned this Jun 13, 2017
@kcondon kcondon closed this as completed Jun 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kcondon kcondon

Labels
Feature: Installer Type: Bug a defect
Projects
None yet
Milestone
4.7 - Customization and Community Rel...
Development

No branches or pull requests
3 participants
@pdurbin @kcondon @bsilverstein95