|
From: | madmurphy |
Subject: | Re: FS as user or not |
Date: | Wed, 26 Oct 2022 12:59:00 +0100 |
Still related to this thread, If I launch gnunet-fs -i
as normal user, first I get printed part of the list, then I get printed
2022-10-24T20:05:56.483363+0100 gnunet-fs-284292 WARNING Failed to receive response from `fs' service (error code is 1). Segmentation fault (core dumped)
The moment in which the error is thrown varies. Sometimes gnunet-fs -i
prints two files that I am sharing and then it throws an error. Other
times it prints ten files and then it throws an error. Etc.
No errors instead if I launch gnunet-fs -i
as gnunet
user.
Error code 1 means GNUNET_MQ_ERROR_READ
. There is only one point in the entire GNUnet project that throws GNUNET_MQ_ERROR_READ
, and that is src/util/client.c
at line 454.
Anyone able to reproduce this bug? Attached is my configuration.
--madmurphy
Hi Christian,
Yes, my username has always been in thegnunet
group. But in the past I always used the system services of GNUnet, except for the cases in which I needed the user services (like for creating egos).
The only (unlikely) explanation I can think of is that when I search the network using thegnunet
system user it shows a lot of results that were cached earlier, while when I search from my personal user it shows only new results, and for some reason there are no more files in the network published under “commons”. This is why I asked if people see the same behavior I see.
If that is not the reason, then I have no explanations.
--madmurphyOn Sat, Oct 8, 2022 at 11:08 AM Christian Grothoff <grothoff@gnunet.org> wrote:Hmm. Is your $USER in the 'gnunet' group?
On 10/6/22 08:54, madmurphy wrote:
> After one of the last commits, if I launch
>
> gnunet-search commons
>
> I get only one file that I am sharing, while if I launch
>
> sudo -u gnunet gnunet-search commons
>
> I get more than 40 results.
>
> For a second I thought that this commit from Jacki
> <https://git.gnunet.org/gnunet.git/commit/?id=1672c85ad702146521dc830298dcb3f802533539>
> was the reason, but it happens also if I restore the configuration
> before Jacki's commit. So I have no idea what happened.
>
> Anyone getting the same behavior?
>
> --madmurphy
>
sample-configuration.zip
Description: Zip archive
[Prev in Thread] | Current Thread | [Next in Thread] |