#It's here ! NAbox 4 is officially released !
1 messages · Page 1 of 1 (latest)
excellent. I'll try to do a new deployment this weekend and an upgrade of our existing 3.x as well. If we run into any issues I'll let you know.
Thanks for all the amazing work
Hi Yann thanks for the GA version 😊 question about customer configs like the collection nfsv4 pool metric. Will these files also be migrated or we need to recreate them
Hi Yann,
The migration failed for me from 3.5.1 to 4 with the output below:
Adding poller 10.141.172.142 OK
Adding poller dub105sgnsnasnet0.sg.viatel.net OK
Adding poller dub1scsdnasnet0.sg.viatel.net OK
Adding poller dub5scsdnasnet0.sg.viatel.net OK
Adding poller dub1sgnsnasnet0.sg.viatel.net OK
Adding poller 10.141.172.150 OK
Restarting Prometheus with admin API enabled... OK
Waiting for Prometheus OK
Taking snapshot... OK
Restarting Prometheus with admin API disabled... OK
Waiting for Prometheus OK
Unable to find image 'victoriametrics/vmctl:heads-master-0-g93a29fce4e' locally
heads-master-0-g93a29fce4e: Pulling from victoriametrics/vmctl
4abcf2066143: Pull complete
1fa950ee645b: Pull complete
936054e38e9e: Pull complete
Digest: sha256:b1b5a7b2acf89c2d285e19120b569b4da64179985f2562008e9211b8c891fe36
Status: Downloaded newer image for victoriametrics/vmctl:heads-master-0-g93a29fce4e
Prometheus import mode
2024/06/07 14:13:03 failed to create prometheus client: failed to open snapshot "/prometheus/data/snapshots/": opening the db dir: stat /prometheus/data/snapshots/: no such file or directory
2024/06/07 14:13:04 ERROR Failed to migrate metrics error="exit status 1"
Hey, might be a failed 3.5 update, try to re apply the latest 3.5.3
once that is done, can i rerun the migrate script or should i reinstall the v4 vm?
No need you can just run the script again it’ll skip the already added system.
V4 should be collecting data actually.
yes, v4 is collecting data and a rerun of the script kicked off the data transfer.
Congratulations on another amazing release!!
Hi Yann,
I have set grafana-default-email and sent test emails successfully.
Do you have any tips on getting the 'Mimir / Cortex / Loki' alerts to send emails in Nabox4?
Grafana itself isn’t sending emails, alert manager will do you don’t have to alter Grafana configuration.
In fact, all alerts are defined in alert manager configuration and Grafana is just displaying alerts and give you an interface to silent them (untested)
When you configure email in nabox admin, your are configuring Prometheus alerting configuration, which does handle all the rules visible in Grafana.
Thanks Yann. I now have some emailed alerts coming in. I'm trying to create silences in Grafana but no luck so far.
@keen herald - website (https://4.nabox.org/) is currently down - expected?
Also "Network settings" doesn't successfull save "Domain names" properly - it shows error with hostname, ip address, and gateway. How do we get around?
Hi ! Yes it moved over to nabox.org
Mmm, that should have been fixed. You have /subnet with two digit ?
@keen herald - ahh yep sorry I missed the "IP Address in the form a.b.c.d/m" - added /subnet and it's now working successfully - thank you and appreciate it!
@keen herald - sorry a "cosmetic" thing - under ONTAP system hostname, cannot successfully change from IP to FQDN, error: Invalid host name. How to get around this?
Any chance you have uppercase letters in host name ?
Oh you have a «-» sorry about that
Yes, our hostnames currently all have dashes "-" in them
https://dl.nabox.org/nabox/NAbox-4.0.0-fix-171.nbx You can apply this update
@keen herald - still broken: Error while updating system
name query authentication failed
Mmm, that would be different. You sure about username and password ?
Yes - it was incorrect password sorry about that. Put in the correct password and it's working now. Thank you!
i need more than the 200gb for /data. so i shutdown the nabox4, added disk space to hard disk 2 and startup the VM again. still see the 200gb for data. i think that was the method for nabox 3 - ho do i extend the HD in nabox4?
EDIT: works with "resize2fs /dev/sdb", but is that the right way?
Yes that what nabox should have done
Can you show me the output of journalctl -u resize ?
tried again a resize from 200gb to 300gb - no entries in journalctl:
journalctl -u resize
-- No entries --
next failure while migrating the data from 3.5.3 to 4.0.0
Restarting Prometheus with admin API enabled... OK
Waiting for Prometheus.......... Failed
Taking snapshot...2024/06/13 12:22:10 ERROR Failed to take Prometheus snapshot error="Failed to parse snapshot response: invalid character 'S' looking for beginning of value"
Would you mind running it manually ? https://nabox.org/faq/#manual-migration
Or just try curl -k -x POST https://localhost/prometheus/api/v1/admin/tsdb/snapshot in nabox 3 appliance.
FYI ... I could not get grafana silences to work at all but found that I can setup silences via the alertmanager UI here: https://<nabox fqdn>/am/#/alerts
Thanks for checking, I’ll see how Grafana implementation works !
Now I'm gonna migrate to NAbox 4. 🙂
You should start here 😄 https://dl.nabox.org/nabox/NAbox-4.0.0-10-g3f1073f.nbx
Fixed in 4.0.1 thanks for reporting !
I'm getting this error "Adding poller s01.bbaas.local2024/06/23 11:09:10 ERROR Failed add poller error="Failed to add poller: response=Post "https://admin:***@s01.bbaas.local/servlets/netapp.servlets.admin.XMLrequest_filer\": dial tcp: lookup s01.bbaas.local on 127.0.0.11:53: server misbehaving"
Adding poller 10.0.2.102024/06/23 11:09:10 ERROR Failed add poller error="Failed to add poller: response={"code":1001,"message":"poller already exists"}""
I upgraded to latest 3. release and I am using 4.0.2 as the target system...
Can you check dns configuration in NAbox 4?
It's DHCP, but the DNS fields looks blank.. I will try to make it static and try again...
That's interesting, let me know if you think the DNS server is distributed through DHCP and for some reason NAbox is ignoring it
It's Processing blocks now.. (seems to take awhile) 🙂 Not sure why Nabox ignored the DNS servers, they are defined in the DHCP... I haven't seen this as an issue with other DHCP clients...
Ok I'll keep an eye on it and open an issue
Maybe it would be a good idea to add more vCPUs before you start the migration? Does it start a worker per CPU core?
Unfortunately no, the default is to start 2 workers, but if you run the migration manually (https://nabox.org/faq/#manual-migration) you can set more workers
OK... I can just see that the CPU usage on the source VM is 100%...
How much data are we talking ?
https://docs.victoriametrics.com/vmctl/#migrating-data-from-prometheus show how to use --vm-concurrency and --prom-concurrency
Documentation for VictoriaMetrics, VictoriaLogs, Operator, Managed VictoriaMetrics and vmanomaly
Well we are at 15% now... 19 blocks.. I'll just keep it running..
good thing this is just a one time thing 😉
Yes, I wish there was a better way, and certainly think NAbox 4 has better foundation and will have a longer run !
@main sage I deployed a new instance, you wouldn't see the current DNS server in web ui, but it should be there in resolvectl status ens192