Public bug reported: On Ubuntu 26.04 (resolute), ospd-openvas 22.10.1 crashes as soon as a scan is started. Scans stop at 0% and systemd restarts the service.
Cause: Python 3.14 changed the default multiprocessing start method on Linux from “fork” to “forkserver”. ospd-openvas passes objects that cannot be pickled (Redis connection pool containing an RLock) to multiprocessing.Process. Traceback excerpt: TypeError: cannot pickle ‘_thread.RLock’ object when serializing redis.connection.ConnectionPool object [...] when serializing multiprocessing.context.Process object (See the attached file for the detailed journal) Workaround: forcing the “fork” start method (multiprocessing.set_start_method(‘fork’, force=True) via sitecustomize.py) fixes the issue. This is fixed upstream in ospd-openvas 22.10.5 (released 2026-08-21, “issue with multiprocessing start method”, commit a99fe321): https://github.com/greenbone/ospd-openvas/releases/tag/v22.10.5 The current upstream release is 22.10.6. Please consider updating the package or backporting the fix to resolute. See also: https://forum.greenbone.net/t/kali-scans-fail-at-0-vas-23-45-1-gvm-libs-22-41-0/22473 ** Affects: ospd-openvas (Ubuntu) Importance: Undecided Status: New ** Attachment added: "ospd-openvas-journal.txt" https://bugs.launchpad.net/bugs/2171586/+attachment/6011208/+files/ospd-openvas-journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2171586 Title: ospd-openvas crashes on scan start with Python 3.14: cannot pickle ‘_thread.RLock’ object To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ospd-openvas/+bug/2171586/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
