Some errors starting ganesha - ceph
Hi, I'm running nfs-ganesha from docker container. It seems work perfectly, nevertheless when I start the server I get the following messages: Bootstrapping Ganesha NFS config, Bootstrapping CA cert, Skipping boostraping idmap config, Starting rpcbind, Starting rpc.statd, Starting sssd, Starting dbus, Starting Ganesha NFS, 28/01/2019 23:15:17 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] main :MAIN :EVENT :ganesha.nfsd Starting: Ganesha Version 2.7.1, 28/01/2019 23:15:17 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_set_param_from_conf :NFS STARTUP :EVENT :Configuration file successfully parsed, 28/01/2019 23:15:17 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] init_server_pkgs :NFS STARTUP :EVENT :Initializing ID Mapper., 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] init_server_pkgs :NFS STARTUP :EVENT :ID Mapper successfully initialized., 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start_grace :STATE :EVENT :NFS Server Now IN GRACE, duration 90, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] lower_my_caps :NFS STARTUP :EVENT :CAP_SYS_RESOURCE was successfully removed for proper quota management in FSAL, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] lower_my_caps :NFS STARTUP :EVENT :currenty set capabilities are: = cap_chown,cap_dac_override,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_net_bind_service,cap_net_raw,cap_sys_chroot,cap_mknod,cap_audit_write,cap_setfcap+eip, *28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Init_svc :DISP :CRIT :Cannot acquire credentials for principal nfs,* 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Init_admin_thread :NFS CB :EVENT :Admin thread initialized, *28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :EVENT :Callback creds directory (/var/run/ganesha) already exists,* *28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :WARN :gssd_refresh_krb5_machine_credential failed (-1765328160:0),* 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :Starting delayed executor., 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :9P/TCP dispatcher thread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :gsh_dbusthread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :admin thread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :reaper thread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :General fridge was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[_9p_disp] _9p_dispatcher_thread :9P DISP :EVENT :9P dispatcher started, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] rpc :TIRPC :EVENT :svc_rqst_hook_events: 0x4b7cb80 fd 1024 xp_refcnt 1 sr_rec 0x4af76d0 evchan 2 ev_refcnt 3 epoll_fd 37 control fd pair (35:36) hook failed (9), *28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nsm_connect :NLM :CRIT :connect to statd failed: RPC: Unknown protocol,* *28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nsm_unmonitor_all :NLM :CRIT :Unmonitor all nsm_connect failed,* 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start :NFS STARTUP :EVENT :-------------------------------------------------, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start :NFS STARTUP :EVENT : NFS SERVER INITIALIZED, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start :NFS STARTUP :EVENT :-------------------------------------------------, *28/01/2019 23:16:50 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[reaper] nfs_lift_grace_locked :STATE :EVENT :NFS Server Now NOT IN GRACE* I'd like to fix them in order to have a clean execution. Is this possible? Any help will be welcome, Thanks a lot. Ó
The first set is related to kerberos. You should be able to disable krb5 config if you're not using it. Otherwise, you'll have to fix the krb5 settings/server to make that work. The second set is failure to connect to statd. This is likely related to running in containers, where the ganesha container cannot connect to the statd. The third one in red is not an error. It's a notification that Ganesha has left Grace. I don't know why your system marks it red. Daniel On 1/28/19 5:20 PM, Oscar Segarra wrote:
Hi,
I'm running nfs-ganesha from docker container. It seems work perfectly, nevertheless when I start the server I get the following messages:
Bootstrapping Ganesha NFS config, Bootstrapping CA cert, Skipping boostraping idmap config, Starting rpcbind, Starting rpc.statd, Starting sssd, Starting dbus, Starting Ganesha NFS, 28/01/2019 23:15:17 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] main :MAIN :EVENT :ganesha.nfsd Starting: Ganesha Version 2.7.1, 28/01/2019 23:15:17 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_set_param_from_conf :NFS STARTUP :EVENT :Configuration file successfully parsed, 28/01/2019 23:15:17 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] init_server_pkgs :NFS STARTUP :EVENT :Initializing ID Mapper., 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] init_server_pkgs :NFS STARTUP :EVENT :ID Mapper successfully initialized., 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start_grace :STATE :EVENT :NFS Server Now IN GRACE, duration 90, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] lower_my_caps :NFS STARTUP :EVENT :CAP_SYS_RESOURCE was successfully removed for proper quota management in FSAL, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] lower_my_caps :NFS STARTUP :EVENT :currenty set capabilities are: = cap_chown,cap_dac_override,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_net_bind_service,cap_net_raw,cap_sys_chroot,cap_mknod,cap_audit_write,cap_setfcap+eip, *28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Init_svc :DISP :CRIT :Cannot acquire credentials for principal nfs,* 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Init_admin_thread :NFS CB :EVENT :Admin thread initialized, *28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :EVENT :Callback creds directory (/var/run/ganesha) already exists,* *28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :WARN :gssd_refresh_krb5_machine_credential failed (-1765328160:0),* 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :Starting delayed executor., 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :9P/TCP dispatcher thread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :gsh_dbusthread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :admin thread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :reaper thread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :General fridge was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[_9p_disp] _9p_dispatcher_thread :9P DISP :EVENT :9P dispatcher started, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] rpc :TIRPC :EVENT :svc_rqst_hook_events: 0x4b7cb80 fd 1024 xp_refcnt 1 sr_rec 0x4af76d0 evchan 2 ev_refcnt 3 epoll_fd 37 control fd pair (35:36) hook failed (9), *28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nsm_connect :NLM :CRIT :connect to statd failed: RPC: Unknown protocol,* *28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nsm_unmonitor_all :NLM :CRIT :Unmonitor all nsm_connect failed,* 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start :NFS STARTUP :EVENT :-------------------------------------------------, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start :NFS STARTUP :EVENT : NFS SERVER INITIALIZED, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start :NFS STARTUP :EVENT :-------------------------------------------------, *28/01/2019 23:16:50 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[reaper] nfs_lift_grace_locked :STATE :EVENT :NFS Server Now NOT IN GRACE*
I'd like to fix them in order to have a clean execution. Is this possible?
Any help will be welcome,
Thanks a lot. Ó
_______________________________________________ Support mailing list -- support@lists.nfs-ganesha.org To unsubscribe send an email to support-leave@lists.nfs-ganesha.org
On Mon, 2019-01-28 at 23:20 +0100, Oscar Segarra wrote:
Hi,
I'm running nfs-ganesha from docker container. It seems work perfectly, nevertheless when I start the server I get the following messages:
Bootstrapping Ganesha NFS config, Bootstrapping CA cert, Skipping boostraping idmap config, Starting rpcbind, Starting rpc.statd, Starting sssd, Starting dbus, Starting Ganesha NFS, 28/01/2019 23:15:17 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] main :MAIN :EVENT :ganesha.nfsd Starting: Ganesha Version 2.7.1, 28/01/2019 23:15:17 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_set_param_from_conf :NFS STARTUP :EVENT :Configuration file successfully parsed, 28/01/2019 23:15:17 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] init_server_pkgs :NFS STARTUP :EVENT :Initializing ID Mapper., 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] init_server_pkgs :NFS STARTUP :EVENT :ID Mapper successfully initialized., 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start_grace :STATE :EVENT :NFS Server Now IN GRACE, duration 90, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] lower_my_caps :NFS STARTUP :EVENT :CAP_SYS_RESOURCE was successfully removed for proper quota management in FSAL, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] lower_my_caps :NFS STARTUP :EVENT :currenty set capabilities are: = cap_chown,cap_dac_override,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_net_bind_service,cap_net_raw,cap_sys_chroot,cap_mknod,cap_audit_write,cap_setfcap+eip, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Init_svc :DISP :CRIT :Cannot acquire credentials for principal nfs, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Init_admin_thread :NFS CB :EVENT :Admin thread initialized, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :EVENT :Callback creds directory (/var/run/ganesha) already exists, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :WARN :gssd_refresh_krb5_machine_credential failed (-1765328160:0),
This is just saying that it can't find a krb5 machine credential for this server. Are you using kerberos? If not, then you can just ignore this. There may be some way to disable krb5 altogether though.
28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :Starting delayed executor., 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :9P/TCP dispatcher thread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :gsh_dbusthread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :admin thread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :reaper thread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :General fridge was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[_9p_disp] _9p_dispatcher_thread :9P DISP :EVENT :9P dispatcher started, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] rpc :TIRPC :EVENT :svc_rqst_hook_events: 0x4b7cb80 fd 1024 xp_refcnt 1 sr_rec 0x4af76d0 evchan 2 ev_refcnt 3 epoll_fd 37 control fd pair (35:36) hook failed (9), 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nsm_connect :NLM :CRIT :connect to statd failed: RPC: Unknown protocol,
28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nsm_unmonitor_all :NLM :CRIT :Unmonitor all nsm_connect failed,
Looks like you're exporting via NFSv3? If so, then you probably want to set up NLM so file locking will work. If not, then you may want to just disable NFSv3/NLM altogether, as that will allow the server to lift the grace period early (see the ceph.conf sample config in the ganesha sources).
28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start :NFS STARTUP :EVENT :-------------------------------------------------, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start :NFS STARTUP :EVENT : NFS SERVER INITIALIZED, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start :NFS STARTUP :EVENT :-------------------------------------------------, 28/01/2019 23:16:50 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[reaper] nfs_lift_grace_locked :STATE :EVENT :NFS Server Now NOT IN GRACE
Not a warning -- just a log message saying that the grace period has ended. The timing of this can be important to know if you have problems with recovery so we log it at a fairly high level.
I'd like to fix them in order to have a clean execution. Is this possible?
Any help will be welcome,
Thanks a lot. Ó
-- Jeff Layton <jlayton@poochiereds.net>
Hi, Thanks a lot for your comments. Regarding the first lines: *28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Init_svc :DISP :CRIT :Cannot acquire credentials for principal nfs,* 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Init_admin_thread :NFS CB :EVENT :Admin thread initialized, *28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :EVENT :Callback creds directory (/var/run/ganesha) already exists,* *28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :WARN :gssd_refresh_krb5_machine_credential failed (-1765328160:0),* For the time being, I don't need krb5 authentication, I just want to filter by client IP address. I have not installed any krb5 package and my ganesha.conf has no refrerence to krb5 therefore I cannot understand why I'm reciving theese messages. Any help in this point will be really welcome. NFSV4 { Allow_Numeric_Owners = false; } NFS_CORE_PARAM { # Enable NLM (network lock manager protocol) Enable_NLM = false; } EXPORT { # Export Id (mandatory, each EXPORT must have a unique Export_Id) Export_Id = 2046; # Exported path (mandatory) Path = /; # Pseudo Path (for NFS v4) Pseudo = /; # Access control options Access_Type = NONE; Squash = No_Root_Squash; Anonymous_Uid = -2; Anonymous_Gid = -2; # NFS protocol options Transports = "TCP"; Protocols = "4"; SecType = "sys"; Manage_Gids = true; CLIENT { Clients = *; Access_Type = RO; } # Exporting FSAL FSAL { Name = CEPH; User_Id = "admin"; } } LOG { Default_Log_Level = WARN; Components { # ALL = DEBUG; # SESSIONS = INFO; } } Are those "red" lines normal? And regarding the other lines: *28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nsm_connect :NLM :CRIT :connect to statd failed: RPC: Unknown protocol,* *28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nsm_unmonitor_all :NLM :CRIT :Unmonitor all nsm_connect failed,* I'm having some problems to start daemons inside my container. Is this statd mandatory for ganesha nfsv4 well working? I have discovered that setting: Enable_NLM = false in the EXPORT block this messages disappear, but I don't know if it is necessary for nfsv4. Thanks a lot El mar., 29 ene. 2019 a las 14:36, Jeff Layton (<jlayton@poochiereds.net>) escribió:
On Mon, 2019-01-28 at 23:20 +0100, Oscar Segarra wrote:
Hi,
I'm running nfs-ganesha from docker container. It seems work perfectly, nevertheless when I start the server I get the following messages:
Bootstrapping Ganesha NFS config, Bootstrapping CA cert, Skipping boostraping idmap config, Starting rpcbind, Starting rpc.statd, Starting sssd, Starting dbus, Starting Ganesha NFS, 28/01/2019 23:15:17 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] main :MAIN :EVENT :ganesha.nfsd Starting: Ganesha Version 2.7.1, 28/01/2019 23:15:17 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_set_param_from_conf :NFS STARTUP :EVENT :Configuration file successfully parsed, 28/01/2019 23:15:17 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] init_server_pkgs :NFS STARTUP :EVENT :Initializing ID Mapper., 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] init_server_pkgs :NFS STARTUP :EVENT :ID Mapper successfully initialized., 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start_grace :STATE :EVENT :NFS Server Now IN GRACE, duration 90, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] lower_my_caps :NFS STARTUP :EVENT :CAP_SYS_RESOURCE was successfully removed for proper quota management in FSAL, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] lower_my_caps :NFS STARTUP :EVENT :currenty set capabilities are: = cap_chown,cap_dac_override,cap_fowner,cap_fsetid,cap_kill,cap_setgid,cap_setuid,cap_setpcap,cap_net_bind_service,cap_net_raw,cap_sys_chroot,cap_mknod,cap_audit_write,cap_setfcap+eip, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Init_svc :DISP :CRIT :Cannot acquire credentials for principal nfs, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Init_admin_thread :NFS CB :EVENT :Admin thread initialized, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :EVENT :Callback creds directory (/var/run/ganesha) already exists, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :WARN :gssd_refresh_krb5_machine_credential failed (-1765328160:0),
This is just saying that it can't find a krb5 machine credential for this server. Are you using kerberos? If not, then you can just ignore this. There may be some way to disable krb5 altogether though.
28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :Starting delayed executor., 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :9P/TCP dispatcher thread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :gsh_dbusthread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :admin thread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :reaper thread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :General fridge was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[_9p_disp] _9p_dispatcher_thread :9P DISP :EVENT :9P dispatcher started, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] rpc :TIRPC :EVENT :svc_rqst_hook_events: 0x4b7cb80 fd 1024 xp_refcnt 1 sr_rec 0x4af76d0 evchan 2 ev_refcnt 3 epoll_fd 37 control fd pair (35:36) hook failed (9), 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nsm_connect :NLM :CRIT :connect to statd failed: RPC: Unknown protocol,
28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nsm_unmonitor_all :NLM :CRIT :Unmonitor all nsm_connect failed,
Looks like you're exporting via NFSv3? If so, then you probably want to set up NLM so file locking will work. If not, then you may want to just disable NFSv3/NLM altogether, as that will allow the server to lift the grace period early (see the ceph.conf sample config in the ganesha sources).
28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start :NFS STARTUP :EVENT :-------------------------------------------------, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start :NFS STARTUP :EVENT : NFS SERVER INITIALIZED, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start :NFS STARTUP :EVENT :-------------------------------------------------, 28/01/2019 23:16:50 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[reaper] nfs_lift_grace_locked :STATE :EVENT :NFS Server Now NOT IN GRACE
Not a warning -- just a log message saying that the grace period has ended. The timing of this can be important to know if you have problems with recovery so we log it at a fairly high level.
I'd like to fix them in order to have a clean execution. Is this
possible?
Any help will be welcome,
Thanks a lot. Ó
-- Jeff Layton <jlayton@poochiereds.net>
From: Oscar Segarra [mailto:oscar.segarra@gmail.com] Sent: Tuesday, February 5, 2019 11:19 AM To: Jeff Layton <jlayton@poochiereds.net>; dang@redhat.com Cc: support@lists.nfs-ganesha.org Subject: [NFS-Ganesha-Support] Re: Some errors starting ganesha - ceph
Hi,
Thanks a lot for your comments.
Regarding the first lines:
28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd- 25[main] nfs_Init_svc :DISP :CRIT :Cannot acquire credentials for principal nfs,
This one can be made to not happen by setting: NFS_KRB5 { Active_krb5 = false; }
28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd- 25[main] nfs_Init_admin_thread :NFS CB :EVENT :Admin thread initialized, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd- 25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :EVENT :Callback creds directory (/var/run/ganesha) already exists,
This one perhaps should not be an EVENT, maybe just an INFO, or maybe silent (with perhaps a INFO if it IS created).
28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd- 25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :WARN :gssd_refresh_krb5_machine_credential failed (-1765328160:0),
Hmm, the code that generates this perhaps should not be executed if Active_krb5 = false.
For the time being, I don't need krb5 authentication, I just want to filter by client IP address. I have not installed any krb5 package and my ganesha.conf has no refrerence to krb5 therefore I cannot understand why I'm reciving theese messages. Any help in this point will be really welcome.
NFSV4 { Allow_Numeric_Owners = false; }
NFS_CORE_PARAM { # Enable NLM (network lock manager protocol) Enable_NLM = false; }
EXPORT { # Export Id (mandatory, each EXPORT must have a unique Export_Id) Export_Id = 2046;
# Exported path (mandatory) Path = /;
# Pseudo Path (for NFS v4) Pseudo = /;
# Access control options Access_Type = NONE; Squash = No_Root_Squash; Anonymous_Uid = -2; Anonymous_Gid = -2;
# NFS protocol options Transports = "TCP"; Protocols = "4";
SecType = "sys"; Manage_Gids = true;
CLIENT { Clients = *; Access_Type = RO; }
# Exporting FSAL FSAL { Name = CEPH; User_Id = "admin"; } }
LOG { Default_Log_Level = WARN; Components { # ALL = DEBUG; # SESSIONS = INFO; } }
Are those "red" lines normal?
And regarding the other lines:
28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd- 25[main] nsm_connect :NLM :CRIT :connect to statd failed: RPC: Unknown protocol, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd- 25[main] nsm_unmonitor_all :NLM :CRIT :Unmonitor all nsm_connect failed,
I'm having some problems to start daemons inside my container. Is this statd mandatory for ganesha nfsv4 well working?
I have discovered that setting: Enable_NLM = false in the EXPORT block this messages disappear, but I don't know if it is necessary for nfsv4.
The statd daemon is not necessary for NFS v4 only, and Enable_NLM = false is just fine in that case. NLM is Network Lock Manager, the lock protocol for NFS v3. You can also set Protocols = 4 in NFS_CORE_PARAM to completely disable NFS v4 (and 9P). Frank
El mar., 29 ene. 2019 a las 14:36, Jeff Layton (<jlayton@poochiereds.net>) escribió: On Mon, 2019-01-28 at 23:20 +0100, Oscar Segarra wrote:
Hi,
I'm running nfs-ganesha from docker container. It seems work perfectly, nevertheless when I start the server I get the following messages:
Bootstrapping Ganesha NFS config, Bootstrapping CA cert, Skipping boostraping idmap config, Starting rpcbind, Starting rpc.statd, Starting sssd, Starting dbus, Starting Ganesha NFS, 28/01/2019 23:15:17 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] main :MAIN :EVENT :ganesha.nfsd Starting: Ganesha Version 2.7.1, 28/01/2019 23:15:17 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_set_param_from_conf :NFS STARTUP :EVENT :Configuration file successfully parsed, 28/01/2019 23:15:17 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] init_server_pkgs :NFS STARTUP :EVENT :Initializing ID Mapper., 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] init_server_pkgs :NFS STARTUP :EVENT :ID Mapper successfully initialized., 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start_grace :STATE :EVENT :NFS Server Now IN GRACE, duration 90, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] lower_my_caps :NFS STARTUP :EVENT :CAP_SYS_RESOURCE was successfully removed for proper quota management in FSAL, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] lower_my_caps :NFS STARTUP :EVENT :currenty set capabilities are: = cap_chown,cap_dac_override,cap_fowner,cap_fsetid,cap_kill,cap_setgid,c ap_setuid,cap_setpcap,cap_net_bind_service,cap_net_raw,cap_sys_chroot, cap_mknod,cap_audit_write,cap_setfcap+eip, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Init_svc :DISP :CRIT :Cannot acquire credentials for principal nfs, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Init_admin_thread :NFS CB :EVENT :Admin thread initialized, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :EVENT :Callback creds directory (/var/run/ganesha) already exists, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :WARN :gssd_refresh_krb5_machine_credential failed (-1765328160:0),
This is just saying that it can't find a krb5 machine credential for this server. Are you using kerberos? If not, then you can just ignore this. There may be some way to disable krb5 altogether though.
28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :Starting delayed executor., 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :9P/TCP dispatcher thread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :gsh_dbusthread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :admin thread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :reaper thread was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_Start_threads :THREAD :EVENT :General fridge was started successfully, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[_9p_disp] _9p_dispatcher_thread :9P DISP :EVENT :9P dispatcher started, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] rpc :TIRPC :EVENT :svc_rqst_hook_events: 0x4b7cb80 fd 1024 xp_refcnt 1 sr_rec 0x4af76d0 evchan 2 ev_refcnt 3 epoll_fd 37 control fd pair (35:36) hook failed (9), 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nsm_connect :NLM :CRIT :connect to statd failed: RPC: Unknown protocol,
28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nsm_unmonitor_all :NLM :CRIT :Unmonitor all nsm_connect failed,
Looks like you're exporting via NFSv3? If so, then you probably want to set up NLM so file locking will work. If not, then you may want to just disable NFSv3/NLM altogether, as that will allow the server to lift the grace period early (see the ceph.conf sample config in the ganesha sources).
28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start :NFS STARTUP :EVENT :----------------------------- --------------------, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start :NFS STARTUP :EVENT : NFS SERVER INITIALIZED, 28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_start :NFS STARTUP :EVENT :-------------------------------------------------, 28/01/2019 23:16:50 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-25[reaper] nfs_lift_grace_locked :STATE :EVENT :NFS Server Now NOT IN GRACE
Not a warning -- just a log message saying that the grace period has ended. The timing of this can be important to know if you have problems with recovery so we log it at a fairly high level.
I'd like to fix them in order to have a clean execution. Is this possible?
Any help will be welcome,
Thanks a lot. Ó
-- Jeff Layton <jlayton@poochiereds.net>
25[main] nfs_Init_svc :DISP :CRIT :Cannot acquire credentials for
Hi Frank, Thanks a lot for your quick answer. I have tried your suggested change: [root@vdicube_pub_ceph_nfs /]# cat /etc/ganesha/ganesha.conf NFSV4 { Allow_Numeric_Owners = false; } NFS_KRB5 { PrincipalName = nfs; KeytabPath = /etc/krb5.keytab; * Active_krb5 = false;* } NFS_CORE_PARAM { # Enable NLM (network lock manager protocol) Enable_NLM = false; } EXPORT { # Export Id (mandatory, each EXPORT must have a unique Export_Id) Export_Id = 2046; # Exported path (mandatory) Path = /; # Pseudo Path (for NFS v4) Pseudo = /; # Access control options Access_Type = NONE; Squash = No_Root_Squash; Anonymous_Uid = -2; Anonymous_Gid = -2; # NFS protocol options Transports = "TCP"; Protocols = "4"; SecType = "sys"; Manage_Gids = true; CLIENT { Clients = 192.168.100.104,192.168.100.105; Access_Type = RO; } # Exporting FSAL FSAL { Name = CEPH; User_Id = "admin"; } } LOG { Default_Log_Level = WARN; Components { # ALL = DEBUG; # SESSIONS = INFO; } } [root@vdicube_pub_ceph_nfs /]# 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd- principal nfs, This one can be made to not happen by setting: NFS_KRB5 { Active_krb5 = false; } You are right, the previous message has dissappeared!
28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd- 25[main] nfs_Init_admin_thread :NFS CB :EVENT :Admin thread initialized, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd- 25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :EVENT :Callback creds directory (/var/run/ganesha) already exists,
This one perhaps should not be an EVENT, maybe just an INFO, or maybe silent (with perhaps a INFO if it IS created). I have deleted the folder /var/run/ganesha before run ganesha and messages have disappeared too.
28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd- 25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :WARN :gssd_refresh_krb5_machine_credential failed (-1765328160:0),
Hmm, the code that generates this perhaps should not be executed if Active_krb5 = false. Unfortunately not. Messages are still in the log: 05/02/2019 22:14:08 : epoch 5c59fc9f : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :WARN :gssd_refresh_krb5_machine_credential failed (-1765328160:0) The statd daemon is not necessary for NFS v4 only, and Enable_NLM = false is just fine in that case. NLM is Network Lock Manager, the lock protocol for NFS v3. Let me another question regarding parallel services. sssd and rpcbind ara necessary for nfsv4 too? You can also set Protocols = 4 in NFS_CORE_PARAM to completely disable NFS v4 (and 9P). I don't want to disable nfsv4... :S. Please can you clarify? Thanks a lot.
From: Oscar Segarra [mailto:oscar.segarra@gmail.com] Sent: Tuesday, February 5, 2019 1:30 PM To: Frank Filz <ffilzlnx@mindspring.com> Cc: Jeff Layton <jlayton@poochiereds.net>; dang@redhat.com; support@lists.nfs-ganesha.org; devel@nfs-ganesha.org Subject: Re: [NFS-Ganesha-Support] Re: Some errors starting ganesha - ceph Hi Frank, Thanks a lot for your quick answer. I have tried your suggested change: [root@vdicube_pub_ceph_nfs /]# cat /etc/ganesha/ganesha.conf NFSV4 { Allow_Numeric_Owners = false; } NFS_KRB5 { PrincipalName = nfs; KeytabPath = /etc/krb5.keytab; Active_krb5 = false; } NFS_CORE_PARAM { # Enable NLM (network lock manager protocol) Enable_NLM = false; } EXPORT { # Export Id (mandatory, each EXPORT must have a unique Export_Id) Export_Id = 2046; # Exported path (mandatory) Path = /; # Pseudo Path (for NFS v4) Pseudo = /; # Access control options Access_Type = NONE; Squash = No_Root_Squash; Anonymous_Uid = -2; Anonymous_Gid = -2; # NFS protocol options Transports = "TCP"; Protocols = "4"; SecType = "sys"; Manage_Gids = true; CLIENT { Clients = 192.168.100.104,192.168.100.105; Access_Type = RO; } # Exporting FSAL FSAL { Name = CEPH; User_Id = "admin"; } } LOG { Default_Log_Level = WARN; Components { # ALL = DEBUG; # SESSIONS = INFO; } } [root@vdicube_pub_ceph_nfs /]# 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd-
25[main] nfs_Init_svc :DISP :CRIT :Cannot acquire credentials for principal nfs,
This one can be made to not happen by setting: NFS_KRB5 { Active_krb5 = false; } You are right, the previous message has dissappeared!
28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd- 25[main] nfs_Init_admin_thread :NFS CB :EVENT :Admin thread initialized, 28/01/2019 23:15:18 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd- 25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :EVENT :Callback creds directory (/var/run/ganesha) already exists,
This one perhaps should not be an EVENT, maybe just an INFO, or maybe silent (with perhaps a INFO if it IS created). I have deleted the folder /var/run/ganesha before run ganesha and messages have disappeared too.
28/01/2019 23:15:20 : epoch 5c4f7ef5 : vdicube_pub_ceph_nfs : ganesha.nfsd- 25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :WARN :gssd_refresh_krb5_machine_credential failed (-1765328160:0),
Hmm, the code that generates this perhaps should not be executed if Active_krb5 = false. Unfortunately not. Messages are still in the log: Yea, we will have to make code changes for that one. 05/02/2019 22:14:08 : epoch 5c59fc9f : vdicube_pub_ceph_nfs : ganesha.nfsd-25[main] nfs_rpc_cb_init_ccache :NFS STARTUP :WARN :gssd_refresh_krb5_machine_credential failed (-1765328160:0) The statd daemon is not necessary for NFS v4 only, and Enable_NLM = false is just fine in that case. NLM is Network Lock Manager, the lock protocol for NFS v3. Let me another question regarding parallel services. sssd and rpcbind ara necessary for nfsv4 too? sssd is not necessary for NFS though I guess maybe it could be used (I really don’t know anything about it… other than knowing it doesn’t need to be part of a minimal NFS implementation…) rpcbind is optional with NFS v4. NFS v4 clients are well prepared to communicate to the server over the default port 2049 or optionally a port specified on the mount command. You can also set Protocols = 4 in NFS_CORE_PARAM to completely disable NFS v4 (and 9P). I don't want to disable nfsv4... :S. Please can you clarify? Sorry, I mistyped, Protocols = 4 will leave NFS v4 active and disable NFS v3 and 9P. Thanks a lot.
participants (4)
-
Daniel Gryniewicz -
Frank Filz -
Jeff Layton -
Oscar Segarra