Hello, I wonder how to solve this issue. I’ve tried on arch and ubuntu (both containers running on Vanilla OS), same result.
Node is stopping in 1s… Node log path: x
Error:
0: Node terminated due to: “UPnP gateway not found. Enable UPnP on your router to allow incoming connections or manually port forward.”
Location:
ant-node/src/bin/antnode/main.rs:585
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
How are you starting your nodes? antctl?
It looks like your router doesn’t support upnp, so you’ll need to add --no-upnp flag to your ‘add’ command (do an antctl reset first to remove the bad node).
If you’re using a different way to start nodes, pass the --no-upnp argument to antnode.
All of this will require you to setup port forwarding from your gateway router to your node machine, which is beyond the scope of this reply.
antctl add --data-dir-path (external disk) --no-upnp --rewards-address (x) evm-arbitrum-one
antctl start gives me this :
Attempting to start antnode2…
Failed to start 1 service(s):
✕ antnode2: Command failed with exit code 5: Failed to start antnode2.service: Unit antnode2.service not found.
Error:
0: Failed to start one or more services
Location:
ant-node-manager/src/cmd/node.rs:882
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
FWIW i just solved similar or same issue. after most recent update/upgrade i got errors, ant status command same thing. restarts didn’t fix it, but a hard shutdown sure did.
oh, on Rpi4 running debian 12
aw bugger, NVM, i had RPC failure issue, whole different world i guess.
on a side note though, when my nodes (30) do start to spin up all 4 cores get rocked hard. i use –interval 360000 and we are just red lining all the way through. i hope more than 10 start before it crashes and reboots.
I’m having problems too. Seems symptomatic of a lot of nodes failing. My nodes keep growing in size, and I’ve had to remove many of them. Each time I delete a node I free up around 10+ GB, but it’s not long before I’m running out of disk space again.
Now I’m scratching my head because I lost the ability to use antctl - even after manually deleting some record_store files from a node to free up space.
me@my-computer ~ $ antctl --version
Autonomi Node Manager v0.14.1
Package version: 2025.12.2.1
Git info: stable / 4c4b17b / 2025-12-18
me@my-computer ~ $ antctl status
Error:
0: EOF while parsing a string at line 1 column 45056
Location:
ant-node-manager/src/bin/cli/main.rs:829
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
me@my-computer ~ $ antctl remove --service-name antnode8
Error:
0: EOF while parsing a string at line 1 column 45056
Location:
ant-node-manager/src/bin/cli/main.rs:829
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
I might just have to start using kill to end antnode processes. Also, looks like the autoupdate that was supposed to be working is updating everything. Running antup update, I see I was some versions behind.
me@my-computer ~ $ antup update
**************************************
* *
* Updating components *
* *
**************************************
Retrieving latest version for autonomi...
Latest version of autonomi is 0.5.2
Current version of autonomi is 0.4.14
Updating autonomi to 0.5.2...
Installing ant for x86_64-unknown-linux-musl at /home/me/.local/bin...
Installing autonomi version 0.5.2...
[00:00:05] [########################################] 11.09 MiB/11.09 MiB (0s) ant 0.5.2 is now available at /home/me/.local/bin/ant
Retrieving latest version for safenode...
Latest version of safenode is 0.4.16
Current version of safenode is 0.4.11
Updating safenode to 0.4.16...
Installing antnode for x86_64-unknown-linux-musl at /home/me/.local/bin...
Installing safenode version 0.4.16...
[00:00:02] [########################################] 11.57 MiB/11.57 MiB (0s) antnode 0.4.16 is now available at /home/me/.local/bin/antnode
Retrieving latest version for safenode-manager...
Latest version of safenode-manager is 0.14.1
Current version of safenode-manager is 0.14.1
safenode-manager is already at 0.14.1, which is the latest version.
No update will be performed.
(Though, when I look in a node’s directory and run ./antnode --version, it’s the latest version: v0.4.16.)
Unless I’m mistaken, the shrinking of the node pool and increase in uploads is putting pressure on your storage. Are you overprovisioned? Deleting stored records is only a temporary solution and not recommended.
Post emission speculation, there has been an intentional withdrawal of resources to cause the network to noticeably fill.
I’m not sure how to directly help with antctl, but it’s just an abstraction of your system process manager. If you want to access the existing processes directly, on linux, you can use
systemctl --user status antnode1 and systemctl --user stop antnode1
Similarly, journalctl --user -u antnode1 will give you the process output.
it’s slightly different to do the same on macos (uses launchd instead of systemd), but I don’t have any idea how windows works.
That’s an odd error, is there a file ~/.config/systemd/user/antnode2.service here?
[Unit]
Description=antnode2
[Service]
ExecStart=/run/media/x/autonomi/antnode2/antnode --rpc 127.0.0.1:40521 --root-dir /run/media/x/autonomi/antnode2 --log-output-dest /home/x/.local/share/autonomi/node/antnode2/logs --no-upnp --port 45853 --rewards-address x --stop-on-upgrade evm-arbitrum-one
Restart=on-success
Hmm. Maybe the definition file is not loaded?
Do systemctl --user status antnode2 and journalctl --user -u antnode2 provide anything useful?
Do either of those output change after systemctl --user start antnode2
If the systemctl commands say something like:
Unit antnode2.service could not be found.
Try reloading the service definition and try again. systemctl --user deamon-reload