Upgrade Error with NABox 3.x | NetApp | Page 1

slow herald Apr 23, 2025, 7:01 PM

#

Hey all!
I realize that the 3.x release is no longer being supported/worked on, but hopefully this is either an easy fix or something someone else has run into.

We are currently running 3.4, and every time we attempt to upgrade to 3.5.x we encounter the error in the screenshot.

Manually restarting services does cause the GUI to show a green checkbox in the upgrade dialogue box, but upon rebooting, the upgrade never completes.

Is this a known error? Would hate to move to 4.x without being able to move our historical metrics with it, but we want to get current.

modern grove Apr 23, 2025, 7:04 PM

#

Didn't see that before but we'll figure it out

#

what happens in nabox-api container logs when upgrading ?

slow herald Apr 23, 2025, 7:12 PM

#

after running it again, looks like the part of the logs that is triggering this is the following:

 * Stopping sshd ... [ ok ]
172.17.0.2 - - [23/Apr/2025 19:11:14] "GET /api/1.0/system/upgrade HTTP/1.1" 200 -
 * Starting sshd ... [ ok ]
Enabled
 * Stopping open-vm-tools ... [ ok ]
 * Starting open-vm-tools ... [ ok ]
 * rc-update: service `fail2ban' does not exist
 * rc-service: service `fail2ban' does not exist
 * Stopping nabox-api-watchdog ... [ ok ]
172.17.0.2 - - [23/Apr/2025 19:11:15] "GET /api/1.0/system/upgrade HTTP/1.1" 200 -
 * Starting nabox-api-watchdog ... [ ok ]
sh: .: line 0: can't open '/etc/profile.d/nabox.sh': No such file or directory```

#

Just let me know if you want more of the log!

modern grove Apr 23, 2025, 7:14 PM

#

try to populate /etc/profile.d/nabox.sh with :

export COMPOSE_FILE=/usr/local/nabox/docker-compose/docker-compose.yaml:/usr/local/nabox/docker-compose/docker-compose.override.yaml
function dc {
  (cd /usr/local/nabox/docker-compose/; docker compose --env-file .env --env-file .env.custom $*;)
}

Use copy/paste

#

Also, should be chmod 755

slow herald Apr 23, 2025, 7:20 PM

#

looks like the error has changed to Couldn't find env file: /usr/local/nabox/docker-compose/.env.custom now; do you have a sample for that file as well?

modern grove Apr 23, 2025, 7:20 PM

#

GF_AUTH_LDAP_ENABLED=false
GF_AUTH_ANONYMOUS_ENABLED=false
GF_AUTH_ANONYMOUS_ORG_NAME=Main Org.
GF_AUTH_ANONYMOUS_ORG_ROLE=Viewer
GF_SMTP_ENABLED=false
GF_SMTP_HOST=
GF_SMTP_USER=
GF_SMTP_FROM_ADDRESS=
GF_SMTP_PASSWORD=

#

really weird though

slow herald Apr 23, 2025, 7:22 PM

#

Yeah, we've barely done any customization to this install aside from a prom_override.yaml so idk how these files wouldve gotten deleted.

#

Trying that now

modern grove Apr 23, 2025, 7:23 PM

#

I suspect the nabox package isn't actually installing for some reason, and you're still running the one from initial install. We might have to force all apk install from the upgrade package

slow herald Apr 23, 2025, 7:28 PM

#

Adding the .env file let the upgrade continue, but it just killed all the services and didn't bring them back up. 😂

So it looks like it's still not working, I just can't see it in the container logs.

modern grove Apr 23, 2025, 7:29 PM

#

ok, containers are running ?

slow herald Apr 23, 2025, 7:30 PM

#

Nope, looks like the upgrade script killed them, docker ps shows nothing is up.

modern grove Apr 23, 2025, 7:30 PM

#

dc up -d

slow herald Apr 23, 2025, 7:33 PM

#

yep, all running now

#

So do I need to kick something off manually to get it complete? (besides just rebooting?)

modern grove Apr 23, 2025, 7:34 PM

#

try a reboot

slow herald Apr 23, 2025, 7:34 PM

#

(Also my apologies, I'm not super familiar with Docker, this is the only app I run that uses it.)

#

Will do.

modern grove Apr 23, 2025, 7:34 PM

#

check /etc/nabox-release also

#

If anything I'm the one screwing up here 😄 Just a long time ago !

slow herald Apr 23, 2025, 7:36 PM

#

modern grove check `/etc/nabox-release` also

After a reboot, everything comes up normally, but it's still showing 3.4 in this file and the GUI.

modern grove Apr 23, 2025, 7:37 PM

#

All right, we might not have a choice then...
https://3.nabox.org/documentation/upgrade/

#

Manual upgrade part

#

this one can be a pain. If that's a package dependency issue (the reason why I started NAbox 4) it might be a few back and forth before we can figure this out, we can have a remote session

#

Finnish ? Damn, pretty late for you !

slow herald Apr 23, 2025, 7:42 PM

#

I will have to run through this tomorrow, but I will get back to you asap with what happens.

Ultimately if it ends up being a real pain in the neck, we may just spin up a 4.x host and run them in tandem for a bit. We only keep data on the host for a short while.

#

I really appreciate your help! Especially for us 3.x laggards. 😄

#Upgrade Error with NABox 3.x