Quantcast
Channel: Active questions tagged ubuntu - Stack Overflow
Viewing all articles
Browse latest Browse all 5956

Varnish stopped working and doesn't start

$
0
0

Varnish suddenly stopped working after an AWS instance reset and I'm not able to start or restart the Varnish service.

Running sudo varnishd -f /etc/varnish/default.vcl -s malloc,1G -T localhost:6082 -a :80 -d

Gives the following:

Debug: Version: varnish-6.2.1 revision 9f8588e4ab785244e06c3446fe09bf9db5dd8753Debug: Platform: Linux,5.15.0-1063-aws,x86_64,-junix,-smalloc,-sdefault,-hcritbit200 315-----------------------------Varnish Cache CLI 1.0-----------------------------Linux,5.15.0-1063-aws,x86_64,-junix,-smalloc,-sdefault,-hcritbitvarnish-6.2.1 revision 9f8588e4ab785244e06c3446fe09bf9db5dd8753startDebug: Child (3771) StartedError: Child (3771) not responding to CLI, killed it.Error: Child (3771) Pushing vcls failed:CLI communication error (hdr)Debug: Stopping ChildError: Child (3771) died signal=6 (core dumped)Info: Child (3771) said Child startsInfo: Child (3771) said Assert error in vsmw_newcluster(), common/common_vsmw.c line 246:Info: Child (3771) said   Condition((VFIL_allocate(fd, (off_t)len, 1)) == 0) not true.Info: Child (3771) said   errno = 28 (No space left on device)Info: Child (3771) said Wrong turn in child_signal_handler(), cache/cache_main.c line 284: Signal 6 (Aborted) received at 0x7200000ebb si_code -6Info: Child (3771) said   errno = 28 (No space left on device)Debug: Child cleanup complete400 0

default.vcl is:

vcl 4.0;import std;backend default {  .host = "127.0.0.1";  .port = "8080";  .first_byte_timeout = 60s;  .connect_timeout = 300s;}# SET THE ALLOWED IP OF PURGE REQUESTSacl purge {"localhost";"127.0.0.1";"34.198.145.153";}

I believe there is space on the device so not sure if the "No space left on device" is relevant or if I'm missing something:

Filesystem      Size  Used Avail Use% Mounted onudev            3.8G     0  3.8G   0% /devtmpfs           765M  976K  764M   1% /run/dev/nvme0n1p1  125G  124G   12M 100% /tmpfs           3.8G     0  3.8G   0% /dev/shmtmpfs           5.0M     0  5.0M   0% /run/locktmpfs           3.8G     0  3.8G   0% /sys/fs/cgroup/dev/loop0       56M   56M     0 100% /snap/core18/2812/dev/loop1       56M   56M     0 100% /snap/core18/2823/dev/loop2       64M   64M     0 100% /snap/core20/2318/dev/loop3       39M   39M     0 100% /snap/snapd/21465/dev/loop4       64M   64M     0 100% /snap/core20/2264/dev/loop5       39M   39M     0 100% /snap/snapd/21759/dev/loop6       92M   92M     0 100% /snap/lxd/24061/dev/loop7       92M   92M     0 100% /snap/lxd/23991tmpfs           765M     0  765M   0% /run/user/1004

Would appreciate any thoughts or pointers.


Viewing all articles
Browse latest Browse all 5956

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>