infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Commented] (INFRA-16082) curl/scripts getting connection refused from -- auto banned?
Date Thu, 22 Feb 2018 18:33:00 GMT


Hoss Man commented on INFRA-16082:

> Thanks for the doc pointer -- I will read up on the tree & depth params and try to
> the neccessary changes today -- although it looks like my laptop / home network has also

> been blocked? I can't even load this URL from the link you provided in my browser to
> out what exactly those options do... 

I used a diff jenkins server to read up on the details & experimented with the options,
and i think i've got everything fixed up so that all "/api/" URLs will incude either a depth
or tree param -- allthough i'm not 100% sure if the requests for the RSS or consoleText feeds
will be a problem?  (they don't seem to support the depth/tree options, so i assume hitting
them doesn't trigger any auto-ban?)

Here's examples of the types of URLs my script(s) should be hitting now...

Once per run...
Once per new job in the feed...
Once per job where tests were run...,name,status%5D%5D
Once per job where any tests failed...

Chris: Do you see any problems with those URLs?  If not, then if you can please remove
& from the ban list I can test this out but we should be all good.

Thanks for your help and the doc pointers.

> curl/scripts getting connection refused from -- auto banned?
> ------------------------------------------------------------------------------
>                 Key: INFRA-16082
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Jenkins
>            Reporter: Hoss Man
>            Assignee: Chris Lambertus
>            Priority: Major
> I've been working on a "planet venus + custom scripts" setup for archiving information
about failed jenkins builds for the lucene/solr project, and it appears that i may have been
auto-blocked by
> full details on my scripts can be found in this github repo...
> ...but in a nutshell: the script first fetches
; then some subsequent custom scripts attempts to download the XML summary of each job;  if
a job says it ran tests: then download the test report xml file; and if the test report says
there were failures: then download the full console logs ... all via URLs like these...
> However, it appears that something in the ASF network stack may have auto-blocked my
IP?  Both the logs and my curl commands seem to indicate a failure to connect to
the port.
> Here's what a (manual) verbose curl says when i try running it from the server where
i have these scripts setup ( ...
> $ nslookup
> Server:
> Address:
> Non-authoritative answer:
> Name:
> Address:
> $ ssh
> hossman@william-whipple:~$ curl -o tmp.xml -D - --verbose
> * Hostname was NOT found in DNS cache
>   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
>                                  Dload  Upload   Total   Spent    Left  Speed
>   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying
> * connect to port 443 failed: Connection refused
> * Failed to connect to port 443: Connection refused
> * Closing connection 0
> curl: (7) Failed to connect to port 443: Connection refused

This message was sent by Atlassian JIRA

View raw message