help-gnunet
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Determining whether gnunet is connected


From: madmurphy
Subject: Re: Determining whether gnunet is connected
Date: Sun, 27 Feb 2022 14:47:17 +0000

Hi Bob,

These might be worth reading:

--madmurphy


On Sun, Feb 27, 2022 at 12:04 PM Bob Ham <rah@settrans.net> wrote:
Hi Martin,

Yesterday my node started to make connections but today it's dying with:

2022-02-27T07:58:50.066009+0000 sqlite-1654 ERROR `sqlite3_step' failed
at ../../../../gnunet/src/datastore/plugin_datastore_sqlite.c:638 with
error: database or disk is full
2022-02-27T07:58:50.107604+0000 sqlite-1654 ERROR `sqlite3_step' failed
at ../../../../gnunet/src/datastore/plugin_datastore_sqlite.c:719 with
error: database or disk is full
2022-02-27T07:58:50.107695+0000 sqlite-1654 ERROR Failed to reset sqlite
statement with error: database or disk is full
2022-02-27T07:58:50.109281+0000 datastore-1654 ERROR database or disk is
full

It seems a file, ~/.local/share/gnunet/datastore/sqlite.db, has grown to
fill the filesystem:

debian@BeagleBone:~$ ls
/home/debian/.local/share/gnunet/datastore/sqlite.db -lh
-rw-r--r-- 1 debian debian 3.7G Feb 27 12:01
/home/debian/.local/share/gnunet/datastore/sqlite.db


Is this expected behaviour?  Regardless, how can I prevent it?

Regards,

Bob


On 26/02/2022 19:53, Schanzenbach, Martin wrote:
> Hi Bob,
>
> I think the situation should have improved.
> The bootstrap peer was somehow crippled through the configuration to accept
> at most 10 peers.
>
> BR
> Martin
>
>> On 26. Feb 2022, at 09:29, Schanzenbach, Martin <mschanzenbach@posteo.de> wrote:
>>
>> Hi,
>>
>> yes our bootstrap peer is acting up lately.
>> We will try and set it up again for the 0.16.0 release this weekend.
>>
>> BR
>> Martin
>>
>>> On 26. Feb 2022, at 02:04, Bob Ham <rah@settrans.net> wrote:
>>>
>>> Hi Martin,
>>>
>>> That prints nothing:
>>>
>>> $ gnunet-core
>>> $
>>>
>>> Presumably that means there are no connected peers?
>>>
>>> Thanks,
>>>
>>> Bob
>>>
>>>
>>> On 25/02/2022 18:53, Schanzenbach, Martin wrote:
>>>> Hi Bob,
>>>>
>>>> in order to check if you currently have any neighbours (directly connected peers)
>>>> you can try:
>>>>
>>>> $ gnunet-core
>>>>
>>>> BR
>>>> Martin
>>>>
>>>>> On 25. Feb 2022, at 19:26, Bob Ham <rah@settrans.net> wrote:
>>>>>
>>>>> Hi there,
>>>>>
>>>>> After having a lot of issues compiling and running different versions
>>>>> of gnunet sources and packages, I've finally managed to compile the
>>>>> latest git.  Lots of services are running:
>>>>>
>>>>> $ gnunet-arm -I
>>>>> Services (excluding stopped services):
>>>>> (started: 25 / stopped: 21)
>>>>> ats (binary='gnunet-service-ats', status=started)
>>>>> cadet (binary='gnunet-service-cadet', status=started)
>>>>> core (binary='gnunet-service-core', status=started)
>>>>> datastore (binary='gnunet-service-datastore', status=started)
>>>>> dht (binary='gnunet-service-dht', status=started)
>>>>> fs (binary='gnunet-service-fs', status=started)
>>>>> gns (binary='gnunet-service-gns', status=started)
>>>>> hostlist (binary='gnunet-daemon-hostlist', status=started)
>>>>> identity (binary='gnunet-service-identity', status=started)
>>>>> namecache (binary='gnunet-service-namecache', status=started)
>>>>> namestore (binary='gnunet-service-namestore', status=started)
>>>>> nat (binary='gnunet-service-nat', status=started)
>>>>> nse (binary='gnunet-service-nse', status=started)
>>>>> peerinfo (binary='gnunet-service-peerinfo', status=started)
>>>>> peerstore (binary='gnunet-service-peerstore', status=started)
>>>>> reclaim (binary='gnunet-service-reclaim', status=started)
>>>>> resolver (binary='gnunet-service-resolver', status=started)
>>>>> rest (binary='gnunet-rest-server', status=started)
>>>>> revocation (binary='gnunet-service-revocation', status=started)
>>>>> setu (binary='gnunet-service-setu', status=started)
>>>>> statistics (binary='gnunet-service-statistics', status=started)
>>>>> topology (binary='gnunet-daemon-topology', status=started)
>>>>> transport (binary='gnunet-service-transport', status=started)
>>>>> zonemaster (binary='gnunet-service-zonemaster', status=started)
>>>>> zonemaster-monitor (binary='gnunet-service-zonemaster-monitor', status=started)
>>>>>
>>>>> but I'm not sure what's happening with the node and whether it's
>>>>> connected to anything.  As per suggestions from IRC, I tried running
>>>>> "gnunet-transport --information" but it hangs for 30 seconds and then
>>>>> prints:
>>>>>
>>>>> $ gnunet-transport --information
>>>>> Failed to list connections, timeout occurred
>>>>>
>>>>> The output of "gnunet-transport --monitor" shows activity but it's
>>>>> like debug output, it's not clear what the activity is and whether any
>>>>> successful connections have occurred.
>>>>>
>>>>> The handbook is of no help, it only discusses graphical programs but I
>>>>> only have terminal access at present.
>>>>>
>>>>> How can I determine whether my node is connected and working?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Bob Ham
>>>>>
>>>>> --
>>>>> Bob Ham <rah@settrans.net>
>>>>>
>>>>> for (;;) { ++pancakes; }
>>>>>
>>>>
>>
>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]