You are not logged in.

Pages: 1

#1 2022-01-23 19:25:53

Morta
Member
Registered: 2019-07-07
Posts: 660

[SOLVED]nfsv4-server don't work

[root@nas ~]# systemctl start nfs
nfs-blkmap.service    nfs-client.target     nfs-utils.service     nfsv4-server.service  
[root@nas ~]# systemctl status nfsv4-server.service 
○ nfsv4-server.service - NFSv4 server and services
     Loaded: loaded (/usr/lib/systemd/system/nfsv4-server.service; disabled; vendor preset: disabled)
     Active: inactive (dead)

Jan 23 19:18:24 nas systemd[1]: Dependency failed for NFSv4 server and services.
Jan 23 19:18:24 nas systemd[1]: nfsv4-server.service: Job nfsv4-server.service/start failed with result 'dependency'.
Jan 23 19:19:44 nas systemd[1]: nfsv4-server.service: Trying to enqueue job nfsv4-server.service/start/replace
Jan 23 19:19:44 nas systemd[1]: nfsv4-server.service: Installed new job nfsv4-server.service/start as 69737
Jan 23 19:19:44 nas systemd[1]: nfsv4-server.service: Enqueued job nfsv4-server.service/start as 69737
Jan 23 19:19:44 nas systemd[1]: nfsv4-server.service: starting held back, waiting for: nfsv4-exportd.service
Jan 23 19:19:44 nas systemd[1]: nfsv4-server.service: starting held back, waiting for: nfsv4-exportd.service
Jan 23 19:19:44 nas systemd[1]: nfsv4-server.service: Job 69737 nfsv4-server.service/start finished, result=dependency
Jan 23 19:19:44 nas systemd[1]: Dependency failed for NFSv4 server and services.
Jan 23 19:19:44 nas systemd[1]: nfsv4-server.service: Job nfsv4-server.service/start failed with result 'dependency'.
[root@nas ~]# exportfs -av
exporting 192.168.1.0/24:/home/data
[morta@nas DATA]$ systemctl start nfsv4-server.service 
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ====
Authentication is required to start 'nfsv4-server.service'.
Authenticating as: morta
Password: 
==== AUTHENTICATION COMPLETE ====
A dependency job for nfsv4-server.service failed. See 'journalctl -xe' for details.
[morta@nas DATA]$ journalctl -xe
Jan 23 19:19:44 nas systemd[1]: Sent message type=method_return sender=n/a destination=:1.1287 path=n/a interface=n/a member=n/a cookie=58817 reply_cookie=4 signature=o error-name=n/a error-message=n/a
Jan 23 19:19:44 nas systemd[1]: systemd-journald.service: Received EPOLLHUP on stored fd 47 (stored), closing.
Jan 23 19:19:44 nas systemd[1]: systemd-journald.service: Received EPOLLHUP on stored fd 48 (stored), closing.
Jan 23 19:19:44 nas systemd[1]: systemd-journald.service: Received EPOLLHUP on stored fd 52 (stored), closing.
Jan 23 19:19:44 nas systemd[1]: Got message type=method_call sender=:1.1287 destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1/unit/nfsv4_2dserver_2eservice interface=org.freedesktop.DBus.Properties member=Get cookie=5 re>
Jan 23 19:19:44 nas systemd[1]: Sent message type=method_return sender=n/a destination=:1.1287 path=n/a interface=n/a member=n/a cookie=58818 reply_cookie=5 signature=v error-name=n/a error-message=n/a
Jan 23 19:19:44 nas kernel: audit: type=1130 audit(1642965584.763:6519): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nfs-mountd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jan 23 19:19:44 nas kernel: audit: type=1130 audit(1642965584.763:6520): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nfsv4-exportd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jan 23 19:19:44 nas polkitd[184467]: Unregistered Authentication Agent for unix-process:184462:71457702 (system bus name :1.1285, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jan 23 19:19:45 nas systemd[1]: php-fpm.service: Got notification message from PID 182932 (READY=1, STATUS=Processes active: 0, idle: 5, Requests: 1096, slow: 0, Traffic: 0.1req/sec)
Jan 23 19:19:45 nas systemd[1]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1/unit/php_2dfpm_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=58819 reply_cookie=0 sig>
Jan 23 19:19:45 nas systemd[1]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1/unit/php_2dfpm_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=58820 reply_cookie=0 sig>
Jan 23 19:19:50 nas systemd[1]: varlink: New incoming connection.
Jan 23 19:19:50 nas systemd[1]: varlink: Connections of user 1000: 0 (of 1024 max)
Jan 23 19:19:50 nas systemd[1]: varlink-26: Setting state idle-server
Jan 23 19:19:50 nas systemd[1]: varlink-26: New incoming message: {"method":"io.systemd.UserDatabase.GetGroupRecord","parameters":{"groupName":"systemd-journal","service":"io.systemd.DynamicUser"}}
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state idle-server → processing-method
Jan 23 19:19:50 nas systemd[1]: varlink-26: Sending message: {"error":"io.systemd.UserDatabase.NoRecordFound","parameters":{}}
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state processing-method → processed-method
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state processed-method → idle-server
Jan 23 19:19:50 nas systemd[1]: varlink-26: Got POLLHUP from socket.
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state idle-server → pending-disconnect
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state pending-disconnect → processing-disconnect
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state processing-disconnect → disconnected
Jan 23 19:19:50 nas systemd[1]: varlink: New incoming connection.
Jan 23 19:19:50 nas systemd[1]: varlink: Connections of user 1000: 0 (of 1024 max)
Jan 23 19:19:50 nas systemd[1]: varlink-26: Setting state idle-server
Jan 23 19:19:50 nas systemd[1]: varlink-26: New incoming message: {"method":"io.systemd.UserDatabase.GetMemberships","parameters":{"groupName":"systemd-journal","service":"io.systemd.DynamicUser"},"more":true}
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state idle-server → processing-method-more
Jan 23 19:19:50 nas systemd[1]: varlink-26: Sending message: {"error":"io.systemd.UserDatabase.NoRecordFound","parameters":{}}
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state processing-method-more → processed-method
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state processed-method → idle-server
Jan 23 19:19:50 nas systemd[1]: varlink-26: Got POLLHUP from socket.
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state idle-server → pending-disconnect
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state pending-disconnect → processing-disconnect
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state processing-disconnect → disconnected
Jan 23 19:19:50 nas systemd[1]: varlink: New incoming connection.
Jan 23 19:19:50 nas systemd[1]: varlink: Connections of user 1000: 0 (of 1024 max)
Jan 23 19:19:50 nas systemd[1]: varlink-26: Setting state idle-server
Jan 23 19:19:50 nas systemd[1]: varlink-26: New incoming message: {"method":"io.systemd.UserDatabase.GetGroupRecord","parameters":{"gid":998,"service":"io.systemd.DynamicUser"}}
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state idle-server → processing-method
Jan 23 19:19:50 nas systemd[1]: varlink-26: Sending message: {"error":"io.systemd.UserDatabase.NoRecordFound","parameters":{}}
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state processing-method → processed-method
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state processed-method → idle-server
Jan 23 19:19:50 nas systemd[1]: varlink-26: Got POLLHUP from socket.
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state idle-server → pending-disconnect
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state pending-disconnect → processing-disconnect
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state processing-disconnect → disconnected
Jan 23 19:19:50 nas systemd[1]: varlink: New incoming connection.
Jan 23 19:19:50 nas systemd[1]: varlink: Connections of user 1000: 0 (of 1024 max)
Jan 23 19:19:50 nas systemd[1]: varlink-26: Setting state idle-server
Jan 23 19:19:50 nas systemd[1]: varlink-26: New incoming message: {"method":"io.systemd.UserDatabase.GetMemberships","parameters":{"groupName":"wheel","service":"io.systemd.DynamicUser"},"more":true}
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state idle-server → processing-method-more
Jan 23 19:19:50 nas systemd[1]: varlink-26: Sending message: {"error":"io.systemd.UserDatabase.NoRecordFound","parameters":{}}
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state processing-method-more → processed-method
Jan 23 19:19:50 nas systemd[1]: varlink-26: Changing state processed-method → idle-server
Jan 23 19:19:50 nas systemd[1]: varlink-26: Got POLLHUP from socket.

What is wrong?

Last edited by Morta (2022-01-25 22:22:55)

Offline

#2 2022-01-23 20:10:00

paulkerry
Member
From: Sheffield, UK
Registered: 2014-10-02
Posts: 611

Re: [SOLVED]nfsv4-server don't work

Wrong command? https://wiki.archlinux.org/title/NFS#St … the_server says...
"Start and enable nfs-server.service"

Offline

#3 2022-01-23 20:40:32

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [SOLVED]nfsv4-server don't work

paulkerry wrote:

Wrong command? https://wiki.archlinux.org/title/NFS#St … the_server says...
"Start and enable nfs-server.service"

Same result with systemctl nfs-server.service

Offline

#4 2022-01-23 20:56:10

paulkerry
Member
From: Sheffield, UK
Registered: 2014-10-02
Posts: 611

Re: [SOLVED]nfsv4-server don't work

Did you do the rest of the server configuration https://wiki.archlinux.org/title/NFS#Configuration i.e. have you correctly setup /etc/exports?

Offline

#5 2022-01-23 20:56:12

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [SOLVED]nfsv4-server don't work

systemctl list-dependencies nfs-server
nfs-server.service
● ├─-.mount
○ ├─auth-rpcgss-module.service
● ├─home-data.mount
● ├─home.mount
× ├─nfs-idmapd.service
× ├─nfs-mountd.service
● ├─nfsdcld.service
● ├─proc-fs-nfsd.mount
● ├─rpc-statd-notify.service
● ├─rpc-statd.service
● ├─rpcbind.socket
● ├─system.slice
● ├─network-online.target
● │ └─NetworkManager-wait-online.service
● └─network.target
systemctl status nfs-mountd
× nfs-mountd.service - NFS Mount Daemon
     Loaded: loaded (/usr/lib/systemd/system/nfs-mountd.service; static)
     Active: failed (Result: exit-code) since Sun 2022-01-23 20:42:14 UTC; 2min 44s ago
    Process: 185367 ExecStart=/usr/sbin/rpc.mountd (code=exited, status=203/EXEC)
        CPU: 470us

Jan 23 20:42:14 nas systemd[1]: nfs-mountd.service: Control process exited, code=exited, status=203/EXEC
Jan 23 20:42:14 nas systemd[1]: nfs-mountd.service: Got final SIGCHLD for state start.
Jan 23 20:42:14 nas systemd[1]: nfs-mountd.service: Failed with result 'exit-code'.
Jan 23 20:42:14 nas systemd[1]: nfs-mountd.service: Service will not restart (restart setting)
Jan 23 20:42:14 nas systemd[1]: nfs-mountd.service: Changed start -> failed
Jan 23 20:42:14 nas systemd[1]: nfs-mountd.service: Job 72417 nfs-mountd.service/start finished, result=failed
Jan 23 20:42:14 nas systemd[1]: Failed to start NFS Mount Daemon.
Jan 23 20:42:14 nas systemd[1]: nfs-mountd.service: Unit entered failed state.
Jan 23 20:42:14 nas systemd[1]: nfs-mountd.service: Consumed 470us CPU time.
Jan 23 20:42:14 nas systemd[1]: nfs-mountd.service: Control group is empty.

Offline

#6 2022-01-23 20:58:57

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [SOLVED]nfsv4-server don't work

paulkerry wrote:

Did you do the rest of the server configuration https://wiki.archlinux.org/title/NFS#Configuration i.e. have you correctly setup /etc/exports?

cat /etc/exports
# /etc/exports - exports(5) - directories exported to NFS clients
#
# Example for NFSv2 and NFSv3:
#  /srv/home        hostname1(rw,sync) hostname2(ro,sync)
# Example for NFSv4:
#  /srv/nfs4	    hostname1(rw,sync,fsid=0)
#  /srv/nfs4/home   hostname1(rw,sync,nohide)
# Using Kerberos and integrity checking:
#  /srv/nfs4        *(rw,sync,sec=krb5i,fsid=0)
#  /srv/nfs4/home   *(rw,sync,sec=krb5i,nohide)
#
# Use `exportfs -arv` to reload.
/home/data  192.168.1.0/24(rw,sync,no_subtree_check,all_squash,anonuid=1,anongid=1)

Offline

#7 2022-01-23 21:04:40

paulkerry
Member
From: Sheffield, UK
Registered: 2014-10-02
Posts: 611

Re: [SOLVED]nfsv4-server don't work

You don't have "fsid=0" in /etc/exports - i.e. you haven't yet exported the nfs root yet which I presume you mean to be /home: re-read the config section.

Offline

#8 2022-01-23 21:07:52

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [SOLVED]nfsv4-server don't work

paulkerry wrote:

You don't have "fsid=0" in /etc/exports - i.e. you haven't yet exported the nfs root yet which I presume you mean to be /home: re-read the config section.

I adjusted it.

/srv/nfs 192.168.1.0/24(rw,sync,crossmnt,no_subtree_check,fsid=0)
/srv/nfs/data 192.168.1.0/24(rw,sync,no_subtree_check,all_squash,anonuid=1,anongid=1)
cat /etc/fstab 
# /dev/mapper/vg_data-root
UUID=40744119-c6a4-4668-a13c-0bb29cf23bef	/         	ext4      	rw,relatime	0 1

# /dev/mapper/vg_data-home
UUID=5e06c66b-a98f-4cc3-815c-a406473472bf	/home     	ext4      	rw,relatime	0 2

# /dev/mapper/vg_data-data
UUID=977b1181-4f6e-4e12-aea5-516452eaf144	/home/data	ext4      	rw,relatime,stripe=640	0 2

# /dev/nvme0n1p1
UUID=C7CE-3B79      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/mapper/vg_data-swap
UUID=b3f0ca47-48e2-4096-83d8-e414dc8c489a	none      	swap      	defaults  	0 0

# /srv/nfs/data
/home/data	/srv/nfs/data	none	bind	0 0

but doesn't work!

Offline

#9 2022-01-23 21:16:41

paulkerry
Member
From: Sheffield, UK
Registered: 2014-10-02
Posts: 611

Re: [SOLVED]nfsv4-server don't work

sanity check - after adding your bind mount did you make the /srv directory tree and

mount -a

and then...

systemctl start nfs-server.service

Offline

#10 2022-01-23 21:19:45

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [SOLVED]nfsv4-server don't work

paulkerry wrote:

sanity check - after adding your bind mount did you make the /srv directory tree and

mount -a

and then...

systemctl start nfs-server.service

/srv/nfs/data exits

mount -a sucsessful but can't start nfs-server!

Offline

#11 2022-01-25 19:48:27

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [SOLVED]nfsv4-server don't work

journalctl -e
Jan 25 19:46:25 nas dbus-daemon[712]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.47' (uid=0 pid=1460 comm="sudo systemctl start nfs-server.service ")
Jan 25 19:46:25 nas dbus-daemon[712]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Jan 25 19:46:25 nas sudo[1460]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Jan 25 19:46:25 nas audit[1460]: USER_ACCT pid=1460 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="morta" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jan 25 19:46:25 nas sudo[1460]:    morta : TTY=pts/0 ; PWD=/home/morta ; USER=root ; COMMAND=/usr/bin/systemctl start nfs-server.service
Jan 25 19:46:25 nas audit[1460]: CRED_REFR pid=1460 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jan 25 19:46:25 nas audit[1460]: USER_START pid=1460 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=succ>
Jan 25 19:46:25 nas sudo[1460]: pam_unix(sudo:session): session opened for user root(uid=0) by morta(uid=1000)
Jan 25 19:46:25 nas kernel: audit: type=1101 audit(1643139985.717:271): pid=1460 uid=1000 auid=1000 ses=3 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="morta" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 >
Jan 25 19:46:25 nas kernel: audit: type=1110 audit(1643139985.717:272): pid=1460 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal>
Jan 25 19:46:25 nas kernel: audit: type=1105 audit(1643139985.717:273): pid=1460 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? >
Jan 25 19:46:25 nas systemd[1]: Kernel Module supporting RPCSEC_GSS was skipped because of a failed condition check (ConditionPathExists=/etc/krb5.keytab).
Jan 25 19:46:25 nas systemd[1]: Starting NFSv4 ID-name mapping service...
Jan 25 19:46:25 nas systemd[1463]: nfs-idmapd.service: Failed to locate executable /usr/sbin/rpc.idmapd: No such file or directory
Jan 25 19:46:25 nas systemd[1463]: nfs-idmapd.service: Failed at step EXEC spawning /usr/sbin/rpc.idmapd: No such file or directory
Jan 25 19:46:25 nas systemd[1]: Starting NFS Mount Daemon...
Jan 25 19:46:25 nas systemd[1464]: nfs-mountd.service: Failed to locate executable /usr/sbin/rpc.mountd: No such file or directory
Jan 25 19:46:25 nas systemd[1464]: nfs-mountd.service: Failed at step EXEC spawning /usr/sbin/rpc.mountd: No such file or directory
Jan 25 19:46:25 nas systemd[1]: Starting NFSv4 Client Tracking Daemon...
Jan 25 19:46:25 nas systemd[1465]: nfsdcld.service: Failed to locate executable /usr/sbin/nfsdcld: No such file or directory
Jan 25 19:46:25 nas systemd[1]: RPC security service for NFS client and server was skipped because of a failed condition check (ConditionPathExists=/etc/krb5.keytab).
Jan 25 19:46:25 nas systemd[1465]: nfsdcld.service: Failed at step EXEC spawning /usr/sbin/nfsdcld: No such file or directory
Jan 25 19:46:25 nas systemd[1]: Starting NFS status monitor for NFSv2/3 locking....
Jan 25 19:46:25 nas systemd[1466]: rpc-statd.service: Failed to locate executable /usr/sbin/rpc.statd: No such file or directory
Jan 25 19:46:25 nas systemd[1466]: rpc-statd.service: Failed at step EXEC spawning /usr/sbin/rpc.statd: No such file or directory
Jan 25 19:46:25 nas systemd[1]: nfs-idmapd.service: Control process exited, code=exited, status=203/EXEC
Jan 25 19:46:25 nas systemd[1]: nfs-idmapd.service: Failed with result 'exit-code'.
Jan 25 19:46:25 nas systemd[1]: Failed to start NFSv4 ID-name mapping service.
Jan 25 19:46:25 nas audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nfs-idmapd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jan 25 19:46:25 nas systemd[1]: nfs-mountd.service: Control process exited, code=exited, status=203/EXEC
Jan 25 19:46:25 nas systemd[1]: nfs-mountd.service: Failed with result 'exit-code'.
Jan 25 19:46:25 nas systemd[1]: Failed to start NFS Mount Daemon.
Jan 25 19:46:25 nas systemd[1]: Dependency failed for NFS server and services.
Jan 25 19:46:25 nas audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nfs-mountd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jan 25 19:46:25 nas systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'.
Jan 25 19:46:25 nas systemd[1]: nfsdcld.service: Control process exited, code=exited, status=203/EXEC
Jan 25 19:46:25 nas systemd[1]: nfsdcld.service: Failed with result 'exit-code'.
Jan 25 19:46:25 nas systemd[1]: Failed to start NFSv4 Client Tracking Daemon.
Jan 25 19:46:25 nas audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nfsdcld comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jan 25 19:46:25 nas systemd[1]: rpc-statd.service: Control process exited, code=exited, status=203/EXEC
Jan 25 19:46:25 nas systemd[1]: rpc-statd.service: Failed with result 'exit-code'.
Jan 25 19:46:25 nas systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 25 19:46:25 nas audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rpc-statd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jan 25 19:46:25 nas kernel: audit: type=1130 audit(1643139985.723:274): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nfs-idmapd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jan 25 19:46:25 nas kernel: audit: type=1130 audit(1643139985.723:275): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nfs-mountd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jan 25 19:46:25 nas kernel: audit: type=1130 audit(1643139985.723:276): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nfsdcld comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jan 25 19:46:25 nas kernel: audit: type=1130 audit(1643139985.723:277): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rpc-statd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jan 25 19:46:25 nas sudo[1460]: pam_unix(sudo:session): session closed for user root
Jan 25 19:46:25 nas audit[1460]: USER_END pid=1460 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=succe>
Jan 25 19:46:25 nas audit[1460]: CRED_DISP pid=1460 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jan 25 19:46:25 nas kernel: audit: type=1106 audit(1643139985.737:278): pid=1460 uid=1000 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=?>
Jan 25 19:46:25 nas kernel: audit: type=1104 audit(1643139985.737:279): pid=1460 uid=1000 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal>
lines 949-1000/1000 (END)
 nas systemd[1]: nfsdcld.service: Failed with result 'exit-code'
 nas systemd[1]: rpc-statd.service: Failed with result 'exit-code'
Jan 25 16:13:02 nas systemd[1]: Starting NFS status monitor for NFSv2/3 locking....
Jan 25 16:13:02 nas systemd[998]: rpc-statd.service: Failed to locate executable /usr/sbin/rpc.statd: No such file or directory
Jan 25 16:13:02 nas systemd[998]: rpc-statd.service: Failed at step EXEC spawning /usr/sbin/rpc.statd: No such file or directory
Jan 25 16:13:02 nas systemd[1]: rpc-statd.service: Control process exited, code=exited, status=203/EXEC
Jan 25 16:13:02 nas systemd[1]: rpc-statd.service: Failed with result 'exit-code'.
Jan 25 16:13:02 nas systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 25 19:41:21 nas systemd[1]: Starting NFS status monitor for NFSv2/3 locking....
Jan 25 19:41:21 nas systemd[1]: rpc-statd.service: Control process exited, code=exited, status=203/EXEC
Jan 25 19:41:21 nas systemd[1]: rpc-statd.service: Failed with result 'exit-code'.
Jan 25 19:41:21 nas systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
Jan 25 19:44:55 nas systemd[1]: Starting NFS status monitor for NFSv2/3 locking....
Jan 25 19:44:55 nas systemd[1]: rpc-statd.service: Control process exited, code=exited, status=203/EXEC
Jan 25 19:44:55 nas systemd[1]: rpc-statd.service: Failed with result 'exit-code'.
Jan 25 19:44:55 nas systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking.

What is wrong and how to fix it?

Last edited by Morta (2022-01-25 19:49:52)

Offline

#12 2022-01-25 21:18:52

-thc
Member
Registered: 2017-03-15
Posts: 775

Re: [SOLVED]nfsv4-server don't work

All the "nfs-utils" in "/usr/sbin" seem to be missing! What happened?

Offline

#13 2022-01-25 21:22:53

seth
Member
Registered: 2012-09-03
Posts: 60,922

Re: [SOLVED]nfsv4-server don't work

/usr/sbin is a symlink to bin and after the previous situation w/ /usr/lib64, I guess dpkg happened here as well.

@Morta

sudo pacman -Qkk filesystem

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#14 2022-01-25 22:10:56

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [SOLVED]nfsv4-server don't work

[morta@nas ~]$ sudo pacman -Qkk filesystem
backup file: filesystem: /etc/fstab (Modification time mismatch)
backup file: filesystem: /etc/fstab (Size mismatch)
backup file: filesystem: /etc/fstab (MD5 checksum mismatch)
backup file: filesystem: /etc/fstab (SHA256 checksum mismatch)
backup file: filesystem: /etc/group (Modification time mismatch)
backup file: filesystem: /etc/group (Size mismatch)
backup file: filesystem: /etc/group (MD5 checksum mismatch)
backup file: filesystem: /etc/group (SHA256 checksum mismatch)
backup file: filesystem: /etc/gshadow (Modification time mismatch)
backup file: filesystem: /etc/gshadow (Size mismatch)
backup file: filesystem: /etc/gshadow (MD5 checksum mismatch)
backup file: filesystem: /etc/gshadow (SHA256 checksum mismatch)
backup file: filesystem: /etc/hosts (Modification time mismatch)
backup file: filesystem: /etc/hosts (Size mismatch)
backup file: filesystem: /etc/hosts (MD5 checksum mismatch)
backup file: filesystem: /etc/hosts (SHA256 checksum mismatch)
backup file: filesystem: /etc/passwd (Modification time mismatch)
backup file: filesystem: /etc/passwd (Size mismatch)
backup file: filesystem: /etc/passwd (MD5 checksum mismatch)
backup file: filesystem: /etc/passwd (SHA256 checksum mismatch)
backup file: filesystem: /etc/resolv.conf (Modification time mismatch)
backup file: filesystem: /etc/resolv.conf (Size mismatch)
backup file: filesystem: /etc/resolv.conf (MD5 checksum mismatch)
backup file: filesystem: /etc/resolv.conf (SHA256 checksum mismatch)
backup file: filesystem: /etc/shadow (Modification time mismatch)
backup file: filesystem: /etc/shadow (Size mismatch)
backup file: filesystem: /etc/shadow (MD5 checksum mismatch)
backup file: filesystem: /etc/shadow (SHA256 checksum mismatch)
backup file: filesystem: /etc/shells (Modification time mismatch)
backup file: filesystem: /etc/shells (Size mismatch)
backup file: filesystem: /etc/shells (MD5 checksum mismatch)
backup file: filesystem: /etc/shells (SHA256 checksum mismatch)
warning: filesystem: /tmp (UID mismatch)
warning: filesystem: /usr/lib64 (Modification time mismatch)
warning: filesystem: /usr/sbin (No such file or directory)
filesystem: 116 total files, 3 altered file

How I can fix /usr/sbin ?

Last edited by Morta (2022-01-25 22:19:24)

Offline

#15 2022-01-25 22:14:45

seth
Member
Registered: 2012-09-03
Posts: 60,922

Re: [SOLVED]nfsv4-server don't work

So it's only 

warning: filesystem: /usr/sbin (No such file or directory)

- dpkg…

ln -s bin /usr/sbin

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#16 2022-01-25 22:21:57

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [SOLVED]nfsv4-server don't work

It's working again.

Thanks so I have to remember this commands...

pacman -Qkk filesystem
ldd /bin/init



Thanks Mate.

Offline

Pages: 1

Board footer

Powered by FluxBB