[Bug 1958929] [NEW] man-db trigger hanging

[Dave Jones]

Public bug reported:

On a jammy image running on Raspberry Pi 400, I've seen the man-db
trigger appear to "hang" a couple of times now (eventually resulting in
me rebooting the system and fixing things up with "sudo dpkg-
reconfigure"). I'm aware of LP: #1858777 but I don't *think* this is the
same thing.

Firstly, there appears to be a mandb process that's pegged in a busy
loop, and despite leaving it a good 20 minutes (far longer than it
usually takes, which is generally no more than half a minute), it's
still there.

The output from the apt process is simply:

    Processing triggers for man-db (2.9.4-4) ...

And the following can be seen in top:

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                           
  75148 man       20   0   12180   2128      0 R 100.0   0.1  24:09.33 /usr/bin/mandb -pq                

(note the value in the TIME+ field)

Any hints for producing some more debug output / logs from mandb so I
can dig into this further, gratefully accepted!

** Affects: man-db (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to man-db in Ubuntu.
https://bugs.launchpad.net/bugs/1958929

Title:
  man-db trigger hanging

Status in man-db package in Ubuntu:
  New

Bug description:
  On a jammy image running on Raspberry Pi 400, I've seen the man-db
  trigger appear to "hang" a couple of times now (eventually resulting
  in me rebooting the system and fixing things up with "sudo dpkg-
  reconfigure"). I'm aware of LP: #1858777 but I don't *think* this is
  the same thing.

  Firstly, there appears to be a mandb process that's pegged in a busy
  loop, and despite leaving it a good 20 minutes (far longer than it
  usually takes, which is generally no more than half a minute), it's
  still there.

  The output from the apt process is simply:

      Processing triggers for man-db (2.9.4-4) ...

  And the following can be seen in top:

      PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                           
    75148 man       20   0   12180   2128      0 R 100.0   0.1  24:09.33 /usr/bin/mandb -pq                

  (note the value in the TIME+ field)

  Any hints for producing some more debug output / logs from mandb so I
  can dig into this further, gratefully accepted!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1958929/+subscriptions