Is this a problem?

Support
1

Hello,

OMV LX 3.03

Just after last updates (kernel 4.16.13, etc), during boot I see this message:

[FAILED] Failed to start Daily man-db cache update
See 'systemctl status man-db.timer' for details

However the suggested command simply returns:

$ systemctl status man-db.timer
● man-db.timer - Daily man-db cache update
   Loaded: loaded (/lib/systemd/system/man-db.timer; enabled; vendor preset: enabled)
   Active: inactive (dead)
  Trigger: n/a

It looks OK to me. Isn’t it OK?

2 Likes
2

Here is what I get:

# systemctl status man-db.timer
● man-db.timer - Daily man-db cache update
   Loaded: loaded (/lib/systemd/system/man-db.timer; enabled; vendor preset: enabled)
   Active: inactive (dead)
  Trigger: n/a

juin 11 11:00:52 localhost systemd[1]: man-db.timer: Refusing to start, unit to trigger not loaded.
juin 11 11:00:52 localhost systemd[1]: Failed to start Daily man-db cache update.
1 Like
3

It’s not just you. I see exactly the same. Bug Report on man-db.service.

You’ll notice that TPG marked bug as fixed. I’m confused.

4

Thanks Ben!

1 Like
5

Workaround for concerened users:

$ sudo systemctl enable man-db.timer

Post edit: After the above and rebooting you’ll see:

$ systemctl status man-db
● man-db.service - Update man-db cache
   Loaded: loaded (/lib/systemd/system/man-db.service; static; vendor preset: enabled)
   Active: inactive (dead)

$ systemctl status man-db.timer
● man-db.timer - Daily man-db cache update
   Loaded: loaded (/lib/systemd/system/man-db.timer; enabled; vendor preset: enabled)
   Active: active (waiting) since Mon 2018-06-11 14:43:38 CDT; 2min 23s ago
  Trigger: Mon 2018-06-11 14:48:32 CDT; 2min 29s left
6

And after the work around:

    $ journalctl -b
-- Logs begin at Tue 2018-06-05 15:57:30 CDT, end at Mon 2018-06-11 14:58:10 CDT. --
Jun 11 14:43:36 omv systemd-journald[160]: Journal started
    ...
    Jun 11 14:48:37 ben79-pc systemd[1]: Started Update man-db cache.
    ...

and no ‘man-db’ errors that I see, unless I missed something. Do notice that is is 5 minutes after login till you will see that.

7

@jclvanier and @adelson.oliveira I missed a very important question. Which man-db .rpm do or did you have installed when reporting above?

This might be fixed with:

$ rpm -qa man-db
man-db-2.8.3-5-omv2015.0.x86_64

I have some confusion on my system due to changes made working on a couple of issues. Will need to verify whether latest packages do or don’t work on another system or another computer when I get time.

8

I’ve just updated man-db-2.8.3-4 to man-db-2.8.3-5-omv2015.0.x86_64 and reboot. That message on man-db is gone.

Thanks

2 Likes
9 
># rpm -qa man-db
> man-db-2.8.3-5-omv2015.0.x86_64

> # systemctl daemon-reload
> # systemctl start man-db
> # systemctl status man-db
> ● man-db.service - Update man-db cache
>    Loaded: loaded (/lib/systemd/system/man-db.service; static; vendor preset: enabled)
>    Active: inactive (dead) since Tue 2018-06-12 13:36:06 CEST; 1min 54s ago
>   Process: 15357 ExecStart=/usr/sbin/update-man-cache (code=exited, status=0/SUCCESS)
>  Main PID: 15357 (code=exited, status=0/SUCCESS)
> 
> juin 12 13:36:03 localhost.localdomain systemd[1]: Started Update man-db cache.
10

$ systemctl status man-db.timer
● man-db.timer - Daily man-db cache update
Loaded: loaded (/lib/systemd/system/man-db.timer; enabled; vendor preset: enabled)
Active: active (waiting) since Tue 2018-06-12 20:47:09 -03; 1h 2min ago
Trigger: Wed 2018-06-13 00:00:00 -03; 2h 10min left

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.