FS#77672 - [rspamd] 3.4-2 refuses to start after hyperscan upgrade 5.4.0-3 -> 5.4.1-1

Attached to Project: Community Packages
Opened by razer raz (razer) - Tuesday, 28 February 2023, 07:54 GMT
Last edited by Maxime Gauduin (Alucryd) - Monday, 20 March 2023, 13:12 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

rspamd 3.4-2 refuses to start after hyperscan upgrade from 5.4.0-3 to 5.4.1-1 with error message:
rspamd_multipattern_compile: fatal error: cannot allocate scratch space for hyperscan: -5

I suppose it needs to be rebuilded from new hyperscan version

Steps to reproduce:

Upgrade hyperscan
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Monday, 20 March 2023, 13:12 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.5-1
Comment by Toolybird (Toolybird) - Tuesday, 28 February 2023, 20:18 GMT
Starts fine here in a fresh VM with default config. Must be something about your setup triggering it..

PS. Please read the guidelines about bug severity level [1]

[1] https://wiki.archlinux.org/title/Bug_reporting_guidelines#Severity
Comment by wommel (wommel) - Wednesday, 01 March 2023, 08:50 GMT
Issue exists upstream https://github.com/rspamd/rspamd/issues/4409 .
Apparently relates to existing state so does not occur for fresh install.
Comment by Oleksandr Natalenko (post-factum) - Wednesday, 01 March 2023, 14:55 GMT
I can confirm the issue in my setup as well.
Comment by Witit Sujjapong (witit) - Thursday, 02 March 2023, 11:26 GMT
Same here. Solved by removing /var/lib/rspamd/*.unsr and restart. Refer to https://github.com/rspamd/rspamd/issues/4329.
Comment by Jonne Haß (MrZYX) - Thursday, 09 March 2023, 11:35 GMT
Same here, downgrading hyperscan to 5.4.0-3 seems to work fine as well for now.

Maybe https://github.com/rspamd/rspamd/commit/e88a512b2f370b3fcf5b0ff1205a0a84d156e060 can be backported?
Comment by Jonne Haß (MrZYX) - Saturday, 18 March 2023, 13:47 GMT
There's a new release now which should include the fix: https://github.com/rspamd/rspamd/releases/tag/3.5
Comment by Oleksandr Natalenko (post-factum) - Monday, 20 March 2023, 10:07 GMT
I can confirm v3.5 fixes the issue with new hyperscan package.

Loading...