Please could you try adding the following to your wp-config.php file, near the top:
This will set UpdraftPlus to use a fallback library for accessing S3.
Does this change improve the backup?
Hi, I tried but it didn’t help. The Upload and execution works now but seems to stuck at following error:
Amazon S3: upload: all chunks uploaded; will now instruct S3 to re-assemble
4324.114 (6) Amazon S3: re-assembly error (others0): Error executing “CompleteMultipartUpload”
I made a new bucket already. I checked my cron jobs and i also added the litespeed noabart tag. However the error seems to persist. I also decreased the split file size. The issues didn’t accuse with significantly older versions.
Please include a link to your backup log file (using pastebin.com).
Hi, @davidanderson the issues seems to be related to /tmp space of ubunutu. Updraft seems to fill it up during the upload to S3 and not getting rid of the already uploaded chunks. This seems to accumulate until the /tmp is running out of space. This happens on all chunk settings (used several). I created a temporary new sized /tmp and the backup went through without issues. But this method isn’t sustainable hence it causes the ram to fill up. Is there a way to use /tmp directory within wordpress which can be defined via wp-config?
If you’ve used the define above, then temporary file space isn’t being used, so please check that you’ve set it correctly, and the datestamps on the temporary files.
Hi @davidanderson thank you very much! I before didn’t add the define (..) on the top. It turns out it really works great. Just one more question, is this just a temporary solution or will this change, and if so would it be announced? Btw. thanks for the amazing support! Really rocks
You can remove the define after 6 weeks, since it will be applied automatically in future.