Bug 1580054

Summary: haproxy fails to preserve previous UNIX socket
Product: [Fedora] Fedora Reporter: Lennart Jern <lennart.jern>
Component: haproxyAssignee: Ryan O'Hara <rohara>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: bperkins, carlwgeorge, jeremy, rohara
Target Milestone: ---   
Target Release: ---   
Hardware: armv7hl   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-21 17:26:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lennart Jern 2018-05-19 15:59:56 UTC 
Description of problem:
The haproxy service fails after upgrade from f27 to f28 with the following error message:
[ALERT] 138/111831 (9623) : Starting frontend GLOBAL: error when trying to preserve previous UNIX socket [/var/lib/haproxy/stats]

Version-Release number of selected component (if applicable):
haproxy-1.8.8-1.fc28

How reproducible:
Always

Steps to Reproduce:
1. Enable haproxy.service on f27
2. Upgrade to f28
3.

Actual results:
The haproxy service fails to start.

Expected results:
The haproxy service is able to run.

Additional info:
I tried reinstalling haproxy and starting it with the default haproxy.cfg but it did not help.
Removing /var/lib/haproxy/stats does not help, just gives the following error:
[ALERT] 138/175716 (30194) : Starting frontend GLOBAL: cannot bind UNIX socket [/var/lib/haproxy/stats]

ls -l /var/lib/haproxy/stats
srwxr-xr-x. 1 root root 0 10 maj 21.50 /var/lib/haproxy/stats
Comment 1 Ryan O'Hara 2018-05-20 15:57:29 UTC 
Please check if selinux is enabled. If so, check you audit log for AVCs. I'm guessing this is a duplicate of rhbz#1575365.
Comment 2 Lennart Jern 2018-05-21 17:26:06 UTC 
It is indeed a duplicate of rhbz#1575365. Closing

*** This bug has been marked as a duplicate of bug 1575365 ***