Category: Housekeeping

Quick flurry of updates as Samba 4.6 finally went out of support earlier this month so no more patches, so quick deinstall of Samba46 and then install of Samba48 to get Samba back into support.

Update to PHP 7.1 was a bit more involved.  Needed to update make.conf to amend the default_versions from 5.6 to 7.1 and then locate the port directories for mod_php56 and de-install.   Quick build of mod_php71 to update that and then pkg delete php56 to remove all the extensions.

I have Kanboard and phpsysinfo installed, so a quick trip to their port directories to re-installed pulled in most of the PHP extensions needed, but oddly not php71-extensions, so on Apachectl Restart WordPress spewed up some Server 500 Errors.  A quick check of the previous php extensions now installed versus the previous 56 variants thru up a few ports that had not been pulled back in.   A quick re-build of those ports and another apachectl restart and all is well and Apache is now running PHP 7.1 happily.

 

My daily and weekly status updates from Root stopped appearing in my main inbox a while back, (probably when I switched from Sendmail to SSMTP.  )  but they did appear in my secondary email account as this was the bounce-back address for email failures, as failure reports.

Issue seemed to be that the Root mail box was not reachable anymore.   Attempts to amend an alias to have them delivered to a live account failed as most of the method listed for amending Root’s alias are for Sendmail.

A bit of googling found this post  http://possiblelossofprecision.net/?p=591 and identified the correct file to edit as /ETC/MAIL.RC and add

set append dot save ask crt
ignore Received Message-Id Resent-Message-Id Status Mail-From Return-Path Via
alias root yournewrootmailboxhere@nowhere.com

to finally restore my housekeeping updates from the system

 

Had been playing around which Apache to add a new virtual host and somewhere, somehow, the auto update on WordPress stopped working and insisted that I entered the FTP credentials which is not something I have enabled on this server.   A bit of googling came across this post highlighted a potential work around in the WP-config.php to allow direct updates.    A quick edit with EE and an apachectl restart and WordPress update routine worked flawlessly as it did before, with out needing FTP access.

https://www.hongkiat.com/blog/update-wordpress-without-ftp/

Finally got around to researching how to automate Certificate renewals on Freebsd and now have the Cron job running to take care of things.

Updating Certificates

 

Website has been down a few days as been very busy, so tried to rely on package updates rather than building from ports to keep everything patched as Perl and Python going thru the ‘Flavour’ splitting and packages where supposed to be easier.    To cut a long story short, it also downgraded my PHP version and dropped the Database support module in the process.  So in order to get the website back up I have had to manually install the port for the DB support, mixing packages and ports which is not a good idea.   At least the site is up and running again and I shall stick to ports in the future to ensure the latest patches are always applied.