Re: Cannot bootstrap GNUnet 0.21.0

marty1885 <[email protected]> Wed, 13 Mar 2024 10:10:14 +0000
Newsgroups gmane.network.gnunet.general
Message-ID <t2EgQGnSEtxfO3ECDYKSCVke5soBkIlNsCRvd7gchrynLjIlIZ5BrcnYVfUXuT8cPvDa3pkWcCcgDHY03IICm73mJfDv6EEJupDT2LToXDg=@protonmail.com>
Hi,

Yes. I've restarted GNUnet several times. For safety I've restarted it once=
 again after reeving your reply. Still can't bootstrap.

Martin

On Tuesday, March 12th, 2024 at 10:15 PM, Schanzenbach, Martin <schanzen@gn=
unet.org> wrote:

> Hi,
>=20
> did you try again the last few days?
> We are currently observing better connectivity after fixing a
> configuration mistake on the bootstrap peer.
>=20
> Best
> Martin
>=20
> On 10.03.24 15:41, marty1885 wrote:
>=20
> > I deleted the databases for namestore and peerstore to get all processe=
s running (peerstore and namestore was failing). But still no peer connecti=
ons.
> >=20
> > `=E2=9D=AF gnunet-arm -I Services (excluding stopped services): (starte=
d: 23 / stopped: 22) cadet (binary=3D'gnunet-service-cadet', status=3Dstart=
ed) core (binary=3D'gnunet-service-core', status=3Dstarted) datastore (bina=
ry=3D'gnunet-service-datastore', status=3Dstarted) dht (binary=3D'gnunet-se=
rvice-dht', status=3Dstarted) fs (binary=3D'gnunet-service-fs', status=3Dst=
arted) gns (binary=3D'gnunet-service-gns', status=3Dstarted) hostlist (bina=
ry=3D'gnunet-daemon-hostlist', status=3Dstarted) identity (binary=3D'gnunet=
-service-identity', status=3Dstarted) namecache (binary=3D'gnunet-service-n=
amecache', status=3Dstarted) namestore (binary=3D'gnunet-service-namestore'=
, status=3Dstarted) nat (binary=3D'gnunet-service-nat', status=3Dstarted) n=
se (binary=3D'gnunet-service-nse', status=3Dstarted) peerstore (binary=3D'g=
nunet-service-peerstore', status=3Dstarted) reclaim (binary=3D'gnunet-servi=
ce-reclaim', status=3Dstarted) rest (binary=3D'gnunet-rest-server', status=
=3Dstarted) revocation (binary=3D'gnunet-service-revocation', status=3Dstar=
ted) rps (binary=3D'gnunet-service-rps', status=3Dstarted) setu (binary=3D'=
gnunet-service-setu', status=3Dstarted) statistics (binary=3D'gnunet-servic=
e-statistics', status=3Dstarted) topology (binary=3D'gnunet-daemon-topology=
', status=3Dstarted) transport (binary=3D'gnunet-service-transport', status=
=3Dstarted) communicator-tcp (binary=3D'gnunet-communicator-tcp', status=3D=
started) zonemaster (binary=3D'gnunet-service-zonemaster', status=3Dstarted=
)`
> >=20
> > On Sunday, March 10th, 2024 at 3:00 PM, Schanzenbach, Martin schanzen@g=
nunet.org wrote:
> >=20
> > > Hi,
> > >=20
> > > what does gnunet-arm -I output? Are all of the services running?
> > > For example, the peerstore database layout changed, so you probably h=
ave
> > > to delete your old database ($HOME/.local/share/gnunet/peerstore/sqli=
te.db).
> > >=20
> > > The road to a stable TNG will also be bumpy, so we rely on reports su=
ch
> > > as this to iron out the remaining bugs with it.
> > >=20
> > > BR
> > > Martin
> > >=20
> > > On 10.03.24 06:08, marty1885 wrote:
> > >=20
> > > > Thanks for the reply.
> > > >=20
> > > > I tried a few commands and still feels like my node is really not c=
onnected. DHT can't put, NSE returns a very small network size and GNS cann=
ot resolve.
> > > >=20
> > > > Is this expected?
> > > >=20
> > > > ```
> > > > =E2=9D=AF gnunet-core -si
> > > > Current local peer identity: CCXHBE49GRQVFAVFQ3BXVXPHHD63NG6ZNY31R0=
F59KVDZQA42PTG
> > > > (no further output)
> > > >=20
> > > > =E2=9D=AF gnunet-dht-put -k "hello" -d "world" -e 40m
> > > > (hangs, this used to return almost immidately)
> > > >=20
> > > > =E2=9D=AF gnunet-nse
> > > > 1710047156276913 1.688203 0.755488 1.474102
> > > >=20
> > > > =E2=9D=AF gnunet-gns -u gnunet.gns.alt -t PKEY
> > > >=20
> > > > > > > Looking for `PKEY' records under` gnunet.gns.alt'
> > > > > > > (no output)
> > > > > > > ```
> > > >=20
> > > > On Saturday, March 9th, 2024 at 11:39 PM, Schanzenbach, Martin scha=
[email protected] wrote:
> > > >=20
> > > > > Hi,
> > > > >=20
> > > > > the behaviour of gnunet-core changed. You can check the new switc=
hes
> > > > > with --help.
> > > > > Long-term core connections are know to be problematic behind NATs=
, still.
> > > > > But with a freshly started peer, "gnunet-core -i" should give you=
 your
> > > > > peer id, "gnunet-core -s" the connections (you can also combine t=
he
> > > > > switches).
> > > > > The command should probably output the help when called without a=
rguments.
> > > > >=20
> > > > > BR
> > > > > Martin
> > > > >=20
> > > > > On 09.03.24 14:55, marty1885 wrote:
> > > > >=20
> > > > > > Hi all,
> > > > > >=20
> > > > > > I've just built and installed the new GNUnet 0.21. But my node =
isn't connected to any peer after hours of waiting. Running gnunet-core sho=
ws no node is connected to me.
> > > > > >=20
> > > > > > `=E2=9D=AF gnunet-core (no output)`
> > > > > >=20
> > > > > > I have also checked `iotop` and can confirm gnunet-service-tran=
sport isn't doing much IO. While I was expecting at least hundreds of Kbps =
from experience in the past.
> > > > > >=20
> > > > > > How can I connect to the network? Please let me know what infor=
mation I can provide to diagnose the issue.
> > > > > >=20
> > > > > > Best,
> > > > > > Martin