Just to clarify: is it Nodes that you don’t want joining from home or is it Clients as well? Sorry if I’ve missed that.
2 Likes
Just nodes.
1 Like
Hows it looking so far? 
My node started up but shows no activity in the log since that.
Update: overnight still no activity in the log since startup.
system: Debian 12 (bookworm)
Started 2 nodes at 17:19 (node 0) and 17:21 (node 1), and both stopped logging about 17:22:20 (all times UTC).
disknet@disknet:~$ uname -a
Linux disknet 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) x86_64 GNU/Linux
disknet@disknet:~$ ls -l
total 25840
-rwxrwxr-x 1 disknet disknet 19904024 May 16 08:29 safenode
drwxr-xr-x 3 disknet disknet 4096 May 16 19:19 safenode0_data
drwxr-xr-x 3 disknet disknet 4096 May 16 19:21 safenode1_data
-rw-r--r-- 1 disknet disknet 6541656 May 16 08:33 safenode-x86_64-unknown-linux-musl.zip
disknet@disknet:~$ ls -lR safenode* | grep .log
-rw-r--r-- 1 disknet disknet 175353 May 16 19:22 safenode.log
-rw-r--r-- 1 disknet disknet 108963 May 16 19:22 safenode.log
disknet@disknet:~$ du
10104 ./safenode0_data/record_store
10280 ./safenode0_data
10876 ./safenode1_data/record_store
10988 ./safenode1_data
4 ./.config/procps
8 ./.config
47132 .
disknet@disknet:~$ ps -aux | grep safe
disknet 514 0.0 2.7 289816 26580 pts/1 Sl 19:19 0:01 ./safenode --root-dir=./safenode0_data --log-dir=./safenode0_data
disknet 531 0.0 2.4 289816 23532 pts/1 Sl 19:21 0:01 ./safenode --root-dir=./safenode1_data --log-dir=./safenode1_data
disknet 1452 0.0 0.0 5496 876 pts/1 S 22:10 0:00 tail -f safenode1_data/safenode.log
disknet 1453 0.0 0.0 5496 888 pts/1 S 22:10 0:00 tail -f safenode0_data/safenode.log
disknet 1467 0.0 0.2 6332 2088 pts/1 S+ 22:19 0:00 grep safe
1 Like
I had this on old system (Debian 10, libc6 2.28), the problem is gone with sytem upgrade (Debian 12, libc6 2.36)
3 Likes
I also had that with the binary but rather than faff around with the library I compiled from source and it worked first time.
This was just for the Client but I’m sure that will work for the Node as well.
2 Likes
It seems I can’t either download or upload. I’m getting this for upload:-
safe files upload tinyfile Removed old logs from directory: "/tmp/safe-client.log" Starting logging to directory: "/tmp/safe-client.log" Instantiating a SAFE client... Storing file "tinyfile" of 24 bytes.. Did not store file "tinyfile" to all nodes in the close group! Network Error Could not get enough peers (8) to satisfy the request, found 0. Writing 8 bytes to "/home/maid/.safe/client/uploaded_files/file_names_2023-05-16_20-39-42"
This is what I’m getting for download:-
safe files download cock01.jpg d724a3ff9b2746e042fa1e8db4c4e0ec5769097042911cc8a34197edc1342e47 Removed old logs from directory: "/tmp/safe-client.log" Starting logging to directory: "/tmp/safe-client.log" Instantiating a SAFE client... Downloading file "cock01.jpg" with address d724a3ff9b2746e042fa1e8db4c4e0ec5769097042911cc8a34197edc1342e47 Did not get file "cock01.jpg" from the network! Network Error Record was not found locally.
I’ve tried the command with --peers in the command line and also by exporting the variable first and also exporting the variable with lots of peers.
1 Like
Likewise, I can no longer connect with a client.
Gave up on the node from AWS a couple hours back cos I was busy with other stuff.
If others are still working I’ll try that again.
I also can’t join an AWS based node. I’m getting this in the logs:-
tail -f safenode.log
[2023-05-16T21:45:18.027717Z INFO safenode]
Running safenode v0.1.0
=======================
[2023-05-16T21:45:18.028119Z INFO safenode] Starting node ...
[2023-05-16T21:45:18.028249Z INFO safenode::network] Node (PID: 18490) with PeerId: 12D3KooWQs6LLk5jDpaVpo145ao7DbRBE85GXA6eDzauXEFMz2rZ
[2023-05-16T21:45:18.030256Z INFO safenode::network::event] Local node is listening on "/ip4/127.0.0.1/udp/37672/quic-v1/p2p/12D3KooWQs6LLk5jDpaVpo145ao7DbRBE85GXA6eDzauXEFMz2rZ"
[2023-05-16T21:45:18.030331Z INFO safenode::network::event] Local node is listening on "/ip4/172.30.3.146/udp/37672/quic-v1/p2p/12D3KooWQs6LLk5jDpaVpo145ao7DbRBE85GXA6eDzauXEFMz2rZ"
[2023-05-16T21:45:18.030472Z ERROR safenode::node::api] Failed to dial 12D3KooWGxWnfChkZTLTqFCkDMafTkpteBvSdJd3bYdA29q3H7GB: AlreadyDialingPeer(PeerId("12D3KooWGxWnfChkZTLTqFCkDMafTkpteBvSdJd3bYdA29q3H7GB"))
[2023-05-16T21:45:23.031078Z WARN safenode::network::event] Having OutgoingConnectionError Some(PeerId("12D3KooWGxWnfChkZTLTqFCkDMafTkpteBvSdJd3bYdA29q3H7GB")) - Transport([("/ip4/52.56.104.157/udp/12000/quic-v1/p2p/12D3KooWGxWnfChkZTLTqFCkDMafTkpteBvSdJd3bYdA29q3H7GB/p2p/12D3KooWGxWnfChkZTLTqFCkDMafTkpteBvSdJd3bYdA29q3H7GB", Other(Custom { kind: Other, error: HandshakeTimedOut }))])
[2023-05-16T21:45:23.031158Z ERROR safenode::node::api] Failed to dial 12D3KooWGxWnfChkZTLTqFCkDMafTkpteBvSdJd3bYdA29q3H7GB: DialError(Transport([("/ip4/52.56.104.157/udp/12000/quic-v1/p2p/12D3KooWGxWnfChkZTLTqFCkDMafTkpteBvSdJd3bYdA29q3H7GB/p2p/12D3KooWGxWnfChkZTLTqFCkDMafTkpteBvSdJd3bYdA29q3H7GB", Other(Custom { kind: Other, error: HandshakeTimedOut }))]))
my nodes:
/ip4/37.233.99.40/udp/41673/quic-v1/p2p/12D3KooWM6TEch7ptxQDprBEn5sooDssPzpQBxWCg143D1kZo8VJ
/ip4/37.233.99.40/udp/47603/quic-v1/p2p/12D3KooWLkDxBMQVUEM7vqJzZrMbBTXsCFk4Td13nDNZWVNLo28B
perhaps somebody would want to add me to their SAFE_PEERS env var and make network alive again 
3 Likes
Tried to use your node as a peer, but it seems failed:
[2023-05-16T21:55:39.102865Z ERROR safenode::node::api] Failed to dial 12D3KooWQs6LLk5jDpaVpo145ao7DbRBE85GXA6eDzauXEFMz2rZ: AlreadyDialingPeer(PeerId("12D3KooWQs6LLk5jDpaVpo145ao7DbRBE85GXA6eDzauXEFMz2rZ"))
[2023-05-16T21:55:39.103183Z WARN safenode::network::event] Having OutgoingConnectionError Some(PeerId("12D3KooWQs6LLk5jDpaVpo145ao7DbRBE85GXA6eDzauXEFMz2rZ")) - Transport([("/ip4/172.30.3.146/udp/37672/quic-v1/p2p/12D3KooWQs6LLk5jDpaVpo145ao7DbRBE85GXA6eDzauXEFMz2rZ/p2p/12D3KooWQs6LLk5jDpaVpo145ao7DbRBE85GXA6eDzauXEFMz2rZ", Other(Custom { kind: Other, error: HandshakeTimedOut }))])
1 Like
Done - how do you find your node addresses?
4 Likes
seems something happened, but went broken anyway:
[2023-05-16T21:56:56.564961Z ERROR safenode::network::event] KademliaEvent has not been implemented: UnroutablePeer { peer: PeerId("12D3KooWCPU3stvzbFrcDMqCc575qRV8DJEd6Jqkx3oWNdugXsXU") }
[2023-05-16T21:56:56.606360Z INFO safenode::network::event] got inbound request: FindNode { num_closer_peers: 0 }
[2023-05-16T21:57:04.156836Z INFO safenode::network::event] IdentifyEvent: Sent { peer_id: PeerId("12D3KooWLdtvaFrgnzrqSW7GnC4KwS7LdmejPtJ9EgKb2UEF9WM8") }
[2023-05-16T21:57:04.158095Z INFO safenode::network::event] IdentifyEvent: Received { peer_id: PeerId("12D3KooWLdtvaFrgnzrqSW7GnC4KwS7LdmejPtJ9EgKb2UEF9WM8"), info: Info { public_key: Ed25519(PublicKey(compressed): a0c1f15ee6834861f29c8d9a8626d5bcb31649e886cc65d37046181ac8961023), protocol_version: "safe/0.1.0", agent_version: "safe/node/0.1.0", listen_addrs: ["/ip4/127.0.0.1/udp/52445/quic-v1", "/ip4/176.58.124.107/udp/52445/quic-v1", "/ip4/176.58.124.107/udp/52445/quic-v1"], protocols: ["/safe/1", "/ipfs/kad/1.0.0", "/ipfs/id/1.0.0", "/ipfs/id/push/1.0.0"], observed_addr: "/ip4/37.233.99.40/udp/41673/quic-v1/p2p/12D3KooWM6TEch7ptxQDprBEn5sooDssPzpQBxWCg143D1kZo8VJ/p2p/12D3KooWM6TEch7ptxQDprBEn5sooDssPzpQBxWCg143D1kZo8VJ" } }
[2023-05-16T21:57:04.158182Z INFO safenode::network::event] Adding peer to routing table, based on received identify info from PeerId("12D3KooWLdtvaFrgnzrqSW7GnC4KwS7LdmejPtJ9EgKb2UEF9WM8"): Info { public_key: Ed25519(PublicKey(compressed): a0c1f15ee6834861f29c8d9a8626d5bcb31649e886cc65d37046181ac8961023), protocol_version: "safe/0.1.0", agent_version: "safe/node/0.1.0", listen_addrs: ["/ip4/127.0.0.1/udp/52445/quic-v1", "/ip4/176.58.124.107/udp/52445/quic-v1", "/ip4/176.58.124.107/udp/52445/quic-v1"], protocols: ["/safe/1", "/ipfs/kad/1.0.0", "/ipfs/id/1.0.0", "/ipfs/id/push/1.0.0"], observed_addr: "/ip4/37.233.99.40/udp/41673/quic-v1/p2p/12D3KooWM6TEch7ptxQDprBEn5sooDssPzpQBxWCg143D1kZo8VJ/p2p/12D3KooWM6TEch7ptxQDprBEn5sooDssPzpQBxWCg143D1kZo8VJ" }
[2023-05-16T21:57:04.158421Z DEBUG safenode::node::api] PeerAdded: 12D3KooWLdtvaFrgnzrqSW7GnC4KwS7LdmejPtJ9EgKb2UEF9WM8
[2023-05-16T21:57:04.158444Z INFO safenode] Connected to the Network
[2023-05-16T21:57:07.065286Z INFO safenode::network::event] IdentifyEvent: Error { peer_id: PeerId("12D3KooWCPU3stvzbFrcDMqCc575qRV8DJEd6Jqkx3oWNdugXsXU"), error: Timeout }
[2023-05-16T21:57:07.068704Z INFO safenode::network::event] IdentifyEvent: Error { peer_id: PeerId("12D3KooWCPU3stvzbFrcDMqCc575qRV8DJEd6Jqkx3oWNdugXsXU"), error: Timeout }
[2023-05-16T21:57:16.565211Z INFO safenode::network::event] Connection closed to Peer 12D3KooWCPU3stvzbFrcDMqCc575qRV8DJEd6Jqkx3oWNdugXsXU - Listener { local_addr: "/ip4/0.0.0.0/udp/41673/quic-v1", send_back_addr: "/ip4/82.32.185.3/udp/35042/quic-v1" } - Some(KeepAliveTimeout)
[2023-05-16T21:57:16.568690Z INFO safenode::network::event] Connection closed to Peer 12D3KooWCPU3stvzbFrcDMqCc575qRV8DJEd6Jqkx3oWNdugXsXU - Listener { local_addr: "/ip4/0.0.0.0/udp/41673/quic-v1", send_back_addr: "/ip4/82.32.185.3/udp/35042/quic-v1" } - Some(KeepAliveTimeout)
[2023-05-16T21:57:23.631550Z INFO safenode::network::event] Connection closed to Peer 12D3KooWLdtvaFrgnzrqSW7GnC4KwS7LdmejPtJ9EgKb2UEF9WM8 - Listener { local_addr: "/ip4/0.0.0.0/udp/41673/quic-v1", send_back_addr: "/ip4/176.58.124.107/udp/52445/quic-v1" } - Some(KeepAliveTimeout)
It’s at the beginning of safenode.log, look for something like this:
Running safenode v0.1.0
=======================
[2023-05-16T21:11:29.801843Z INFO safenode] Starting node ...
[2023-05-16T21:11:29.802017Z INFO safenode::network] Node (PID: 1557) with PeerId: 12D3KooWM6TEch7ptxQDprBEn5sooDssPzpQBxWCg143D1kZo8VJ
[2023-05-16T21:11:29.804633Z INFO safenode::network::event] Local node is listening on "/ip4/127.0.0.1/udp/41673/quic-v1/p2p/12D3KooWM6TEch7ptxQDprBEn5sooDssPzpQBxWCg143D1kZo8VJ"
[2023-05-16T21:11:29.804720Z INFO safenode::network::event] Local node is listening on "/ip4/37.233.99.40/udp/41673/quic-v1/p2p/12D3KooWM6TEch7ptxQDprBEn5sooDssPzpQBxWCg143D1kZo8VJ"
4 Likes
This’ll be me. Maybe try the same?
/ip4/127.0.0.1/udp/48861/quic-v1/p2p/12D3KooWCEB6oQNFwGa52Mg4nqE25QTob6v
wPPQo9VjyBdoJD2Rm
Edit: or rather
/ip4/176.58.124.107/udp/48861/quic-v1/p2p/12D3KooWCEB6oQNFwGa52Mg4nqE25Q
Tob6vwPPQo9VjyBdoJD2Rm
2 Likes
Done. It seems that your node has responded, but logs say a connection gets closed. Probably something to investigate by the team. Their nodes already look dead.
7 Likes
ah. That’s because that IP address 172.30.3.146 is an AWS internal IP address! This is my AWS external one: 44.213.89.235
I added you as a peer and tried another upload and got:-
safe files upload tinyfile
Removed old logs from directory: "/tmp/safe-client.log"
Starting logging to directory: "/tmp/safe-client.log"
Instantiating a SAFE client...
Storing file "tinyfile" of 24 bytes..
Did not store file "tinyfile" to all nodes in the close group! Network Error Could not get enough peers (8) to satisfy the request, found 4.
Writing 8 bytes to "/home/maid/.safe/client/uploaded_files/file_names_2023-05-16_22-45-42"
so we just need another 4 and we might be back in business!
3 Likes
just another 3 needed
Could not get enough peers (8) to satisfy the request, found 5.
2 Likes
A quick check is to see if you can create a register
make sure you have exported the SAFE_PEERS env var then
safe register create mytestreg
For now it will fail but soon…
2 Likes
Because network failed?
Do you mean that register creation will fail with NAT (or with closed port in general) and succeed if port is open and no NAT present?