Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

petasan 4.0.0 ganesha question


alexevon
3 Posts
May 4, 2025, 10:30 pm

Installed petasan 4.0 without any issues, RBD works perfectly for our ACS clusters.  When an NFS name was supplied via the gui, a mishap of using a full path was applied, such as "/export/secondary" instead of just "secondary".

 

When looking inside podman at the ganesha.conf we see this:

 

"EXPORT
{
Export_ID = 1;
Path = /nfs//export/secondary/;
Pseudo = //export/secondary/;
Protocols = 4;"

Which of course reports an error and ganesha now will not start since this error is being reported.

the GUI for NFS now only shows "Grace" now while each podman on each node reloads in a loop.

 

Is there a way, via the CLI, to update the ganesha.conf file, or at least rebuild it without the above path applied?

 

Thank you!

Alex

 

Last edited on May 4, 2025, 10:30 pm by alexevon · #1

admin
2,980 Posts
May 5, 2025, 12:39 pm

# read configuration from consul
consul kv get -recurse PetaSAN/NFSExports > exports.json

# edit/fix
cp exports.json exports-backup.json
nano exports.json

# write configuration in consul (notice the @)
consul kv put PetaSAN/NFSExports @exports.json

#2

alexevon
3 Posts
May 5, 2025, 12:52 pm

Admin-

 

Thank you for the quick response!  I followed the above, and it stated it copied correctly, yet now the nfs server does not start, complaining about a bad json on line 1:

"storage1 nfs_exports_server.py[2450744]: Error start_nfs_exports_service , Exception : Expecting value: line 1 column 1 (char 0)"

 

PetaSAN/NFSExports:{
"exports": [
{
"active": false,
"export_quota_enabled": false,
"export_quota_size": "",
"filesystem": "cephfs",
"id": "1",
"layout_path": "",
"name": "secondary2",
"restricted_access": "no",
"ro_clients": "",
"rw_clients": "",
"snapshot_dest_path": "",
"snapshot_exported": false,
"snapshot_mount_path": "",
"snapshot_name": "",
"snapshot_src_path": ""
},
{
"active": true,
"export_quota_enabled": false,
"export_quota_size": "",
"filesystem": "cephfs",
"id": "2",
"layout_path": "",
"name": "secondary",
"restricted_access": "no",
"ro_clients": "",
"rw_clients": "",
"snapshot_dest_path": "",
"snapshot_exported": false,
"snapshot_mount_path": "",
"snapshot_name": "",
"snapshot_src_path": ""
}
],
"recovery_db_pool": ""
}

 

 

 

Last edited on May 5, 2025, 12:53 pm by alexevon · #3

alexevon
3 Posts
May 5, 2025, 1:10 pm

Admin-

 

I deleted the "PetaSAN/NFSExports:" and it seemed to validate the json now.  I seem to be back in business.  Thank you!

 

Alex

#4

admin
2,980 Posts
May 5, 2025, 1:31 pm

Good it is working now.

Actually you should also remove the

PetaSAN/NFSExports:

at top of file. Sorry.

Last edited on May 5, 2025, 1:38 pm by admin · #5