RPC call failing with `Client error: timeout during get_status: deadline has elapsed'`

[BatiGencho]

I have a tokio thread which has a loop inside making rpc calls to e.g. get node status using the massa-sdk/client, the public sub-client:

tokio::spawn(async move {
        loop {
                let cfg = match client.public.get_status().await {
                  Ok(node_status) => node_status,
                  Err(e) => return Err(anyhow::anyhow!(e.to_string())),
                };
        }
    });

After some time of the code actually running, I get the following error: Client error: timeout during get_status: deadline has elapsed' as a result of the tokio timeout on the client side (see this line : https://github.com/massalabs/massa/blob/main/massa-sdk/src/lib.rs#L82 ) which is currently set to 10 secs.

The current labnet version I am getting is: Version { instance: ['L', 'A', 'B', 'N'], major: 0, minor: 10 } from rpc and it corresponds to the explorer one too: Testnet version: LABN.0.10

I can only explain it as it being caused either by:

• a rate limiting
• some ip blocking
• ddos attack protection
• Node Rpc server issues

[BatiGencho]

@damip @AurelienFT Maybe NGINX settings if there is one sitting in front of the node/s ??? I guess @qdrn can also check that here ? Thanks

[damip]

@BatiGencho your loop is calling get_status non-stop without delay ?

[damip]

For info, the labnet is currently running 14.6, we should update it to 14.7

[qdrn]

AFAIK there is no rate limiting on the labnet server. Can you provide a bit more details ? Does it work for a while and then it doesn't ? How can we reproduce the issue ?

[AurelienFT]

For info, the labnet is currently running 14.6, we should update it to 14.7

There is no difference between 14.6 and 14.7 but as soon as there is an update we could

[BatiGencho]

@AurelienFT I added some now, but it was without before. I am inspecting it to see if it will fail again.

[AurelienFT]

@BatiGencho do you still have this error or we can close ?