Message boards :
Number crunching :
Unusual (blocked) Requests to apfmon.lancs.ac.uk
Message board moderation
Author | Message |
---|---|
Send message Joined: 15 Jun 08 Posts: 2401 Credit: 225,540,856 RAC: 120,699 |
Since Friday afternoon I notice strange TCP entries of the following kind in my proxy log. I'm not 100% sure if the requests are made by Theory VMs or by ATLAS native (but I tend to ATLAS). Direct UDP requests to the same target system are blocked by my firewall. [14/Dec/2018:14:55:10 +0100] "POST http://apfmon.lancs.ac.uk/api/jobs/: HTTP/1.1" 404 669 "-" "curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.27.1 zlib/1.2.3 libidn/1.18 libssh2/1.4.2" TCP_MISS:HIER_DIRECT [14/Dec/2018:16:05:22 +0100] "POST http://apfmon.lancs.ac.uk/api/jobs/: HTTP/1.1" 404 669 "-" "curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.27.1 zlib/1.2.3 libidn/1.18 libssh2/1.4.2" TCP_MISS:HIER_DIRECT [14/Dec/2018:22:12:36 +0100] "POST http://apfmon.lancs.ac.uk/api/jobs/: HTTP/1.1" 502 741 "-" "curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.27.1 zlib/1.2.3 libidn/1.18 libssh2/1.4.2" TCP_MISS:HIER_DIRECT [14/Dec/2018:22:21:29 +0100] "POST http://apfmon.lancs.ac.uk/api/jobs/: HTTP/1.1" 502 741 "-" "curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.27.1 zlib/1.2.3 libidn/1.18 libssh2/1.4.2" TCP_MISS:HIER_DIRECT [15/Dec/2018:12:09:54 +0100] "POST http://apfmon.lancs.ac.uk/api/jobs/: HTTP/1.1" 404 669 "-" "curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.27.1 zlib/1.2.3 libidn/1.18 libssh2/1.4.2" TCP_MISS:HIER_DIRECT [15/Dec/2018:12:28:38 +0100] "POST http://apfmon.lancs.ac.uk/api/jobs/: HTTP/1.1" 404 669 "-" "curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.27.1 zlib/1.2.3 libidn/1.18 libssh2/1.4.2" TCP_MISS:HIER_DIRECT <ongoing> |
Send message Joined: 24 Oct 04 Posts: 1118 Credit: 49,727,516 RAC: 13,445 |
|
Send message Joined: 15 Jun 08 Posts: 2401 Credit: 225,540,856 RAC: 120,699 |
ATLAS pilot factory monitor This server never replied an HTTP status that indicates a success. Instead it replied a couple of "502" (Bad Gateway) and lots of "404" (Not Found). This may be caused by the incomplete/malformed URL sent by the ATLAS task: http://apfmon.lancs.ac.uk/api/jobs/: The question is: What should ATLAS send instead of "jobs/:"? |
Send message Joined: 13 May 14 Posts: 387 Credit: 15,314,184 RAC: 0 |
This is a mistake on our side due to a change introduced last week. These calls to one of our ATLAS monitoring systems are not supposed to be sent from the running tasks and I have fixed it this morning so that newly submitted tasks will not do this. But the errors you see in the current WU are harmless and do not affect the running tasks. |
©2024 CERN