stable

nfs-utils-2.8.1-1.rc1.fc41

FEDORA-2024-3925a63d2a created by steved a year ago for Fedora 41

Updated to the latest RC release: nfs-utils-2-8-2-rc1

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2024-3925a63d2a

This update has been submitted for testing by steved.

a year ago

This update's test gating status has been changed to 'waiting'.

a year ago

This update's test gating status has been changed to 'passed'.

a year ago

This update has been pushed to testing.

a year ago

bojan commented & provided feedback a year ago

karma

Broken:

UNIT LOAD ACTIVE SUB DESCRIPTION > ● nfs-mountd.service loaded failed failed NFS Mount Daemon ● rpc-statd.service loaded failed failed NFS status monitor for NFSv2/3 lockin> ● rpcbind.service loaded failed failed RPC Bind > ● rpcbind.socket loaded failed failed RPCbind Server Activation Socket

Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.

a year ago

bojan commented & provided feedback a year ago

karma

I am not 100% sure whether it's just nfs-utils package that is broken or both it and libtirpc. In any event, reverting both to the previous version made NFS server work again. New packages are dumping core.

derekenz commented & provided feedback a year ago

karma

Works

steved commented a year ago

UNIT LOAD ACTIVE SUB DESCRIPTION > ● nfs-mountd.service loaded failed failed NFS Mount Daemon ● rpc-statd.service > loaded failed failed NFS status monitor for NFSv2/3 lockin> ● rpcbind.service loaded failed failed RPC Bind > ● rpcbind.socket loaded failed failed RPCbind Server Activation Socket

Were are these failures coming from and I do I reproduce them?

steved commented a year ago

I am not 100% sure whether it's just nfs-utils package that is broken or both it and libtirpc. In any event, reverting both to > the previous version made NFS server work again. New packages are dumping core.

What is dumping core and when is it happening... Can you supply the core so it can be examined?

bojan commented & provided feedback a year ago

karma

Example:

coredumpctl dump 2047

       PID: 2047 (rpcbind)
       UID: 32 (rpc)
       GID: 32 (rpc)
    Signal: 6 (ABRT)
 Timestamp: Tue 2024-11-12 15:14:34 AEDT (22h ago)

Command Line: /usr/bin/rpcbind -w -f Executable: /usr/bin/rpcbind Control Group: /system.slice/rpcbind.service Unit: rpcbind.service Slice: system.slice Boot ID: 6faf5fe6882f4f3ca145f80d1a70da81 Machine ID: 41bfab309fa3f480517fa60045e51175 Hostname: <host> Storage: /var/lib/systemd/coredump/core.rpcbind.32.6faf5fe6882f4f3ca145f80d1a70da81.2047.1731384874000000.zst (present) Size on Disk: 130.3K Package: rpcbind/1.2.7-1.rc1.fc41 build-id: ef33ced525724c79d3df2aa7286dc53bc4d5a2c9 Message: Process 2047 (rpcbind) of user 32 dumped core.

            Module libpcre2-8.so.0 from rpm pcre2-10.44-1.fc41.1.x86_64
            Module libz.so.1 from rpm zlib-ng-2.1.7-3.fc41.x86_64
            Module libselinux.so.1 from rpm libselinux-3.7-5.fc41.x86_64
            Module libcrypto.so.3 from rpm openssl-3.2.2-9.fc41.x86_64
            Module libkeyutils.so.1 from rpm keyutils-1.6.3-4.fc41.x86_64
            Module libkrb5support.so.0 from rpm krb5-1.21.3-3.fc41.x86_64
            Module libcap.so.2 from rpm libcap-2.70-4.fc41.x86_64
            Module libcom_err.so.2 from rpm e2fsprogs-1.47.1-6.fc41.x86_64
            Module libk5crypto.so.3 from rpm krb5-1.21.3-3.fc41.x86_64
            Module libkrb5.so.3 from rpm krb5-1.21.3-3.fc41.x86_64
            Module libgssapi_krb5.so.2 from rpm krb5-1.21.3-3.fc41.x86_64
            Module libsystemd.so.0 from rpm systemd-256.7-1.fc41.x86_64
            Module libtirpc.so.3 from rpm libtirpc-1.3.6-0.rc1.fc41.x86_64
            Module rpcbind from rpm rpcbind-1.2.7-1.rc1.fc41.x86_64
            Stack trace of thread 2047:
            #0  0x00007f982ac43624 __pthread_kill_implementation (libc.so.6 + 0x72624)
            #1  0x00007f982abead1e raise (libc.so.6 + 0x19d1e)
            #2  0x00007f982abd2942 abort (libc.so.6 + 0x1942)
            #3  0x00007f982abd37a7 __libc_message_impl.cold (libc.so.6 + 0x27a7)
            #4  0x00007f982ac4d7a5 malloc_printerr (libc.so.6 + 0x7c7a5)
            #5  0x00007f982ac4fdaf _int_free (libc.so.6 + 0x7edaf)
            #6  0x00007f982ac5250e free (libc.so.6 + 0x8150e)
            #7  0x00007f982aebb4bd freenetconfigent (libtirpc.so.3 + 0x54bd)
            #8  0x00007f982aebced8 __rpc_sockinfo2netid (libtirpc.so.3 + 0x6ed8)
            #9  0x00007f982aed0bdc makefd_xprt (libtirpc.so.3 + 0x1abdc)
            #10 0x00007f982aed0d73 rendezvous_request (libtirpc.so.3 + 0x1ad73)
            #11 0x00007f982aed062f svc_getreq_common (libtirpc.so.3 + 0x1a62f)
            #12 0x00007f982aed0906 svc_getreq_poll (libtirpc.so.3 + 0x1a906)
            #13 0x00005585e6afc879 main (rpcbind + 0x2879)
            #14 0x00007f982abd4248 __libc_start_call_main (libc.so.6 + 0x3248)
            #15 0x00007f982abd430b __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x330b)
            #16 0x00005585e6afcd35 _start (rpcbind + 0x2d35)
            ELF object binary architecture: AMD x86-64

bojan commented a year ago

On the client, I have something like this in /etc/fstab:

<server>:<path> /net/<server>/<dir> nfs nofail,x-systemd.automount,x-systemd.mount-timeout=10,x-systemd.idle-timeout=300 0 0

On the server, I have this in /etc/exports:

<path> *.mydomain.com(rw,sync,sec=krb5)

Basically, systemd automount takes care of this for me. It works just fine when I downgrade.