Temporary files not cleaned up

Hi,

There is a Cron job that will remove these in an hour or they will be removed when the backup is run.

Although there may be quite a few of these they are very small is size.

Hi, those ‘.part’ files are around 35 MB and for each backup there are 3 or 4 of those files remaining in the updraft folder. These are not deleted by the daily cleanup cron job. As a daily backup is scheduled, this is about 1 GB per week, so imho this is substantial. At the archive destination folder, located at a Google drive, there are about 25 backup files for each backup set. The updraftplus settings are to split the backup set into 50 Mb files.

Can you send me your backup log from the backup/restore tab?

Can you you post it using a tool such as patebin.com?

Hi, I assume you suggest pastebin.com (patebin.com is a very unsecure site). See the log at FA20240605 – Pastebin.com

From this backup the following files are not removed by the cron job:

backup_2024-06-05-0200_Farms_Around_731f62c87837-uploads3.zip.tmp.2k476z.part

backup_2024-06-05-0200_Farms_Around_731f62c87837-uploads14.zip.tmp.bgfm6l.part

backup_2024-06-05-0200_Farms_Around_731f62c87837-uploads19.zip.tmp.67d2pa.part

Hope you can find the issue ….

Regards,

Eric

• This reply was modified 5 months, 3 weeks ago by Eric Sprangers.
• This reply was modified 5 months, 3 weeks ago by Eric Sprangers.

this might be related: during the backup I noticed the following in the apache error log:

[Wed Jun 05 02:02:33.957220 2024] [fcgid:warn] [pid 25374:tid 139646482732800] [client 116.203.134.67:57670] mod_fcgid: read data timeout in 120 seconds
[Wed Jun 05 02:02:33.957259 2024] [core:error] [pid 25374:tid 139646482732800] [client 116.203.134.67:57670] End of script output before headers: wp-cron.php
[Wed Jun 05 02:08:05.355285 2024] [fcgid:warn] [pid 25374:tid 139646549874432] [client 116.203.134.67:60818] mod_fcgid: read data timeout in 120 seconds
[Wed Jun 05 02:08:05.649234 2024] [core:error] [pid 25374:tid 139646549874432] [client 116.203.134.67:60818] End of script output before headers: wp-cron.php
[Wed Jun 05 02:14:04.526655 2024] [fcgid:warn] [pid 25374:tid 139646533089024] [client 116.203.134.67:36018] mod_fcgid: read data timeout in 120 seconds
[Wed Jun 05 02:14:04.526686 2024] [core:error] [pid 25374:tid 139646533089024] [client 116.203.134.67:36018] End of script output before headers: wp-cron.php
[Wed Jun 05 02:20:04.507253 2024] [fcgid:warn] [pid 5545:tid 139646482732800] [client 116.203.134.67:39754] mod_fcgid: read data timeout in 120 seconds
[Wed Jun 05 02:20:04.611287 2024] [core:error] [pid 5545:tid 139646482732800] [client 116.203.134.67:39754] End of script output before headers: wp-cron.php
[Wed Jun 05 02:25:47.784260 2024] [fcgid:warn] [pid 5545:tid 139646549874432] [client 185.107.112.117:42898] mod_fcgid: read data timeout in 120 seconds
[Wed Jun 05 02:25:47.784311 2024] [core:error] [pid 5545:tid 139646549874432] [client 185.107.112.117:42898] End of script output before headers: wp-cron.php

• This reply was modified 5 months, 3 weeks ago by Eric Sprangers.

Hi,

These files seem to be associated with a time out and a resumption.

Would you be able to ask your hosts if they can increase in the timeout to more than 120 seconds?

I will also ask our development team to take a look as even with a timeout, the files should be removed

Why was this topic closed? I’ve got the same issue on a client’s site, that’s using the same host (Hostnet). They know about the 120 second time limit, as we can read in their docs. I’ve translated the paragraph:

Solution: For both web hosting packages and WordPress packages, the limit is set by default to a maximum throughput time of 120 seconds. This cannot be changed. However, you can optimize your used script. You can also check whether your WordPress plugin has advanced settings for adjusting the time-out limit.

Can something be done to make sure the time limit is not reached? On bigger sites, UpdraftPlus seems to slow down, by waiting longer times each iteration.