Details about this thread
  • State Verified Answer
  • Replies 11 replies
  • Subscribers 313 subscribers
  • Views 6169 views
  • Users 0 members are here
Related content from around SugarClub

VERY frustrating problem...Can't log in and gives me an error which doesn't tell me anything...

Pete Johnstone

This is SugarCRM Enterprise, Version 7.6.2.2 (Build 45)

So this instance all of a sudden won't let anyone log in.  Here is the VERY non-descript/unhelpful error message:

Unable to sync with server.  A request is failing that makes the application unusable.  Please contact technical support.

It runs on Linux (CentOS 6.x) and the database is MySQL, and I have full access to a Linux terminal.  I've restarted MySQL and Apache and the problem continues to persist.

Is there something useful being logged somewhere, and where should I look?

Thanks!

Parents
  • 0

    Hi Pete Johnstone

                                    This issue usually occurs
    1.When you have done an  incorrect customization,it is usually fixed by tracing where the issue has occurred and fixing it.

    You can check the sugarcrm.log file and the apache error logs for checking the errors.

    Also check in the network tab of chrome developer tool to trace which request if failing.

    Take backup of the cache folder and purge the cache.

    Remove your browser cache and reload the page.

    2.Insufficient disk space.

    Please update your status so that we can help you out further.

    HTH

    Regards

    Sidhu

  • 0 in reply to sidhu sidhu

    Thanks everyone who answered...I was able to locate the problem (had to abandon it for a few days to work on more pressing issues), it was a memory allocation error (which I found in the ssl error logs).  I had to increase the memory limit in the php.ini file, which by default was set at 128 MB, I went ahead and doubled that to 256M and everything seems to be working fine again.

    The give away is that I did a tail -f on the log via the console while simultaneously trying to log in and that error kept generating.  Whatever modifications that were added by the employee must've increased memory utilization during login.

Reply
  • 0 in reply to sidhu sidhu

    Thanks everyone who answered...I was able to locate the problem (had to abandon it for a few days to work on more pressing issues), it was a memory allocation error (which I found in the ssl error logs).  I had to increase the memory limit in the php.ini file, which by default was set at 128 MB, I went ahead and doubled that to 256M and everything seems to be working fine again.

    The give away is that I did a tail -f on the log via the console while simultaneously trying to log in and that error kept generating.  Whatever modifications that were added by the employee must've increased memory utilization during login.

Children