fatrace reports file access events from all running processes.
$ sudo apt-get install fatrace
nJoy 😉
fatrace reports file access events from all running processes.
$ sudo apt-get install fatrace
nJoy 😉
for i in {1..100} ; do echo '{"version": "1.1","host":"david.org","short_message":"A short message that helps you identify what is going on","full_message":"Backtrace here\n\nmore stuff","level":1,"_user_id":9001,"_some_info":"foo","_some_env_var":"bar"}' | nc -w 1 -u graylog.mydomain.com 12201 ; done
nJoy 😉
Unlike most other configuration systems varnish went with a compiled configuration so if there is a mistake all you get is :
Starting varnish HTTP accelerator: [FAILED]
To check what the problem is use the following :
varnishd -C -f default.vcl
varnishd -C -f default.vcl
Message from VCC-compiler:
Expected return action name.
(input Line 37 Pos 13)
return (hit_for_pass);
————############–
Running VCC-compiler failed, exit 1[root@MyHost1 varnish]# vim default.vcl
[root@MyHost1 varnish]# varnishd -C -f default.vcl
Message from VCC-compiler:
Invalid condition ‘&’ on numeric variable
only ‘==’, ‘!=’, ‘<‘, ‘>’, ‘<=’ and ‘>=’ are legal
(input Line 51 Pos 17)
if (obj.hits > 0) {
—————-#——–
Rightly so the error shouts back at you with a # under it.
Very clear and to the point, the vcl I had was HTML’ed and replaced > with >
That’s it..
nJoy 😉