Closed Jollyfant closed 6 years ago
Thanks, for your input.
Maybe because of the xmlns:ingv namespace?
Seems you're right. I'm going to fix it in the upcoming streaming-federator version.
Hi Philipp, THIS IS A REMINDER :)
cheers, Daniel
Hi @Jollyfant,
the Federator should be able to handle the xmlns:ingv
namespace.
However, it seems to be an endpoint configuration issue. Even though I decreased already the number of parallel requests to 5 I receive HTTP status code 429 (Too many requests. By the way this is no valid FDSNWS HTTP status code.)
With pleasure I'd like to check the maximum number of parallel requests, but now the federator seems to be blocked by fail2ban
. And after more than half an hour it is still blocked ...
cheers
@damb are you in the EIDA mailing list? We can discuss the issue there. Also, I think RESIF has a custom XML namespace that needs to be included (if its not handled automatically already). The 429 status code for the Federator means the IP(s) running the Federator service(s) should be whitelisted.
We should really look in to improving the endpoints eventually.
As the topic moved to eida_maint
mailing list I close this ticket here.
Requests for node INGV returns 204:
Maybe because of the
xmlns:ingv
namespace?