7:29 a.m.
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(a)lists.nfs-ganesha.org
To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org