Few weeks ago I encountered one of the most bizzare issues I ever got to debug. On my testing Galera Cluster, one of the nodes failed and refused to join back the cluster. What I initially observed was the MySQL process looping with the error message that was caught in
NGINX Extended💡UPDATE (April 26, 2019): this post has been updated to include latest changes made to the project. You can jump directly to it here → I was lucky enough that in relatively early time in my career I bet on NGINX as my default HTTP server and essentially never
BCC & libbpf Latest versions of BCC (v0.22.0) and libbpf (v0.5.0) are now available from the bpftrace PPA[1] for bionic, focal and hirsute: sudo add-apt-repository ppa:hadret/bpftrace sudo apt update sudo apt install bpftrace bpfcc-tools libbpf Right now bionic builds of bpftrace are still
In June latest release of libbpf has landed in Ubuntu repositories for impish (upcoming 21.10 release). I grabbed the 0.4.0 version and backported it to bionic, focal, groovy and hirsute – these are test builds and are available from the following PPA: sudo add-apt-repository ppa:hadret/libbpf sudo
Last month I patched NGINX Extended against the CVE-2021-23017. I was still having trouble with upgrading to anything higher than 1.19.5 though – which I wrote about back in January. I was getting to the point where I started to explore alternatives when I finally got it building properly.
Recently I wanted to go through the bunch of facts from different parts of the infrastructure I maintain. I’ve been already collecting Ansible facts in Redis to speed things up and then I noticed that they are actually still stored in JSON. I always had a soft spot for