I haven’t been keeping up for the last couple months, but when I come back, I’m not really sure what the state of things are. Does it even work on Windows? Why can’t I connect a node then?
.\antctl.exe start
Just hangs. Not even a timeout. Can’t report that as a bug. Why doesn’t the homepage have a download link to antctl? Frankly I find it easier to use than the launchpad(neither are suitable for non-technical people, a terminal app is a terminal app). Why doesn’t Automatic (UPnP) work and do I need to port forward? If so, why is none of this mentioned on the Quickstart Guide?
To help, we would need more context than just a single command. Really depends what you done before that. If you have more commands and output to show, we can try.
As to UPnP and port forwarding, we have a huge piece of work in the pipeline we refer to internally as “reachability”. This is essentially the node being able to configure itself to a large extent in this respect. We should hopefully see this released in perhaps a few weeks from now.
Right now, on the latest version of antctl/antnode, UPnP is the default. If you want to go for port forwarding instead, you should use --no-upnp on the add command.
The last version of launchpad I had installed before this was 0.5.1
Today I downloaded the latest antctl and deleted all autonomi related files in ProgramData
I had 3 nodes running at one point and so 3 services, antnode1, antnode2, antnode3. I had some problem with them I don’t recall from back then and shut them down.
.\antctl.exe start
failed will some error until I deleted these three services with sc delete.
(Some automated clean-up would be nice)
After re-adding my wallet with antctl,
.\antctl.exe status
╔══════════════════════╗
║ Antnode Services ║
╚══════════════════════╝
Service Name Peer ID Status Connected Peers Failure
antnode1 - ADDED - -
and running
.\antctl.exe start
it hangs like I described in my op.
Using the latest launchpad, connection is labeled as so
Ctrl+c followed by .\antctl.exe status
gives the status as RUNNING, however, .\antctl.exe balance gives a value of 0, which I’m sure isn’t accurate.
A few minutes latter, .\antctl.exe status gives the status as STOPPED
This is pretty much all the context I can give you.
There is an antctl reset command that deletes the services, or at least it tries to, and is successful most of the time. It uses WinSW under the hood, which about 10% of the time doesn’t succeed in clearing the services out. We might need to switch over to sc.exe just for the deletion.
I would advise doing a reset, and then using the add command again.
Using my laptop which is running Fedora Linux however does work. Never installed it on there before. Both my Windows desktop and laptop are using wi-fi. It really does seems like a Windows-specific problem.
The only output of antctl start
is Attempting to start antnode1...
I don’t remember every interaction my desktop had with autonomi and its tools over the course of a year. If you can tell me how to reset the state and what output or log files would be helpful, I will provide that.
