Unstable website.

Permalink
I've just finished to publish my website on Online.net.

Solved numerous problems (Directory www and file rights to 755, config/site.php and file storage correctly configured, folder /tmp rights sets to 777) and now we can see something (almost) fine.

Does anyone know why these message appear on my website randomly ?
Your surely can get one onhttp://www.communeetmoi.fr (I'm french).

Warning: require_once(/flex/domain/communeetmoi.fr/site/www/concrete/helpers/security.php): failed to open stream: Input/output error in /flex/domain/communeetmoi.fr/site/www/concrete/core/libraries/loader.php on line 297 Fatal error: require_once(): Failed opening required '/flex/domain/communeetmoi.fr/site/www/concrete/helpers/security.php' (include_path='/flex/domain/communeetmoi.fr/site/www/libraries/3rdparty:/flex/domain/communeetmoi.fr/site/www/concrete/libraries/3rdparty:.:/usr/share/php:/usr/share/pear') in /flex/domain/communeetmoi.fr/site/www/concrete/core/libraries/loader.php on line 297

Warning: require_once(/flex/domain/communeetmoi.fr/site/www/concrete/libraries/events.php): failed to open stream: Input/output error in /flex/domain/communeetmoi.fr/site/www/concrete/core/libraries/loader.php on line 30 Fatal error: require_once(): Failed opening required '/flex/domain/communeetmoi.fr/site/www/concrete/libraries/events.php' (include_path='/flex/domain/communeetmoi.fr/site/www/libraries/3rdparty:/flex/domain/communeetmoi.fr/site/www/concrete/libraries/3rdparty:.:/usr/share/php:/usr/share/pear') in /flex/domain/communeetmoi.fr/site/www/concrete/core/libraries/loader.php on line 30

Warning: require_once(/flex/domain/communeetmoi.fr/site/www/concrete/helpers/text.php): failed to open stream: Input/output error in /flex/domain/communeetmoi.fr/site/www/concrete/core/libraries/loader.php on line 297 Fatal error: require_once(): Failed opening required '/flex/domain/communeetmoi.fr/site/www/concrete/helpers/text.php' (include_path='/flex/domain/communeetmoi.fr/site/www/libraries/3rdparty:/flex/domain/communeetmoi.fr/site/www/concrete/libraries/3rdparty:.:/usr/share/php:/usr/share/pear') in /flex/domain/communeetmoi.fr/site/www/concrete/core/libraries/loader.php on line 297

Sometimes I also have a "gateway time out" page, is it a hoster problem, a configuration problem or a concrete5 problem ?

When I use the dashboard, I have frequently crash and editing page is difficult (I must retry a lot of times).

Clearing cache seems to be the worst solution. When I do this I must review all the page one by one to make sure the website appear correctly.

Does anyone has an idea to assist me ?

 
JohntheFish replied on at Permalink Reply
JohntheFish
I just got a few good pages and then when looking at recommendations got:

Syntax error in file: /flex/domain/communeetmoi.fr/site/www/concrete/libraries/3rdparty/adodb/drivers/adodb-mysqlt.inc.php

The link to recommendations from the autonav is
http://www.communeetmoi.fr/espace-public/recommandations/... (looks good)

For a syntax error to pop up in a well established library file that is used throughout c5, I suspect something in the environment. Perhaps the php version.
santeroc replied on at Permalink Reply
Thank you for your attention,

The php version is 5.4.6-1.

You could see my phpinfo at this URL if it could help you to understand the crash :

http://www.communeetmoi.fr/phpinfo.php...
nazweb replied on at Permalink Reply
Gateway timeouts usually mean that some server in the path to your webserver (probably a proxy) decided that things were taking too long and closed the connection. It probably happens regularly after 30s, 45s or 60s.

Concrete5 is extremely flexible, but it thrashes the database. A couple of my customer-facing pages do upwards of 300 queries if nothing is cached. I control my environment, so the network cost is very low for me, but let's look at how that could cripple your website.

300 queries * 50 millisecond round-trip database response time = 15 seconds just sending and receiving data, not counting any php processing time, i/o, query time, etc...

The fix is to enable caching. Go to /dashboard/system/optimization/cache/ and set block cache to on, overrides cache to on, full page caching to on, and expire pages from cache to something that makes sense to you. I have it at 15 minutes, but a lot of people use an hour, 6 hours, 24 hours, whatever.

This isn't a silver bullet, caching in itself is a complex topic and requires a lot of forethought to use properly, but it's absolutely necessary to make Concrete5 performant. Good luck!