Hmm, updates on that second link I thought I might follow:
it’s definitely not 1 or 2, and I don’t think 3 either since we have version 1.16.26 and haven’t been alerted about that.
4: we use godaddy, seems pretty unlikely to me that they do this but I will check.
5: using the shell doesn’t seem like the best long-term solution for us b/c I want the owner of this site to be able to do some of this himself in future, and he would not be comfortable doing so.
6: nope
So I guess I need to reach out to GoDaddy next – before I do though: if I were to try adding the line define(‘ALTERNATE_WP_CRON’, true); to the config file, will it cause any errors if that is NOT the problem? (is there a way to check that this is the best solution before I add that?)
-
This reply was modified 5 years, 10 months ago by
bonnie447.
Plugin Contributor
bcrodua
(@bcrodua)
Hi @bonnie447
Apologies for the late reply.
Thanks for sending the log. I think I found the culprit –
“3921.205 (6) [Warning] A very large file was encountered: debug.log.bak (size: 1741.9 Mb)”, the log shows a very large file on your WP install.
Please can you check and delete the file? Then do a test backup and see if that works now.
Thanks,
Bryle
“The backup apparently succeeded and is now complete (Jul 23 13:06:13)”
That was it!! Thank you so much Bryle!!
Plugin Contributor
bcrodua
(@bcrodua)
Hi @bonnie447
You’re welcome! If you like UpdraftPlus, please do consider giving us a 5-star review: https://ww.wp.xz.cn/support/plugin/updraftplus/reviews/?rate=5#new-post
Best Wishes,
Bryle