Bug 261939 - Kerberized NFS mount requires the gssd to be restarted
Summary: Kerberized NFS mount requires the gssd to be restarted
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: misc (show other bugs)
Version: Unspecified
Hardware: Any Any
: --- Affects Some People
Assignee: Rick Macklem
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-13 21:59 UTC by Rick Macklem
Modified: 2022-02-22 04:37 UTC (History)
1 user (show)

See Also:
rmacklem: mfc-stable13+
rmacklem: mfc-stable12+


Attachments
Modify rc.d/gssd so that daemon starts after NETWORKING, kdc (275 bytes, patch)
2022-02-13 22:05 UTC, Rick Macklem
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Rick Macklem freebsd_committer freebsd_triage 2022-02-13 21:59:34 UTC

    
Comment 1 Rick Macklem freebsd_committer freebsd_triage 2022-02-13 22:05:32 UTC
Created attachment 231803 [details]
Modify rc.d/gssd so that daemon starts after NETWORKING, kdc

Arno Tuber reported via email that he had to restart the gssd
daemon after booting, to get a Kerberized NFS mount to work.

When I did an rcorder in /etc/rc.d, I noticed that the gssd
would start before NETWORKING and the kdc. The latter would
only matter if the KDC is on the same machine, but the gssd
will need to use NETWORKING to communicate with the KDC.

This patch adds NETWORKING and kdc to the REQUIRE line in
/etc/rc.d/gssd so that the daemon starts later.

Hopefully Arno will be able to test this and report if it
fixes the problem for him?
Comment 2 commit-hook freebsd_committer freebsd_triage 2022-02-15 22:20:06 UTC
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/src/commit/?id=0f5e9425e74b0e0ecf60c293525a307a6e709967

commit 0f5e9425e74b0e0ecf60c293525a307a6e709967
Author:     Rick Macklem <rmacklem@FreeBSD.org>
AuthorDate: 2022-02-15 22:18:23 +0000
Commit:     Rick Macklem <rmacklem@FreeBSD.org>
CommitDate: 2022-02-15 22:18:23 +0000

    gssd: Modify /etc/rc.d/gssd so that it starts after NETWORKING

    Arno Tuber reported via email that he needed to restart the gssd daemon
    after booting, to get his Kerberized NFS mount to work.

    Without this patch, rcorder shows that the gssd starts before NETWORKING
    and kdc. The gssd will need NETWORKING to connect to the KDC and, if
    the kdc is running on the same system, it does not make sense to start it
    before the kdc.  This fixed the problem for Arno.

    While here, I also added a "# BEFORE: mountcritremote".
    It does not affect ordering at this time, but I felt
    it should be added, since the gssd needs to be running
    when remote NFS mounts are done.

    PR:     261939
    Reported by:    anothatuber@gmail.com
    Tested by:      anothatuber@gmail.com
    Reviewed by:    rew
    MFC after:      1 week
    Differential Revision:  https://reviews.freebsd.org/D34265

 libexec/rc/rc.d/gssd | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
Comment 3 Rick Macklem freebsd_committer freebsd_triage 2022-02-15 22:33:48 UTC
Arno confirmed via email that the patch fixed his problem.
It has been committed and will be MFC'd.
Comment 4 commit-hook freebsd_committer freebsd_triage 2022-02-22 00:42:15 UTC
A commit in branch stable/13 references this bug:

URL: https://cgit.FreeBSD.org/src/commit/?id=cc6f50fc371f6a04fd20dd4f4d08e5d3fcdf6319

commit cc6f50fc371f6a04fd20dd4f4d08e5d3fcdf6319
Author:     Rick Macklem <rmacklem@FreeBSD.org>
AuthorDate: 2022-02-15 22:18:23 +0000
Commit:     Rick Macklem <rmacklem@FreeBSD.org>
CommitDate: 2022-02-22 00:40:10 +0000

    gssd: Modify /etc/rc.d/gssd so that it starts after NETWORKING

    Arno Tuber reported via email that he needed to restart the gssd daemon
    after booting, to get his Kerberized NFS mount to work.

    Without this patch, rcorder shows that the gssd starts before NETWORKING
    and kdc. The gssd will need NETWORKING to connect to the KDC and, if
    the kdc is running on the same system, it does not make sense to start it
    before the kdc.  This fixed the problem for Arno.

    While here, I also added a "# BEFORE: mountcritremote".
    It does not affect ordering at this time, but I felt
    it should be added, since the gssd needs to be running
    when remote NFS mounts are done.

    PR:     261939

    (cherry picked from commit 0f5e9425e74b0e0ecf60c293525a307a6e709967)

 libexec/rc/rc.d/gssd | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
Comment 5 commit-hook freebsd_committer freebsd_triage 2022-02-22 00:48:17 UTC
A commit in branch stable/12 references this bug:

URL: https://cgit.FreeBSD.org/src/commit/?id=0dd60a57103e7aa539f2a6916c3b774167dc664c

commit 0dd60a57103e7aa539f2a6916c3b774167dc664c
Author:     Rick Macklem <rmacklem@FreeBSD.org>
AuthorDate: 2022-02-15 22:18:23 +0000
Commit:     Rick Macklem <rmacklem@FreeBSD.org>
CommitDate: 2022-02-22 00:46:30 +0000

    gssd: Modify /etc/rc.d/gssd so that it starts after NETWORKING

    Arno Tuber reported via email that he needed to restart the gssd daemon
    after booting, to get his Kerberized NFS mount to work.

    Without this patch, rcorder shows that the gssd starts before NETWORKING
    and kdc. The gssd will need NETWORKING to connect to the KDC and, if
    the kdc is running on the same system, it does not make sense to start it
    before the kdc.  This fixed the problem for Arno.

    While here, I also added a "# BEFORE: mountcritremote".
    It does not affect ordering at this time, but I felt
    it should be added, since the gssd needs to be running
    when remote NFS mounts are done.

    PR:     261939

    (cherry picked from commit 0f5e9425e74b0e0ecf60c293525a307a6e709967)

 libexec/rc/rc.d/gssd | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
Comment 6 Rick Macklem freebsd_committer freebsd_triage 2022-02-22 04:37:48 UTC
Patch has been committed and MFC'd and seems to fix the problem.