• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question .nfsxxxxx files

lema

New Pleskian
Server operating system version
Debian 11.11
Plesk version and microupdate number
18.0.66 Update #2
Hello!
We are using an NFS mounted disk for storing the vhost files, according to this Plesk article.

Although everything seems to function correctly, a user received the following error message:
Publication failed. Please try again
filemng failed: rm: cannot remove '/var/www/vhosts/mydomain.tld/httpdocs/css/.nfs0000000000010d7600000ee7': Device or resource busy.
filemng: Error occurred during /bin/rm command.

The .nfs0000000000010d7600000ee7 file appears to be held open by the Nginx service, which releases the file after restarting the service.
I assume the creation of .nfsxxxxx files is normal behavior with NFS, but is there a way to perform regular cleanup of such files?

In the case of .nfs0000000000010d7600000ee7, the file remained locked for 2-3 days until the Nginx service was restarted.

Thank you in advance for your help!
 
The issue occurs on both of our Plesk servers.
I have tried every possible option in the NFS mount settings, but I haven't been able to resolve it.

The .nfs000000 files are kept open by Nginx, and when running the following commands,
I can see that nginx: worker process is shutting down

In panel.ini I 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

Any idea ??


Bash:
#lsof .nfs000000000001d29900000001
COMMAND   PID  USER   FD   TYPE DEVICE SIZE/OFF   NODE NAME
nginx   29486 nginx   48r   REG   0,45    54822 119449 .nfs000000000001d29900000001

Bash:
#ps aux | grep 29486
nginx  29486  0.0  0.1 102428 18172 ?  S  13:23  0:00 nginx: worker process is shutting down

2025-02-25_19-25-42.PNG
 
Hello, @lema Could you please open a report here and provide step-by-step instructions on how we can attempt to reproduce the issue on a test environment so I can forward it to our team for a further review? Thank you in advance for your cooperation.
 
Hello @Sebahat.hadzhi
I will open the report, Now I see that the site was built using Sitejet Builder.
The user reports that the issue occurs (sometimes) during publishing.
The server hosts 50 domains without similar issues, all of which are dynamic PHP sites.
 
Back
Top