NFS share is not working anymore: polkitd Unregistered Authentication Agent for unix-service

English Network/Internet
#1

Hi,

i have a NFS share to allow my main pc to access a data storage on my NAS pc. I use this for years but as i tried to access the share today it did not worked. I do not understand what changed. Here is my system mount unit file for that was working before:


[Unit]
Description=Mount /mnt/nas/public
Wants=network-online.target
After=network-online.target

[Mount]
What=192.168.178.137:/mnt/volume1/public
Where=/mnt/nas/public
Type=nfs

[Install]
WantedBy=multi-user.target

192.168.178.137 is the local IP of my NAS. It is still there and healthy the services are also still running.

journalctl -xe has this related entries:


-- The job identifier is 2832.
Feb 08 22:12:15 mypc.fritz.box mount[2879]: Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service.
Feb 08 22:12:15 mypc.fritz.box systemd[1]: Reloading.
Feb 08 22:12:15 mypc.fritz.box systemd[1]: /usr/lib/systemd/system/rpc-statd.service:15: PIDFile= references a path below legacy directory /var/run/, updating /var/run/rpc.statd.pid → /run/rpc.statd.pid; please update the unit file >
Feb 08 22:12:15 mypc.fritz.box systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please updat>
Feb 08 22:12:15 mypc.fritz.box systemd[1]: /usr/lib/systemd/system/ntpd.service:15: PIDFile= references a path below legacy directory /var/run/, updating /var/run/ntp/ntpd.pid → /run/ntp/ntpd.pid; please update the unit file accordi>
Feb 08 22:12:15 mypc.fritz.box systemd[1]: /usr/lib/systemd/system/pcscd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/pcscd/pcscd.comm → /run/pcscd/pcscd.comm; please update the unit >
Feb 08 22:12:15 mypc.fritz.box systemd[1]: /usr/lib/systemd/system/usbmuxd.service:7: PIDFile= references a path below legacy directory /var/run/, updating /var/run/usbmuxd.pid → /run/usbmuxd.pid; please update the unit file accordi>
Feb 08 22:12:15 mypc.fritz.box mount[2859]: mount.nfs: Protocol not supported
Feb 08 22:12:15 mypc.fritz.box systemd[1]: mnt-nas-public.mount: Mount process exited, code=exited, status=32/n/a
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- An n/a= process belonging to unit mnt-nas-public.mount has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 32.
Feb 08 22:12:15 mypc.fritz.box systemd[1]: mnt-nas-public.mount: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit mnt-nas-public.mount has entered the 'failed' state with result 'exit-code'.
Feb 08 22:12:15 mypc.fritz.box systemd[1]: Failed to mount Mount /mnt/nas/public.
-- Subject: A start job for unit mnt-nas-public.mount has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit mnt-nas-public.mount has finished with a failure.
-- 
-- The job identifier is 2704 and the job result is failed.
Feb 08 22:12:15 mypc.fritz.box polkitd[1464]: Unregistered Authentication Agent for unix-process:2818:5299 (system bus name :1.56, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8) (disconnected from b>
Feb 08 22:12:17 mypc.fritz.box PackageKit[2782]: daemon quit
Feb 08 22:12:17 mypc.fritz.box systemd[1]: packagekit.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit packagekit.service has successfully entered the 'dead' state.
Feb 08 22:12:19 mypc.fritz.box kwin_x11[2532]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 11845, resource id: 35651727, major code: 18 (ChangeProperty), minor code: 0
Feb 08 22:12:19 mypc.fritz.box plasmashell[2534]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:454: TypeError: Cannot read property 'length' of undefined
Feb 08 22:12:19 mypc.fritz.box plasmashell[2534]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:371: Unable to assign [undefined] to QString
Feb 08 22:12:21 mypc.fritz.box nscd[1476]: 1476 Prüfe auf überwachte Datei »/etc/services«: Datei oder Verzeichnis nicht gefunden

Does anyone know what could be the problem here?

#2

Hi
There are a couple of long threads on the Mailing List that should shed some light…
https://lists.opensuse.org/opensuse-factory/2020-02/
https://lists.opensuse.org/opensuse-factory/2020-02/msg00023.html

#3

ok so this will get resolved with the next updates?

#4

Hi
Did you check for rpmnew files, did you merge the changes, eg /etc/nsswitch.conf file?

#5

[QUOTE=sabo007;2926642today it did not worked. I do not understand what changed.[/quote]
So why you decided to put “polkitd” in the subject as if you debugged it and found polkitd was the reason?

Feb 08 22:12:15 mypc.fritz.box mount[2859]: mount.nfs: Protocol not supported
Feb 08 22:12:15 mypc.fritz.box systemd[1]: mnt-nas-public.mount: Mount process exited, code=exited, status=32/n/a

https://forums.opensuse.org/showthread.php/539038-mount-command-not-working

No (at least, in foreseeable future). You need to adjust local configuration file /etc/nsswitch.conf on your system manually.

#6

I made the changes in the nsswitch.conf now, did not reboot but will right after finishing this post (edit: reboot was not necessary, the mount is working now).

I did not made them before because i thought they where just forgotten and such get added by the next update. Manually doing such changes seems like provisional to me, something which maybe has to be reverted later… but is in my personal responsibility now. As i do not fully understand what some changes do, i can imagine that they can become a security problem later, as soon as the original conflict is solved.

Or do you imply that my specific problem with the nfs mount would not occur on a freshly installed system?

My assumption that the problem is polkit related is because of a line in journalctl (which i posted above)… but i noticed that i get the same line on my notebook… but the nfs mount is working there… but also hold the backups back

#7

where do i find those rpmnew files?

#8

Hi
Run the command;


rpmconfigcheck

It will tell you, then use the diff command to see what changed (I use diff -Naur <old_file> <new_file> ).

#9

thank you that was very insightful.