Issue

• We are trying to setup haproxy with multi process option using nbproc parameter where each of the process will be tied to specific CPU using cpu-map parameter.
• We see following messages when the haproxy service is started on the nodes:

Jun  9 15:16:53 localhost haproxy-systemd-wrapper: [WARNING] 159/151653 (1715) : stats socket will not work as expected in multi-process mode (nbproc > 1), you should force process binding globally using 'stats bind-process' or per socket using the 'process' attribute.
Jun  9 15:17:00 localhost haproxy-systemd-wrapper: [WARNING] 159/151700 (1734) : Proxy 'stats': in multi-process mode, stats will be limited to process assigned to the current request.
Jun  9 15:17:00 localhost haproxy-systemd-wrapper: [WARNING] 159/151700 (1734) : Proxy 'Group-1': in multi-process mode, stats will be limited to process assigned to the current request.
Jun  9 15:17:00 localhost haproxy-systemd-wrapper: [WARNING] 159/151700 (1734) : Proxy 'Group-2': in multi-process mode, stats will be limited to process assigned to the current request.
Jun  9 15:17:00 localhost haproxy-systemd-wrapper: [WARNING] 159/151700 (1734) : Proxy 'Group-3': in multi-process mode, stats will be limited to process assigned to the current request.
Jun  9 15:17:00 localhost haproxy-systemd-wrapper: [WARNING] 159/151700 (1734) : Proxy 'Group-4': in multi-process mode, stats will be limited to process assigned to the current request.
Jun  9 15:17:00 localhost haproxy-systemd-wrapper: [WARNING] 159/151700 (1734) : Proxy 'Group-5': in multi-process mode, stats will be limited to process assigned to the current request.
Jun  9 15:17:00 localhost haproxy-systemd-wrapper: [WARNING] 159/151700 (1734) : stats socket will not work as expected in multi-process mode (nbproc > 1), you should force process binding globally using 'stats bind-process' or per socket using the 'process' attribute.

• Why do such messages appear?
• How to avoid such warning messages?