Skip to content
This repository has been archived by the owner on Feb 7, 2021. It is now read-only.

Centos installations have wrong path for agent_secret (4.1) #166

Closed
hugocruz opened this issue Apr 20, 2016 · 1 comment
Closed

Centos installations have wrong path for agent_secret (4.1) #166

hugocruz opened this issue Apr 20, 2016 · 1 comment

Comments

@hugocruz
Copy link
Contributor

hugocruz commented Apr 20, 2016

If you install either centos6 or centos7 :

$rpm -q varnish-agent
varnish-agent-4.1.0-1.el7.centos.x86_64

$ sudo systemctl start varnish-agent
Job for varnish-agent.service failed. See 'systemctl status varnish-agent.service' and 'journalctl -xn' for details.
$sudo journalctl -xe

Apr 20 21:16:46 centos7-varnish4.1 varnish-agent[21864]: varnish-agent: Cannot open file /usr/etc/varnish/agent_secret for reading: No such file or director
Apr 20 21:16:46 centos7-varnish4.1 varnish-agent[21864]: varnish-agent: No password present. Put one in /usr/etc/varnish/agent_secret using "user:password"
Apr 20 21:16:46 centos7-varnish4.1 systemd[1]: varnish-agent.service: control process exited, code=exited status=1
Apr 20 21:16:46 centos7-varnish4.1 systemd[1]: Failed to start Varnish Agent.

Path for agent_secret is wrong. Should be /etc/varnish/agent_secret
If the secret path is added in the params it works. I guess is something with the .spec file. Looking into it.

I think the issue is related to this:

${sysconfdir} in

AGENT_CONF_DIR='${sysconfdir}/varnish'

@hugocruz
Copy link
Contributor Author

hugocruz commented Apr 20, 2016

From the jenkins build:

Debian: build has sysconfdir=/etc

In centos no sysconfdir is defined, just:
./configure --prefix=/usr --localstatedir=/var/lib

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant