A lot or retry api request

[realtebo]

Prologue: I'm using go-mega through rclone

I am here to kindly ask what does it means all of these retry

2020/11/10 09:49:28 DEBUG : *go-mega*: Retry API request 1/10: Try again
2020/11/10 09:49:28 DEBUG : *go-mega*: Retry API request 2/10: Try again
2020/11/10 09:49:28 DEBUG : *go-mega*: pollEvents: Parsing event "t": {"a":"t","t":{"f":[{"h":"3ch3lAiQ","t":0,"a":"SGl3AnM6QwGnzXr8HgcrYujlxkChJWNtY6qQ74mtomNT9ljR87Kjxl8Z7oAM__CV","k":"_kyLsFDdbX8:T9OhFfWcvPdANm1SDphlt9Ymu90E5RIKGS63psjlkkc","p":"7VoliIIS","ts":1604998168,"u":"_kyLsFDdbX8","s":432549}]},"ou":"_kyLsFDdbX8"}

I'm syncing a big folder, near 2500 files. And I counted [from console tools] near 3500 occurences of "try again".

I am doing this debug because I've a lot of problem from logging in on mega that happens 'randomly'.

We sync only one time at hour, and are shipping <20 MBytes / hour of new data.

So this is not a bug for me, but I am here to ask for more infor to investigate if the 2 things could be somehow related [all of there retries and my login problems]

[realtebo]

We investigated further and discovere a LOT of login failed attempts. Randomly.

Linodes VPS's support told us there is no limitation serer-side Mega.,nz support told use there is no bandwidth limitation [It's a paid account]

[cristianlivella]

I'm having the same problem and I'm currently unable to log into Mega because every API request fails.

The API returns the error code -3, according to the documentation it seems that it's a temporary server-side problem, however I'm experiencing that problem from more than 10 hours. I can use Mega via web browser without any problem.

The response to the request [...] is structured as single number (e.g. -3 for EAGAIN) in the case of a request-level error [...] A request may return the error code EAGAIN in the event of a failed locking attempt or a temporary server-side malfunction. The request is likely to complete when retried. [...]

2021/02/14 22:51:38 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2021/02/14 22:51:38 DEBUG : HTTP REQUEST (req 0xc002f39100)
2021/02/14 22:51:38 DEBUG : POST /cs?id=[REDACTED]&sid=[REDACTED] HTTP/1.1
Host: g.api.mega.co.nz
User-Agent: rclone/v1.54.0
Content-Length: 17
Content-Type: application/json
Accept-Encoding: gzip

[{"a":"f","c":1}]
2021/02/14 22:51:38 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2021/02/14 22:51:38 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2021/02/14 22:51:38 DEBUG : HTTP RESPONSE (req 0xc002f39100)
2021/02/14 22:51:38 DEBUG : HTTP/1.1 200 OK
Content-Length: 2
Access-Control-Allow-Headers: Content-Type, MEGA-Chrome-Antileak
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: Original-Content-Length
Access-Control-Max-Age: 86400
Connection: keep-alive
Content-Type: application/json
Original-Content-Length: 2

-3
2021/02/14 22:51:38 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2021/02/14 22:51:38 DEBUG : *go-mega*: Retry API request 10/10: Try again

Edit: if I open Mega in the browser while I'm trying to log into via go-mega, I can't login not even from the browser and I can see the error code -3 in the requests log. When rclone/go-mega process stop, after about 5 minutes I can log in again with the browser. It looks like there is something wrong in the library that trigger a temporary block at the server side.