500 - Internal Error

scorpiotiger — Thu, 26 May 2016 09:18:02 GMT

After 8 months, Alfresco has started giving an error when navigating to the user dashboard. For users not logged in, they are unable to do so at the login page. I'm constantly logged in, so I don't get the login screen, but the dashboard page.Every evening we have a script that stops Alfresco and pe

Re: 500 - Internal Error

steven_okennedy — Thu, 26 May 2016 16:57:51 GMT

Hi ScorpioTiger,

From the logs you've included, it appears as though Share is having trouble determining the status of the IMAP subsystem but the reason behind it is not clear. The error is coming as a result of the inclusion of the my-sites dashlet on a user's dashboard, so users who don't use this dashlet or who have removed it from their personal dashboard won't be affected by the problem.

This share dashlet makes a remote call to alfresco to the url http://<alfresco-server>/alfresco/service/imap/servstatus to determine whether or not to certain elements of the UI should be rendered. Once it gets the value of the imap server status, it will store it and won't make any further calls. Generally this means that it should only make the call once after each server restart, but in your case the call seems to be failing and in that case, every subsequent rendering of the my-sites dashlet will continue to try and call the server (and potentially keep failing). The share code doesn't deal gracefully with the fact that the imap server status isn't reachable and it causes the whole dashboard load to fail.

In order to get to the bottom of this, you need to identify what's going wrong with the call to alfresco/service/imap/servstatus. For some reason this request is sending a 404 response back, indicating that the webscript itself can't be found. Check in your alfresco.log for any issues during server startup as well as in the tomcat/logs/localhost_access_log<date>.txt and look to identify when calls to this url fail (404 response) and when they succeed (200 response).

If you can isolate a time when users are encountering the problem, try calling http://<alfresco-server>/alfresco/service/imap/servstatus manually through a browser and verify that the script is viewed by the system as deployed using http://<alfresco-server>/alfresco/service/script/org/alfresco/repository/imap/imap-enabled.get to see the status of the webscript itself.

It's worth noting that you could see this problem whether or not IMAP is enabled, as the check will be done by share regardless - so just disabling IMAP if you don't want it is probably not an option.

Are you running many custom/3rd party extensions?

Regards

Steven

Re: 500 - Internal Error

scorpiotiger — Fri, 27 May 2016 05:53:07 GMT

Thanks for your comprehensive response. To be honest, Alfresco was deployed to meet an urgent need for document mangement and sharing. I'm sure that we're not getting the most out of it as we just don't have enough knowledge of its capability and how to implement it. As such we've not installed any extensions or done any configuration beyond Nginx for SSL and reverse proxy, and of course our backup script.

It just seems strange that this problem has suddenly appeared after all these months, and that it's intermittent. I'll try what you've suggested and post again if I can get to the bottom of it.

topic Re: 500 - Internal Error in Alfresco Archive

500 - Internal Error

Re: 500 - Internal Error

Re: 500 - Internal Error