Dunno how I forgot the /deploy/local bit…
But now I get this screen which is generally unresponsive… I can change the values but “save” does nothing
AFAICS all my existing nodes are still happily chugging away.
Try refreshing the page with Ctrl+F5 to make sure the browser it’s not using the old version from its cache. You can also try with opening it in a “new private window” as well.
1 Like
In the case that a node is too shunned or is otherwise malfunctioning (refusing to run, in one instance), and thus needing replacement, I think that it would be handy to have a “Replace node” button on each instance. That way it could just harvest the port info, get a new note ID and launch a new node easily.
Not a big deal, but would be pretty slick.
4 Likes
Formicaio: Active nodes, 0 Inactive!
Ahem, not correct in my setup:
1 Like
Sorry @bochaco but since I did the upgrade, I cannot start any new nodes at all whether individually or by batch.
Existing nodes are still running but show “unknown” for StoreCost, Relevant and Shunned. THey still seem to earn OK though 
Don’t you get any error in an alert popup and/or in the browser console (open it with F12) ?
You can also use docker compose logs -f and see what it’s logged when you try to create a node, some log entry should show up and tell what is happening when trying to execute the request.
1 Like
Sorry @bochaco - called away to diagnose Firestick errors for Mrs Southside.
Forced to the conclusion her Firestick is effed. Naturally this is my fault…
It does however answer the Q about what she is getting for Xmas.
I’ll look at Formicaio again in the morning.
It is too early to say LaunchPad should be abandoned for Formicaio? This is something regular folk can use and understand.
2 Likes
Yes, too early I’m afraid.
We would have too many n00bs that havent a clue about Docker. We’d need to do Docker support as well.
But in general, I’d agree with you Formicaio seems to (mostly) Just work and is streets ahead of anything else. - IF you are comfortable with Docker.
Big thanks again to @bochaco for the work he puts into this. 
2 Likes
Exactly and creates yet another barrier to adoption for people.
2 Likes
Until we can get Docker setup with 1-2 clicks on Windows Mac and linux, formicaio is sadly not for absolute beginners.
That is no reason to stop work on it as it could be a viable replacement for LaunchPad.
Im off to try being absolutely dumb on a Win10 box here to see just how much work it takes to put Docker on WIndows.
Lets not forget that its users NOW we need and they are more likely to come from folks are geeky enough to consider using Docker. If we have to wait a few weeks/months until we can get a reliable Docker/Autonomi/Formaciao install script then so be it.
That may be something the community can deliver, it would need no/minimal input from the devs.
Definitely not a reason to stop.
Just not as a only way to run nodes.
1 Like
Generally agreed, but if you’re willing to dedicate a whole machine and install Umbrel on it (or buy an Umbrel machine from the company), it really can’t get much simpler. I haven’t plumbed the Docker mystery, though I plan to. 
Docker Desktop on a Win10 box needs a reboot.
this is unfortunate.
Agreed. It would have to be extracted from Docker to make in workable.
I’ve released a version with a new feature to ‘recycle’ nodes, it simply generates a fresh peer-id and restarts the node. If this works as expected (…we’ll see), eventually, whenever we know how to accurately define a node as “unstable”/“malfunctioning”, then Formicaio could automate the task of recycling those falling into that category.
6 Likes
Thank you for effort on this. I’ll give it a go and report back.
2 Likes
Yeah, I’d noticed this and taken advantage of it. Thanks.
I’m running 20 nodes and have noticed that some few just never get up and running, when checked by the individual stats function (also very cool). Occasionally, a node will just refuse to restart. After a couple tries and letting it sit, if it doesn’t come up, I recycle it. If it still doesn’t get running I have to just delete it and add another.
Overall, functioning is looking better and better.
Appreciate what you’re doing!!
2 Likes
I have also found using my own scripts that sometimes a particular port number, even though the OS reports its not used, the node still cannot accept using it. Typically the metrics port# or RPC port# but if its the listening port it seems the node doesn’t say why and balks with address in use or just doesn’t work.
The point I am trying to say is that at times you may just have to mark some ports as do not use (until computer restart). But even then I’ve still had a particular port# unusable and maybe in this case it might be some system/application process using it for internals. I use port numbers above 40000 in an attempt to stay away form clashing though.
3 Likes