Mensaje de error al intentar iniciar el barniz en centos 5.5

Acabo de instalar y configurar barniz para trabajar en el puerto 80, y Apache para trabajar en el puerto 8080. Estoy tratando de iniciar barniz con el service varnish start command service varnish start , pero me dio este error:

varnishd muerto pero existe file pid

He editado esta configuration en /etc/sysconfig/varnish :

 DAEMON_OPTS="-a :80 \ -T localhost:6082 \ -f /etc/varnish/default.vcl \ -u varnish -g varnish \ -S /etc/varnish/secret \ -s file,/var/lib/varnish/varnish_storage.bin,1G" 

Este es el contenido del file default.vcl:

 backend default { .host = "127.0.0.1"; .port = "8080"; .connect_timeout = 600s; .first_byte_timeout = 600s; .between_bytes_timeout = 600s; } sub vcl_recv { if (req.request != "GET" && req.request != "HEAD" && req.request != "PUT" && req.request != "POST" && req.request != "TRACE" && req.request != "OPTIONS" && req.request != "DELETE") { // Non-RFC2616 or CONNECT which is weird. return (pipe); } if (req.request != "GET" && req.request != "HEAD") { // We only deal with GET and HEAD by default return (pass); } // Remove has_js and Google Analytics cookies. set req.http.Cookie = regsuball(req.http.Cookie, "(^|;\s*)(__[az]+|__utma_a2a|has_js)=[^;]*", ""); // To users: if you have additional cookies being set by your system (eg // from a javascript analytics file or similar) you will need to add VCL // at this point to strip these cookies from the req object, otherwise // Varnish will not cache the response. This is safe for cookies that your // backend (Drupal) doesn't process. // // Again, the common example is an analytics or other Javascript add-on. // You should do this here, before the other cookie stuff, or by adding // to the regular-expression above. // Remove a ";" prefix, if present. set req.http.Cookie = regsub(req.http.Cookie, "^;\s*", ""); // Remove empty cookies. if (req.http.Cookie ~ "^\s*$") { unset req.http.Cookie; } if (req.http.Authorization || req.http.Cookie) { // Not cacheable by default return (pass); } // Skip the Varnish cache for install, update, and cron if (req.url ~ "install\.php|update\.php|cron\.php") { return (pass); } // Normalize the Accept-Encoding header // as per: http://varnish-cache.org/wiki/FAQ/Compression if (req.http.Accept-Encoding) { if (req.url ~ "\.(jpg|png|gif|gz|tgz|bz2|tbz|mp3|ogg)$") { # No point in compressing these remove req.http.Accept-Encoding; } elsif (req.http.Accept-Encoding ~ "gzip") { set req.http.Accept-Encoding = "gzip"; } else { # Unknown or deflate algorithm remove req.http.Accept-Encoding; } } // Let's have a little grace set req.grace = 30s; return (lookup); } sub vcl_hash { if (req.http.Cookie) { hash_data (req.http.Cookie); } } // Strip any cookies before an image/js/css is inserted into cache. sub vcl_fetch { if (req.url ~ "\.(png|gif|jpg|swf|css|js)$") { // For Varnish 2.0 or earlier, replace beresp with obj: // unset obj.http.set-cookie; unset beresp.http.set-cookie; } } // Set a header to track a cache HIT/MISS. sub vcl_deliver { if (obj.hits > 0) { set resp.http.X-Varnish-Cache = "HIT"; } else { set resp.http.X-Varnish-Cache = "MISS"; } } sub vcl_error { // Let's deliver a friendlier error page. // You can customize this as you wish. set obj.http.Content-Type = "text/html; charset=utf-8"; synthetic {" <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html> <head> <title>"} + obj.status + " " + obj.response + {"</title> <style type="text/css"> #page {width: 400px; padding: 10px; margin: 20px auto; border: 1px solid black; background-color: #FFF;} p {margin-left:20px;} body {background-color: #DDD; margin: auto;} </style> </head> <body> <div id="page"> <h1>Page Could Not Be Loaded</h1> <p>We're very sorry, but the page could not be loaded properly. This should be fixed very soon, and we apologize for any inconvenience.</p> <hr /> <h4>Debug Info:</h4> <pre>Status: "} + obj.status + {" Response: "} + obj.response + {" XID: "} + req.xid + {"</pre> </div> </body> </html> "}; return(deliver); } 

¿Cómo soluciono este problema?

2 Solutions collect form web for “Mensaje de error al intentar iniciar el barniz en centos 5.5”

. . . asegúrese de que Varnish no se está ejecutando, y si no se elimina el file PID?

Compruebe el file secreto en / etc / verniz. Debe tener un valor.

  • ¿Cómo puedo secar esta configuración de Nginx?
  • Proxy inverso para 3 sitios web todo en context raíz
  • Manejo de errores con php en nginx reverse proxy y respuesta de correo a los administradores
  • Proxy SSL inverso: NGINX delante de NGINX y Joomla
  • ¿Cómo puedo usar el service web de apache para reescribir URL?
  • cómo puedo get el valor del server upstream en la configuration de proxy inverso nginx
  • Cómo invertir el proxy con o sin barra diagonal
  • Proxy inverso para un subdirectory en nginx
  • El barniz no funciona con Apache Virtualhosts
  • Modificar los datos que son procesados ​​por nginx sobre la marcha
  • SharePoint MOSS - Servir contenido HTTP en una página HTTPS sin contenido mixto ¿Advertencia?
  • Proxy de SSL en nginx - comportamiento diferente en diferentes clientes
  • proxy inverso con NGINX a dos serveres back-end
  • El linux y los temas del servidor de Windows, como ubuntu, centos, apache, nginx, debian y consejos de red.