Max execution time, and Max allocated memory errors

Hello,

Thank you for reaching out to us. Could you please share the debug information from BackWPup > Settings > Information along with the list of plugins you have? In the meantime, have you tried running basic troubleshooting by deactivating other plugins to find any conflicts? If you find any, please let us know.

This will help us analyze the issue more effectively.

Looking forward to your response.

Best regards,

I did not start any troubleshooting as backups are completing after 1 or 2 retries as you see on what I shared here above.

Tonight no error, only an alert after near 1 hour inactivity :

Job restarts due to inactivity for more than 5 minutes.

Here the information requested :

                                Version WordPress : 6.5.5

Version BackWPup: 4.1.3
Version PHP: 7.4.33 (64bit)
Version MySQL: 10.11.6-MariaDB-0+deb12u1
Version cURL: 7.74.0
Version SSL cURL: OpenSSL/1.1.1w
URL WP-Cron: https://xxx.fr/wordpress/wp-cron.php
Connexion au serveur: Réponse HTTP non attendue?:
Code d’état?: 200
Date: Fri, 12 Jul 2024 13:56:35 GMT
Content-type: text/html; charset=UTF-8
Content-length: 1
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-control: no-cache, must-revalidate, max-age=0
Vary: Accept-Encoding,User-Agent
Content-encoding: br
X-request-id: 2abaa0ad7af694a16b1b657324e8318e
Document root: /var/www/xxx.com/htdocs
Dossier temporaire: /htdocs/xxx.fr/wordpress/wp-content/uploads/backwpup/af794b/temp/
Dossier des fichiers journaux: /htdocs/xxx.fr/wordpress/wp-content/uploads/backwpup-af794b-logs/
Serveur: Apache/2.4.59 (Debian)
Système d’exploitation: Linux
PHP SAPI: fpm-fcgi
Utilisateur PHP actuel: exper919990
Temps maximum d’exécution: 120 secondes
Temps maximum d’exécution d’un script de BackWPup: 30 secondes
WP Cron alternatif: Off
WP Cron désactivé: Off
CHMOD Dir: 493
Heure du serveur: 13:56
Heure du site web: 15:56
Fuseau horaire du site web: Europe/Paris
Décalage temps avec le site web: 2 heures
Langue du site: fr-FR
Type d’encodage du client MySql: utf8mb4
Limite mémoire de PHP: 256M
Limite mémoire de WP: 256M
Limite mémoire maximum de WP: 256M
Mémoire utilisée: 4,00 Mo
Fonctions PHP désactivées?:: pcntl_alarm, pcntl_fork, pcntl_waitpid, pcntl_wait, pcntl_wifexited, pcntl_wifstopped, pcntl_wifsignaled, pcntl_wexitstatus, pcntl_wtermsig, pcntl_wstopsig, pcntl_signal, pcntl_signal_dispatch, pcntl_get_last_error, pcntl_strerror, pcntl_sigprocmask, pcntl_sigwaitinfo, pcntl_sigtimedwait, pcntl_exec, pcntl_getpriority, pcntl_setpriority, passthru, system, pcntl_exec, proc_open, proc_nice, proc_terminate, proc_get_status, proc_close, leak, apache_child_terminate, posix_kill, posix_mkfifo, posix_setpgid, posix_setsid, posix_setuid, highlight_file, popen, show_source, ini_alter, diskfreespace, disk_total_space, source, proc_exec, symlink, dl, ftp_exec, apache_setenv, define_syslog_variables, openlog, syslog, virtual, bzopen, pspell_config_personal
Extension PHP chargées?:: Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, bcmath, bz2, calendar, cgi-fcgi, ctype, curl, date, dba, dom, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, imagick, imap, intl, ionCube Loader, json, libxml, mbstring, memcached, mysqli, mysqlnd, openssl, pcntl, pcre, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, posix, ps, pspell, readline, redis, session, shmop, snmp, soap, sockets, sodium, sqlite3, standard, sysvsem, sysvshm, tidy, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib

Hi,

Thank you so much for your reply.

Can you try rolling back to older version 4.1.0 and see if backup works seamlessly?

You can download an older version to install from here: https://www.ads-software.com/plugins/backwpup/advanced/.

I look forward to your reply.

Best Regards,

I just downgraded to V 4.1.0, I will let you know tomorow.

Just verified issues started on June 20th. May be an older version is needed ?

Hello,

Tonight no error with V 4.1.0, status O.K. !

What is next step ?

Hello,

Thank you for your reply and confirmation.

I’ve sent the relevant information to our developers to debug this further so they can fix it in upcoming versions.

Until then, please continue using this version.

Thank you for your understanding.

Best Regards,

Hello,

After upgrade to V 4.1.6 version issue pop out again. So issue was not solved.

How should I manage this situation ?