[arch-general] Can't start mariadb and avahi anymore, cannot connect users
Hi Yesterday, it seems i broke something in my system: Arch is updated. Linux-lts kernel. 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. But I can connect as root. Other services are started normally: ntpd, connmand, bumblebeed, syslog-ng or metalog, sshd. I don't use any login manager like gdm. I don't use X, i use only tty, wayland and enlightenment-git. I remember i killed by hand yesterday in the evening ssh-agent processes. Problem came after that but may be a coincidence... It's a permission issue. I don't find any solution to debug it.
I have good symlinks in /var ls /var -1 -p cache/ db/ empty/ games/ lib/ local/ lock -> /run/lock log/ mail -> spool/mail net-snmp/ opt/ run -> /run spool/ tmp/
Syslog message
Feb 19 14:54:27 nalik systemd[965]: mariadb.service: Failed to connect stdout to the journal socket, ignoring: Permission denied Feb 19 14:54:27 nalik systemd[966]: mariadb.service: Failed to connect stdout to the journal socket, ignoring: Permission denied Feb 19 14:54:27 nalik systemd[980]: mariadb.service: Failed to connect stdout to the journal socket, ignoring: Permission denied Feb 19 14:54:27 nalik systemd[1]: mariadb.service: Main process exited, code=exited, status=200/CHDIR Feb 19 14:54:27 nalik systemd[1]: mariadb.service: Failed with result 'exit-code'. Feb 19 14:54:27 nalik kernel: audit: type=1130 audit(1550584467.632:72): 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 14:54:51 nalik systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Feb 19 14:54:51 nalik avahi-daemon[989]: Found user 'avahi' (UID 84) and group 'avahi' (GID 84). Feb 19 14:54:51 nalik avahi-daemon[989]: Successfully dropped root privileges. Feb 19 14:54:51 nalik systemd[1]: avahi-daemon.service: Main process exited, code=exited, status=255/EXCEPTION Feb 19 14:54:51 nalik systemd[1]: avahi-daemon.service: Failed with result 'exit-code'. Feb 19 14:54:51 nalik kernel: audit: type=1130 audit(1550584491.312:73): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=avahi-daemon comm="systemd" exe="/usr/lib/systemd/sy stemd" hostname=? addr=? terminal=? res=failed' Feb 19 14:55:20 nalik systemd[1]: Created slice User Slice of UID 1000. Feb 19 14:55:20 nalik systemd[1]: Starting User Runtime Directory /run/user/1000... Feb 19 14:55:20 nalik kernel: audit: type=1006 audit(1550584520.233:74): pid=642 uid=0 old-auid=4294967295 auid=1000 tty=tty1 old-ses=4294967295 ses=8 res=1 Feb 19 14:55:20 nalik systemd[1]: Started User Runtime Directory /run/user/1000. Feb 19 14:55:20 nalik systemd[1]: Starting User Manager for UID 1000... Feb 19 14:55:20 nalik systemd[996]: user@1000.service: Failed to connect stdout to the journal socket, ignoring: Permission denied Feb 19 14:55:20 nalik kernel: audit: type=1130 audit(1550584520.243:75): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/s ystemd/systemd" hostname=? addr=? terminal=? res=success' Feb 19 14:55:20 nalik kernel: audit: type=1006 audit(1550584520.253:76): pid=996 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=9 res=1 Feb 19 14:55:20 nalik kernel: audit: type=1130 audit(1550584520.263:77): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1000 comm="systemd" exe="/usr/lib/systemd/syste md" hostname=? addr=? terminal=? res=failed' Feb 19 14:55:20 nalik kernel: audit: type=1131 audit(1550584520.273:78): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/syst emd" hostname=? addr=? terminal=? res=success' Feb 19 14:55:20 nalik kernel: audit: type=1130 audit(1550584520.273:79): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/syst emd" hostname=? addr=? terminal=? res=success' Feb 19 14:55:20 nalik kernel: audit: type=1131 audit(1550584520.273:80): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/syst emd" hostname=? addr=? terminal=? res=success' Feb 19 14:55:20 nalik kernel: audit: type=1130 audit(1550584520.283:81): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/syst emd" hostname=? addr=? terminal=? res=success' Feb 19 14:55:20 nalik kernel: audit: type=1131 audit(1550584520.333:82): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/s ystemd/systemd" hostname=? addr=? terminal=? res=success' Feb 19 14:55:20 nalik systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 19 14:55:20 nalik systemd[1]: Started Session 8 of user fre. Feb 19 14:55:20 nalik systemd[1]: getty@tty1.service: Succeeded. Feb 19 14:55:20 nalik systemd[1]: getty@tty1.service: Service has no hold-off time (RestartSec=0), scheduling restart. Feb 19 14:55:20 nalik systemd[1]: getty@tty1.service: Scheduled restart job, restart counter is at 2. Feb 19 14:55:20 nalik systemd[1]: Stopped Getty on tty1. Feb 19 14:55:20 nalik systemd[1]: Started Getty on tty1. Feb 19 14:55:20 nalik systemd[1]: session-8.scope: Succeeded. Feb 19 14:55:20 nalik systemd[1]: Stopping User Runtime Directory /run/user/1000... Feb 19 14:55:20 nalik systemd[475]: run-user-1000.mount: Succeeded. Feb 19 14:55:20 nalik systemd[1]: run-user-1000.mount: Succeeded. Feb 19 14:55:20 nalik systemd[1]: user-runtime-dir@1000.service: Succeeded. Feb 19 14:55:20 nalik systemd[1]: Stopped User Runtime Directory /run/user/1000. Feb 19 14:55:20 nalik systemd[1]: Removed slice User Slice of UID 1000.
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?
Does reversing this change help? https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/pamb...
https://lists.archlinux.org/pipermail/arch-general/2019-February/046038.html is some of the background.
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/pamb...
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.
On 2/19/19 5:29 PM, leoutation@gmx.fr wrote:
Hi Yesterday, it seems i broke something in my system: Arch is updated. Linux-lts kernel. 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. But I can connect as root.
I solved problem doing: chmod --preserve-root 755 / I posted explanations here: https://bbs.archlinux.org/viewtopic.php?id=244335
participants (2)
-
leoutation＠gmx.fr
-
Ralph Corderoy