You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After three hours of debugging, I found that the latest PHP patch versions 8.1.22 and 8.2.9, which many people use, have a changed way of getting the PID after SIGCHLD (see php/php-src#11509). This change is reverted in the PHP development branch (php/php-src#11863).
This causes asynchronous jobs to not be marked as complete and cron.php to run indefinitely. When used with a daemon, this causes cron to stop completely as all daemonMaxProcessNumber processes are stuck.
The developers of spatie/async were quick to react to this change, so you need to update the dependency to the latest version.
NOTE: This is the relevant fix, that new dependency version adds:
The text was updated successfully, but these errors were encountered:
mozkomor05
changed the title
Old spatie/async version causes stuck cron
Old spatie/async version causes stuck cron with parallel execution
Aug 27, 2023
yurikuzn
changed the title
Old spatie/async version causes stuck cron with parallel execution
Jobs running in-parallel processes not working in PHP 8.1.22, 8.2.9 (exclusively)
Aug 27, 2023
After three hours of debugging, I found that the latest PHP patch versions 8.1.22 and 8.2.9, which many people use, have a changed way of getting the PID after SIGCHLD (see php/php-src#11509). This change is reverted in the PHP development branch (php/php-src#11863).
This causes asynchronous jobs to not be marked as complete and cron.php to run indefinitely. When used with a daemon, this causes cron to stop completely as all
daemonMaxProcessNumber
processes are stuck.The developers of spatie/async were quick to react to this change, so you need to update the dependency to the latest version.
NOTE: This is the relevant fix, that new dependency version adds:
https://github.com/spatie/async/blob/59985e70e94b8afb1ef1d65de73e8f80cddb4146/src/Pool.php#L323-L335
The text was updated successfully, but these errors were encountered: