5.6.0.1 upgrade has slowed site and causes Fatal Error max execution time exceeded

Permalink 1 user found helpful
Hi everyone.

I just upgraded a client's site from 5.5.2.1 to 5.6.0.1, and have updated the few addons to their latest versions as well.

The site has slowed noticeably (pages load in 7 - 18 seconds) and occasionally throws the Fatal Error:

"Maximum execution time of 30 seconds exceeded in /home/nadlca/domains/nadleh.ca/public_html/concrete/libraries/3rdparty/Zend/Cache/Backend/File.php on line 956"

I have also have problems getting into the dashboard I'm assuming because of the slowness.

I have checked the cache settings which are:
- Basic Cache is turned ON
- Full-page caching is ON
- Overrides cache is turned ON
- Full page cache rebuild is AUTO

The company I work for hosts this concrete5 site on our own server. We only have 1 concrete5 site and the other client sites are static. So I don't feel we are a budget host.

ANY insights as to why the site has slowed since the upgrade?

Has anyone else experienced slower page loads after upgrading to 5.6.0.1?

Thanks for any responses.

- Michael -

splashmg
 
hostco replied on at Permalink Reply
hostco
Hello,

Is it possible to provide a link to your site?
splashmg replied on at Permalink Reply
splashmg
Hi Hostco

http://www.nadleh.ca

PLEASE NOTE: I just found a post which refers to Andrew's method of updating the config/site.php with the code:

[define('CACHE_FRONTEND_OPTIONS', serialize(array('automatic_cleaning_factor' => 0)));


I have implemented it and it seems significantly faster.

That being said...
1) is what I've done fine, or is there some new info against it?

2) Can you see anything apparent that I've done wrong? It is my first c5 site.

Thanks much.

- Michael -
splashmg replied on at Permalink Reply
splashmg
Hi again Hostco.
I feel I should include the log reports that occurred just after my upgrade to the latest c5.

I'm doing so because I see there appears to be a permissions issues for each of the exceptions noted.

Even though the upgrade went smoothely, perhaps there's something behind the scenes on the server/permissions that just isn't correct?

--- EXCEPTIONS ---

DATE/TIME: 2:05:03 PM at 9/11/2012
TYPE: exceptions
USER: Guest

Exception Occurred: /home/nadlca/domains/nadleh.ca/public_html/concrete/core/models/permissions.php:71 Unable to get permission key for view_edit_interface (0)

#0 /home/nadlca/domains/nadleh.ca/public_html/concrete/tools/edit_block_popup.php(18): Concrete5_Model_Permissions->__call('canViewEditInte...', Array)
#1 /home/nadlca/domains/nadleh.ca/public_html/concrete/tools/edit_block_popup.php(18): Permissions->canViewEditInterface()
#2 /home/nadlca/domains/nadleh.ca/public_html/concrete/startup/tools.php(29): include('/home/nadlca/do...')
#3 /home/nadlca/domains/nadleh.ca/public_html/concrete/dispatcher.php(122): require('/home/nadlca/do...')
#4 /home/nadlca/domains/nadleh.ca/public_html/index.php(2): require('/home/nadlca/do...')
#5 {main}

---------------------------------

DATE/TIME: 1:41:19 PM at 9/11/2012
TYPE: exceptions
USER: Guest

Exception Occurred: /home/nadlca/domains/nadleh.ca/public_html/concrete/core/models/permissions.php:71 Unable to get permission key for view_edit_interface (0)

#0 /home/nadlca/domains/nadleh.ca/public_html/concrete/tools/edit_block_popup.php(18): Concrete5_Model_Permissions->__call('canViewEditInte...', Array)
#1 /home/nadlca/domains/nadleh.ca/public_html/concrete/tools/edit_block_popup.php(18): Permissions->canViewEditInterface()
#2 /home/nadlca/domains/nadleh.ca/public_html/concrete/startup/tools.php(29): include('/home/nadlca/do...')
#3 /home/nadlca/domains/nadleh.ca/public_html/concrete/dispatcher.php(122): require('/home/nadlca/do...')
#4 /home/nadlca/domains/nadleh.ca/public_html/index.php(2): require('/home/nadlca/do...')
#5 {main}


------------------------------------

DATE/TIME: 1:33:48 PM at 9/11/2012
TYPE: exceptions
USER: Guest

Exception Occurred: /home/nadlca/domains/nadleh.ca/public_html/concrete/core/models/permissions.php:71 Unable to get permission key for view_edit_interface (0)

#0 /home/nadlca/domains/nadleh.ca/public_html/concrete/tools/edit_block_popup.php(18): Concrete5_Model_Permissions->__call('canViewEditInte...', Array)
#1 /home/nadlca/domains/nadleh.ca/public_html/concrete/tools/edit_block_popup.php(18): Permissions->canViewEditInterface()
#2 /home/nadlca/domains/nadleh.ca/public_html/concrete/startup/tools.php(29): include('/home/nadlca/do...')
#3 /home/nadlca/domains/nadleh.ca/public_html/concrete/dispatcher.php(122): require('/home/nadlca/do...')
#4 /home/nadlca/domains/nadleh.ca/public_html/index.php(2): require('/home/nadlca/do...')
#5 {main}


------------------------------------

DATE/TIME: 1:29:17 PM at 9/11/2012
TYPE: exceptions
USER: Guest

Exception Occurred: /home/nadlca/domains/nadleh.ca/public_html/concrete/core/models/permissions.php:71 Unable to get permission key for view_edit_interface (0)

#0 /home/nadlca/domains/nadleh.ca/public_html/concrete/tools/edit_block_popup.php(18): Concrete5_Model_Permissions->__call('canViewEditInte...', Array)
#1 /home/nadlca/domains/nadleh.ca/public_html/concrete/tools/edit_block_popup.php(18): Permissions->canViewEditInterface()
#2 /home/nadlca/domains/nadleh.ca/public_html/concrete/startup/tools.php(29): include('/home/nadlca/do...')
#3 /home/nadlca/domains/nadleh.ca/public_html/concrete/dispatcher.php(122): require('/home/nadlca/do...')
#4 /home/nadlca/domains/nadleh.ca/public_html/index.php(2): require('/home/nadlca/do...')
#5 {main}
hostco replied on at Permalink Reply
hostco
Hi,

Sorry for the delay, I stepped away for lunch.

We do see any errors and the site seems to be loading pretty quickly.

Are you still seeing the issue?
splashmg replied on at Permalink Reply
splashmg
Sorry HOSTCO, do you mean that you 'don't' see any errors?

I have disabled errors from being displayed to site visitors now the site is live. I only noticed the 'exceptions' in the logs in the dashboard.

Other than that, the additioal code to the config/site.php (as shown above) file seems to have really sped things up.

I'm happy now, however I was wondering if the change to the config is just masking an underlying issue with the site, and thought that the logs might be indicating something.
hostco replied on at Permalink Reply
hostco
Sorry, yes I forgot the word not.

We do not see any errors.

Do you have any customized core files located in any of the root directories?
splashmg replied on at Permalink Reply
splashmg
Not that I'm aware of.

I do have some custom templates (outside of the concrete folder of course) that I've used as overrides. Other than that I don't touch anything core related.

The 5.6.0.1 upgrade did place a 'core' folder within the concrete folder. I've never seen that before and figured it was from the upgrade itself.

Could you be a bit more specific as I'm afraid my technical understanding is still quite novice.
hostco replied on at Permalink Reply
hostco
Are the custom templates for core blocks or 3rd party add-ons?
splashmg replied on at Permalink Reply
splashmg
I see what you mean. Both.

For the core blocks I have custom templates to mostly just change what things look like, not to alter functionality:

- autonav: (using Jordan Lev's ' Customizing the AutoNav template')

- image: (created a custom template for a header image, as well as tweaked the thumbnail size for Composer)

- page list: (I created a template for a New (EDIT: News) page list)

- search: (simply a template that comments out a php line that displays the truncated body of the content. Also a custom template for a global search)

- date archive: (can't remember what this custom template does... but I think it was to just modify some text which displays)
Phallanx replied on at Permalink Best Answer Reply
Phallanx
I'm not sure about the errors but it looks like you have a redirect problem which probably isn't helping.

If you look at the page analysis
http://www.webpagetest.org/result/120914_7M_FBP/1/details/...

You will notice that many of your files are listed twice.
All those listed twice are 301 redirects so you have redirects from
http://www.nadleh.ca/themes/nadleh_whuten/css/normalize.css

to
http://nadleh.ca/themes/nadleh_whuten/css/normalize.css


All those being redirected are ones which have relative paths (i.e. "/themes/nadleh_whuten/css/normalize.css"). So it is to do with the way relative URLs are resolved.

Check to see what is in your site.php as the base url and also what is in your .htaccess or httpd.conf (a rewrite rule from http://www.nadleh.ca to nadleh.ca).
splashmg replied on at Permalink Reply
splashmg
I will.

I'll check with our company's server admin regarding this as well.

Thank you.
splashmg replied on at Permalink Reply
splashmg
Hi Phallanx,
There is no BASE URL (edit:) in my site.php file.

I didn't put that in because I read in a few posts (likely by Franz or Andrew) in which c5 says you don't need it and that c5 should be smart enough to know.

I read that early on when I was first building this site (my 1st c5 site)

Should I go in and add it then?
hostco replied on at Permalink Reply
hostco
Definitely add it.
splashmg replied on at Permalink Reply
splashmg
Will do.
splashmg replied on at Permalink Reply
splashmg
Hi HOSTCO
Should I also add the DIR_URL?

So I would then have these 2 additional lines in my config/site.php

define('BASE_URL', 'http://www.nadleh.ca');
define('DIR_REL', '');


... or just the BASE_URL as mentioned?
hostco replied on at Permalink Reply
hostco
Yes add that as well.
splashmg replied on at Permalink Reply
splashmg
THANKS HOSTCO!
The site is running quite fast now.

I appreciate you taking the time to assist a newcomer to c5.

Greatly appreciated and your quick response to this whole post was remarkable.

- Michael -
splashmg replied on at Permalink Reply
splashmg
THANKS!
The redirect issue has been resolved from the tests I've run at webpagetest.org

I appreciate you taking the time to assist.

Really impressed.

- Michael -
hostco replied on at Permalink Reply
hostco
No problem at all.

Lets give a thank you to Phallanx as well.

He took the time to view your source code to see you were loading double CSS and discovered the redirect issue.

Glad all is well.

Jonah
splashmg replied on at Permalink Reply
splashmg
Already ahead-of-ya ;)
splashmg replied on at Permalink Reply
splashmg
Hey Phallanx,

In case my previous 'thank you' from above was placed incorrectly in this post and you haven't been notified...

THANK YOU!

I learned something new today which is much appreciated.
Phallanx replied on at Permalink Reply
Phallanx
No problem.
But are you sure it's fixed? (And don't forget to sort out the two 404 errors)
splashmg replied on at Permalink Reply
splashmg
Hi Phallanx,

I thought it was fixed because I ran a test and didn't see the repeated entries (ie:http://www.nadleh.ca VS nadleh.ca) at webpagetest.org.

Based on your message I guess I'm still missing something though.

- Could you verify if what I've done (added the BASE_URL & DIR_URL) has actually fixed my problem, or if it hasn't yet... what I'll need to do to correct it.

(UPDATE) When I go to webpagetest.org and view the 'Page Speed Optimization' page it tells me there are still redirects on some images. Not sure how to get rid of them.

- How do I sort out the two 404 errors?

- Will I'll need my company's server admin to help?

Thanks Phallanx. As a newcomer to c5, there's things that I just am completely unaware of.

- - Michael -
hostco replied on at Permalink Reply
hostco
The 404s are being caused by a custom template added to your root blocks directory

http://www.nadleh.ca/blocks/flex_slider/css/theme/bg_control_nav.pn...

http://www.nadleh.ca/blocks/flex_slider/css/theme/bg_direction_nav....

Make sure these images exist in this location. If they do not, upload them to this location.

If the images do exist, make sure they have proper permissions.

It is possible that the duplicate content seen from the webpagetest.org test results are being caused by something .htaccess related.

Try deleting the code you have in your .htaccess file and running another test. If you still see duplicate content being loaded you can eliminate this possibility and put the code back in place.
splashmg replied on at Permalink Reply
splashmg
Hi Jonah,

1) .PNGs
I will check out the .pngs and make sure they are there, or if their permissions need modification.

If the permissions need modifying, should they be set to 777?

2) .htaccess
I have pretty URLs enabled. Won't deleting the .htaccess code conflict with the pretty URLs?

Or should I disable Pretty URLs first and then remove the code in the .htaccess file?
hostco replied on at Permalink Reply
hostco
Yes go ahead and disable pretty urls.

This is just for a test so you can turn them right back on.

777 or 755 on the images would be fine.
splashmg replied on at Permalink Reply
splashmg
Hi Jonah,

1) PNG Issue
- fixed

------------------

2) Redirects
The redirects are not fixed and they appear to be only on the images used within my custom theme...

http://www.webpagetest.org/result/120917_SS_f6dfb87ca08d8cac1ad7975...

*click 'minimize redirects' to expand and view the redirects

I tried disabling the Pretty URLs and removed the code from the .htaccess file and ran another test a webpagetest.org. The redirects are still appearing for the images contained within my custom theme... either from within the css (calling a background image), or outside the css (such as the logo)

I'm wondering if it has something to do with the httpd.conf that Phallanx mentioned above. I'm not sure what the httpd.conf is or how to check/modify it.

(EDIT) Perhaps my company's server admin could check it out?
hostco replied on at Permalink Reply
hostco
Hello,

This issue is a server config issue and not concrete5.

http://www.nadleh.ca/themes/nadleh_whuten/css/images/bg_homepage.jp...

As you can see the direct link to this image gives this error

"The page isn't redirecting properly


Firefox has detected that the server is redirecting the request for this address in a way that will never complete."


http://nadleh.ca/themes/nadleh_whuten/images/bg_homepage.jpg...

The direct link with no www. will load without issue.

Concrete5 configured to use www. but your domain and server is not configured to use it.

It would seem the easiest thing to do at this point is to remove www. from your base url in /config/site.php and run the test again to see if it clears up the problem.
splashmg replied on at Permalink Reply
splashmg
Hi Jonah,
Changing the BASE_URL seems to have eliminated the redirects on the images.

Technically, should I have the server admin who works for the company I work for, correct this at the server level... or would it be a massive job?

He actually did the initial install of the concrete5 site on the server, and then I went in and created what you see now. Perhaps when he set up the site he specified nadleh.ca instead ofhttp://www.nadleh.ca?

I guess I want to ensure that the server is configured properly as we'll be doing more c5 sites in the future.


Please advise.

- Michael -
hostco replied on at Permalink Reply
hostco
Hello Michael,

It sounds like when he set up the site he did not use www.

Allowing both to resolve would not be that big of a job, however you should really choose one and use it.

If this has solved the redirect issue, you can consider the issue resolved.

Thanks,
Jonah
splashmg replied on at Permalink Reply
splashmg
I've contacted the server admin with your info. Hopefully this will do the trick!

Thanks Jonah.
splashmg replied on at Permalink Reply
splashmg
Hi Jonah,
Our server admin checked the setup and said it doesn't look like anything is incorrect. Here's a snippet of his response:

"This is what the relevant nadleh apache conf file looks like:
- ServerNamehttp://www.nadleh.ca
- ServerAliashttp://www.nadleh.ca nadleh.ca

So I think what your asking is already set there. I suppose when C5 was installed we might have used nadleh.ca, so maybe there's some
configuration somewhere that needs to be tweaked withing C5? Have you
tried re-installing the theme since this was first setup?"

I'm not sure as to what to do or where to look now. I realize this is taking up your time and we must move on at some point.

So, if there is anything else you can think of, please advise. Otherwise, thanks very much for your help.

(ADDITIONAL - IMPORTANT)
I looked at the File Storage locations in the dashboard and this is what I found:
/home/nadlca/domains/nadleh.ca/public_html/files

Could this have something to do with it???

- Michael -
hostco replied on at Permalink Reply
hostco
Hello,

Are you wanting to use www. ?

It appears that google has indexed mostly www. but its hard to say if that is from a recent index.

I would not say there is anything wrong with your server at all, it just needs to be configured the way you would like it to work.

If you want to use www. hard code the links in your CSS to use www.

The problem with that is the images will not resolve using www.

You need to ask you server admin why your images will not resolve when using www. This has nothing to do with concrete5 or your concrete5 theme.

When we first took a look if you tried to use www. when directly visiting an image url we would get an error message. Now you can type in www. but it automatically forwards to

http://nadleh.ca/themes/nadleh_whuten/images/bg_homepage.jpg...

Also ask them what they changed to make that happen.

Jonah
splashmg replied on at Permalink Reply
splashmg
Thanks Jonah,
I am wanting to use www.

I don't believe the server admin changed anything from his correspondence with me yesterday. He simply checked the settings and said that perhaps when he setup the c5 site, he may have done it without the www. I will pass this along to him though.

All I did was try your fix in the config/site.php by changing the BASE_URL tohttp://nadleh.ca. I then changed it back to include the www.

q1) I'm wondering where you detected the image error that threw the error page. I wasn't able to discover that. I looked through webpagetest.org and couldn't find that particular error there.

q2) I noticed that in the dashboard for 'File Storage locations' it is set to /home/nadlca/domains/nadleh.ca/public_html/files

Should I change this or leave that alone?
hostco replied on at Permalink Reply
hostco
/home/nadlca/domains/nadleh.ca/public_html/files

This could have something to do with it.

Try adding www. and clicking save
splashmg replied on at Permalink Reply
splashmg
Nope,

It breaks some of the images on the site such as the homepage slideshow, and the sub page's header images... but it doesn't affect the themes images (ie:backgrounds, logo), the 4 feature boxes on the homepage or the images within the content blocks.

(EDIT)
When I look at the File Manager for a header image that is broken... I see that it says the default file is: (/home/nadlca/domains/nadleh.ca/public_html/files)
hostco replied on at Permalink Reply
hostco
Ask your server admin why your images will not resolve to www.

http://nadleh.ca/themes/nadleh_whuten/images/bg_homepage.jpg...

Tell him this has nothing to do with concrete5 or your concrete5 theme.

Jonah
splashmg replied on at Permalink Reply
splashmg
I will do that right now.
Phallanx replied on at Permalink Reply
Phallanx
Difficult to say what is going on here, but all the files that are being redirected are Theme files (and only theme files). All concrete5 core files or assets are not being redirected; only those that reside in the theme folder.
splashmg replied on at Permalink Reply
splashmg
Hi Phallanx,
I agree.

In my theme, I'm calling the css this way:
<link rel="stylesheet" href="<?php  echo $this->getThemePath(); ?>/css/normalize.css">
 <link rel="stylesheet" href="<?php  echo $this->getThemePath(); ?>/css/main.css">
<link rel="stylesheet" href="<?php  echo $this->getThemePath(); ?>/css/fonts.css">


I'm calling the images (ie: logo) this way:
<img src="<?php  echo $this->getThemePath(); ?>/images/logo_icon2.png" alt="Nadleh Whut'en First Nation">


*And within the CSS I'm calling background images this way:
background:url(../images/bg_header.jpg) top center repeat-y;


*Within the css I tried removing the ../ (on my local test site - WAMP on Windows 7) and the background image disappeared... so I left it as indicated above.
Phallanx replied on at Permalink Reply
Phallanx
OK.
Here's a question for your IT guru.

If I manually type into the address bar of my browser:
www.nadleh.ca/concrete/css/ccm.base.css

I get the contents of ccm.base.css at that that location (the address in my address bar remains the same).

If I manually type into the address bar of my browser
www.nadleh.ca/themes/nadleh_whuten/css/normalize.css

I get redirected to
nadleh.ca/themes/nadleh_whuten/css/normalize.css

and then get the contents of normalize.css (the address does not remain the same).

Why does one get redirected but the other not?
hostco replied on at Permalink Reply
hostco
The issue has been resolved.

http://www.nadleh.ca/themes/nadleh_whuten/images/bg_main.jpg...

You have a .htaccess file located in your theme directory that was causing the issue.

/public_html/themes/nadleh_whuten/.htaccess

I renamed it to .htaccess- and the problem went away.

You can feel free to delete this file as it is not needed.
Phallanx replied on at Permalink Reply
Phallanx
Let me guess.
it had
RewriteCond %{HTTP_HOST} ^www\.nadleh.ca\.com$ [NC]
RewriteRule ^(.*)$ http://nadleh.ca.com/$1 [R=301,L]


Well done Hostco.
hostco replied on at Permalink Reply
hostco
Hi Phallanx,

It actually had the entire contents of the php.ini file. This is not recommended or safe.

php.ini can be modified using .htaccess but not in the location this file was.

Small mods, such as adjusting memory, are okay but not the entire php.ini file.

Thank you,
Jonah
splashmg replied on at Permalink Reply
splashmg
This was completely unintentional. YIKES!
splashmg replied on at Permalink Reply
splashmg
Thanks for your assistance as well Phallanx!

You and HOSTCO have been great.

- Michael -
splashmg replied on at Permalink Reply
splashmg
OH MAN.

Thanks Jonah, I wouldn't have picked up on that... but now that you've found it, it totally makes sense!

Something I will never forget.

Thanks again.

sincerely,
- Michael (and I'm sure our server admin as well!) -