In that case, maybe your could run the 2.4.55 mod_http2 with "LogLevel http2:debug" until some 500s show up. 
That would be very interesting to analyze.

 $ cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
md126 : active raid1 sdd2[1] sde2[0]
      976629696 blocks super 1.2 [2/2] [UU]
      bitmap: 0/8 pages [0KB], 65536KB chunk

md127 : active raid0 nvme1n1p2[1] nvme0n1p2[0]
      1931212800 blocks super 1.2 512k chunks

md0 : active raid0 sdb[0] sdc[1]
      976508928 blocks super 1.2 512k chunks

unused devices: <none>

  # Finally, we should check if base device is
  # a real block device or a RAID volume:
  for MD in  $(cat /proc/mdstat | grep -w active | cut -d' ' -f1) ; do
    if [ "$BASEDEV" = "/dev/$MD" ]; then
      USING_RAID=1
      break
    fi
  done
  # Additional check in case $BASEDEV is a partition of /dev/$MD:
  for BLK in $(sfdisk -ld /dev/$MD 2> /dev/null | grep "^/dev" | cut -d " " -f 1); do
    if [ "$BASEDEV" = "$BLK" ]; then
      USING_RAID=1
      break
    fi
  done

  for MD in  $(cat /proc/mdstat | grep -w active | cut -d' ' -f1) ; do
    if [ "$BASEDEV" = "/dev/$MD" ]; then
      USING_RAID=1
      break
    fi
  done
  
  # Additional check in case $BASEDEV is a partition of /dev/$MD:
  for MD in  $(cat /proc/mdstat | grep -w active | cut -d' ' -f1) ; do
    for BLK in $(sfdisk -ld /dev/$MD 2> /dev/null | grep "^/dev" | cut -d " " -f 1); do
      if [ "$BASEDEV" = "$BLK" ]; then
        USING_RAID=1
        break
      fi
    done
  done

  for MD in  $(cat /proc/mdstat | grep -w active | cut -d' ' -f1) ; do
    if [ "$BASEDEV" = "/dev/$MD" ]; then
      USING_RAID=1
      break
    fi
    # Additional check in case $BASEDEV is a partition of /dev/$MD:
    for BLK in $(sfdisk -ld /dev/$MD 2> /dev/null | grep "^/dev" | cut -d " " -f 1); do
      if [ "$BASEDEV" = "$BLK" ]; then
        USING_RAID=1
        break
      fi
    done
    # Break out of outer loop if needed.
    if [ "$USING_RAID" = "1" ]; then
      break
    fi
  done

Thunderbird 102.7.0 will not automatically update due to a critical authentication 
issue with Microsoft 365 Business accounts. 
Affected users should not update until Thunderbird 102.7.1 is released with a fix