-
Notifications
You must be signed in to change notification settings - Fork 488
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
Document the EJB timer issue workaround in the admin guide #3669
Comments
@shlake thanks for opening this issue and for all the chatter in http://irclog.iq.harvard.edu/dataverse/2017-03-06 ! This issue is related to #3336 and the task should be to document these steps, especially the bit about the |
Since no one objected on slack - I went ahead and merged in Pete's PR with the sample cleanup script. This way I'll add a doc section that will have a link to it. |
@landreev I'm glad you went ahead and merged #3670 but I wonder if we should |
Pete put the script there because he meant it to be an example. Something that they can copy and paste and use as the base of their own script that will actually work on their system. I support that. It's not a ready-to-run script; unlike, say, the scripts that come with the installer. It really is an example; with absolutely no promise that it will work as is. (mostly because of how it relies on su postgres to run a psql command) |
not sure why this was already in code review... but I've checked in the doc, so it should go into review now. |
PR: #3674 |
@landreev pull request #3674 looks great. I made a few minor tweaks in 4a0a7e2. Thanks for the script @pameyer ! I just moved this issue to QA in https://waffle.io/IQSS/dataverse |
@pdurbin - if there's a better place for example utility scripts to go, please feel free to move it there. |
@pameyer meh, let's wait until we create an rpm or a deb of Dataverse scripts and such. Not that we're working on that. 😄 |
Dataverse 4.5.1:
After yum update within OS version, part of quarterly patching, On deploy of 4.5.1 war file got the error:
remote failure: Error occurred during deployment: Exception while loading the app : EJB Timer Service is not available. Please see server.log for more details.
dataverse would not deploy/start
Fix was as follows:
The text was updated successfully, but these errors were encountered: