Announcement

**GreyGeek** · Jan 02, 2021, 04:04 PM

Your situation is classical.
My first question is: did you make a backup of your system before you tried this?
If you did then you can avoid wasting a lot of time and just roll back.
If you didn't make a backup then that is a procedure you should begin to do daily, or at least just before you do any changes like what you tried to do.

So, from this state you can purge php and apache and then "sudo apt autoremove" to remove orphaned dependencies and "sudo apt-get clean" to clean the apt cache. Then, power down and power back up. Then re-install apache and php 7.4 from the repository. That *should* get you back to where you were before you attempted to upgrade php to 8.0. Then make a backup in case you need to recover again.

What you use to make a backup depends on what FS you are using. IF EXT4 then TimeShift (which is in the repository) will use rsync to make backups. IF you are using BTRFS then TimeShift can make the BTRFS snapshots and roll back easily to any pre-existing snapshot, or you can do the snapshotting and rolling back manually.

**Hoth** · Jan 03, 2021, 01:42 PM

Nuking the system to restore a backup every time there's an error seems a rather odd way of doing things, and prevents learning. Admittedly I ought to make external backups of flies more often, and I'll have a look at TimeShift.

I was able to fix the problem by doing a complete removal of libapache2-mod-php 7.4 and 8.0 along with apache2, and then reinstalling only the 8.0 version. Apparently that caused new correct configuration files to be written. I'd swear there used to be a configuration file for apache that specified the PHP version so it'd be nice to know where that is now if anyone knows... but perhaps apache has changed and doesn't configure in that way anymore.

**Snowhog** · Jan 03, 2021, 02:34 PM

Of help maybe: https://ubuntu.com/server/docs/web-servers-apache

**jlittle** · Jan 03, 2021, 11:46 PM

Originally posted by Hoth View Post

Nuking the system to restore a backup every time there's an error seems a rather odd way of doing things

Using the terms "nuke" and "restore a backup", I suspect you don't appreciate how simple and quick reverting to a snapshot is. And on a COW fs the updated system is still there, one can boot to either if you want to. A snapshot is not a backup; a drive failure or fs corruption and you need a real backup.

Originally posted by Hoth View Post

and prevents learning.

Yes, I have that attitude, and persist with problematic situations when abandoning them would save time.

**GreyGeek** · Jan 04, 2021, 05:06 PM

Originally posted by jlittle View Post

Using the terms "nuke" and "restore a backup", I suspect you don't appreciate how simple and quick reverting to a snapshot is. And on a COW fs the updated system is still there, one can boot to either if you want to. A snapshot is not a backup; a drive failure or fs corruption and you need a real backup.

Yes, I have that attitude, and persist with problematic situations when abandoning them would save time.

I have an addition SDD and a spinner installed, besides the SSD my Kubuntu 20.04 is residing on. To make a daily incremental backup I issue

Code:

sudo /make_snapshot.sh

It creates a labeled snapshot on the primary drive and then makes an incremental snapshot on the 2nd SSD. Then it deletes the oldest snapshot on my system and the oldest snapshot on the 2nd SSD. Then it umounts the 2nd SSD and the /mnt of the primary BTRFS <ROOT_FS>, and returns to the prompt. It usually takes only 30 seconds to a minute, depending on how many changes I made from the previous day. Here is the script that I use:

Code:

********************************
#!/bin/bash
#
# script to create backup snapshots to /mnt/snapshots and a differential backup to /backup
# To be run as root from /
#
echo "Mounting drives"
eval "mount /dev/disk/by-uuid/ce2b5741-c01e-4b3d-b6ba-401ad7f7fcdf /mnt"
eval "mount /dev/disk/by-uuid/e84e2cdf-d635-41c5-9f6f-1d0235322f48 /backup"

NOW=$(date +%Y%m%d%H%M)
echo "Making today's snapshot"
MKSNAP='btrfs su snapshot -r /mnt/@ /mnt/snapshots/@'$NOW
eval $MKSNAP
eval 'sync'
eval 'sync'

echo "Finding previous snapshot as parent "
PREVSNAP=""
list=($(ls /mnt/snapshots/))
PREVSNAP=${list[-2]}
NOW=${list[-1]}
echo "Attempting incremental backup"
if [[ -s "/mnt/snapshots/"$PREVSNAP ]]; 
then
    MKINC='btrfs send -p /mnt/snapshots/'$PREVSNAP
    MKINC=$MKINC' /mnt/snapshots/'$NOW
    MKINC=$MKINC' | btrfs receive /backup'
    echo $MKINC
    eval $MKINC
    eval 'sync'
    eval 'sync'
    eval "sync"
    DELSNAP='btrfs subvol delete -C /mnt/snapshots/'${list[0]}
    eval $DELSNAP
    eval 'sync'
    eval 'sync'
    eval 'sync'
    list=''
    list=($(ls /backup))
    DELSNAP='btrfs subvol delete -C /backup/'${list[0]}
    eval $DELSNAP
    eval 'sync'
    eval 'sync'
    eval 'sync'
    echo "Snapshots completed, oldest snapshots deleted"
    eval 'umount /backup'
    eval 'umount /mnt'
    echo "Drives unmounted"
else
    echo 'Incremental backup failed using '$PREVSNAP' and '$NOW
    echo 'Drives still mounted, ready to clean up'
fi

*******************************

Since I've combined @ and @home into @ I need snapshot only @.

Announcement

Php 8

Php 8

Comment

Comment

Comment

Comment

Comment