#Nabox 3.5 StorageGRID Dashboards missing
1 messages · Page 1 of 1 (latest)
@frigid verge Did you try Reset button as in attached screenshot?
Hi Rahul,
yes we tried to reset, unfortunately that does not change anything.
Can you try running below command from nabox root user in CLI
dc exec -w /conf nabox-harvest2 /netapp-harvest/bin/grafana import --multi -a http://grafana:3000/ --overwrite -f "StorageGRID" -d grafana/dashboards/storagegrid
@violet burrow Any idea why Reset may not be working?
The cli asks for an API-token, am i missing something?
This probably explains why reset is not working. Can you share output of below command
dc exec -w /conf nabox-harvest2 /netapp-harvest/bin/harvest doctor --print
Hey gents, customer sent me the log output where it appears that the reset button requests an api token too
It seems that you are missing the grafana_api_token in the Harvest configuration. @violet burrow , is there a command to reinsert it into the file in NABox, or does it need to be done manually by generating from grafana UI?
It's weird that it's missing indeed. We can re-create a token in Grafana and configure it back in the yml
If that's easily fixable i'd do that with my customer, if it's more complex i'd go for a redeployment of the whole appliance as we won't loose anything effectively
@violet burrow Could you share those steps for NABox
Is it enough to just create the token in grafana or do i have to edit it in somewhere?
Actually, the key isn't stored in harvest.yml
It's possible grafana put an end to API tokens in 9.x.
Well, sounds like a redeployment would be an easier solution then 😉
We can have a call and fix it also
Customer is off duty until next week though, i do not have access to the vm myself
If you delete /opt/secrets/harvest-grafana and dc stop nabox-api it will recreate the key, but you have to set the admin password to Netapp01first
alright, let me try that with the customer and see if that fixes it
Hi @violet burrow i am currently in a remote session with the customer and dc stop nabox-api does not work because of permission denied ... if run under the root user we get dc: can't open 'stop': no such file or directory
we opted for a reinstall instead for a quick fix
Ok