Blank page help. Prestashop 1.6

[drowned]

Hello, yesterday my site crashed.

I've now a blank page, and it's impossible to see why.

 

As i read in this forum, i've changed the defines.inc.php to see the errors. But the blank page is still here. Anyone can help me ? Many Thanks

/* Debug only */
define('_PS_MODE_DEV_', true);
/* Compatibility warning */
define('_PS_DISPLAY_COMPATIBILITY_WARNING_', true);
if (_PS_MODE_DEV_)
{
    @ini_set('display_errors', 'on');
    @error_reporting(E_ALL | E_STRICT);
    define('_PS_DEBUG_SQL_', true);
}
else
{
    @ini_set('display_errors', 'off');
    define('_PS_DEBUG_SQL_', false);
}

[vekia]

where you've got blank page? back office ? front office?

[drowned]

Back office and front office :

http://www.boutique-triathlon.fr/

[vekia]

strange

so if you don't see errors even with error reporting turned on, i have to ask about access to server log files.

have you got an access to php error log file? or apache error log file?

[drowned]

I went to my private sql space (OVH) and i saw a warning message. memory exceed : 1860K / 128 M

I've an access to Logs MySQL (mysql.err)

Version: '5.1.31' socket: '/bdd/mysql.sock' port: 3306 MySQL Community Server (GPL)
140406 16:52:51 [Note] /opt/mysql/mysql/bin/mysqld: ready for connections.
140406 16:52:51 [Note] Event Scheduler: Loaded 0 events
140406 16:52:51 InnoDB: Started; log sequence number 0 9939910
140406 16:52:51 mysqld_safe Starting mysqld daemon with databases from /bdd
140406 16:52:48 mysqld_safe mysqld from pid file /bdd/sqlprive-as79341-001.pid ended
140406 16:52:48 [Note] /opt/mysql/mysql/bin/mysqld: Shutdown complete
140406 16:52:48 [Warning] Forcing shutdown of 1 plugins
140406 16:52:48 InnoDB: Shutdown completed; log sequence number 0 9939910
140406 16:52:47 InnoDB: Starting shutdown...
140406 16:52:47 [Note] /opt/mysql/mysql/bin/mysqld: Normal shutdown
Version: '5.1.31' socket: '/bdd/mysql.sock' port: 3306 MySQL Community Server (GPL)
140406 16:52:14 [Note] /opt/mysql/mysql/bin/mysqld: ready for connections.
140406 16:52:14 InnoDB: Started; log sequence number 0 9939910
140406 16:52:14 mysqld_safe Starting mysqld daemon with databases from /bdd
140406 16:52:08 mysqld_safe mysqld from pid file /bdd/sqlprive-as79341-001.pid ended
140406 16:52:08 [Note] /opt/mysql/mysql/bin/mysqld: Shutdown complete
140406 16:52:08 [Warning] Forcing shutdown of 1 plugins
140406 16:52:08 InnoDB: Shutdown completed; log sequence number 0 9939910
140406 16:52:06 InnoDB: Starting shutdown...
140406 16:52:06 [Note] Event Scheduler: Purging the queue. 0 events
140406 16:52:06 [Note] /opt/mysql/mysql/bin/mysqld: Normal shutdown
Version: '5.1.31' socket: '/bdd/mysql.sock' port: 3306 MySQL Community Server (GPL)
140310 15:56:31 [Note] /opt/mysql/mysql/bin/mysqld: ready for connections.
140310 15:56:31 [Note] Event Scheduler: Loaded 0 events
140310 15:56:31 InnoDB: Started; log sequence number 0 46409
140310 15:56:28 mysqld_safe Starting mysqld daemon with databases from /bdd
140310 15:56:17 mysqld_safe Starting mysqld daemon with databases from /bdd
140310 15:56:14 mysqld_safe mysqld from pid file /bdd/sqlprive-as79341-001.pid ended
140310 15:56:14 [Note] /opt/mysql/mysql/bin/mysqld: Shutdown complete
140310 15:56:14 [Warning] Forcing shutdown of 1 plugins
140310 15:56:14 InnoDB: Shutdown completed; log sequence number 0 46409
140310 15:56:14 InnoDB: Starting shutdown...
140310 15:56:14 [Note] /opt/mysql/mysql/bin/mysqld: Normal shutdown
Version: '5.1.31' socket: '/bdd/mysql.sock' port: 3306 MySQL Community Server (GPL)
140310 15:56:01 [Note] /opt/mysql/mysql/bin/mysqld: ready for connections.
140310 15:56:01 InnoDB: Started; log sequence number 0 46409
140310 15:56:01 mysqld_safe Starting mysqld daemon with databases from /bdd
140310 15:55:54 mysqld_safe mysqld from pid file /bdd/sqlprive-as79341-001.pid ended
140310 15:55:54 [Note] /opt/mysql/mysql/bin/mysqld: Shutdown complete
140310 15:55:54 [Warning] Forcing shutdown of 1 plugins
140310 15:55:54 InnoDB: Shutdown completed; log sequence number 0 46409
140310 15:55:53 InnoDB: Starting shutdown...
140310 15:55:53 [Note] Event Scheduler: Purging the queue. 0 events
140310 15:55:53 [Note] /opt/mysql/mysql/bin/mysqld: Normal shutdown
Version: '5.1.31' socket: '/bdd/mysql.sock' port: 3306 MySQL Community Server (GPL)
140310 15:55:51 [Note] /opt/mysql/mysql/bin/mysqld: ready for connections.
140310 15:55:51 [Note] Event Scheduler: Loaded 0 events
140310 15:55:51 InnoDB: Started; log sequence number 0 46409
140310 15:55:51 mysqld_safe Starting mysqld daemon with databases from /bdd
140310 15:55:47 mysqld_safe mysqld from pid file /bdd/sqlprive-as79341-001.pid ended
140310 15:55:47 [Note] /opt/mysql/mysql/bin/mysqld: Shutdown complete
140310 15:55:47 [Warning] Forcing shutdown of 1 plugins
140310 15:55:47 InnoDB: Shutdown completed; log sequence number 0 46409
140310 15:55:45 InnoDB: Starting shutdown...
140310 15:55:45 [Note] /opt/mysql/mysql/bin/mysqld: Normal shutdown
Version: '5.1.31' socket: '/bdd/mysql.sock' port: 3306 MySQL Community Server (GPL)
140310 15:55:12 [Note] /opt/mysql/mysql/bin/mysqld: ready for connections.
140310 15:55:12 InnoDB: Started; log sequence

[vekia]

so your problem is strictly related to this memory exceeded.

there is not enough memory to run your script.

are you able (for test purposes) to increase this limit?

[drowned]

Hello Vekia,

i reboot the mysql server this morning and the site is now accessible, I also clear the cache in Prestashop because Images didn't appear. I've the possible to upgrade the Ram memory on my hosting (256Mo : 10 €/month; 512Mo : 20€).

 

Do you think it's necessary to upgrade ?

Many thanks for you help.

[vekia]

at the moment i think that it's not necessary.

will see what's going on in the nearest future

[Darius Webdevelopers]

Hi, 

 

I think I have the same B.O. blank problem. After upgrade using 1 click upgrade module, I have blank B.O. 

I have enabled error reporting. So you can see as my B.O. looks like ant errors. I have cleaned smarty cash.

Edited May 21, 2014 by E=mc^2 (see edit history)

[drowned]

Hi, the problem came on a prestashop 1.6 normal installation. (not after an upgrade with "1 click upgrade")

 

- after rebooting the mysql server, the website worked

- but the blank page came back after 1 day.

- we find in this forum this solution : "desactivate the expertise module in BO"

- today the blank page problem is solved.