#NAbox migrate fails

1 messages · Page 1 of 1 (latest)

floral pulsar
#

Hi there,
we are trying to migrate our nabox3 data to nabox 4. Import runs for serveral hours and fails without reason.
Is there a way to see a log or something else to narrow down the issue?

Error message on CLI is:

~ # migrate
Migrate v4.2.0-0-gf2056a6
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
Prometheus import mode
Prometheus snapshot stats:
blocks found: 47;
blocks skipped by time filter: 0;
min time: 1714728744444 (2024-05-03T09:32:24Z);
max time: 1776925438476 (2026-04-23T06:23:58Z);
samples: 367230995063;
series: 19459512.
VM worker 0:↖ 0 samples/s
VM worker 1:↖ 0 samples/s
VM worker 0:← 9 samples/s
VM worker 1:← 9 samples/s
VM worker 0:↓ 9206 samples/s
VM worker 1:↓ 9369 samples/s
VM worker 0:← 7537 samples/s
VM worker 1:← 7670 samples/s
VM worker 0:↗ 5051 samples/s
VM worker 1:↗ 5141 samples/s
VM worker 0:↗ 2425 samples/s
VM worker 1:↗ 2469 samples/s
VM worker 0:↓ 639 samples/s
VM worker 1:↓ 650 samples/s
VM worker 0:↙ 62 samples/s
VM worker 1:↙ 63 samples/s
VM worker 0:↗ 1 samples/s
VM worker 1:↗ 1 samples/s
VM worker 0:↓ 0 samples/s
VM worker 1:↓ 0 samples/s
VM worker 0:← 0 samples/s
VM worker 1:← 0 samples/s
VM worker 0:↑ 0 samples/s
VM worker 1:↑ 0 samples/s
VM worker 0:↑ 0 samples/s
VM worker 1:↑ 0 samples/s
Processing blocks: 15 / 47 [████████████████████████████████████████████████████████████████▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒] 31.91%
2026/04/24 03:55:21 import process failed: import failed with 10 retries: execution failed after 10 retry attempts
Importing batch failed for timestamps range 1737847793079 - 1739102393078 (enable --verbose output to get more details)

time=2026-04-24T03:55:24.450Z level=ERROR source=main.go:192 msg="Failed to migrate metrics" error="exit status 1"

wanton cypress
#

@high oxide

high oxide
#

Can you check capacity at the destination ?

floral pulsar
#

Filesystem Size Used Avail Use% Mounted on
/dev/sda9 5.8G 2.9G 2.5G 54% /
sysext 1.9G 8.0K 1.9G 1% /usr
/dev/sda6 128M 4.1M 121M 4% /oem
overlay 5.8G 2.9G 2.5G 54% /etc
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 776M 1.6M 774M 1% /run
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup-dev-early.service
tmpfs 1.9G 0 1.9G 0% /media
tmpfs 1.9G 0 1.9G 0% /tmp
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-network-generator.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-udev-load-credentials.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-sysctl.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-sysusers.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup-dev.service
/dev/sdb 590G 311G 254G 56% /data
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-vconsole-setup.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-resolved.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-networkd.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/getty@tty1.service
tmpfs 388M 4.0K 388M 1% /run/user/1000

#

254G Free

#

found this on the target appliance. Timeframe seems to match when the migrate failed:

#

seems to be a memory error. Maybe i can bump it up to 8GB RAM or so?

high oxide
#

Very good catch. Yes it's a memory error, and yes 8GB would be much better !