Arch Linux

OrigBitmancer

Member

Registered: 2019-01-22

Posts: 144

pacman error : where?

I run a pacman -Syuv update and sometimes get the following (after downloads and upgrades are successful...) :

# pacman -Syyuuvv --ignore x265,ffmpeg,dav1d,libplacebo,mpv --noprogressbar
... 90 update messages ...
:: Running post-transaction hooks...
( 1/15) Creating system user accounts...
( 2/15) Reloading system manager configuration...
( 3/15) Creating temporary files...
error: command failed to execute correctly
( 4/15) Reloading device manager configuration...

What do I instrument to debug the error? Just add --debug to the pacman invocation? Even though the next several runs have no such message?
Or are there pieces of pacman that I can observe for issues?

Slithery

Administrator

From: Norfolk, UK

Registered: 2013-12-01

Posts: 5,776

Re: pacman error : where?

Does your pacman log show any more information?

---

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

loqs

Member

Registered: 2014-03-06

Posts: 17,427

Re: pacman error : where?

What is the output from:

# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create

OrigBitmancer

Member

Registered: 2019-01-22

Posts: 144

Re: pacman error : where?

@Slithery:
It shows lines like

[2019-11-25T13:03:49-0600] [ALPM] running '20-systemd-sysusers.hook'...
[2019-11-25T13:03:50-0600] [ALPM] running '30-systemd-daemon-reload.hook'...
[2019-11-25T13:03:52-0600] [ALPM] running '30-systemd-tmpfiles.hook'...
[2019-11-25T13:03:52-0600] [ALPM] running '30-systemd-udev-reload.hook'...
[2019-11-25T13:03:52-0600] [ALPM] running '30-systemd-update.hook'...

so should I investigate 30-systemd-tmpfiles.hook?

@loqs:
I get a zillion lines of

Reading config file "/usr/lib/tmpfiles.d/apache.conf"…

interspersed with lines of

Ignoring entry C! "/etc/issue" because --boot is not specified.

then I get

Running create action for entry d /run/httpd
Found existing directory "/run/httpd".
"/run/httpd" matches mode 755 already.

...and later I get

Found existing directory "/var/lib/dbus".
"/var/lib/dbus" matches mode 755 already.
Running create action for entry L /var/lib/dbus/machine-id
"/var/lib/dbus/machine-id" is not a symlink or does not point to the correct path.

I will put the output from the systemd-tmpfiles command in an online file (https://gist.github.com/BitMancer1/c4f7 … 518358ac53)

Last edited by OrigBitmancer (2019-11-26 07:48:13)

loqs

Member

Registered: 2014-03-06

Posts: 17,427

Re: pacman error : where?

Detected unsafe path transition /etc/couchdb → /etc/couchdb/local.ini during canonicalization of /etc/couchdb/local.ini.                           

What is the output of

stat /etc/couchdb /etc/couchdb/local.ini

OrigBitmancer

Member

Registered: 2019-01-22

Posts: 144

Re: pacman error : where?

the output of that stat command is:

  File: /etc/couchdb
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: 821h/2081d      Inode: 7359160     Links: 2
Access: (0755/drwxr-xr-x)  Uid: (  997/ couchdb)   Gid: (    2/  daemon)
Access: 2019-11-17 02:54:10.786608630 -0600
Modify: 2019-11-17 02:54:10.816608631 -0600
Change: 2019-11-17 02:54:10.816608631 -0600
 Birth: 2013-08-29 23:48:03.568973592 -0500
  File: /etc/couchdb/local.ini
  Size: 4055            Blocks: 8          IO Block: 4096   regular file
Device: 821h/2081d      Inode: 7345783     Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2019-11-17 02:54:10.799941964 -0600
Modify: 2019-11-12 13:31:02.000000000 -0600
Change: 2019-11-17 02:54:10.809941965 -0600
 Birth: 2019-11-17 02:54:10.799941964 -0600

What should I be looking for?

loqs

Member

Registered: 2014-03-06

Posts: 17,427

Re: pacman error : where?

The directory /etc/couchdb is owned couchdb:daemon but the file local.ini within it is owned by root:root.
tmpfiles considers that root ownership of a file or directory inside a path not owned by root unsafe and it generates an error.
If you chown the file couchdb:couchdb does that resolve the issue?

# systemd-tmpfiles --create && echo 'no error'