1

I have a problem with starting vanishncsa. after rebooting a VM, the varnish daemon does not start or even enable.

here is the log:

 [root@respina ~]# systemctl status varnishncsa  
     ● varnishncsa.service

     Varnish Cache HTTP accelerator NCSA logging daemon     Loaded: loaded >(/usr/lib/systemd/system/varnishncsa.service; enabled; vendor
     preset:disabled)     Active: failed (Result: exit-code) since Mon
     2018-10-29 08:46:50 +0330; 9min ago

      Oct 29 08:46:50 respina.cache.aba.digital systemd[1]: Starting Varnish
      Cache HTTP accelerator NCSA logging ...... Oct 29 08:46:50
     respina.cache.aba.digital systemd[1]: varnishncsa.service: control
      process exited, code=exi...s=1 Oct 29 08:46:50
      respina.cache.aba.digital systemd[1]: Failed to start Varnish Cache
      HTTP accelerator NCSA l...on. Oct 29 08:46:50
      respina.cache.aba.digital systemd[1]: Unit varnishncsa.service entered
      failed state. Oct 29 08:46:50 respina.cache.aba.digital systemd[1]:
      varnishncsa.service failed. Hint: Some lines were ellipsized, use -l
      to show in full.

closed as unclear what you're asking by Rui F Ribeiro, thrig, schily, Jeff Schaller, RalfFriedl Oct 29 '18 at 17:33

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • you'll probably need to find where systemd is hiding (or binarily corrupting) the logs, or to try manually starting up the daemon to see what is awry – thrig Oct 29 '18 at 14:12

Browse other questions tagged or ask your own question.