• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

PSABackup High CPU ?

S

Starwing

Guest
Currently having problems with PSAbackup when its being called from cron.

I have PRM (Process resource monitor) installed that kills a process that is taking too much CPU.

When psabackup kicks in during cron, I notice that prm kills it.

- Event Summary:
USER: 10092
PID : 4526
CMD : gzip
CPU%: 46 (limit: 45)
MEM%: 0 (limit: 20)
PROCS: 1 (limit: 80)

When I refer to the email that cron sents, it always stop at this particular domain, with the UID of 10092. I have tried removing gzip from my cron but that did not help, which leads me to think that psabackup itself calls on gzip.

I do not have this problem often, just sometimes.

The said user do not have much files in his directory. Just some MP3s. Thanks about it, but it always stops at this user's directory.

TIA
 
Try using the --no-internal-zip flag too ... by high load what do you mean? It may be that the load is just normal anyway, and PRM could be interfering with normal functionality of psadump.
 
I could try that flag --no-internal-zip.

But what I do not understand is, PRM always kills the process when psabackup is compressing this particular user's directory.

[Fri May 13 07:14:42 2005] dumping hosting user data for domain
'/home/httpd/vhosts/problemdomain.net' ... error!
The child process with pid 4521 was terminated by other process.

Its always this way, and I do not understand why.

It does not happen daily, just once in a blue moon. The process is then terminated by PRM. I could, however exclude PRM into checking that, but that does not solve the problem why when dumping that current user we have problems.

Could it be because of the files that they have? Corrupted files? Something? This again, do not happen always, just when it feels like it.

TIA.
 
Check their files. There may be a directory with too many files in or something.
 
I have checked their files. They have only a few files, and are MP3 files. Huge MP3 files like 100-200 MB each. Could that be the problem ?
 
Back
Top