client.gc: garbage collection skipped because no terminal allocations: reason="disk usage of 93 is over gc threshold of 80.
Unable to find log files.
Error reading file: Unexpected response code: 500 (failed to list entries: open /tmp/client/alloc/b8c78c5b-384f-cfe8-295d-643793101491/alloc/logs: no such file or directory)
Hi @shoryavj! This message from Nomad:
client.gc: garbage collection skipped because no terminal allocations: reason="disk usage of 93 is over gc threshold of 80.
indicates that the disk usage is high enough that Nomad wants to garbage collect, but that there aren’t any allocations on the node that can be garbage collected – all the jobs are running!
For this message:
Unable to find log files.
Error reading file: Unexpected response code: 500 (failed to list entries: open /tmp/client/alloc/b8c78c5b-384f-cfe8-295d-643793101491/alloc/logs: no such file or directory)
You’re getting this from running nomad alloc logs? I’d expect to see that only if the alloc’s directory was deleted. What is the output of nomad alloc status b8c78c5b?