Facebook
Twitter-
Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products ! WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
Join the pilot program today! -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
-
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.
How to clean temporary Plesk files on a Linux server
Applicable to: Plesk for Linux Question How to clean temporary Plesk files on a Linux server to free up disk space? Answer There are two ways in Plesk to safely clean temporary Plesk files on a ...
Thanks, but if any files are used?
talk.plesk.com
Resolved - Safe deletion of the contents of /tmp directories
Having an interest in keeping things organised on our server, we ran several content queries. The two items with results that may warrant some re-organisation are these two: # du -sk /usr/local/psa/tmp/*and this one:# du -sk /var/tmp/* The question is (for those with lots more Plesk experience...
talk.plesk.com
Stop Plesk services:
# service psa stopall
Stop PHP-PFM:
# service plesk-php<version>-fpm stop
Just in case some stuff is still running:
# service postfix stop
# service dovecot stop
# service nginx stop
# service httpd stop (or # service apache2 stop)
# service mariadb stop (or # service mysqld stop)
Then remove the temp files, then in the opposite order:
# service mariadb start
# service httpd start
.
.
.
Stopping services is not necessary - with linux, you can delete files that are still open, and they will only really be removed from disk & the space recovered when the last access handle to the file is closed.
As files in /tmp, by definition, aren't guaranteed to be persistent, it should not break anything if you just remove everything. But to be safe, you can use the suggestion to use find with option -mtime +1 to get only files older than a day, and then let it remove them with -exec rm -rf {} \;. Note that if you don't understand how this works you probably shouldn't use it, as there is ample opportunity to introduce bugs that sooner or later do a rm -rf /, wiping your system.
As files in /tmp, by definition, aren't guaranteed to be persistent, it should not break anything if you just remove everything. But to be safe, you can use the suggestion to use find with option -mtime +1 to get only files older than a day, and then let it remove them with -exec rm -rf {} \;. Note that if you don't understand how this works you probably shouldn't use it, as there is ample opportunity to introduce bugs that sooner or later do a rm -rf /, wiping your system.
