ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

An Error Was Encountered on EE 2.5.2 *without* MSM

August 22, 2012 12:12pm

Subscribe [2]
  • #1 / Aug 22, 2012 12:12pm

    teixido

    21 posts

    This question may be related to a resolved thread.

    Not sure what should I do. I found the link above but they all refer to an EE installation WITH MSM in it. Mine does not have MSM so I’m not sure if I should apply the fix. Help?

  • #2 / Aug 23, 2012 10:35am

    Dan Decker

    7338 posts

    Hi teixido,

    Thanks for posting to the forums!

    I’m afraid you haven’t given us much to go on. I really want to help, but I need a clear and thorough explanation of your problem. Be sure to include any errors you are seeing. What action you’ve taken, what you expected to happen and what happened instead.

    I look forward to your reply!

    ~

  • #3 / Aug 24, 2012 9:44am

    teixido

    21 posts

    Hello Dan, sorry for the hiatus, I’ve been putting out fires everywhere with this thing.

    Ok so, I did check the file, the only difference I found inside the huge string was my avatar directory didn’t have the right path. I corrected it, re serialized and replace the string, YET I’M STILL having those issues. Should I perform the fix suggested here: http://ellislab.com/forums/viewthread/218258/ even though I do not have MSM installed?

  • #4 / Aug 24, 2012 6:02pm

    Dan Decker

    7338 posts

    Sure thing! Give it a try.

    The fix wasn’t specific to MSM, so it may help you as well.

    Make a backup copy of the file before changing it.

    Let us know how it goes!

  • #5 / Aug 27, 2012 9:29am

    teixido

    21 posts

    Just to be very clear on this one, this is what my mysql_driver.php file looks like. I don’t see the same lines as the one on the related bug. Would you mind telling which of these should I comment?

    UPDATE: I just PM’ed @khronos the guy who posted the bug in the first place and according to him this bug was already fixed so it looks like my file already had the fix in it.

    Words are not enough to describe how confused I am right now. Any more ideas on what I should try? This is a high profile website, a local newspaper site with over 300K visits a day which means I get at least 5~10 emails a day from angry readers. Please help!

  • #6 / Aug 27, 2012 10:35am

    khronos

    19 posts

    Please provide the specific error(s) you are getting and the steps you take to reproduce this error. Provide server errors and EE errors if possible.

    Thanks.

  • #7 / Aug 27, 2012 10:50am

    teixido

    21 posts

    The hiccups are very weird and I cannot seem to reproduce it. Every X amount of hits both both the front-end and the CP would throw a green screen (attached) with nothing but a “An Error Was Encountered” message.

    If you hit refresh, the error goes away and you’re able to continue browsing the page/cp.

    Couple thoughts I wanted to share here:

    * I already told you guys this is a high traffic website. Could this error be evoked due to a congestion with the DB? The server stats are telling me otherwise (plenty of RAM and MYSQL connections available)
    * Could it be due to a complex DB password? I read it here.

    Where should I start looking for errors? I have mysql logging disabled due to performance but if you think I should give it a look I’ll put it back.

    thanks

  • #8 / Aug 27, 2012 11:06am

    khronos

    19 posts

    Starting with what you know, have you changed the database password to something short and sweet. Not that you want to keep it at that, but, this will help eliminate an unknown.

    - Do you have debugging in EE turned on to see if there are additional errors?
    - Are there any errors in the MySQL, PHP or Apache logs on the server?
    - Do specific pages produce the error, or does it just appear randomly?

    You mention you have MySQL logging disabled due to performance. Are you experience performance issues with MySQL logging turned on? If so, I would suggest that perhaps your server isn’t keeping up with your demands. Yes, MySQL will take a performance hit with logging on, but this should not affect regular server operation.

    Turn on MySQL logging until the error happens a couple of times, and then you could turn it back off. This will at least let you see if MySQL is spouting errors.

  • #9 / Aug 27, 2012 11:16am

    teixido

    21 posts

    K, that’s a great start khronos.

    * I will change the password to something short and no weird characters.
    * I do have EE debugging enabled, I don’t see any errors and when I do get the weird green page I don’t see any debugging at all, just the blank screen.
    * I will turn on logging and check for errors, as for PHP/Apache, just a bunch of non-existent images, favicon.ico and such, nothing major at least.
    * No specific pages, any page whether it’s the front-end or the CP.

    As for your specific question in regards to the performance, no, the server is doing great actually, I just didn’t turn MYSQL logging on because of how the very my.cnf advices you not to given the performance issues but I’ll give it a go and let you know.

  • #10 / Aug 27, 2012 11:19am

    khronos

    19 posts

    * I do have EE debugging enabled, I don’t see any errors and when I do get the weird green page I don’t see any debugging at all, just the blank screen.

    Blank screen. Just white no error message? If so perhaps a memory issue in PHP, or your server could be segfaulting, which will introduce incredible randomness for you to figure out.

  • #11 / Aug 27, 2012 11:42am

    teixido

    21 posts

    Blank Screen = the green screen I uploaded with the error message. Sorry, my bad.

  • #12 / Aug 27, 2012 3:05pm

    Kevin Smith

    4784 posts

    Thanks for the excellent troubleshooting advice, khronos!

    teixido, given the error you’re receiving AND the fact that it’s intermittent, I would seriously suspect that EE is having trouble connecting to the database (those times when the error appears). An application like EE would typically see this when the database has locked up or if there are not enough connections available. The steps khronos suggested are exactly what I would suggest here, too. Let us know what you find after working with your host to gather this information. That will be super helpful in determine how to resolve this.

  • #13 / Aug 27, 2012 3:19pm

    teixido

    21 posts

    Quick question Kevin, while I gather enough info to come back to this post, could this be due to the fact to locked tables on the DB? Cause I’m not sure if this would tell you something:

    +-----------------------+----------+
    | Variable_name         | Value    |
    +-----------------------+----------+
    | Table_locks_immediate | 15194626 |
    | Table_locks_waited    | 1        |
    +-----------------------+----------+
  • #14 / Aug 27, 2012 3:37pm

    Kevin Smith

    4784 posts

    That doesn’t necessary throw up any warning flags, no.

  • #15 / Sep 06, 2012 7:42pm

    teixido

    21 posts

    Ok guys, I’d like to shed some more light after a few days of debugging, moving stuff from the server, changing servers, etc.

    I managed to recreate the error on purpose and yes, it was related to a performance issue, in fact, it might just be as simple as the amount of max user connections settings in my.cnf

    I’ll increase it from 8 to at least 4 times as much and see how that goes.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases