[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: openbsd - gnunet warnings in logs
|
From: |
Schanzenbach, Martin |
|
Subject: |
Re: openbsd - gnunet warnings in logs |
|
Date: |
Mon, 4 Apr 2022 10:46:50 +0000 |
Hi,
> On 4. Apr 2022, at 12:32, Mikhail <mp39590@gmail.com> wrote:
>
> I've installed latest in git (60e93b8f0) on the OS, I didn't use
> --prefix, so installation has gone to default /usr/local, when I run
> gnunet-peerinfo I see several types of warnings in the logs.
>
> I'd like to package gnunet for OpenBSD, but first I need to understand
> that the application is working properly and usable for end users, I'll
> be definitely asked by OpenBSD committers about those warnings and if
> they are critical to general availability of the service of gnunet.
>
If you get core connections (gnunet-core shows at least one connection)
and "gnunet-arm -I" does not show any failed services you are pretty much
good to go (for now).
> Also 'make check' has 1 test failed, I sent email to bug-gnunet@ about
> it.
I tried to reproduce it yesterday, but I did not get gnunet to compile at all
for some
reason and gave up :(
>
> Can you prompt me if the warnings are critical, or they can be ignored?
>
> The type of warnings:
>
>> WARNING Failed to find plugin `http_client'
>> WARNING Failed to find plugin `https_client'
>> WARNING Failed to find plugin `udp'
Those warnings are FINE. It means that you have found a peer with
an endpoint (e.g. udp) that you have not configured for your peer.
see
$ gnunet-config -s transport -o PLUGINS
The default is that only TCP is loaded.
> but at least http and https plugins are there:
>
> ec2-user:/usr/local/lib/gnunet:324$ f http_client
> ./libgnunet_plugin_transport_http_client.so
> ./libgnunet_plugin_transport_http_client.la
> ec2-user:/usr/local/lib/gnunet:325$ f https_client
> ./libgnunet_plugin_transport_https_client.so
> ./libgnunet_plugin_transport_https_client.la
>
> for 'udp' I get something different:
>
> ec2-user:/usr/local/lib/gnunet:331$ f udp
> ./libexec/gnunet-communicator-udp
> ./libgnunet_test_transport_plugin_cmd_udp_backchannel.so
> ./libgnunet_test_transport_plugin_cmd_udp_backchannel.la
>
> Also I'm interested in following warning, which I see quiet often:
>
>> WARNING Processing code for message of type 367 did not call
>> `GNUNET_SERVICE_client_continue' after 1 m
>
> The full log:
>
> 2022-04-04T10:18:19.865427+0000 nat-19169 ERROR UPnP enabled in
> configuration, but UPnP client `upnpc` command not found, disabling UPnP
> 2022-04-04T10:18:19.924010+0000 transport-tcp-91112 WARNING Unexpected
> address length: 24 bytes
> 2022-04-04T10:18:19.924406+0000 transport-91112 ERROR Assertion failed at
> gnunet-service-transport_validation.c:902.
> 2022-04-04T10:18:19.924442+0000 transport-91112 ERROR Address with 24 bytes
> for plugin tcp and peer DSTJ is malformed
> 2022-04-04T10:18:19.924467+0000 transport-tcp-91112 WARNING Unexpected
> address length: 12 bytes
> 2022-04-04T10:18:19.924488+0000 transport-91112 ERROR Assertion failed at
> gnunet-service-transport_validation.c:902.
> 2022-04-04T10:18:19.924508+0000 transport-91112 ERROR Address with 12 bytes
> for plugin tcp and peer DSTJ is malformed
> 2022-04-04T10:18:19.925709+0000 transport-tcp-91112 WARNING Unexpected
> address length: 24 bytes
> 2022-04-04T10:18:19.925735+0000 transport-91112 ERROR Assertion failed at
> gnunet-service-transport_validation.c:902.
> 2022-04-04T10:18:19.925756+0000 transport-91112 ERROR Address with 24 bytes
> for plugin tcp and peer V8XX is malformed
> 2022-04-04T10:18:19.925779+0000 transport-tcp-91112 WARNING Unexpected
> address length: 12 bytes
> 2022-04-04T10:18:19.925799+0000 transport-91112 ERROR Assertion failed at
> gnunet-service-transport_validation.c:902.
> 2022-04-04T10:18:19.925818+0000 transport-91112 ERROR Address with 12 bytes
> for plugin tcp and peer V8XX is malformed
> 2022-04-04T10:18:42.864454+0000 transport-91112 WARNING Failed to find plugin
> `http_client'
> 2022-04-04T10:18:42.868543+0000 transport-91112 WARNING Failed to find plugin
> `http_client'
> 2022-04-04T10:18:42.880047+0000 transport-91112 WARNING Failed to find plugin
> `http_client'
> 2022-04-04T10:18:42.880289+0000 transport-91112 WARNING Failed to find plugin
> `http_client'
> 2022-04-04T10:18:42.880337+0000 transport-91112 WARNING Failed to find plugin
> `http_client'
> 2022-04-04T10:18:42.882589+0000 transport-91112 WARNING Failed to find plugin
> `http_client'
> 2022-04-04T10:18:42.882777+0000 transport-91112 WARNING Failed to find plugin
> `https_client'
> 2022-04-04T10:18:42.882850+0000 transport-91112 WARNING Failed to find plugin
> `https_client'
> 2022-04-04T10:18:42.882890+0000 transport-91112 WARNING Failed to find plugin
> `http_client'
> 2022-04-04T10:18:42.882929+0000 transport-91112 WARNING Failed to find plugin
> `http_client'
> 2022-04-04T10:18:42.882973+0000 transport-tcp-91112 WARNING Unexpected
> address length: 24 bytes
> 2022-04-04T10:18:42.883019+0000 transport-tcp-91112 WARNING Unexpected
> address length: 12 bytes
> 2022-04-04T10:18:42.883167+0000 transport-91112 WARNING Failed to find plugin
> `udp'
> 2022-04-04T10:18:42.883207+0000 transport-91112 WARNING Failed to find plugin
> `udp'
> 2022-04-04T10:18:42.883246+0000 transport-91112 WARNING Failed to find plugin
> `udp'
> 2022-04-04T10:18:42.883430+0000 transport-91112 WARNING Failed to find plugin
> `udp'
> 2022-04-04T10:18:42.883470+0000 transport-91112 WARNING Failed to find plugin
> `udp'
> 2022-04-04T10:18:42.883508+0000 transport-91112 WARNING Failed to find plugin
> `udp'
> 2022-04-04T10:18:42.883586+0000 transport-91112 WARNING Failed to find plugin
> `https_client'
> 2022-04-04T10:18:42.883626+0000 transport-91112 WARNING Failed to find plugin
> `https_client'
> 2022-04-04T10:18:42.883664+0000 transport-91112 WARNING Failed to find plugin
> `http_client'
> 2022-04-04T10:18:42.883702+0000 transport-91112 WARNING Failed to find plugin
> `http_client'
> 2022-04-04T10:18:42.883745+0000 transport-tcp-91112 WARNING Unexpected
> address length: 24 bytes
> 2022-04-04T10:18:42.883788+0000 transport-tcp-91112 WARNING Unexpected
> address length: 12 bytes
> 2022-04-04T10:19:34.905188+0000 util-connection-91112 WARNING `shutdown'
> failed at ./tcp_connection_legacy.c:1075 with error: Invalid argument
> 2022-04-04T10:19:34.915204+0000 util-connection-91112 WARNING `shutdown'
> failed at ./tcp_connection_legacy.c:1075 with error: Invalid argument
> 2022-04-04T10:19:36.875002+0000 util-connection-91112 WARNING `shutdown'
> failed at ./tcp_connection_legacy.c:1075 with error: Invalid argument
> 2022-04-04T10:19:36.884963+0000 util-connection-91112 WARNING `shutdown'
> failed at ./tcp_connection_legacy.c:1075 with error: Invalid argument
> 2022-04-04T10:19:42.874992+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.875553+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.894968+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.895397+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.895750+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.896095+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.896424+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.896758+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.897089+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.897273+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.897766+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.898090+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.898428+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.898479+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.898518+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.898556+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.898594+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.898632+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.898669+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
> 2022-04-04T10:19:42.898707+0000 util-service-91112 WARNING Processing code
> for message of type 367 did not call `GNUNET_SERVICE_client_continue' after 1
> m
>
This warning also originates in transport for unclear reasons. It is not
limited to openbsd.
We expect this to be fixed with the transport rewrite which is currently
ongoing.
> here I had called 'gnunet-arm -e'
>
> 2022-04-04T10:19:49.884614+0000 gns-api-20029 WARNING Problem with message
> queue. error: 1
> 2022-04-04T10:19:49.896043+0000 gns-api-49916 WARNING Problem with message
> queue. error: 1
> 2022-04-04T10:19:49.915683+0000 gns-api-49916 WARNING Problem with message
> queue. error: 1
>
This may be an issue. Does it terminate the processes or does it just hang?
signature.asc
Description: Message signed with OpenPGP