labarbiche

Hello,
Thank you for your answer.
But I opened this thread to report that these warning are flooding the reports, filling the disks. You should remove them, as they happen in the official docker image of latest WordPress and the latest version of BackWPUp. Not a high priority task, of course ??
Thank you,

Hello,
Here are the informations:

                                Version WordPress : 6.5.5

Version BackWPup: 4.1.3
Version PHP: 8.2.21 (64bit)
Version MySQL: 11.4.2-MariaDB-ubu2404
Version cURL: 7.88.1
Version SSL cURL: OpenSSL/3.0.13
URL WP-Cron: https://—mysite—/wp-cron.php
Connexion au serveur: Réponse au test positive
Document root: /var/www/html
Dossier temporaire: /var/www/html/wp-content/uploads/backwpup/0bea90/temp/
Dossier des fichiers journaux: /var/www/html/wp-content/backwpup-0bea90-logs/
Serveur: Apache/2.4.59 (Debian)
Système d’exploitation: Linux
PHP SAPI: apache2handler
Utilisateur PHP actuel: www-data
Temps maximum d’exécution: 30 secondes
Temps maximum d’exécution d’un script de BackWPup: 0 secondes
WP Cron alternatif: Off
WP Cron désactivé: Off
CHMOD Dir: 493
Heure du serveur: 8:9
Heure du site web: 08:09
Fuseau horaire du site web:
Décalage temps avec le site web: 0 heures
Langue du site: fr-FR
Type d’encodage du client MySql: utf8
Limite mémoire de PHP: 256M
Limite mémoire de WP: 40M
Limite mémoire maximum de WP: 256M
Mémoire utilisée: 12,00 Mo
Extension PHP chargées?:: Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, apache2handler, bcmath, ctype, curl, date, dom, exif, fileinfo, filter, gd, hash, iconv, imagick, intl, json, libxml, mbstring, mysqli, mysqlnd, openssl, pcre, pdo_sqlite, posix, random, session, sodium, sqlite3, standard, tokenizer, xml, xmlreader, xmlwriter, zip, zlib

Thank you,

I’ve the same issue on WordPress 5.9, when updating backWpUp to 4.1.3 (latest as of today)

Hi David,

I’ve a dedicated server for my wordpress sites, so I wasn’t charged ￡150 ??
I ran into a similar probem (the apache error.log was growing very quickly / the BackWPUp admin panel was not responding, but it seems that a job was running and stuck near 11%), with the same kind of error message:

feof() expects parameter 1 to be resource, boolean given in /home/…onMyServer…/wordpress/wp-content/plugins/backwpup/inc/class-job.php on line 1077

Then I found that directory
/home/…onMyServer…/wordpress/wp-content/uploads/backwpup-7c5caf-temp

In that directory I found out that a file named backwpup-working.php contained an incorrect log path.

I (made a backup then) deleted the whole backwpup-7c5caf-temp directory.

I restarted the apache2 service. The error went away.

I think it’s a bug in backwpup when
– you move your wordpress directory on disk and
– you upgrade backwpup (but I don’t remember from which version… I made several upgrades)

Hope this helps…
Labarbiche

Please note: I’ve replaced in this post my wordpress location on disk with /home/…onMyServer…/wordpress

Thanks for the quick fix !
Works like a charm now !
Have a nice day

Hi there !
Thanks Caspar for this great plugin.
After few investigations, I think the problem is a bug when storing successful backup infos, and retrieving the existing FTP file list:

These problems appear only when the “Folder to store files in” field is not empty (ie you decide to store your backups in a FTP subfolder)
When updating the lastbackupdownloadurl (line 335 in class-destination-ftp.php) you use $current_ftp_dir instead of $job_object->backup_folder. This leads to wrong FTP download links in the Backups list.

In that backup list, the Folder is wrong (it shows on my site (with “Folder to store files in” set to MyFolder): ftp://some.ftp.sever.net:21./ instead of ftp://some.ftp.sever.net:21/MyFolder/ (again, $current_ftp_dir equals ‘.’ and the backup_folder is not taken in account). As a side effect, the date of the backups are always Jan, 1 1970, and backup size always ‘?’

This should explain the FTP deletion error.

I think there’s no bugs if you leave the “Folder to store files in” field empty.

Hope this helps

Regards !