conntrackd crashes in SEGFAULT just after starting

Solution Verified - Updated -

Issue

  • The conntrackd service dies in SEGFAULT just after starting when using a custom configuration, as seen in the journal excerpt below:

    [...] kernel: conntrackd[385]: segfault at 10 ip 000000000040ea11 sp 00007ffd2c0c8080 error 4 in conntrackd[400000+34000]
[...] systemd[1]: conntrackd.service: main process exited, code=killed, status=11/SEGV
[...] systemd[1]: Unit conntrackd.service entered failed state.
[...] systemd[1]: conntrackd.service failed.

Environment

  • Red Hat Enterprise Linux 7 and later
    • conntrack-tools

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content