• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

pleskbackup fills up my /tmp directory

P

panaman

Guest
My pleskbackup is not working anymore... it fills up my /tmp directory and crashes........

my /tmp is 2GB in size....
I heard something that the new pleskbackup writes everything to /tmp before it makes the file... well that is stupid if it does that..

if this is the case is there a way to specify an alternate place for pleskbackup to dump its temporary files during the backup?
 
This has become a big problem for me and I was wondering if anyone had any ideas? I had a look at all the scripts and it felt like I was looping.

I have a 100G site and a 4G /tmp that is mounted no exec due to past problems on the server.

Any help would be appreciated.


Thank you,

Joshua
 
yeah.. big problem for me still too...
i have a 2gb /tmp on my server mounted noexec

a 2 gb tmp has been no problem in the past until now..... i have about 250 websites on this box and can't do backups because of this stupid new backup script that writes each site to /tmp first...there has to be a way to have it write to an alternate place
 
Anyone find a solution to this in 8.1?

I heard it's fixed in 8.2 but I don't want to attempt the upgrade.

This is a BIG problem.
 
seems to be solved in 8.3 as you can specify path of output file. however you can specify an ftp destination instead and in this case pleskbackup uses /tmp to build the backup first and of course /tmp fills up and the utility dies.
 
Back
Top