Cluster crashes when using long parameter in cluster.conf

Solution Verified - Updated -

Issue

When trying to include long parameters into the file /etc/cluster/cluster.conf (e.g. SCSI fencing devices that are used in configuration) corosync crashes with signal 6 and coredumps. For example following configuration works:

 <fencedevice agent="fence_scsi" devices="/dev/a1,/dev/a2,/dev/a3,/dev/a4,/dev/a5" name="SCSI_Reservation_Fencing"/>

But following doesn't:

 <fencedevice agent="fence_scsi" devices="/dev/a1,/dev/a2,/dev/a3,/dev/a4,/dev/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa5" name="SCSI_Reservation_Fencing"/>

This "aaaa" name is used to verify the problem. Originally we had five entries like "/dev/disk/by-id/dm-uuid-mpath-360a9800037543735305d424147624b7a".

Environment

  • Red Hat Enterprise Linux 6
  • Red Hat Enterprise Linux High Availability add-on

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