我们正在尝试在 Cent OS 6.5 64 上安装 varnish，但无法使其作为服务运行。以下错误可能是什么原因造成的？
[root@server]# service varnish start
Starting Varnish Cache: 0
[FAILED]
这很完美，它与配置中的 DAEMON_OPTS 参数相同。
varnishd -a :80 -T localhost:6082 -b localhost:8080 -u varnish -g varnish -s file,/var/lib/varnish/varnish_storage.bin,1G
我在清漆论坛这给了我这个：
[root@server]# varnishd -C -f /etc/sysconfig/varnish
Message from VCC-compiler:
VCL version declaration missing
Update your VCL to Version 4 syntax, and add
vcl 4.0;
on the first line the VCL files.
('input' Line 8 Pos 1)
NFILES=131072
######-------
Running VCC-compiler failed, exit 1
VCL compilation failed
但是我们没有使用任何 VCL，那么为什么它会抱怨 VCL？
清漆配置文件：
# Configuration file for varnish
#
# /etc/init.d/varnish expects the variable $DAEMON_OPTS to be set from this
# shell script fragment.
#
# Maximum number of open files (for ulimit -n)
NFILES=131072
# Locked shared memory (for ulimit -l)
# Default log size is 82MB + header
MEMLOCK=82000
# Maximum number of threads (for ulimit -u)
NPROCS="unlimited"
# Maximum size of corefile (for ulimit -c). Default in Fedora is 0
# DAEMON_COREFILE_LIMIT="unlimited"
# Set this to 1 to make init script reload try to switch vcl without restart.
# To make this work, you need to set the following variables
# explicit: VARNISH_VCL_CONF, VARNISH_ADMIN_LISTEN_ADDRESS,
# VARNISH_ADMIN_LISTEN_PORT, VARNISH_SECRET_FILE, or in short,
# use Alternative 3, Advanced configuration, below
#RELOAD_VCL=1
# This file contains 4 alternatives, please use only one.
## Alternative 1, Minimal configuration, no VCL
#
# Listen on port 6081, administration on localhost:6082, and forward to
# content server on localhost:8080. Use a fixed-size cache file.
#
DAEMON_OPTS="-a :80 -T localhost:6082 -b localhost:8080 -u varnish -g varnish -s file,/var/lib/varnish/varnish_storage.bin,1G"
## Alternative 2, Configuration with VCL
#
# Listen on port 6081, administration on localhost:6082, and forward to
# one content server selected by the vcl file, based on the request. Use a
# fixed-size cache file.
#
# DAEMON_OPTS="-a :80 -T localhost:6699 -f /etc/varnish/default.vcl -u varnish -g varnish -S /etc/varnish/secret -s malloc,1G"
## Alternative 3, Advanced configuration
#
# See varnishd(1) for more information.
#
# # Main configuration file. You probably want to change it :)
#VARNISH_VCL_CONF=/etc/varnish/default.vcl
#
# # Default address and port to bind to
# # Blank address means all IPv4 and IPv6 interfaces, otherwise specify
# # a host name, an IPv4 dotted quad, or an IPv6 address in brackets.
# VARNISH_LISTEN_ADDRESS=
#VARNISH_LISTEN_PORT=80
#
# # Telnet admin interface listen address and port
#VARNISH_ADMIN_LISTEN_ADDRESS=127.0.0.1
#VARNISH_ADMIN_LISTEN_PORT=6082
#
# # Shared secret file for admin interface
#VARNISH_SECRET_FILE=/etc/varnish/secret
#
# # The minimum number of worker threads to start
#VARNISH_MIN_THREADS=50
#
# # The Maximum number of worker threads to start
#VARNISH_MAX_THREADS=1000
#
# # Idle timeout for worker threads
#VARNISH_THREAD_TIMEOUT=120
#
# # Cache file size: in bytes, optionally using k / M / G / T suffix,
# # or in percentage of available disk space using the % suffix.
#VARNISH_STORAGE_SIZE=256M
#
# # Backend storage specification
#VARNISH_STORAGE="malloc,${VARNISH_STORAGE_SIZE}"
#
# # Default TTL used when the backend does not specify one
VARNISH_TTL=120
#
# # DAEMON_OPTS is used by the init script. If you add or remove options, make
# # sure you update this section, too.
#DAEMON_OPTS="-a ${VARNISH_LISTEN_ADDRESS}:${VARNISH_LISTEN_PORT} \
# -f ${VARNISH_VCL_CONF} \
# -T ${VARNISH_ADMIN_LISTEN_ADDRESS}:${VARNISH_ADMIN_LISTEN_PORT} \
# -t ${VARNISH_TTL} \
# -p thread_pool_min=${VARNISH_MIN_THREADS} \
# -p thread_pool_max=${VARNISH_MAX_THREADS} \
# -p thread_pool_timeout=${VARNISH_THREAD_TIMEOUT} \
# -u varnish -g varnish \
# -S ${VARNISH_SECRET_FILE} \
# -s ${VARNISH_STORAGE}"
#
## Alternative 4, Do It Yourself. See varnishd(1) for more information.
#
# DAEMON_OPTS=""
注意：/var/log/varnish也是空的并且没有提供任何线索。
更新：
[root@server]# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 54665
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 54665
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
更新2：
如果我这样做，Varnish 就会启动：
bash -x /etc/init.d/varnish start
但不是
/etc/init.d/varnish start
有什么区别呢？
答案1
我遇到了同样的问题，我找到了原因。
这是由 SELinux 引起的，您可以暂时禁用它， echo 0 >/selinux/enforce但不建议这样做，您应该创建一个策略文件来运行它。我可能会在有空的时候再回来讨论这个问题。
答案2
执行bash -x /etc/init.d/varnish restart以查找 varnish 真正尝试启动的选项，然后尝试在 cli 上使用它们运行。
答案3
假设你这样做了不是修改你init.d的Varnish脚本（尝试使用 md5 算法）
[root@6svprx01 ~]# head -1 /etc/init.d/varnish
#! /bin/sh
[root@6svprx01 ~]# rpm -q varnish
varnish-3.0.6-1.el5.centos.x86_64
[root@6svprx01 ~]# md5sum /etc/init.d/varnish
a69b3b55a8d5da5b9b9c24a62774aa80 /etc/init.d/varnish
[root@6svprx01 ~]# service varnish
Usage: /etc/init.d/varnish {start|stop|status|restart|condrestart|try-restart|reload|force-reload}
[root@6svprx01 ~]# service varnish status
varnishd (pid 6188) is running...
[root@6svprx01 ~]#
还：
varnishd -C -f /etc/sysconfig/varnish
不正确，应为：
varnishd -C -f /etc/varnish/default.vcl
答案4
我遇到了类似的问题，发现在 Ubuntu 上（我知道这是 CentOs，但我认为它可能仍然有用）我需要配置服务如何启动，/etc/systemd/system/varnish.service.d/override.conf类似于下面这样：
ExecStart=/usr/sbin/varnishd -j unix,user=vcache -F -a :80 -T localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret -s malloc,1024m
这是为了代替设置守护进程配置/etc/default/varnish，但对我来说似乎不起作用。