Comment 11 for bug 1272840

Hi all,
  since I m running Fuel 4.0 and hardly can move to next releases now, can you kindly suggest me a "hot" workaround in order to fix the problem without patching??

According to your discussion(pavel) the only worth option according to my need is to :
1) edit "/etc/init.d/corosync"
2) add ""ulimit -n 1024000" line before any" start" command in the script.
3) restart corosync

can you confirm this workaround ? is there any another choice?

This bug heavily affects the system as each time it occurs , I need to restart in sequence all of the three controller-nodes to recover the situation

many thanks for the support

mauro