Search Engine: Elastic
  • Article for your preferred language does not exist. Below is international version of the article.

Article ID: 6466, created on Jun 22, 2009, last review on Nov 4, 2017

  • Applies to:
  • Web Presence Builder 11.5
  • Operations Automation 6.0

Symptoms

Site cannot be published, the following error is shown in Sitebuilder Wizard:

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

Cause

The problem is caused by NFS locking.:

http://www.sqlite.org/faq.html

"SQLite uses reader/writer locks to control access to the database. But use caution: this locking mechanism might not work correctly if the database file is kept on an NFS filesystem. This is because fcntl() file locking is broken on many NFS implementations. You should avoid putting SQLite database files on NFS if multiple processes might try to access the file at the same time."

Configuration of Sitebuilder modules is stored in SQLite database on publishing host. The file is located at /data/storage/sb_modules.php under publishing location. When you edit site in Sitebuilder Wizard or if site is published Parallels Plesk Sitebuilder locks the SQLite database file and then edits it.

If publishing host is mounted as NFS file system locking is not possible by default. This causes Sitebuilder is unable to work with SQLite database and the error occurs.

Resolution

  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 Web Presence Builder that works without SQLite database.

fad6dc0c8e983c17ae70a51ac7952cd0 56797cefb1efc9130f7c48a7d1db0f0c 18f5eb2d7a7972323627b40f015d5a19 9305481d3bd31663b68451e3bfdec5a5 0efe2234e2ce513f2186f26c68447702 5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF