Hello,

starting from yesterday's update on one of my systems (RaspberryPi) I
get the following when I ssh into it:

pihole pam_openrc[some_user][4421]: starting session
pihole pam_openrc[some_user][4421]: 1 sessions
pihole supervise-daemon[4645]: Supervisor command line: supervise-daemon user.some_user --start /usr/libexec/rc/bin/openrc-user -- some_user
pihole supervise-daemon[4647]: Child command line: /usr/libexec/rc/bin/openrc-user some_user
pihole openrc-user.some_user[4647]: uid 0d, gid 0d, euid 0d, egid 0d.
pihole supervise-daemon[4646]: /usr/libexec/rc/bin/openrc-user, pid
4647, exited with return code 255
pihole supervise-daemon[4656]: Child command line: /usr/libexec/rc/bin/openrc-user some_user
pihole openrc-user.some_user[4656]: uid 0d, gid 0d, euid 0d, egid 0d.
(the last three lines repeated over and over, then:)
pihole supervise-daemon[4646]: respawned
"/usr/libexec/rc/bin/openrc-user" too many times, exiting

I never noticed supervise-daemon (https://wiki.gentoo.org/wiki/OpenRC/supervise-daemon) before, I suppose
it is a new component of OpenRC. From the above log I understand that
pam is trying to start an openrc session (whatever that is) for user
some_user but fails. supervise-daemon tries to restart the service
several times and finally gives up.

Any idea why openrc-user is failing? And what is an openrc user session?

The ssh succeeds but with a longer delay compared to previous version of OpenRC, which is now sys-apps/openrc-0.60.

thanks,

raffaele

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

--b1bc6ba15ddb314eaa491fd7b003f75762bf8f6ba6ee68e968f9256b5457
Content-Type: multipart/mixed;
boundary=2d2ed61a136e74be0fb2293519b235c01899328ec16dd5c9c88a3af33012

--2d2ed61a136e74be0fb2293519b235c01899328ec16dd5c9c88a3af33012
Content-Type: multipart/alternative;
boundary=06c9d48edb0dde2b7adf90ff84e2ab4b19c797625066b9dc68eccfa88103

--06c9d48edb0dde2b7adf90ff84e2ab4b19c797625066b9dc68eccfa88103 Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Content-Type: text/plain; charset=UTF-8

Any idea why openrc-user is failing? And what is an openrc user session?

openrc user session is a similar concept to systemd --user, and is
experimental in openrc. it's made to run services that run as your user,
like dbus, pipewire, ssh-agent, emacs.

if i were to guess why it's failing, XDG_RUNTIME_DIR might not be set
for the session. can happen on systems without neither elogind nor pam_xdg

The ssh succeeds but with a longer delay compared to previous version of OpenRC, which is now sys-apps/openrc-0.60.

the login sequence shouldn't be waiting until openrc-user succeeds or
failes, yet at least. i do think now that it's probably warranted to
reduce the number of re-tries we do though.

to disable the attempt of starting all toghether, remove or comment out
the line with pam_openrc.so from /etc/pam.d/system-login

---

I never noticed supervise-daemon (https://wiki.gentoo.org/wiki/OpenRC/supervise-daemon) before, I suppose
it is a new component of OpenRC. From the above log I understand that
pam is trying to start an openrc session (whatever that is) for user some_user but fails. supervise-daemon tries to restart the service
several times and finally gives up.

supervise-daemon is a supervisor built into openrc for a good while now,
but most services did not move over to it yet.

-- navi

--06c9d48edb0dde2b7adf90ff84e2ab4b19c797625066b9dc68eccfa88103--

--2d2ed61a136e74be0fb2293519b235c01899328ec16dd5c9c88a3af33012 Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename=68990292A7A98C5E.asc
Content-Type: application/pgp-keys; charset=UTF-8

LS0tLS1CRUdJTiBQR1AgUFVCTElDIEtFWSBCTE9DSy0tLS0tCgptUUlOQkdOMWVrNEJFQURSZEZa cUgzM3JZay84eUhwblM0U25UUUlGZnNTN3hNUy9sSG9JWVBUcXVUK1RHL0dwClFOQnZxZXh0dDhS c1duQ1k2WEE1dEdNWVg3Y3V0VFBqRjg2WTJwWWJMbzd5N010L3hnZGhDeUYzeUZsSGdGW