To whom it may concern, I hope this is the right mailing list to post this question to.
We have recently installed DSpace 5 xmlui on a Redhat 6.6 Server, and are experiencing persisent 503 Service Temporarily Unavailable errors from DSpace. While contact a url outside of DSpace returns fine, contacting the url /xmlui will work immediately after a tomcat7 restart but after some time passes (I have witnessed it after an hour passed between tomcat7 restarts) it will revert to the 503 Service Temporarily Unavailable errors. This server is not yet in production, so any traffic is from one of three workstations) all on our network, and the logs don't show anything suspicious or any access that I can see is unusual. though the dspace logs shows a lot of most likely tomcat7 restart related configuration checking. In fact, it just happened this morning: first thing in the morning I tried to load the base dspace url and got a 503 Service Temporarily Unavailable Error. After a restart, it did it again but after three tries it returned the page correctly. Things seem to be working correctly now, and I can browse and update the site, but I am assuming that like the past few days this is a temporary situation before it happens again. Does DSpace itself do a lot of traffic and therefore the servers need to have extra capacity? Could I have something misconfigured somewhere that's causing this? I am lost. I hope someone here can shed some light. With warm regards, Tyler Danstrom Programmer/Analyst, University of Chicago Library
------------------------------------------------------------------------------
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
