#No data in NFS Clients dashboard

1 messages · Page 1 of 1 (latest)

spiral hedge
#

I've followed guidance in all of the posts here attempting to get Rest to work correctly and still not successful. I've created the role & account on my clusters, I think I've modified all the appropriate yaml files. How can I continue to troubleshoot? NAbox 4.0.10 / Harvest 25.02.0

elfin condor
#

Hi Lorne, sorry that you've hit a snag. What do you have in the collectors section of the poller in question in your /etc/nabox/harvest/harvest.yml file?

spiral hedge
#

Should I add the others? Also note that I just setup this NAbox instance and just completed the migration of data from NAbox3 to NAbox4. I was also never able to get Rest working in NAbox3.

elfin condor
#

What version of ONTAP is running on your clusters? In Nabox, what do you have selected in edit

spiral hedge
#

9.15.1p3. Auto is currently selected. If I select Rest, will it still use Zapi where needed?

elfin condor
#

I'm not sure, but we can check. Select Rest, click Modify and then let's check the /etc/nabox/harvest/harvest.yml again. I assume it will look similar to what I pasted about

spiral hedge
#

Getting this...

elfin condor
#

let' see what @edgy harbor says about why Nabox is failing there. In the meantime, you can edit /etc/nabox/harvest/harvest.yml to have

        - Rest
        - RestPerf
        - Zapi
        - ZapiPerf
        - Ems
#

after making that change, restart the container via dc restart havrest, wait a couple of minutes and then run docker logs havrest --since 5m 2>&1 | grep NFSClients

spiral hedge
#

Waited at least 10 minutes after the restart and the "docker" command produces nothing.

elfin condor
spiral hedge
#

Support bundle has been uploaded

elfin condor
#

thanks, looking

spiral hedge
#

One quick note. I am now getting Rest data in the FSA dashboard, but nothing in the NFS Clients dashboard

elfin condor
#

thanks, that's good to know, progress! I assume you didn't see data in the FSA dashboard before?

spiral hedge
#

Correct

elfin condor
#

ok good

#

try changing your etc/nabox/harvest/user/rest/custom.yaml to this:

objects:
    NFSClients: nfs_clients.yaml
    Volume: custom_volume_flexgroup.yaml

After making that change, restart the container via dc restart havrest, wait a couple of minutes and then run docker logs havrest --since 5m 2>&1 | grep NFSClients

spiral hedge
#

Still not getting anything back from the "docker" command. Where and what should be in the nfs_clients.yaml file?

elfin condor
#

the custom.yaml is enabling the out-of-the-box nfs_clients.yaml template that you should see in /data/packages/harvest/conf/rest/9.7.0/nfs_clients.yaml

spiral hedge
#

10-4. I do see the file in that location

elfin condor
#

can you grab another support bundle and upload so I can take a look at the logs files after the custom.yaml change?

spiral hedge
#

Done

elfin condor
#

thank you

#

while I dig through the logs, change your etc/nabox/harvest/user/rest/custom.yaml to only this. In other words delete the collector: line.

objects:
    NFSClients: nfs_clients.yaml
    Volume: custom_volume_flexgroup.yaml

Save and do the restart dance

spiral hedge
#

Done.
And still nothing from the "docker logs" command

elfin condor
#

ok does this return anything? docker logs havrest --since 10m 2>&1 | grep 'unable to merge config'

spiral hedge
#

time=2025-03-27T19:28:29.598Z level=ERROR source=havrest.go:49 msg="unable to merge config" error="yaml: unmarshal errors:\n line 4: cannot unmarshal !!seq into string"

elfin condor
#

can you tell by the timestamp of when you restarted if that is from the most recent restart or the one before you fixed custom.yaml?

spiral hedge
#

I believe after. You asked me to restart at 19:22 and I responded done at 19:32

elfin condor
#

can you copy paste into the chatcat etc/nabox/harvest/user/rest/custom.yaml?

spiral hedge
#

objects:
NFSClients: nfs_clients.yaml
Volume: custom_volume_flexgroup.yaml

elfin condor
#

thanks. I think i see the (a) problem. We fixed rest/custom.yaml but not restperf/custom.yaml that is causing the merge problem which unfortunately is breaking rest when nabox does its merge. For restperf/custom.yaml, can you comment out all the lines, move the file somewhere else, etc. so we can focus on the NFSClients issue?

edgy harbor
elfin condor
#

@edgy harbor when logging this, it would be nice to also log the file that has the syntax error {"log":"time=2025-03-27T14:51:59.014Z level=ERROR source=havrest.go:49 msg=\"unable to merge config\" error=\"yaml: unmarshal errors:\\n line 4: cannot unmarshal !!seq into string\"\n","stream":"stdout","time":"2025-03-27T14:51:59.014711405Z"}

edgy harbor
#

Good point !

elfin condor
#

@edgy harbor also not sure if you expected it or not but a syntax error in restperf custom.yaml seems to cause rest custom.yaml merging to fail too. I assume an error bails? But might be worth trying to improve

spiral hedge
#

After commenting out the restperf/custom.yaml and restarting, I'm not getting output from the docker logs command and also see data in NFS clients dashboard.

#

Sorry!!! 'now' not 'not' 😀

elfin condor
#

🙂 I was confused

spiral hedge
#

Meaning, it's working now

elfin condor
#

Great! So three issues: 1) REST was not in your harvest.yml 2) rest/custom.yaml had a syntax error that prevented the NFSClients template from loading. 3) restperf/custom.yaml also had a syntax error that prevented the REST NFSClients template from loading

spiral hedge
#

Thanks for all the help 🏆

elfin condor
#

your welcome!