Unexpectedly Being Logged Out

**hcdsugar** · 2008-10-20, 01:13 AM

Having a problem where while working will all the sudden be popped back to the login page. When it occurs the following error shows up in the error_log file:

[Sun Oct 19 21:01:16 2008] [error] [client 10.0.14.110] PHP Warning: session_destroy() [<a href='function.session-destroy'>function.session-destroy</a>]: Trying to destroy uninitialized session in /u/apps/sugarcrm-5.1.0a/htdocs/sugarcrm/include/MVC/SugarApplication.php on line 101, referer: http://crm1.hcd.net/sugarcrm/index.p...ities&offset=0

... the issue can be caused at will by going to, for example, either Leads or Opportunities then clicking on a column to change the sort. I will click to sort the column, then click to reverse the sort, then say go into a Lead (or Opportunity), click Return To List then start clicking to sort the column again and it will happen. It is not consistent that it happens after X clicks, but within a minute or so of clicking around I can get it to happen consistently.

I am running under CentOS v5.2 and using the SugarCRM FastStack Version 5.1.0a (Build 4837). The issue occurs in both FireFox and MS IE so it is not browser related (plus, as shown above a PHP error is occurring).

I have tried doing a Quick Repair & Rebuild and have also used the Repair utility to rebuild the php config file - all to no avail.

Any help would be great. Thank you!!

**hcdsugar** · 2008-10-20, 07:58 PM

Update: Went to the Live Demo area on the www.sugarcrm.com website and was able to re-create the problem in the demo site, so that would seem to point to it truly being a bug and not an issue specific to our setup.

**susiewilliams** · 2008-10-20, 09:35 PM

Hi there,

Thanks for finding this bug. I have logged it in our bug tracker (bug number 25607). You can go to the Bug Tracker to see the progress of this issue.

**hcdsugar** · 2008-10-20, 10:04 PM

Many thanks!! ... guess I should have mentioned I had also logged it to the bug tracker after posting this. My apologies for not mentioning. The one I logged to is bug #25576.

**susiewilliams** · 2008-10-20, 11:34 PM

So this bug was reported initially as patch 25421 and it's been fixed in the Venice release (the next patch release, slated for sometime later this month).