[INFO] Site cannot be opened in Sitebuilder Wizard because of file sb_modules.php-journal with zero size.


2016-11-16 13:16:46 UTC


2017-04-24 11:40:45 UTC


Was this article helpful?

Have more questions?

Submit a request

[INFO] Site cannot be opened in Sitebuilder Wizard because of file sb_modules.php-journal with zero size.

Applicable to:

  • Plesk Sitebuilder 4.5 for Linux


Module pages (Image Gallery, eShop, other) cannot be opened in Sitebuilder Wizard - the page is loaded and finally gives "Internal Server Error" . The following error appears in the log file:

[Wed Nov 21 06:28:56 2012] [warn] [client] Timeout waiting for output from CGI script /opt/php52/cgi-bin/php5, referer: http://sitebuilder.hostname/Wizard/Edit/Html?currentPageId=fhxq2ly0rfa

Where sitebuilder.hostname is hostname of Parallels Plesk Sitebuilder.

File sb_modules.php-journal with zero size, permission 000 and a random timestamp exits in subdirectory /data/storage/ near regular database file sb_modules.php:

~# ls -l /VAR/WWW/VHOSTS/site.tld/httpdocs/data/storage/
total 44
drwxrwxrwx 2 sb45 psacln 4096 Nov 15 14:04 attachments
-rwxrwxrwx 1 sb45 psacln 40960 Nov 15 14:16 sb_modules.php
---------- 1 root root 0 May 31 2018 sb_modules.php-journal

There "/VAR/WWW/VHOSTS/site.tld/httpdocs/" is publishing location of site site.tld.


When you edit modules through Wizard or publish a site with changed modules, Parallels Plesk Sitebuilder 4.5 updates SQLite database file sb_modules.php on the publishing host. File sb_modules.php-journal is created by SQLite at the start of a transaction and removed upon commit. Here you may find some detail:


SQLite by default creates the journal file at the start of a transaction, which is a good thing. Normally it deletes the file upon commit.


The rollback journal is always located in the same directory as the database file and has the same name as the database file except with the 8 characters "-journal" appended. The rollback journal is usually created when a transaction is first started and is usually deleted when a transaction commits or rolls back.

File sb_modules.php-journal remain because the publishing process was not completed successfully.

The issue might be caused by NFS share where to the sites are published.


  1. Add option "nolock" to NFS mount parameters
  2. Change site publishing location – the site should be published into real directory, not to NFS share.
  3. Migrate affected sites to Parallels Presence Builder that works without SQLite database.

Refer to this KB for the detail.

Note: all files sb_modules.php-journal are temporary ones, they may be safely removed.

Have more questions? Submit a request
Please sign in to leave a comment.