Some indication:
this particular task fail (randomly, but almost each time) when scanning for wp-content/
I activated xdebug, and the journal get this message:
ERROR:
Exception caught in Error: Xdebug has detected a possible infinite
loop, and aborted your script with a stack depth of '256' frames
I do not have any symbolic link in there.
It seems that there is an error with the spider ; and by some way leverage an error (trigger_error) but with a bad argument (see the original error). Despite this, the job terminate with a “OK” status because of the failed error leverage.
Hi @bws-online ;
Have you found a workaround for that bug? I do have exactly the same.
Strange thing is, the other jobs run well, the backup and files are really tiny and there is no problem with a second wordpress+backwup (very similar WP installation) in the same host, same config.
Thanks for reply;
GT
