The problem is antctl, no matter if new version or old, will download the latest antnode when it starts.
As long as you have not restarted then its fine
1 Like
I understand this and see it in the ongoing payments. I am asking about the new nodes that I add with antctl what command should I use 
Check out the Impossible Futures!
1 Like
Don’t add new ones with antctl at this time, they won’t work. Wait till they fix the mismatch
Seems if you upgrade antctl before adding more nodes then its fine and use --no-upnp if you need to disable upnp
4 Likes
If you upgrade to the latest version of antctl and then use antctl add --no-upnp for new nodes, that is fine.
It’s the upgrade that is the problem.
2 Likes
For me the upgrade went smoothly, but I think I created them with --no-upnp.
1 Like
I thought you said upgrade was ok and that reset was the problem, so I went ahead and started an upgrade?
I set the interval to an hour. Should I stop, reset and start again?
I need --no-upnp
1 Like
Sorry, I don’t think I said that anywhere in this thread. I’m inferring it from what other people have said. I’m still investigating the situation myself. But I have verified what I posted in my reply to Dimitar.
2 Likes
It may be my mistake, but I’d appreciate your advice on my question if you have enough information to do so.
If not, fair enough enough, just say so.
Thanks. I didn’t intend to sound confrontational. I realise this is your weekend too.
2 Likes
What’s happening so far? Do you see nodes failing to start?
2 Likes
Just a general update: I actually haven’t been able to reproduce a problem with upgrading myself. It’s part of the tests that get run before any release and I didn’t have any errors there either.
3 Likes
Isn’t this contradicting yourself, or was it not explained properly?
You said first “if you upgrade then that is fine”, then you said “It’s the upgrade that is the problem”
Maybe it’s not completely clear. The upgrade of antctl and the node are different things. The second one is referring to the node upgrade. However, as I’ve said, I’ve not reproduced any problem here myself.
1 Like
Both of these rely on antctl, and antctl downloads the latest node each time
I’m not sure what point you are making. You need to be clearer for me, sorry.
They have problems with antctl not starting the nodes correctly
Seems there is an issue somewhere
I can’t say anything about Formicaio because I’ve never used it. I suspect it will be simple enough to make a change for the use of different arguments.
I tried to do a bit of work on reproducing the problem with the launchpad today, but I couldn’t. I think it’s going to need to wait until Monday.
1 Like
Btw, would you mind editing your post here please? Just put a strikethrough on that if you can please, because it is not the case.
If antctl is upgraded to the latest version you will be able to add nodes using --no-upnp.
3 Likes
Yeh, using ‘upgrade’ on VPS is not advised. Here’s the antctl status after it completed with errors saying some nodes were not upgraded:
Refreshing the node registry...
Service Name Peer ID Status Connected Peers Failure
antnode5 12D3KooWBoYiEYgzwV6EypdjjQuL29QSNgCn6dHrWcEcj3XmSqiA RUNNING 70 -
antnode6 12D3KooWDsD8LJ7ja8rg8JyLqpFNo5fbZ8RxqFvWB1JywpTPJPa8 RUNNING 90 -
antnode7 12D3KooWLi5U9D2U3zxNkPJDuaFQq1qXBrFprKjVvni85aPJeJJb RUNNING 89 -
antnode8 12D3KooWRVaLA8cngr2hhBVUrgstp7j1MJzxEDjZR1PbESQtoPog RUNNING 62 -
antnode9 12D3KooWQtyZsE2q39A9HwSUcpPk5caPgRA6aowj6DzaMhorDFSZ RUNNING 63 -
antnode10 12D3KooWCBf9YxgfFwhtC7oSbSY79ph3iUPBrHMCimiKsQLGR6mp STOPPED - "UPnP gateway not found. Enable UPnP on your router to allow incoming connections or manually port forward."
antnode11 12D3KooWSdc2g6xeZEkRZZkRMmJcK6g5MAsGvbHhFUdh9damnCYj STOPPED - "UPnP gateway not found. Enable UPnP on your router to allow incoming connections or manually port forward."
antnode12 12D3KooWRjWhBSbX4g6KPoepk9jro6cB8yKFa4eYhhhhDdRmYNcr STOPPED - "UPnP gateway not found. Enable UPnP on your router to allow incoming connections or manually port forward."
antnode13 12D3KooWAqJcyFj6Pc5YRmsuKYxxPtTuUkkrAYVzwhYaKUudWR1d STOPPED - "UPnP gateway not found. Enable UPnP on your router to allow incoming connections or manually port forward."
antnode14 12D3KooWFecBHtH1ebceUX4SbfaAef5gVaFYkBxcwYHR34q1pg37 STOPPED - "UPnP gateway not found. Enable UPnP on your router to allow incoming connections or manually port forward."
antnode15 12D3KooWFXkeHf5warSBkA6fsuMQMAweyvnPFbDJA95NhMnuNYNu STOPPED - "UPnP gateway not found. Enable UPnP on your router to allow incoming connections or manually port forward."
antnode16 12D3KooWLDcaBxp12gvABa9YinrsJtyiDN1ecck82pQgP14iqa3j STOPPED - "UPnP gateway not found. Enable UPnP on your router to allow incoming connections or manually port forward."
antnode17 12D3KooWFBRfcgLA2DqvEKF1Kq9xD4W8YpxoqphSQ75DLMFJ5uw4 STOPPED - "UPnP gateway not found. Enable UPnP on your router to allow incoming connections or manually port forward."
antnode18 12D3KooWNfqZykKv7mWGbhRPKx5hmEiUdYCsSsFE1LAL2BnTKMkX STOPPED - "UPnP gateway not found. Enable UPnP on your router to allow incoming connections or manually port forward."
antnode19 12D3KooWNyH65KpPFgTyCAC3CJFpDVs5EKukNGqPEVUAzxRcJ3Qn STOPPED - "UPnP gateway not found. Enable UPnP on your router to allow incoming connections or manually port forward."
I think I’ll reset and start with --no-upnp.
1 Like
Uuh.. is majority of the network going to be reset.. let’s see how it works out!
Hmm, what’s really puzzling about that is the fact that some upgraded and some didn’t.
You were on the new version of antctl?
1 Like