I ended up needing to install hitch on a server recently, so the https:// traffic could be routed through Varnish (along with the existing ‘http’ stuff) for performance reasons.
The server only runs WordPress sites, so there are WordPress specific things in the Varnish configuration (vcl) file below.
Versions: Varnish 5.2, Hitch 1.4.4, Apache 2.4 and Debian Jessie.
Continue reading “Using hitch with varnish on Debian Jessie”
This might work to configure monit on Debian (Jessie) to monitor postsrsd.
check process postsrsd matching "/usr/sbin/postsrsd"
start program = "/etc/init.d/postsrsd start"
stop program = "/etc/init.d/postsrsd stop"
if failed host localhost port 10001 then restart
if failed host localhost port 10002 then restart
Random notes from installing Linux on it … it does just work – but ….
Continue reading “Intel NUC6i7KYK with Debian Jessie”
As I keep losing this….
Creating a .deb kernel package from a vanilla kernel.org kernel :
- wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.4.24.tar.xz
- tar -xf linux-4.4.24.tar.xz
- cd linux-4.4.24
- cp /boot/config-whatever .config
- Optionally: edit and set: CONFIG_DEBUG_INFO=n to stop the *dbg* package being generated
- make olddefconfig
- make deb-pkg -j6 LOCALVERSION=-dg1
As of last night, Debian Security released PHP 5.4.44 for Wheezy. Wheezy shipped with PHP 5.4.12 or something like that.
DotDeb is currently on 5.4.43, and if you’ve been using it based on the assumption that it has a newer version of a package over Debian, then an upgrade will leave your PHP install in a mess (e.g. no php5-gearman or php5-imagick).
To fix this, the following in e.g. /etc/apt/preferences.d/dotdeb will help :
Pin: origin packages.dotdeb.org
This should make apt choose dotdeb packages over Debian, even if Debian contains a newer version.
i.e. stop apt relying on just the package version number, and previously dotdeb always had a higher one.
I came across the varnish throttle module the other day – which seems quite useful – and certainly gives better control over abusive requests than using fail2ban (in that, only specific URLs/request types can be targeted and blocked with the throttle module, while fail2ban tends to trigger the blocking of any traffic from a client which can be more painful).
Continue reading “varnish throttling”
I found MySQL was being annoying earlier and not ‘accepting’ my max_connections = 450 directive on a Debian Wheezy install, and being seemingly stuck on having 214 connections….
Continue reading “MySQL Max_connections stuck on 214 ?”
I have an Intel NUC d54250wyk as my work computer (it’s a little dinky thing, which somehow manages to pack a reasonable punch).
On board it has a mini-hdmi port, and a mini-display port – which I used for a dual monitor configuration.
But two monitors is so last year …. and after 5+ years of having two monitors to stare at, I thought it was perhaps time to move up to 3 (or more).
Continue reading “More monitors.”
I’ve been using BTRFS for a few weeks now, and some bits are great (filesystem snapshots, dynamic resizing etc).
The “Good” and “Bad” things follow:
Continue reading “BTRFS gotchas… (balance / scrub / snapshots / quota)”
I needed a variant of Squid which supported transparent SSL interception (i.e via iptables redirection) so I could log outgoing HTTPS requests without the client being aware.
The stock wheezy variant doesn’t support SSL (see : Debian Bug Report).
Even after recompiling Wheezy’s squid3 it didn’t seem to work (perhaps my stupidity) so I ended up moving to the latest-and-greatest squid (3.4.9 at the time of writing) and getting that to work. Brief notes follow.
Continue reading “Squid 3.4.x for with transparent ssl proxying/support for Debian Wheezy.”