#NEW: Harvest 24.05.2 has been released

1 messages · Page 1 of 1 (latest)

halcyon barn
#

https://github.com/NetApp/harvest/releases/tag/v24.05.2

📌 This release is identical to 24.05.0, with the addition of two fixes:

  1. A fix that makes the NFS Troubleshooting dashboards load in NAbox and via bin/harvest grafana import.
  2. A fix for a regression introduced in 24.05.1, that causes FlexGroup volume performance metrics to be skipped.

Upgrade Recommendation:
You should upgrade to 24.05.2 if any of the following apply to you:

  • You want to use the NFS troubleshooting dashboards.
  • You are on version 24.05.1 and your cluster includes FlexGroup volumes.
weak jasper
#

i upgraded harvest to the latest and then tried to upgrade nabox to 4.0.2. however i'm now stick with the attached screen when i access the update page. any tips on how to proceed?

kindred shale
#

Sorry I didn't see this post

weak jasper
#

uploaded now. i get the same page anytime i click on upgrade even after logging out and back in.

kindred shale
#

Ok to clear that you can delete /data/update.json and run systemctl restart naboxd

weak jasper
#

ok, i did that and when i login and access Settings->Upgrade I see the NAbox upgrade option which when selected displays the attached dialog with "Pre install" displayed and its unclear if anything is happening:

kindred shale
#

Ok ill Check your logs and let you know

kindred shale
#

Ok, it looks like you upgraded the package on 2024/06/24 17:13:21, but it failed : "unexpected EOF"
On 2024/06/24 17:18:43, you clicked the upgrade button, which failed with:

Jun 24 17:18:43 nabox4 naboxd[1337]: time=2024-06-24T17:18:43.909Z level=ERROR source=upgrader.go:74 msg="error while running upgrade" error="stat /data/uploads/upgrade/pre.sh: no such file or directory"

Which makes sense as the upload wasn't complete, and I don't see any other attempt to upload a new package

This would lead to that kind of inconsistencies indeed.

You can clean up by running

rm -f /data/update.json
rm -rf /data/uploads/upgrade/
systemctl restart naboxd
weak jasper
#

i re-downloaded the 4.0.2 package, uploaded it but the upgrade process hangs at 42% for some reason. how can i check if it has completed or complete the uprgrade?

kindred shale
#

You are uploading via internet ? Any way you could use a local connection ?

weak jasper
#

Uploading over a VPN but there is no connection or bandwidth issues.

When I logout and back in I see the attached. Is it possible to check on the VM if the upload is actually complete?

kindred shale
#

it's better once you get to 4.0.2, it will not let you upgrade if incomplete

#

you can go in /data/uploads/upgrade and see if you have pre and post.sh there

weak jasper
#

Attached is what i see in /data/uploads/upgrade but the uploaded file (NAbox-4.0.2.nbx) is 744GB as far as I can see.

kindred shale
#

yes that's not good, files are missing

#

What you can do is upload nbx file and uncompress it in /data/uploads/upgrade

weak jasper
#

how do i uncompress NAbox-4.0.2.nbx? also, could the problem be that that the root volume is nearly full?

kindred shale
#

Well, that wouldn't help indeed 😄

#
sudo ls -l /var/lib/docker/containers/*/*.log
weak jasper
kindred shale
#

ok.

echo > /var/lib/docker/containers/165*/*.log

Then you can run the update again. The update also fixes the ever growing log files

stone spruce
#

@kindred shale , I have nabox3.X version data on NFS path how to migrate the same NFS path to nabox 4.x

kindred shale
# stone spruce <@323825973718155265> , I have nabox3.X version data on NFS path how to migrate ...

That's tricky. I guess you could do what you did with NAbox 3 (which I didn't encourage in any way :-)) with NAbox 4.
I guess it's an interesting solution anyways, we can work together on it.
It would be totally unsupported in a sense that if there is performance issues or misbehaviours I'll do my best to help but can't guarantee the result.

It would be as follows :

stone spruce
#

i can mount the same NFS on nabox 4 and can i restart the service so that it will use the same NFS

kindred shale
#

No, you will have to migrate data in any case

#

I setup a test instance on NFS, seems to be working as advertised in the procedure above

stone spruce
#

@kindred shale what is the default root password for nabox 4

kindred shale
#

no root password

stone spruce
#

i tried with admin password but it didnt work

kindred shale
#

from admin you can sudo your way to root

stone spruce
#

when i try to switch su root

#

it was aking for passowrd

kindred shale
#

sudo bash ?

stone spruce
#

Works