Pulledpork: Deep recursion on subroutine “main::compare_md5”

This morning the error disappeared by itself. I didn’t do anything because I didn’t find a solution …

Instead another error appeared:

/etc/cron.daily/pulledpork:

Deep recursion on subroutine “main::compare_md5” at /usr/bin/pulledpork line 386.

Error downloading ET OPEN Ruleset Download Instructions 504 Gateway Time-out [ 504 ]

Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286

What is this error and can it be fixed?

Thanks for your help

It comes from Suricata IPS. Couldn’t download some ruleset.
Possibly from EmergingThreats ruleset and the way perl tar processes it:

A quick search brought up this (a more extensive search could bring other hints):

Thank you @dnutan !

Until then, I understood that the meerkat problem exists with one of the rules, but I don’t understand the reason.

I’m also trying to find a solution but I can’t find a solution. There was no update for suricata for a long time, only the rules were updated in the background. They also write about this in the attached link, but there is no solution, because it seems that there may be a problem with the creation and format of the rule. I hope the package makers will notice and fix it, until then the meerkat rule won’t work.

Does suricata still work or does the Nethserver remain unprotected?

A fix should come through soon:

Suricata still works fine.
The fix has been released, automatic rule update will work again from tonight.

Thanks @filippo_carletti !

The update notification has arrived. In the evening, when everyone has finished the work, I will update and in the morning I will see the result of the repair.

Thanks everyone for your help.