Could Not Get Hold Of Varnishd Is It Running

Recently, I encountered an issue where I couldn’t get hold of varnishd, and I started to question if it was running at all. As someone who is passionate about running sports, I understand the frustration of encountering unexpected hurdles, and I was determined to get to the bottom of this issue.

Understanding the Problem

First, I had to understand the role of varnishd in the context of web performance. Varnish is a caching HTTP reverse proxy, which means it stores a copy of web pages served by the web server. This can significantly improve the speed and reliability of a website. Varnishd is the daemon process that manages the caching and serving of cached content.


I started by checking if varnishd was running as expected. I ran the command ps aux | grep varnishd to list all processes and look for any running instances of varnishd. To my surprise, there were no results returned, indicating that the varnishd process was not running.

Checking the Logs

Next, I examined the system logs to see if there were any relevant error messages or clues. I used the command journalctl -xe | grep varnishd to focus on logs related to varnishd. This step is crucial in identifying any potential issues that may have caused varnishd to stop running.

Restarting varnishd

After reviewing the logs, I attempted to restart varnishd using the command sudo systemctl restart varnish. This command initiates the restart of the varnishd service. However, despite restarting the service, I still couldn’t get hold of varnishd.

Verifying the Configuration

I then turned my attention to the configuration of varnishd. I checked the configuration file located at /etc/varnish/default.vcl to ensure that the settings were correct. I also reviewed the varnish.params file to verify the runtime parameters.

Checking Port Usage

Another aspect I examined was the port usage. I used the command netstat -tuln | grep :80 to check if varnishd was listening on the specified port (port 80 by default). It was essential to verify that there were no port conflicts preventing varnishd from running.


After thorough investigation and troubleshooting, I was able to determine that the issue preventing me from getting hold of varnishd was related to a misconfiguration in the settings. By rectifying the configuration and restarting the service, I successfully resolved the issue. This experience served as a reminder of the importance of meticulous attention to detail and systematic troubleshooting in the world of running sports.