-
Notifications
You must be signed in to change notification settings - Fork 34
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
Insufficient TemporaryStore disk space halting FEDORA #401
Comments
@McFateM if you can find this file I can help you get a PR in to lower the temp requirement: |
Yup, that is the thread I found yesterday. Going to have a look in the config for it now. Thanks! |
Well, I couldn't find ANY of the config files mentioned in that thread, or others I followed. But, I did find a lot of conversation from a long time ago suggesting that ActiveMQ has the ability to adjust/reconfigure itself automatically. So, I decided to do some experimentation with my Recognizing that running out of ActiveMQ space is problematic, in the past I have always redirected my
Hoping to gain some insight into this I changed that line to read:
That change eliminated ALL of the ActiveMQ space-related warnings and ERRORs that I was seeing. Yay! But FEDORA is still crashing at the same point in the ISLE spin-up, where I am trying to engage the MySQL container to import a large Drupal database. That makes some sense since I suspect ActiveMQ is involved in messaging FEDORA as MySQL makes progress. Seems reasonable, eh? In any event, I've since turned my attention back to those other, seemingly inconsequential INFO messages that
I'm seeing lots of these and wondering exactly why? So my plan here is to rewind my workflow back to a stable state and repeat my attempt to upgrade from ISLE v1.5.1 to v1.5.2, step-by-step to try and determine where these curious issues are coming from. |
Hi @SummittDweller aka @McFateM aka Mark ;) Would you like to submit a PR to the Fedora image https://github.com/Islandora-Collaboration-Group/isle-fedora with that fix for the next ISLE release? We'd love to give you credit and a big thanks for this! Hope you are well. Cheers |
Issue description
In my local instance of ISLE the FEDORA container frequently crashes with an ERROR like this:
These ERRORs are often accompanied by warnings that don't appear to kill the container, like so:
For an issue, describe steps to reproduce the issue
System setup (OS information, software versions, etc):
Steps:
docker-compose up -d
. The container appears to be OK.docker ps
.What's the expected result?
Seven healthy containers with a new imported Drupal database.
What's the actual result?
In my case, the
isle-fedora-ld
container stops and the logs show the ERROR and WARN messages I've included above.The text was updated successfully, but these errors were encountered: