• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Sitejet Builder - Publication failed

lema

New Pleskian
Username:

TITLE


Sitejet Builder - Publication failed

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian v18.0.67_build1800250217.08 os_Debian 11.0

PROBLEM DESCRIPTION

We are using an NFS mounted disk for storing the vhost files, according to this Plesk article.

Everything seems to be working fine, and the server hosts multiple dynamic PHP sites without any issues,
except for one static site built with Sitejet Builder.

In panel.ini we have the:
[webserver]
syncModeOnRemoveConfiguration = true

and the /etc/fstab entry is:
192.168.1.10:/plesk-vhosts /var/www/vhosts nfs hard,timeo=150,retrans=2,_netdev 0 0

STEPS TO REPRODUCE

The user has created a site using Sitejet Builder. They enter the environment, make the necessary changes, and click publish and -most of the time- the following message appears.

Code:
Publication failed. Please try again
filemng failed: rm: cannot remove '/var/www/vhosts/ml.xx.xxxxxxxxx.gr/httpdocs/css/.nfs000000000000e85300000069': Device or resource busy
filemng: Error occurred during /bin/rm command.

They inform us that the message always concerns the /css directory.

ACTUAL RESULT

The Sitejet Builder does not properly update the site's files (we are informed that the CSS file is missing).

The /css/.nfs0000000xxxx file cannot be deleted, and using lsof, it appears to be held open by Nginx.
The only way to release/delete the .nfs0000000xxxx file is to restart the Nginx service.

EXPECTED RESULT

The expected behavior is for the old CSS file to be deleted and the new one to be written.

ANY ADDITIONAL INFORMATION

The storage we use is a Dell Unity XT, and we have not encountered any issues with any other use of it.
Additionally, we have checked for any network malfunctions, but nothing has been found.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Help with sorting out
 
Last edited by a moderator:
Thank you for the report, @lema I forwarded it to our team and according to them it looks like nginx holds open a static file it was serving - and when Sitejet tries to remove it, it gets renamed to .nfs* instead due to the NFS configuration. However, it is difficult to get to the root cause of the issue without server access. With that said, please submit a ticket with Plesk support for an investigation of the issue on your server. To sign-in to support and open a ticket go to:
https://support.plesk.com
If you have got the license from a Plesk partner, what you can do is either request a free trial for Plesk support or get in touch with the support staff of the company from which you got the license and ask them forward the case to our support team:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk
 
Unfortunately, the problem reappeared, not only on sites with Sitejet Builder but also for users with dynamic sites (WordPress, Drupal).
I tried all possible settings on the NFS mount, but nothing changed.

In the end, I removed the NFS mount, and the entire /var/www/vhosts was moved to a new local disk*.
Everything seems to be working fine now.

I should note that PLESK runs as a VM under VMWare ESXi, and the new disk* I mounted,
is the same NFS share where I was facing the issue.

Should the option syncModeOnRemoveConfiguration = true be retained in panel.ini?
What exactly does it do?
 
Essentially, it enables NFS support. It is required for cases when subscription/domain should be removed from the configuration. If your website files are no longer accessed via NFS, you can disable it.
 
Back
Top