Re: Bullseye to Bookworm upgrade issues
On Sat 3 Jun 2023, at 01:15, Gareth Evans wrote:
> On Fri 2 Jun 2023, at 03:58, Gareth Evans wrote:
>> I have upgraded Bullseye with root on ZFS to Bookworm, but I wonder if
>> the 4 upgrade issues I encountered are worth reporting?
>>
>> If so, which packages would be advisable to report against, please?
>
> I forgot to mention, after the upgrade failure after DM restart, on
> logging in again I was "required by the administrator" to change my
> password. This seems odd.
And syslog shows repeatedly:
2023-06-03T01:16:33.008969+01:00 qwerty mariadbd[2469]: 2023-06-03 1:16:33
1793 [ERROR] Incorrect definition of table mysql.column_stats: expected column
'hist_type' at position 9 to have type
enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type
enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2023-06-03T01:16:33.009050+01:00 qwerty mariadbd[2469]: 2023-06-03 1:16:33
1793 [ERROR] Incorrect definition of table mysql.column_stats: expected column
'histogram' at position 10 to have type longblob, found type varbinary(255).
...which I think may pertain to the apache 503 issue.
Re: Bullseye to Bookworm upgrade issues
On Fri 2 Jun 2023, at 03:58, Gareth Evans wrote: > I have upgraded Bullseye with root on ZFS to Bookworm, but I wonder if > the 4 upgrade issues I encountered are worth reporting? > > If so, which packages would be advisable to report against, please? I forgot to mention, after the upgrade failure after DM restart, on logging in again I was "required by the administrator" to change my password. This seems odd. Thanks, Gareth
Bullseye to Bookworm upgrade issues
Hello, I have upgraded Bullseye with root on ZFS to Bookworm, but I wonder if the 4 upgrade issues I encountered are worth reporting? If so, which packages would be advisable to report against, please? Having followed the draft release notes, here is the output from my script files (with my ): 1. DM restart issue root@qwerty:~# apt upgrade --without-new-pkgs The release notes seem to suggest the upgrade should continue: "4.5.6. Change of session to console If you are running the upgrade using the system's local console you might find that at some points during the upgrade the console is shifted over to a different view and you lose visibility of the upgrade process [...]" https://www.debian.org/releases/bookworm/amd64/release-notes/ch-upgrading.en.html#trouble 2. dmsetup problem root@qwerty:~# apt full-upgrade dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. root@qwerty:~# dpkg --configure -a Setting up libcrypt-openssl-random-perl:amd64 (0.15-3+b1) ... dependency problems prevent configuration of dmsetup: dmsetup depends on libdevmapper1.02.1 (>= 2:1.02.181); however: Version of libdevmapper1.02.1:amd64 on system is 2:1.02.175-2.1. error processing package dmsetup (--configure): dependency problems - leaving unconfigured Processing triggers for initramfs-tools (0.140) ... update-initramfs: Generating /boot/initrd.img-5.10.0-23-amd64 Errors were encountered while processing: dmsetup root@qwerty:~# apt upgrade libdevmapper You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: dmsetup : Depends: libdevmapper1.02.1 (>= 2:1.02.181) but 2:1.02.175-2.1 is installed Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@qwerty:~# apt --fix-broken install update-initramfs: Generating /boot/initrd.img-5.10.0-23-amd64 Jneedrestart is being skipped since dpkg has failed 3. Apt doesn't finish its jobs and doesn't restart them on re-run root@qwerty:~# apt full-upgrade APT had planned for dpkg to do more than it reported back (7296 vs 7329). Affected packages: texlive-fonts-recommended:amd64 texlive-lang-greek:amd64 texlive-latex-base:amd64 texlive-latex-extra:amd64 texlive-latex-recommended:amd64 texlive-pictures:amd64 texlive-plain-generic:amd64 texlive-science:amd64[0m root@qwerty:~# apt full-upgrade 4. Apache (config?) is broken after upgrade user@qwerty:~$ sudo service apache2 status > a.txt user@qwerty:~$ cat a.txt ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; preset: enabled) Active: active (running) since Fri 2023-06-02 03:36:07 BST; 4min 47s ago Docs: https://httpd.apache.org/docs/2.4/ Main PID: 2570025 (apache2) Tasks: 8 (limit: 14100) Memory: 20.7M CPU: 153ms CGroup: /system.slice/apache2.service ├─2570025 /usr/sbin/apache2 -k start ├─2570026 /usr/sbin/apache2 -k start ├─2570028 /usr/sbin/apache2 -k start ├─2570030 /usr/sbin/apache2 -k start ├─2570031 /usr/sbin/apache2 -k start ├─2570032 /usr/sbin/apache2 -k start ├─2570033 /usr/sbin/apache2 -k start └─2570034 /usr/sbin/apache2 -k start Jun 02 03:36:07 qwerty systemd[1]: Starting apache2.service - The Apache HTTP Server... Jun 02 03:36:07 qwerty apachectl[2570024]: [Fri Jun 02 03:36:07.491684 2023] [alias:warn] [pid 2570024] AH00671: The ScriptAlias directive in /etc/apache2/sites-enabled/munin.conf at line 13 will probably never match because it overlaps an earlier ScriptAlias. Jun 02 03:36:07 qwerty apachectl[2570024]: [Fri Jun 02 03:36:07.491727 2023] [alias:warn] [pid 2570024] AH00671: The Alias directive in /etc/apache2/sites-enabled/munin.conf at line 14 will probably never match because it overlaps an earlier Alias. Jun 02 03:36:07 qwerty apachectl[2570024]: [Fri Jun 02 03:36:07.491761 2023] [alias:warn] [pid 2570024] AH00671: The Alias directive in /etc/apache2/sites-enabled/munin.conf at line 44 will probably never match because it overlaps an earlier Alias. Jun 02 03:36:07 qwerty apachectl[2570024]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message Jun 02 03:36:07 qwerty systemd[1]: Started apache2.service - The Apache HTTP Server. Firefox at http(s)://localhost/sitename gives a 503 "Service Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later." Neither /var/log/apache2/error.log nor /var/log/syslog seem to provide any clues to the problem. I said Yes to new config files (etc) during upgrade. user@qwerty:/etc/apache2/mods-available$ ls access_compat.loaddump_io.load proxy.conf actions.conf
