Forum Replies Created

Viewing 15 replies - 1 through 15 (of 28 total)
  • Thread Starter zedomingues

    (@zedomingues)

    Hi, thanks for the quick response.

    Reset Permalinks: I did the permalink reset procedure, but the error remains

    Theme Conflict: I’m already using the Hello Elementor theme, however, I changed it to the default WP theme (Twenty Twenty-Four) and the error also remains.

    Plugin Conflict: I deactivated all plugins except: Elementor, ShopEngine, WooCommerce (you forgot that one) and YITH Custom Thank You Page, but the error also remained.

    the site is still in a test version, so I will upload a new version again and install only the necessary plugins (Elementor, ShopEngine, WooCommerce and YITH Custom Thank You) and redo the test. what do you think?

    The link with Elementor information is here: https://pastebin.com/Pk8yd1cj

    Thread Starter zedomingues

    (@zedomingues)

    Thanks for the quick response, @wpmudevsupport13

    It would be very interesting if the development team could create this form of mass editing.

    I will edit the links manually.

    Best Regards

    • This reply was modified 10 months, 3 weeks ago by zedomingues.
    Thread Starter zedomingues

    (@zedomingues)

    @duongcuong96

    I understand that reducing server load can change job execution time.

    What I don’t understand, and I’m trying to show it from the start, is how a 4,45 GB backup can take 11053 seconds? That’s the explanation I’m trying to get here (or trying to figure out what’s wrong to fix).

    again: If I compare with another site I run, a 4.11 GB backup took 595 seconds

    Is this a common mistake? Are there any settings I should observe that I am not observing?

    tks

    Thread Starter zedomingues

    (@zedomingues)

    now the backup took 11053 seconds (log below) yet, from my experience, it’s very strange

    [INFO] BackWPup 3.6.10; A project of Inpsyde GmbH
    [INFO] WordPress 5.2.4 on xxxxxx
    [INFO] Log Level: Normal (translated)
    [INFO] BackWPup job: Backup Diário
    [INFO] Logfile is: xxxxxx
    [INFO] Arquivo de backup é: xxxxxx1.tar.gz
    [21-Oct-2019 02:10:00] 1. Try to backup database …
    [21-Oct-2019 02:10:00] Conectado ao banco de dados xxxxxx in xxxxxx
    [21-Oct-2019 02:10:51] Added database dump "xxxxxx.sql" with 758,40 MB to backup file list
    [21-Oct-2019 02:10:51] Database backup done!
    [21-Oct-2019 02:10:51] 1. Trying to make a list of folders to back up …
    [21-Oct-2019 02:10:58] Added "wp-config.php" to backup file list
    [21-Oct-2019 02:10:58] 1858 folders to backup.
    [21-Oct-2019 02:10:59] 1. Trying to generate a manifest file …
    [21-Oct-2019 02:10:59] Added manifest.json file with 6,05 KB to backup file list.
    [21-Oct-2019 02:10:59] 1. Trying to create backup archive …
    [21-Oct-2019 02:10:59] Compressing files as TarGz. Please be patient, this may take a moment.
    [21-Oct-2019 02:51:58] AVISO: File name "xxxxxx" is too long to be saved correctly in TarGz archive!
    [21-Oct-2019 02:54:54] AVISO: File name "xxxxxx.jpg.webp" is too long to be saved correctly in TarGz archive!
    [21-Oct-2019 02:55:26] AVISO: File name "xxxxxx.jpg.webp" is too long to be saved correctly in TarGz archive!
    [21-Oct-2019 05:07:52] Backup archive created.
    [21-Oct-2019 05:07:53] Tamanho do arquivo é 3,52 GB.
    [21-Oct-2019 05:07:53] 101877 arquivos com 4,45 GB em Arquivo.
    [21-Oct-2019 05:07:53] 1. Trying to send backup file to S3 Service …
    [21-Oct-2019 05:07:53] Connected to S3 Bucket "xxxxxx" in us-east-1
    [21-Oct-2019 05:07:54] Checking for not aborted multipart Uploads …
    [21-Oct-2019 05:07:54] Starting upload to S3 Service …
    [21-Oct-2019 05:13:55] Backup transferido para hxxxxxx.tar.gz.
    [21-Oct-2019 05:13:56] Um arquivo excluído no repositório da S3.
    [21-Oct-2019 05:13:56] 1. Trying to check database …
    [21-Oct-2019 05:14:13] Verifica??o de banco de dados feita!
    [21-Oct-2019 05:14:13] Um antigo log foi excluídos
    [21-Oct-2019 05:14:13] AVISO: Job finished with warnings in 11053 seconds. Please resolve them for correct execution.

    If I compare with another site I run, a 4.11 GB backup took 595 seconds

    Thread Starter zedomingues

    (@zedomingues)

    Today I had to cancel the backup job after 14219 seconds of execution.

    I can not understand which configuration may be wrong and generating all this delay to do the back up a 4.6 GB file

    below the backup job log:

    [INFO] BackWPup 3.6.10; A project of Inpsyde GmbH
    [INFO] WordPress 5.2.4 on XXXXXXXXXXXXXX
    [INFO] Log Level: Normal (translated)
    [INFO] BackWPup job: Backup Diário
    [INFO] Logfile is: XXXXXXXXXX
    [INFO] Arquivo de backup é: xxxxxxxxxxxx
    [16-Oct-2019 02:10:03] 1. Try to backup database …
    [16-Oct-2019 02:10:03] Conectado ao banco de dados xxxxxxxxx in  xxxxxxxxxxxxx
    [16-Oct-2019 02:10:45] Added database dump "xxxxxx.sql" with 734,41 MB to backup file list
    [16-Oct-2019 02:10:45] Database backup done!
    [16-Oct-2019 02:10:46] 1. Trying to make a list of folders to back up …
    [16-Oct-2019 02:10:51] Added "wp-config.php" to backup file list
    [16-Oct-2019 02:10:51] 1858 folders to backup.
    [16-Oct-2019 02:10:52] 1. Trying to generate a file with installed plugin names …
    [16-Oct-2019 02:10:52] Added plugin list file "xxxxxxxxx" with 4,53 KB to backup file list.
    [16-Oct-2019 02:10:52] 1. Trying to generate a manifest file …
    [16-Oct-2019 02:10:52] Added manifest.json file with 6,10 KB to backup file list.
    [16-Oct-2019 02:10:52] 1. Trying to create backup archive …
    [16-Oct-2019 02:10:53] Compressing files as ZipArchive. Please be patient, this may take a moment.
    [16-Oct-2019 06:07:01] ERRO: Aborted by user!
    [16-Oct-2019 06:07:01] ERRO: Job has ended with errors in 14219 seconds. You must resolve the errors for correct execution.

    any suggestions for correction?

    Thread Starter zedomingues

    (@zedomingues)

    Strange, with this change, now the backup takes 18512 seconds. I still find it very strange for a 3 GB backup to take more than 5 hours to complete.

    Thread Starter zedomingues

    (@zedomingues)

    certainly.
    tks

    Thread Starter zedomingues

    (@zedomingues)

    Ohhh

    now it works!

    Thank you for the clarifications

    Thread Starter zedomingues

    (@zedomingues)

    another backup log with finished with error.

    [INFO] BackWPup 3.4.1; A project of Inpsyde GmbH
    [INFO] WordPress 4.8.1 on [sensitive information]
    [INFO] Log Level: Normal 
    [INFO] BackWPup job: Rotina de Backup Diária Para Vendas Ativas
    [INFO] Logfile is: [sensitive information]
    [INFO] Backup file is: [sensitive information]
    [31-Aug-2017 03:40:48] 1. Try to backup database …
    [31-Aug-2017 03:40:48] Connected to database [sensitive information] on localhost
    [31-Aug-2017 03:40:53] Added database dump "[sensitive information]" with 29,70 MB to backup file list
    [31-Aug-2017 03:40:53] Database backup done!
    [31-Aug-2017 03:40:55] 1. Trying to make a list of folders to back up …
    [31-Aug-2017 03:41:00] Added "wp-config.php" to backup file list
    [31-Aug-2017 03:41:00] 2120 folders to backup.
    [31-Aug-2017 03:41:01] 1. Trying to generate a file with installed plugin names …
    [31-Aug-2017 03:41:01] Added plugin list file "[sensitive information]" with 8,54 KB to backup file list.
    [31-Aug-2017 03:41:01] 1. Trying to generate a manifest file …
    [31-Aug-2017 03:41:01] Added manifest.json file with 10,38 KB to backup file list.
    [31-Aug-2017 03:41:01] 1. Trying to create backup archive …
    [31-Aug-2017 03:41:01] Compressing files as ZipArchive. Please be patient, this may take a moment.
    [31-Aug-2017 03:50:42] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [31-Aug-2017 03:50:42] 2. Trying to create backup archive …
    [31-Aug-2017 03:58:46] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [31-Aug-2017 03:58:46] 3. Trying to create backup archive …
    [31-Aug-2017 04:36:43] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [31-Aug-2017 04:36:43] ERROR: Step aborted: too many attempts!
    [31-Aug-2017 04:36:43] 1. Trying to send backup file to S3 Service …
    [31-Aug-2017 04:36:59] Backup transferred to [sensitive information]
    [31-Aug-2017 04:36:59] 2 old logs deleted
    [31-Aug-2017 04:36:59] ERROR: Job has ended with errors in 3371 seconds. You must resolve the errors for correct execution.

    tks

    Thread Starter zedomingues

    (@zedomingues)

    Fala @claudiosanches

    primeiro, malz n?o responder aqui, me enrolei e acabei esquecendo.

    eu atualizei o plugin e funcionou corretamente, todavia, quando a compra é feita com o checkout do pagar.me ativado, a meta-data do código da compra (aliás, preciosa atualiza??o que você fez antes) n?o vai.

    quando eu notei aqui, voltei para o checkout do site e a meta-data foi.

    abs

    • This reply was modified 8 years, 2 months ago by zedomingues.
    Thread Starter zedomingues

    (@zedomingues)

    @claudiosanches

    Eu pensei a mesma coisa que vc (uma transa??o isolada), porém, numa primeira tentativa, fiz o teste no meu cart?o pessoal (que também uso pra testes) e n?o foi (estornou). Depois, liguei a API de testes, e erro foi confirmado.

    Pra tentar sair, desliguei o checkout do pagar.me e fiz duas transa??es (live e teste). Ambas passaram.

    Thread Starter zedomingues

    (@zedomingues)

    @claudiosanches

    Funcionou!
    que bizarro, uma vírgula influenciando em tudo!

    Muito obrigado!

    Forte abs

    Thread Starter zedomingues

    (@zedomingues)

    @claudiosanches

    Feito. Checkout normal ativado.

    API teste ainda está ativa.

    Vlw!

    Thread Starter zedomingues

    (@zedomingues)

    @claudiosanches

    o checkout do pagar.me foi ativado.

    vlw

    Thread Starter zedomingues

    (@zedomingues)

    @claudiosanches

    se tu puder ficar online no site nos próximos 5 minutos eu ativo o checkout do pagar.me

    pode ser?

    vlw!

    ps: vou colocar a API de teste

Viewing 15 replies - 1 through 15 (of 28 total)