lvsd segmentation fault on configuration reload

Solution Verified - Updated -

Issue

When updating the LVS-configuration and using reload to effect the changes in the configuration, a segmentation fault was observed. The lvsd ends up as a defunct process (but pulse does not restart it), and all nanny processes are inherited by the init process. Restarting lvs afterwards creates a new lvsd with new nanny processes, but of course the old nanny processes are not cleaned up.

Environment

  • Red Hat Enterprise Linux 6, piranha-0.8.5-9.el6

  • Red Hat Enterprise Linux 5, piranha-0.8.4-22.el5

  • Reload of LVS configuration, e.g.

    • service pulse reload,

    • kill -HUP $(pgrep pulse), or

    • kill -HUP $(pgrep lvsd)

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