noticed my secondary node didn't have this config issue after forcing a regenerate while it was carp master.
uninstalled the haproxy plugin on primary node and reinstalled -- the error is gone now!
uninstalled the haproxy plugin on primary node and reinstalled -- the error is gone now!