Article ID: 6894, created on Nov 11, 2009, last review on Aug 12, 2014

  • Applies to:
  • Plesk Sitebuilder 4.5 for Linux/Unix


The site cannot be published through Parallels Plesk Sitebuilder Wizard correctly:

The site has been published with errors.
Cannot update modules data.

And the following error is shown in Sitebuilder logs at Sitebuilder -> System -> Logs:

System          7/10/2009 5:06:57 AM    admin   The site 'domain.tld' has been published, but with errors....
System          7/10/2009 5:06:55 AM    admin   Cannot update modules data....
Modules         7/10/2009 5:06:55 AM    admin   Invalid server response: http/1.0 500 internal server error ...

Empty page is shown when try to open published site via http://domain.tld. The following error is shown in Apache error log:

[Fri Jul 10 05:06:55 2009] [error] [client] PHP Fatal error:  Allowed memory size of 100663296 bytes exhausted (tried to allocate 142401972731904 bytes) in /PATH/TO/domain.tld/httpdocs/include/SB/Modules/Storage/Db/Adapter/Sqlite.php on line 764


During publishing Parallels Plesk Sitebuilder tries to allocate 142401972731904 bytes* (129T) of memory. This huge value of PHP memory is requested by PHP module SQLite 2.8.14.

To verify version of SQLite module it is recommended to login to the publishing server** and run the following command:

~# php -i | grep 'SQLite Library'
SQLite Library => 3.3.6
SQLite Library => 2.8.14                <=== this version of SQLite module


It is recommended to upgrade SQLite to version 2.8.17 or above.
For details about compilation procedure please refer to this article:

Additional information

*Value of required PHP memory may be other then 142401972731904.

**Publishing host is server with FTP and HTTP where Sitebuilder site is published to. It may be one of several physical servers. During site publishing files are uploaded via FTP, Parallels Plesk Sitebuilder queries published site via HTTP requests.
If publishing host consists of several servers, SQLite should be upgraded on server where HTTP runs.

f7f840260c1591440648a375a64b5b75 fad6dc0c8e983c17ae70a51ac7952cd0 d055be4fdc562a8ecb8e6d0bf419f946 ea6a61e571a858aa6019ceb068ea403a 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF