Linux

I was trying to build coreutils the other day and kept running into an error with docbooks. I’d initially figured out I was missing the docbook and docbook-xsl packages (fairly obvious given it said it couldn’t find it…), but having installed them, I then got this more cryptic error: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" Some searching and trawling through forum posts led me to try installing docbook-xml — this solved the problem. ...

I synchronise my .ssh/config file between (most of) my laptops, including some Linux and macOS ones. On Mac, it’s quite nice to be able to use the UseKeychain option to store SSH passphrases in the secure keychain thing.. until you then try to use the same config file on Linux that is..! Thankfully, the IgnoreUnknown option can be used to tell Linux to stop whining about a bad configuration option, like so: ...

This’ll be a short post, more for my own reference than anything else! When running sudo apt update, I got the following error: Err:8 https://dl.yarnpkg.com/debian stable InRelease The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <[email protected]> [...] W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <[email protected]> W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <[email protected]> W: Some index files failed to download. They have been ignored, or old ones used instead. Googling this returns a mixture of results and fixes, but the one I’ve found works the majority of the time is: sudo apt-key adv --refresh-keys --keyserver keyserver.ubuntu.com Running sudo apt update again then works — yay! 🎉

I just upgraded the version of PHP on the server running this blog, and popped over to /wp-admin/site-health.php to check for any errors. There were a few, the main one which caught my eye being The REST API encountered an error. For the Google results, that error message in text is: The REST API request failed due to an error. Error: stream_socket_client(): SSL operation field with code 1. OpenSSL Error messages: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure stream_socket_client(): Failed to enable crypto stream_socket_client(): unable to connect to ssl://words.samtarling.co.uk:443 (Unknown error) (http_request_failed) ...

Okay, I know we’re not upgrading Apache, but y’know what I mean - let’s upgrade a Debian web server using PHP 7.3 to PHP 7.4! I’ll also cover some pointers on if that web server is running WordPress. 0) Assumptions I’m assuming: The server runs Debian 9 (Stretch) or Debian 10 (Buster) with Apache version 2.4.38* (though it should work for other versions) Apache is using the PHP module, not PHP-FPM You have sudo and SSH access You’ve made backups and any sites you’re hosting can tolerate downtime 😉 * You can get this info by running /usr/sbin/apache2 -v ...