I notice the southern hemisphere doesn’t exist. Its a conspiracy I tell ya. Like the flat earth, Australia doesn’t exist and they just drug you on boarding the planes and fly you somewhere else and just tell you you are in Australia in the sourthern hemisphere. Its a global conspiracy that the southern hemisphere exists I tell ya
12 Likes
We all know that Australia is on the other side of the planet that is why it does not show or maybe you need to look at the map upside down. 
Jim will probably fix another map in the future, hold on.
3 Likes
We all know Australia is at the top of the world, its just you all are looking at it upside down
6 Likes
@joshuef
Re 1 I did not receive answer to my question.
Re 2 Shouldn’t the network be up and running first, and only when the network is up and running should you correct the errors?
Isn’t the fact, that you can’t get the nodes up and running at all because something isn’t working in the shared Lanchpad (and as far as I know I’m not the only one) a bug that should take priority?
I have not received an answer to the question - how can I change the memory path supported by Launchpad in the CLI node management tool? (I have been trying to get an answer for two days but no one has answered so far).
Re 3 I don’t have any logs because these nodes can’t be started but as I wrote, after adding the nodes, the computer slowed down very significantly and you can see in the task manager in Windows that the nodes are participating in processes e.g.:
Please answer my questions very carefully.
No Safe, no wave.
Sorry, what is this?
1 Like
A map of what Jim’s nodes are seeing around the world 
His 3 nodes are well connected to my dozens in Bulgaria. Eternal friendship!
Privacy. Security. Freedom
5 Likes
Is he in the Azzores or is that just for display purposes?
3 Likes
Do you want to visit him for a green tea?
Privacy. Security. Freedom
1 Like
I think this is Australia:
7 Likes
I dunno, maybe if I’m in the area?
3 Likes
what - never never land ?
3 Likes
Someone please could help me with this? 
I honestly don’t have a clue…
1 Like
You can see the link going towards Australia and New Zealand but Jim took the photo during the day so Australia is not included because at night the nodes don’t work, when the day gets up Jim will post a photo with only Australia and New Zealand on it.
It’s just that Autonomi doesn’t work at night 
3 Likes
From the map, it seems that my nodes are working after all, as confirmed by screenshots from the task managerWin
3 Likes
I now can’t start any nodes, having cleared out my old ones
Steps
rm -rf ~/.local/share/safe
rm ~/.config/systemd/user/safe*
rm -rf /var/log/safenode
node-manager reset
node-manager add --owner <discordid>
1 service(s) to be added
Retrieving latest version for safenode…
Using cached safenode version 0.108.2…
Download completed: /home/user/.local/share/safe/node/downloads/safenode
Services Added:
- ✓ safenode1*
-
- Safenode path: /home/user/.local/share/safe/node/safenode1/safenode*
-
- Data path: /home/user/.local/share/safe/node/safenode1*
-
- Log path: /home/user/.local/share/safe/node/safenode1/logs*
-
- RPC port: 127.0.0.1:33197*
[!] Note: newly added services have not been started
- RPC port: 127.0.0.1:33197*
safenode-manager start
Refreshing the node registry…
Attempting to start safenode1…
Failed to start 1 service(s):
✕ safenode1: Failed to start safenode1.service: Unit safenode1.service has a bad unit file setting.
See user logs and ‘systemctl --user status safenode1.service’ for details.
*Error: *
- 0: Failed to start one or more services*
Location:
- sn_node_manager/src/cmd/node.rs:705*
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
systemctl --user status safenode1.service
Systemctl error message
○ safenode1.service - safenode1
Loaded: bad-setting (Reason: Unit safenode1.service has a bad unit file setting.)
Active: inactive (dead)
Jun 07 18:58:05 dell systemd[4030]: /home/user/.config/systemd/user/safenode1.service:4: Failed to resolve unit specifiers in /ip4/167.99.206.36/udp/33566/quic-v1/p2p/12D3KooWGjne8BKZTmDpBD4G9Yxk4tBBEPqdVeUX9Uy5i4yDTDhV,/ip4/159.65.56.11>
Jun 07 18:58:05 dell systemd[4030]: safenode1.service: Unit configuration has fatal error, unit will not be started.
Jun 07 19:41:02 dell systemd[4030]: /home/user/.config/systemd/user/safenode1.service:4: Failed to resolve unit specifiers in /ip4/167.99.206.36/udp/33566/quic-v1/p2p/12D3KooWGjne8BKZTmDpBD4G9Yxk4tBBEPqdVeUX9Uy5i4yDTDhV,/ip4/159.65.56.11>
Jun 07 19:41:02 dell systemd[4030]: safenode1.service: Unit configuration has fatal error, unit will not be started.
Jun 07 19:45:17 dell systemd[4030]: /home/user/.config/systemd/user/safenode1.service:4: Failed to resolve unit specifiers in /ip4/178.128.34.57/udp/42231/quic-v1/p2p/12D3KooWSn9FhKHBbTRuS9FfydrfQ17tGGDByW6SJiSMeW3Gogdo,/ip4/159.65.31.14>
Jun 07 19:45:17 dell systemd[4030]: safenode1.service: Unit configuration has fatal error, unit will not be started.
Jun 07 19:51:46 dell systemd[4030]: /home/user/.config/systemd/user/safenode1.service:4: Failed to resolve unit specifiers in /ip4/209.97.138.10/udp/42240/quic-v1/p2p/12D3KooWFiDxHr3RpovdqShNuzbM5NAQSF7ctT6f5m4mxuRS4asB,/ip4/138.68.132.1>
Jun 07 19:51:46 dell systemd[4030]: safenode1.service: Unit configuration has fatal error, unit will not be started.
Jun 07 19:53:30 dell systemd[4030]: /home/user/.config/systemd/user/safenode1.service:4: Failed to resolve unit specifiers in /ip4/209.97.138.10/udp/42240/quic-v1/p2p/12D3KooWFiDxHr3RpovdqShNuzbM5NAQSF7ctT6f5m4mxuRS4asB,/ip4/138.68.132.1>
Jun 07 19:53:30 dell systemd[4030]: safenode1.service: Unit configuration has fatal error, unit will not be started.
lines 1-14/14 (END)
I know other people have been having this issue too. Previously it was working for me with sudo, but that’s stopped working now too.
Any ideas? 
Linux Mint 21.1
safenode-manager v 0.9.6
4 Likes
I don’t see a reboot of the machine after clearing everything out. You might have defunct processes locking up deleted files preventing new files from being created
Need the reboot after clearing out to remove the locked file entries in the OS
1 Like
When went above 130 nodes to 150-180 my internet seem to became laggy, a large % of nodes became inactive for minutes. The hardware seem ok, CPU, memory, router cpu, router memory, bandwidth, all good low/mid. Thinking it might be a general internet problem or maybe something with the ISP. Remeber think it was @yeezy who also had problem with limits, with his ISP.
2 Likes
Almost certainly not.
This is the exact expected result of the router losing NAT connections because you need more nat connections than the router’s nat table can handle.
It causes packets to be dropped because the router sees them as invalid due to the nat connection no longer existing for that packet’s source dest address port details
2 Likes
Ok, thought the router would be limited by cpu and memory, when looked at the interface usage cpu 40%, memory 56%.
So it it some kind of software limit then?
1 Like
Yes. The router does NAT translations where you have an application reaches out to an address with a packet. The router changes the source address:port (your device) to the router’s IP WAN address with a port it assigns. The information is entered into a table source:port, dest:post, its assigned port and from that info when a packet arrives to the router from the internet it takes the port number the packet is going to and finds the LAN address and port to translate the addressing of the packet coming in.
Now if you have 100 connections then there is 100 entries in that table and the router is doing that work for every packet going out or coming in. If you exceed the router’s nat table limit on number of connections then it gets rid of the oldest entry (or least used).
So for 150 nodes you have anywhere from 30,000 to 45,000 nat table entries. From your experience I would guess the table size is set to 40,000 to 64,000 entries. Cannot be better at guessing because it depends on the actual number of connections your 150 nodes are using.
5 Likes