Backup not starting

Hi @richy66,

I’m sorry to hear about the issue you’re having creating a backup.

The last 2 items in the log you provided are Warnings, not fatal errors, so those errors themselves would not cause the backup process to crash.

Is this the full error log?

If you look at these two lines in the code:

https://github.com/BoldGrid/boldgrid-backup/blob/master/admin/class-boldgrid-backup-admin-core.php#L3064-L3065

$logger->init( 'retention-local.log' );
$logger->add( 'Beginning core::enforce_retention...' );

The first line is trying to initialize the “retention-local.log” log file, and the second line is trying to add a message to the log – but that message is not showing in the log you provided.

At first glance, it does look like a permissions issue. You mentioned Updraft doesn’t restore backups – do you have any error messages from that attempt? I’m curious if both Updraft and Total Upkeep are getting permissions related warnings.

Thanks!
– Brad

Hi Brad,

thanks for your fast reply. I thin you are right. If i look in the retention-log it looks like this:

`[2021-05-20 07:28:20 UTC] Last error: Array
(
[type] => 2
[message] => file_get_contents(/var/www/html/wp-content/updraft/logs-b729045a-5a6f4f0ff6f73145/archive-1621495700.log): failed to open stream: No such file or directory
[file] => /var/www/html/wp-admin/includes/class-wp-filesystem-direct.php
[line] => 39
)

[2021-05-20 07:28:20 UTC] Cannot add signal handlers, pcntl_async_signals function does not exist.
[2021-05-20 07:28:20 UTC] Last error: Array
(
[type] => 2
[message] => file_get_contents(/var/www/html/wp-content/updraft/logs-b729045a-5a6f4f0ff6f73145/retention-local.log): failed to open stream: No such file or directory
[file] => /var/www/html/wp-admin/includes/class-wp-filesystem-direct.php
[line] => 39
)

[2021-05-20 07:28:20 UTC] Beginning core::enforce_retention…
[2021-05-20 07:28:20 UTC] Retention count: 5
[2021-05-20 07:28:20 UTC] Number of archives found: 0
[2021-05-20 07:28:20 UTC] Number of protected archives found: 0
[2021-05-20 07:28:20 UTC] No backups to delete at this time due to retention settings.

I just tried to contact the Hosting-Provider as i do not have any ssh and ftp access to the old server right now. I keep you informed!

Thanks,
Richy

Hello Brad,

i have no a idea what is the problem. I have ssh-access. The site i want to backup is running in a docker-image. the folders have access rights, but i don’t know why it is not starting. maybe its a problem of the paths?

Thx,
Richard

Hi Richard,

Sometimes I can get stuck going down rabbit holes, and lose my direction when troubleshooting. I think our first focus, instead of “Why is my backup not starting?”, is now “Why am I getting permissions related warnings?”.

One of the errors you received is:

file_get_contents(/var/www/html/wp-content/updraft/logs-b729045a-5a6f4f0ff6f73145/archive-1621495700.log): failed to open stream: No such file or directory

The file that has this error message, is it “archive-1621495700.log”? It seems strange that the file that apparently doesn’t exist, actually exists and includes an error message that it does not exist lol.

—-

Also, both warnings are referring to the “logs-b729045a-5a6f4f0ff6f73145” folder.

/var/www/html/wp-content/updraft/logs-b729045a-5a6f4f0ff6f73145/archive-1621495700.log
/var/www/html/wp-content/updraft/logs-b729045a-5a6f4f0ff6f73145/retention-local.log

You did not create “logs-b729045a-5a6f4f0ff6f73145” correct? If not, Total Upkeep created the folder. That means Total Upkeep can create folders but not files?

—-

Can you confirm what the permissions are to that “logs-b729045a-5a6f4f0ff6f73145” folder?

Also, to rule out whether or not this is a permissions issue, can you please:
1. Take note of the current permissions for that folder
2. Change the permissions to 777 and try another backup. Has anything changed?
3. Revert the permission changes

Thanks,
– Brad

Hi Brad,

thanks for the great tipps.

In the end i had the luck to get full ssh-access to both servers and so i did a full export via mysqldump and transfered it to the new server manually.

The Problem had for sure to do with the docker-installation.

I just tried a backup & restore on the new system without problems.

Thanks,
Rihcard