Job has started, but not responded for 10 seconds.

@artphotoasia

I think there is server permission issue, please show us your server configuration by go to BackWPUp -> Settings -> Infomation -> and press “Get debug info”

Hello,
I have the same problem.
When I switch the website to php 8.x the problem occurs
The “Backup” task started but did not respond for 10 seconds. Check the information.

I’m sending info about the debut and I’m asking for help. Thank you.

Version WP: 6.6
Version BackWPup: 4.1.4
Version PHP: 8.2.1 (64bit)
Version MySQL: 10.4.33-MariaDB-log
Version cURL: 7.29.0
Version cURL SSL: NSS/3.36
WP-Cron url: https://website.test/wp-cron.php
Separate server connection: Unexpected HTTP response:
Status-Code: 200
Date: Tue, 23 Jul 2024 08:51:46 GMT
Server: Apache
Pragma: no-cache
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-control: no-cache, must-revalidate, max-age=0
Set-cookie: PHPSESSID=328d7b9a2df0d8725e2dd4b4af34e2a4; path=/; secure; HttpOnly
Vary: User-Agent
Upgrade: h2,h2c
Content-length: 0
Content-type: text/html; charset=UTF-8

Document root: /data/web/virtuals/93279/virtual/www
Directory Temp: /data/web/virtuals/93279/virtual/www/domains/website.test/wp-content/uploads/backwpup/4f721c/temp/
Directory log: /data/web/virtuals/93279/virtual/www/domains/website.test/wp-content/uploads/backwpup-b8ad05-logs/
Server: Apache
Operation system: Linux
PHP SAPI: fpm-fcgi
Current PHP user: w93279
Maximum operation time: 200 seconds
Maximum script execution time BackWPup: 30 seconds
WP Cron Alternative: Vypnuto
Disabled WP Cron: Vypnuto
CHMOD Dir: 493
Server time: 8:51
Blog time: 10:51
Blog time zone: Europe/Prague
Blog time difference: 2 hours
Blog language: cs
Coding the MySQL client: utf8mb4
PHP Memory limit: 512M
WP memory limit: 512M
WP maximum memory limit: 512M
Memory usage: 24,00 MB
Disabled PHP functions:: apache_child_terminate, apache_setenv, define_syslog_variables, diskfreespace, disk_free_space, disk_total_space, dl, exec, leak, link, openlog, passthru, pfsockopen, popen, posix_getgrnam, posix_getpgid, posix_getpwuid, posix_getpwnam, posix_getrlimit, posix_initgroups, posix_kill, posix_mkfifo, posix_mknod, posix_setpgid, posix_setsid, posix_setuid, posix_uname, proc_close, proc_get_status, proc_nice, proc_open, proc_terminate, putenv, readlink, register_tick_function, shell_exec, show_source, symlink, syslog, system
Active PHP extension:: Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, bcmath, bz2, calendar, cgi-fcgi, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, imagick, imap, intl, json, libxml, mbstring, mysqli, mysqlnd, openssl, pcre, pdo_mysql, pdo_sqlite, posix, random, session, soap, sockets, sodium, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tokenizer, xml, xmlreader, xmlwriter, xsl, zip, zlib

Hi @zzzek,

could you please add wp-cron.php from the caching system and try again?

For another solution, you can fix this by using another cron method.
modify wp-config.php ( you can find this file in your root directory ), and before the line:
/* That’s all, stop editing! Happy blogging. */
add this line:
define(‘ALTERNATE_WP_CRON’ , true );

Hello,

thank you for answer. I tried adding ALTERNATE_WP_CRON but unfortunately no result.
What do you mean by “add wp-cron.php from the caching system”? I don’t have any chaching plugin in wordpress.
This problem only appeared after switching to PHP version 8.x, when I switch the website to 7.4, the backup works. It is possible that there is some incompatibility with web hosting or plugin compatibility with version 8.2.

I hope the bug will be fixed in some future version.

Thank you again.

Hi,

Thank you for your reply.

PHP 8.2 is not fully compatible with WordPress yet, and this may also be the case with other plugins. For more details, please refer to the WordPress PHP compatibility handbook.

Therefore, I suggest continuing to use PHP 7.4 as it is currently working for you.

Best Regards,