[ERROR] Can't open and lock privilege tables: Got error 9 from storage engine
Nice error. Googling for it doesn’t reveal much on how to fix it. The good news is that I only use MySQL for Phabricator and PostreSQL for everything else. The bad news is that my Phabricator instance is no longer working. The worse news is that I get the same error when trying to use backups, so there must be something else in play here.
I’m desperately trying to retire a server i have. It’s sole remaining task is to share the attached printer on the network via Samba. It uses CUPS as the backend. Trying to print a test page gives No such file or directory. That’s nice, but it should at least say what the file or directory it cannot find actually is.
Trying to connect to the printer from a Windows machine (I can see the printer find in the server share) gives an error that it cannot connect, but nothing appears in the Samba or CUPS logs.
So dhcpcd has supported a shared IP address for a long time. It did this by removing the address from the non preferrred interface and then adding it to the preferred interface.
Easy!
But this came with some issues:
There is a window where the IP address doesn’t exist, and the kernel may wipe out the subnet route at that point also. DHCP renews didn’t come through to the right interface.
I’ve been using Fossil as my SCM for quite a few years now and it has served me well. It replaced my aging Trac (which I’ve now really retired in the recent server move … it didn’t move) + GIT setup. There is nothing inherently wrong with it and upstream are quite quick to resolve any issues. So lets start with a list of Fossil plus points, in no particular order:
So finally I’ve moved all services from my old server to my Christmas Xen box! This was not without problems due to the fact it had to run NetBSD-current
gcc toolchain is broken for some packages which affected running any PHP build clang toolchain was broken for my config (USE_SSP= yes and CPUFLAGS+=-march=core2) clang compiles as a whole were broken due to a recent efiboot import In hind-sight, I could have had the box up and running a lot sooner if I used NetBSD-7 guests (or maybe just a NetBSD-7 build box), but no, I just had to get-current running.
Roy's Blog