- Issue created by @nicxvan
- πΊπΈUnited States nicxvan
The error is thrown in the purge module, but only happens when the varnish image purge module is also enabled.
- πΊπΈUnited States nicxvan
After further investigation this is not from the varnish image purger, it's the varnish purger module in general, if there is a varnish purger enabled then it fails.
- πΊπΈUnited States nicxvan
This also occurs on config import if there is config to import. If there are no config changes config import is fine.
- πΈπͺSweden MiSc
Thanks for the report. I never had this issue myself, do you have steps to reproduce the error? Which version of the Purge module are you using?
- Status changed to Postponed: needs info
about 1 year ago 8:36pm 29 October 2023 - πΊπΈUnited States nicxvan
For me it occurs when I have a cache tag invalidation set to an ip address with ban requests and then run a drush command that accomplishes something.
E.g. drush cim when there are config changes to import, updb when there is a database update or cron when there is a batch to process.I am using the following:
queuers
core tags, p:queue-add, Purge blocksQueue
databaseProcessors
p:invalidate, p:queue-work, Purge blocksThis only started after updating to Drupal 10 and Drush 11.
I am using drupal/purge 3.5
I am using drupal/varnish_purge 2.2.0 - πͺπΈSpain vidorado Pamplona (Navarra)
@Nicxvan, Maybe it is related with this issue and you have, like me, a patch applied?
https://www.drupal.org/project/purge/issues/2921309 β
https://www.drupal.org/files/issues/2921309-17-port-purge-drush-9.patch β