- Revamped migration tool
- Add link to dashboards and API on Admin UI
- Update default firewall rules to allow ping
- Fix NAbox system metrics not being fetched
- Enable Harvest exporter setting sort_labels
- Fix missing system logs in export bundle
- Update Victoria Metrics maxQueryLen and maxScrapeSize
- Fix a bug with 7-mode systems missing metrics
- Minor bug fixes and improvements
#NAbox 4.0.0b5 available
1 messages · Page 1 of 1 (latest)
Will be installed on Monday
Hey @pulsar hazel , first, thanks for all your efforts for this incredible tool. I’m trying to migrate from nabox3 to nabox4 (latest version on both installations), but I got this error message before it starts the migration process: ~ # migrate
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
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io on 127.0.0.1:53: server misbehaving.
See 'docker run --help'.
2024/05/12 05:33:23 ERROR Failed to migrate metrics error="exit status 125"
Can you do docker image ls on the source ?
Can you also double check the version you are running at the source ?
REPOSITORY TAG IMAGE ID CREATED SIZE
prom/prometheus latest 6a5ddde754b6 2 months ago 254MB
registry.lab/nabox-api latest b3a5fcbec8b3 3 months ago 213MB
registry.lab/nabox-admin latest ed4d33ea0f43 3 months ago 199MB
registry.lab/nabox-harvest latest b9cea1c367ae 3 months ago 270MB
grafana/grafana-oss 9.5.14 489869599fe2 5 months ago 321MB
prom/node-exporter latest 72c9c2088986 6 months ago 22.7MB
graphiteapp/graphite-statsd latest f358fa45fd82 10 months ago 851MB
traefik v2.6 22c6901de2be 23 months ago 102MB
gcr.io/cadvisor/cadvisor latest 68c29634fe49 3 years ago 163MB
alexandertgtalbot/go-carbon latest 778bcddfd6dd 4 years ago 405MB
Source nabox is 3.5.2
Are you positive the maintenance page says 3.5.2?
well that's weird indeed. Can you re-download/re update ?
Yes, I will try that and update you on Wednesday. Thanks !
what is the rough ETA for GA of 4.0 ? I need to do a deployment of this and dont want to deploy a beta?
Hi Greg. I think early June seem reasonable. Maybe before.
Hey Yann, so I re-installed 3.5.2 and the missing docker image is now there, successfully started a migration, thanks !
Hi @pulsar hazel the default size of the data VMDK is 200GB in the OVA. If we now have like 1 TB on the NABox 3, should I also size the disk in the 4er to also 1 TB for the migration?
That’s what I would recommend but it’s probably going to be smaller.
I can give you then some numbers 😊
Yes I’m curious. I wouldn’t be surprised you get 30% back
On our dev system we went from 80gb (nabox 3 with 2 years retention 4 nodes) to 30gb after the migration
Ok that's impressive ! Did you notice improvements loading dashboards with large time span ? (not that it's recommended anyways, but curious if it works better)
With the smaller instance we never had issues in that direction. As soon the big ones are in the pipeline I can tell you 😊
Hi everyone
We are trying to deploy 4.0.0b5 after having gotten a v3 up and running yesterday. Since you recommend going to v4, we've been trying unsuccessfully. It never comes online.
First entry after boot was /dev/sda3 duplicate warning and since then we only see network messages looping
See screenshot
Thanks @visual river for reporting.
Do you see an IP address for NAbox in vCenter ?
If so, log in with ssh as admin (Netapp01 is the password) and run this :
{ sudo journalctl -S "yesterday" -u nabox; sudo journalctl -S "yesterday" -u naboxd; sudo journalctl --system -S "yesterday";} | gzip > nabox-logs-`date +%Y-%m-%d_%H:%M:%S`.gz
The send the file to help@nabox.org
We have deleted the VM in the meantime. I think I once saw an IP like 192.0.0.1.
How would you propose one send you that gz file without networking?
If there is no networking indeed that would be a problem.
We can try to figure out why you wouldn't have networking.
How did you deploy NAbox ? The wizard asks for network configuration, which defaults to DHCP.
We deploy the OVA into a vsphere environment and give it IP, subnetmask and a gateway address. We tried deploying without DNS at first but even with DNS it amounted to the same thing.
Is it possible that the OVA is incompatible with ESXi/vCenter 8? I have had OVAs in the past that seemingly were not meant to be deployed through a vCenter.
I can retry and document with screenshots, if you'd like but deploying OVAs with the wizard really doesn't leave much room to mess up.
I'd appreciate it indeed. You noticed the netmask actually goes in the IP address with a "/" notation correct ?
Then once it's deployed, It would be interesting to have the output of :
vmware-rpctool info-get guestinfo.ovfEnv
You may be onto the root issue... With v3 it was its own field, no?
it was 🙂
That's definitely going to be a problem, it might confuse lots of users, I'll think about something better
Well if I hadn't isntalled v3 several times two days ago, it might not have mattered. In this case, the hands were inputting on auto-pilot 🙂
I didn't even think to read the instruction but also did not notice the missing netmask.
From the console, can you "cat /etc/systemd/network/10-nabox.network" ?
journalctl -u naboxd
That's nabox, not naboxd 😄
It is unfortunately easy to enter typossince it periodically fills your screen with junk and you lose the prompt.
I see I’ll get that error fixed. Unfortunately it doesn’t explain why the IP config isn’t applied. I’ll do some more tests next week
I will also perform a clean installation on Tuesday or Wednesday
Hi @pulsar hazel probably a stupid question 🙈 is it from your end support to change the ip address of the nabox 3/4?
I'm assuming you don't have access to the web ui ?
As usual you are right 🙈 after changing the ip the web ui does not work anymore. Ssh and ping does
ah... Nabox 3 I suppose ?
For NAbox 4 https://4.nabox.org/faq/#reset-network-configuration
For NAbox 3 : https://nabox.org/faq/#reset-network-configuration
But as SSH is working, I don't think it'll help.
can I see dc ps ?
I will try it today with the NA
ahhh no container is running. After changeing the IP a restart is needed
What version ?
4.0.0b6
HI @pulsar hazel ,
i have forget the admin password how to rest it
Did you try the default Netapp01 ?
Ok it has not been documented yet. Give me a few hours and I’ll update the FAQ. Basically you need to boot the appliance in single user mode and reset with « passwd » command line
@pulsar hazel , i need to boot the VM or we need to resrt the docker container ?
The VM. If I understand correctly you don’t have access to the containers anymore
understood
can you help update the document or share the steps, so that i can reset it
Will do
@pulsar hazel , i am not geeting flacter default screen, I am getting alpine linux and it was taking direct to os
Ah, that’s for NAbox 3 then
Did you try to login a root / NetappGrafanaVA with ssh ?
yes