Large Scale Central

On sign out

Second time I tried to sign out and second time I got this. …

Fatal error: Uncaught exception ‘Zend_Db_Adapter_Mysqli_Exception’ with message ‘User rmccown3_rmccown already has more than ‘max_user_connections’ active connections’ in /home/rmccown3/public_html/application/libraries/Zend/Db/Adapter/Mysqli.php:352 Stack trace: #0 /home/rmccown3/public_html/application/libraries/Zend/Db/Adapter/Abstract.php(448): Zend_Db_Adapter_Mysqli->_connect() #1 /home/rmccown3/public_html/application/modules/Core/Bootstrap.php(112): Zend_Db_Adapter_Abstract->query(‘SET time_zone =…’) #2 /home/rmccown3/public_html/application/libraries/Engine/Application/Bootstrap/Abstract.php(256): Core_Bootstrap->_initDb() #3 /home/rmccown3/public_html/application/libraries/Engine/Application/Bootstrap/Abstract.php(207): Engine_Application_Bootstrap_Abstract->_executeResource(‘db’) #4 /home/rmccown3/public_html/application/libraries/Engine/Application/Bootstrap/Abstract.php(150): Engine_Application_Bootstrap_Abstract->_bootstrap(NULL) #5 /home/rmccown3/public_html/application/libraries/Engine/Application.php(149 in /home/rmccown3/public_html/application/libraries/Zend/Db/Adapter/Mysqli.php on line 352

Anybody else. Any explanation ?

Gee, I don’t sign out. I just close the window.

Those of us who are chat regulars prefer to sign out, if we don’t our name remains on the “who is chatting” list and anyone who stops by may think they are being ignored when in fact the only one there is a computer that wasn’t signed out.

OH Hollywood, At least you did not blow up the site for the rest of us.:stuck_out_tongue:

Our Benevolent Dictator:

I am now getting the same message on log out attempt. Note: attempt. If I kill the browser, next time I open the browser and load up MLS I am still logged in.

I have just acquired an NTY computer, an HP WX9400 workstation. Windows 7 Home Premium SP1 with all the updates except KB3004395. It has installed Internet Explorer 11, but I am using SeaMonkey Version 2.31.

Any ideas, suggested solutions…

Bob C.

Now they start coming out of their corners.:wink:

When in doubt, rip it out, err ah sign out.

Dan Padova said:

When in doubt, rip it out, err ah sign out.

That’s the problem Dan. If this happens, you can’t

Hollywood,

That is why I specified I am having this issue with a NEW computer and setup. I didn’t have the problem with the old computer before the motherboard took a permanent vacation. One used to be able to completely UNINSTALL Internet Explorer, however I don’t believe you can in Windows 7.

Dan,

That is why I am looking to the Big Kahuna for some possible assistance…

That error isnt a browser end issue, but on the server. And, of course, doesnt duplicate here, so its pretty hard to figure out whats going on. I know what the error MEANS,but tracking down the “why” is a bit difficult.

Bob,

Thank you for your efforts on our behalf. I suppose I can stay ‘logged in’ until you figure it out. I guess the folks in chat will have to understand. :slight_smile:

Duplicate post - deleted

Bob (BD) - Do you have a way to run the system as another user? Perhaps there is something in Hollywood or Bob Cope’s user file that the SQL server barfs on. It’s never happened to me, but then again I never log out on purpose. I get bumped out regularly, but that’s no big deal.

John and BD,

I have tried an experiment here, and loaded Opera browser. I am working in that now, have logged in and out several times without issue, on the same computer I am having issues with SeaMonkey. I hope this may help zero in on the solution.

Bob C.

got this also …

We’re sorry!

We are currently experiencing some technical issues. Please try again or report this to your site administrator using the contact form.

Administrator: Please check the error log in your admin panel for more information regarding this error.

Error Code: a54d25

That error code is definitely Barts fault!

Dave, N.B., Marconi said:

got this also …

We’re sorry!

We are currently experiencing some technical issues. Please try again or report this to your site administrator using the contact form.

Administrator: Please check the error log in your admin panel for more information regarding this error.

Error Code: a54d25

I’ve gotten that once or twice myself. I just hit the “Back” button and try again. It’s fine the second try.

Besides that Dave, your not using the correct “contact form”…:wink:

1)Somehow I just knew my computer savvy would come to light from this.

2)So it’s all my fault

  1. I must admit that it did stop doing it, and I figured BD had fixed it on the QT

  2. I hope four lines of post is enough for the police, so I don’t get a ticket.

Nope, don’t think it is fixed. Just opened up LSC in the browser of choice and am still logged in from the other day.