Troubleshooting stuck at logging screen
Troubleshooting stuck at logging screen
Symptom
User enters his/hers login name and password, press the Sign In, but the login screen is stuck on loading.
Logging
To troubleshoot this problem, we would first rely on log files from the /opt/zimbra/log directory. Run "tail -f" for different logs, and reproduce the issue to collect clues as to what the problem might be. The first place we would be looking is in mailbox.log. Then we can check the mysql_error.log, zmmailboxd.out, nginx.access.log, nginx.log, myslow.log, audit.log, httpd_error.log.xxxx-xx-xx logs. After checking these logs, you may have some idea as to what the problem might be and where to check.
Sometimes, we may not see anything in the logs, and then we should relay on different troubleshooting. The below steps are to give you more ideas as to where to check.
Troubleshooting
1. The very first thing to do, even before you try to check the logs, is to change the zimbraPrefMailInitialSearch attribute for the problematic user to the "sent" folder. That will change the default login folder from Inbox, to be the Sent folder.
zmprob ma rambo@domain.com zimbraPrefMailInitialSearch in:sent
Next, try to login with the user. If you can login with AJAX, then when you check the Inbox folder, it will probably show empty, or an error will be produced when you click on the Inbox tab. If the folder is empty, the problem is most likely an email that contains invalid character/formatting.
How to check the emails in the Inbox. Change back the zimbraPrefMailInitialSearch attribute to its original value:
zmprob ma rambo@domain.com zimbraPrefMailInitialSearch in:inbox
Try to login with Ajax, you will get stuck, then click on the link
3. Try checking each tab individually, click on them and see if you will get an error while doing that. Go to the Preferences tab of the user, and click each menu on the left. Sometimes you may have error when you click the Sharing option.
2. Invalid calendar or folder shares
For this point, there is a wiki created here. Follow the wiki to troubleshoot the issue.
3. MySQL issues. Sometimes, this problem can be caused by corrupted mysql index. If you find in the logs that there is a problem with the index, please follow this wiki
4.