-
Notifications
You must be signed in to change notification settings - Fork 492
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
Deployment fails with 5.7 (5.4 works just fine) #8208
Comments
@sergejzr Hello, have you tried giving it |
Just tried both, without config file as well as with --config_file=config_file |
thanks, @pdurbin for the ticket reference. I noticed, our payara was 2020, I will update payara and report. |
The erros is gone, but other another one occured: ` ` |
Huh, could it be a permission issue? I'm seeing this: Caused by: com.sun.messaging.jmq.jmsserver.util.BrokerException: Authentication failed for username guest in service jmsdirect: javax.security.auth.login.LoginException: [B3052]: Failed to read password file: /usr/local/payara5/glassfish/domains/domain1/imq/instances/imqbroker/etc/passwd |
Sorry, there were probably some configuration issues. After a complete re-install on a fresh server, the problem is gone. Overall - updating to payara 5.2021.1 solved the issue. I guess it can be closed now. Thank you very much again! |
@sergejzr - Great to hear! Thanks @pdurbin and @donsizemore for the responses! |
What steps does it take to reproduce the issue?
With a fresh installation of v5.7
Which page(s) does it occurs on?
What happens?
Following error when deploying:
$ python install.py config_file
The server log reports:
To whom does it occur (all users, curators, superusers)?
All
What did you expect to happen?
The same as with the version 5.4 - the deployment should happen without any problem
Which version of Dataverse are you using?
The error occurs in 5.7
5.4 works just fine
Any related open or closed issues to this bug report?
Screenshots:
No matter the issue, screenshots are always welcome.
To add a screenshot, please use one of the following formats and/or methods described here:
The text was updated successfully, but these errors were encountered: