All things Geek / OS / VM / Webservers

Pound Gateway Won’t Start on CentOS 7

ImelaLeave a comment

Problem

I had Setup the pound gateway as per the steps here. The issue was that the gateway wasn’t starting. The following error was on the log:

Sep 7 15:09:49 localhost systemd: Starting Pound Reverse Proxy And Load-balancer...
Sep 7 15:09:49 localhost pound: starting...
Sep 7 15:09:50 localhost pound: get_host(192.168.56.101, res, 0)
Sep 7 15:09:50 localhost pound: getaddrinfo OK
Sep 7 15:09:50 localhost pound: ret OK
Sep 7 15:09:50 localhost pound: done
Sep 7 15:09:50 localhost pound: get_host(192.168.56.101, res, 0)
Sep 7 15:09:50 localhost pound: getaddrinfo OK
Sep 7 15:09:50 localhost pound: ret OK
Sep 7 15:09:50 localhost pound: done
Sep 7 15:09:50 localhost pound: get_host(192.168.56.102, res, 0)
Sep 7 15:09:50 localhost pound: getaddrinfo OK
Sep 7 15:09:50 localhost pound: ret OK
Sep 7 15:09:50 localhost pound: done
Sep 7 15:09:50 localhost pound: get_host(192.168.56.103, res, 0)
Sep 7 15:09:50 localhost pound: getaddrinfo OK
Sep 7 15:09:50 localhost pound: ret OK
Sep 7 15:09:50 localhost pound: done
Sep 7 15:09:50 localhost systemd: Failed to read PID from file /var/run/pound.pid: Invalid argument
Sep 7 15:11:19 localhost systemd: pound.service operation timed out. Terminating.
Sep 7 15:11:19 localhost systemd: Failed to start Pound Reverse Proxy And Load-balancer.
Sep 7 15:11:19 localhost systemd: Unit pound.service entered failed state.

Solution

According to this mailing list, the solution is to edit the file pound.service shown below and remove the line with something like PID.

After editing, the file should have the following:

[root@localhost ~]# cat /usr/lib/systemd/system/pound.service
[Unit]
Description=Pound Reverse Proxy And Load-balancer
After=syslog.target network.target

[Service]
Type=forking
ExecStart=/usr/sbin/pound

[Install]
WantedBy=multi-user.target

Resources

[Pound Mailing List] pound won’t start

When i try to logon to my WordPress Backend with pound in front it tells me this error “You do not have sufficient permissions to access this page.”

 

Leave a comment