I'm in the process of upgrading from Drupal 8 to 9. Using purge version 3.0 runs as expected, however after updating to purge 3.2, I get the following whenever I run drush updb
[error] purger_varnishbundled_6bb40645e9: item failed due GuzzleHttp\Exception\ClientException, details (JSON): {"msg":"Client error: `BAN http:\/\/127.0.0.1:6081\/` resulted in a `400 Bad Request` response","uri":"http:\/\/127.0.0.1:6081\/","method":"BAN","guzzle_opt":{"http_errors":true,"connect_timeout":1,"timeout":1},"headers":{"user-agent":"varnish_purger module for Drupal 8.","cache-tags":"config:..."}}
Using Drupal 9.3 with Purge version 3.2
Run drush updb
As of now using Purge version 3.0 does not throw the error.
Fix purge version 3.2
None
TBD
TBD
Active
3.2
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Can confirm this is still an issue in version 3.4 (using Drupal 9.5).
The errors seem to go away when you disable the `purge_processor_lateruntime` module which may be partially be explained by
https://www.drupal.org/project/purge/issues/3264141 →
. It seems that the fact that the Lateruntime module now uses kernel.terminate rather than kernal.finish, means that it runs on every drush command, sometimes causing this error.