On 2/19/19 6:21 PM, Ralph Corderoy wrote:
Hi Maderios,
I can't connect users in tty. Mariadb and avahi-daemon don't start at
boot. I can't start them manually too using systemctl.
...
stdout to the journal socket, ignoring: Permission denied
Feb 19 14:54:27 nalik systemd[980]: mariadb.service: Failed to connect
Do you see anything extra in journalctl(1)'s output around the time of
these errors?
journalctl -xe | grep mariadb
-- Subject: A start job for unit mariadb.service has begun execution
-- A start job for unit mariadb.service has begun execution.
Feb 19 18:29:16 nalik kernel: audit: type=1130 audit(1550597355.812:84):
pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=mariadb
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=failed'
Feb 19 18:29:15 nalik audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=mariadb comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Feb 19 18:29:15 nalik systemd[1669]: mariadb.service: Failed to connect
stdout to the journal socket, ignoring: Permission denied
Feb 19 18:29:15 nalik systemd[1670]: mariadb.service: Failed to connect
stdout to the journal socket, ignoring: Permission denied
Feb 19 18:29:15 nalik systemd[1684]: mariadb.service: Failed to connect
stdout to the journal socket, ignoring: Permission denied
Feb 19 18:29:15 nalik systemd[1]: mariadb.service: Main process exited,
code=exited, status=200/CHDIR
-- An ExecStart= process belonging to unit mariadb.service has exited.
Feb 19 18:29:15 nalik systemd[1]: mariadb.service: Failed with result
'exit-code'.
-- The unit mariadb.service has entered the 'failed' state with result
'exit-code'.
-- Subject: A start job for unit mariadb.service has failed
-- A start job for unit mariadb.service has finished with a failure.
journalctl -xe | grep user
Feb 19 18:45:28 nalik login[999]: pam_unix(login:session): session
opened for user fre by LOGIN(uid=0)
Feb 19 18:45:28 nalik kernel: audit: type=1130 audit(1550598328.582:86):
pid=1 uid=0 auid=4294967295 ses=4294967295
msg='unit=user-runtime-dir@1000 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 19 18:45:28 nalik kernel: audit: type=1130 audit(1550598328.612:88):
pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1000
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=failed'
Feb 19 18:45:28 nalik audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Feb 19 18:45:28 nalik audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=user@1000 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Feb 19 18:45:28 nalik systemd[1737]: pam_unix(systemd-user:session):
session opened for user fre by (uid=0)
-- Subject: A start job for unit user-1000.slice has finished successfully
-- A start job for unit user-1000.slice has finished successfully.
Feb 19 18:45:28 nalik systemd[1738]: pam_unix(systemd-user:session):
session closed for user fre
Feb 19 18:45:28 nalik kernel: audit: type=1131 audit(1550598328.682:93):
pid=1 uid=0 auid=4294967295 ses=4294967295
msg='unit=user-runtime-dir@1000 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 19 18:45:28 nalik audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 19 18:45:28 nalik systemd[1]: Starting User Runtime Directory
/run/user/1000...
-- Subject: A start job for unit user-runtime-dir@1000.service has begun
execution
-- A start job for unit user-runtime-dir@1000.service has begun execution.
Feb 19 18:45:28 nalik systemd-logind[434]: New session 10 of user fre.
-- Subject: A new session 10 has been created for user fre
-- A new session with the ID 10 has been created for the user fre.
Feb 19 18:45:28 nalik login[999]: pam_unix(login:session): session
closed for user fre
Feb 19 18:45:28 nalik systemd[1]: Started User Runtime Directory
/run/user/1000.
-- Subject: A start job for unit user-runtime-dir@1000.service has
finished successfully
-- A start job for unit user-runtime-dir@1000.service has finished
successfully.
-- Subject: A start job for unit user@1000.service has begun execution
-- A start job for unit user@1000.service has begun execution.
Feb 19 18:45:28 nalik systemd[1737]: user@1000.service: Failed to
connect stdout to the journal socket, ignoring: Permission denied
Feb 19 18:45:28 nalik systemd[1]: user@1000.service: Failed with result
'protocol'.
-- The unit user@1000.service has entered the 'failed' state with result
'protocol'.
-- Subject: A start job for unit user@1000.service has failed
-- A start job for unit user@1000.service has finished with a failure.
Feb 19 18:45:28 nalik systemd[1]: Started Session 10 of user fre.
Feb 19 18:45:28 nalik systemd[1]: Stopping User Runtime Directory
/run/user/1000...
-- Subject: A stop job for unit user-runtime-dir@1000.service has begun
execution
-- A stop job for unit user-runtime-dir@1000.service has begun execution.
Feb 19 18:45:28 nalik systemd[475]: run-user-1000.mount: Succeeded.
Feb 19 18:45:28 nalik systemd[1]: run-user-1000.mount: Succeeded.
-- The unit run-user-1000.mount has successfully entered the 'dead' state.
Feb 19 18:45:28 nalik systemd[1]: user-runtime-dir@1000.service: Succeeded.
-- The unit user-runtime-dir@1000.service has successfully entered the
'dead' state.
Feb 19 18:45:28 nalik systemd[1]: Stopped User Runtime Directory
/run/user/1000.
-- Subject: A stop job for unit user-runtime-dir@1000.service has finished
-- A stop job for unit user-runtime-dir@1000.service has finished.
-- Subject: A stop job for unit user-1000.slice has finished
-- A stop job for unit user-1000.slice has finished.
Does reversing this change help?
https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/pambase&id=3552aba772e8bebbe754a4d01f2729e291dd2070
https://lists.archlinux.org/pipermail/arch-general/2019-February/046038.html
is some of the background.
I use without any problem last pambase-20190105.1-1 since january to
yesterday, each day.
--
Maderios
