Cron job stuck

  • Resolved rafael777

    (@rafael777)


    3 years, 11 months ago

    Hi,

    I received an email from my hosting provider saying that they noticed a large number of cron processes initiated by UpdraftPlus were stuck and continue to get initiated, which is consuming lots of server resources. They had to kill all the stalled processes manually in order to free up the CPU and memory.

    They told me to disable the plugin for the time being and install another backup plugin, or to reach out to you asking to look into it.

    Here’s the process that keeps spawning and getting stuck:

    amenvame 849265 0.0 0.3 500732 127380 ? S Dec06 2:58 | \_ /opt/cpanel/ea-php72/root/usr/bin/php-cgi /home/amenvame/public_html/amenvamen/wp-cron.php
amenvame 849721 0.0 0.0 103732 956 ? S Dec06 0:00 | | \_ /usr/bin/zip -n .jpg:.JPG:.jpeg:.JPEG:.png:.PNG:.gif:.GIF:.zip:.ZIP:.gz:.GZ:.bz2:.BZ2:.xz:.XZ:.rar:.RAR:.mp3:.MP3:.mp4:.MP4:.mpeg:.MPEG:.avi:.AVI:.mov:.MOV -v -@ /home/amenvame/public_html/amenvamen/wp-content/updraft/backup_2020-12-06-1957_Amen_V039Amen_681f144551da-plugins.zip.tmp
amenvame 893932 0.0 0.3 500596 128604 ? S Dec06 2:59 | \_ /opt/cpanel/ea-php72/root/usr/bin/php-cgi /home/amenvame/public_html/amenvamen/wp-cron.php
amenvame 894001 0.0 0.0 103732 952 ? S Dec06 0:00 | \_ /usr/bin/zip -n .jpg:.JPG:.jpeg:.JPEG:.png:.PNG:.gif:.GIF:.zip:.ZIP:.gz:.GZ:.bz2:.BZ2:.xz:.XZ:.rar:.RAR:.mp3:.MP3:.mp4:.MP4:.mpeg:.MPEG:.avi:.AVI:.mov:.MOV -v -@ /home/amenvame/public_html/amenvamen/wp-content/updraft/backup_2020-12-06-1957_Amen_V039Amen_681f144551da-plugins.zip.tmp
amenvame 959701 0.0 0.3 500596 128656 ? S Dec06 2:57 | \_ /opt/cpanel/ea-php72/root/usr/bin/php-cgi /home/amenvame/public_html/amenvamen/wp-cron.php
amenvame 959788 0.0 0.0 103732 956 ? S Dec06 0:00 | \_ /usr/bin/zip -n .jpg:.JPG:.jpeg:.JPEG:.png:.PNG:.gif:.GIF:.zip:.ZIP:.gz:.GZ:.bz2:.BZ2:.xz:.XZ:.rar:.RAR:.mp3:.MP3:.mp4:.MP4:.mpeg:.MPEG:.avi:.AVI:.mov:.MOV -v -@ /home/amenvame/public_html/amenvamen/wp-content/updraft/backup_2020-12-06-1957_Amen_V039Amen_681f144551da-plugins.zip.tmp

    Any ideas?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter rafael777

    (@rafael777)

    Update: I just removed the “plugins” (and “themes”) folder from the backup as it seemed from their logs that the culprit might be related to the backup of the plugins folder. I then ran a manual backup to see what happens. Turns out the backups don’t even work anymore. It just hangs on “Creating file backup zips (Uploads)”.

    Here’s the log from the backup I just ran: https://drive.google.com/file/d/13C5Ic5WqZLt3QoKctwfK325lt1tgH5sP/view?usp=sharing

    And here’s the log from the last successful backup from last week (the one where my hosting provider complained about): https://drive.google.com/file/d/1xhr8lWv5wrA5J1exF5Y8JRIUR6sp3q1F/view?usp=sharing

    • This reply was modified 3 years, 11 months ago by rafael777.
    Thread Starter rafael777

    (@rafael777)

    OK the manual backup I ran just completed… but once again, the hosting provider said that lots of processes continue to be initiated, and continue to run even after the backup is completed… These processes end up hogging all of the server resources and the hosting provider has to kill the processes manually.

    My hosting provider told me to deactivate the plugin immediately.

    Please advise.

    Plugin Contributor bcrodua

    (@bcrodua)

    Hi Rafael,

    Please check this FAQ on how to stop a backup in progress – https://updraftplus.com/faqs/how-do-i-stop-an-in-progress-backup/

    Let me know if that helps resolve the issue.

    Thanks,
    Bryle

    Thread Starter rafael777

    (@rafael777)

    The problem isn’t canceling backups in progress. The problem is that there are still backup processes running in the background, consuming resources, days after the backup has already been completed. These backups don’t appear in the UI, the only way to cancel them is to kill the server processes (which I can’t do myself, only my hosting provider can)

    From the log, it appears that there is no binary zip executable or ZipArchive available. When this happens, UpdraftPlus has to use the slowest method for creating zip files. It might be work asking your hosts/server admin to enable the PHP ZipArchive module or a zip executable.

    You could also try reducing your archive split. To do this goto the ‘Expert settings’ section of the UpdraftPlus page, and reduce the default setting for how much data is stored in each zip file. e.g. Reduce it from the default of 400Mb down to 100Mb. This will mean that UpdraftPlus spends less time in manipulating large zip files – which can use a lot of resources and be quite time-consuming, especially on slower servers.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Cron job stuck’ is closed to new replies.