* Ross Boylan <rossboy...@stanfordalumni.org> [230301 21:09]: > It is unclear to me if there is any real problem, as it is unclear if the > package > is operating properly. The journalctl logs seem to show a successful start, > but > the aptitude messages indicate a job failed. > > The apparent failure messages buried in the logs are > Mar 01 09:49:46 barley systemd[1]: multipathd.socket: Socket service > multipathd.service already active, refusing.
Thats the part causing the failed message in the apt/dpkg postinst output, and is TTBOMK harmless. Chris
