Message boards : ATLAS application : Firewall Complaints caused by ATLAS
Message board moderation

To post messages, you must log in.

AuthorMessage
computezrmle
Volunteer moderator
Volunteer developer
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 15 Jun 08
Posts: 2386
Credit: 222,944,101
RAC: 137,246
Message 37869 - Posted: 31 Jan 2019, 7:00:29 UTC

ATLAS native again causes firewall complaints.


1.
Target-IP: 141.108.38.67
DNS: atlas-svc-07.roma1.infn.it.
Target-Port: 8080 TCP


2.
Target-IP: 148.88.67.14
DNS: py-dev.lancs.ac.uk.
Target-Port: different UDP
ID: 37869 · Report as offensive     Reply Quote
computezrmle
Volunteer moderator
Volunteer developer
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 15 Jun 08
Posts: 2386
Credit: 222,944,101
RAC: 137,246
Message 37914 - Posted: 3 Feb 2019, 7:52:16 UTC

Another firewall complaint.

https://lhcathome.cern.ch/lhcathome/result.php?resultid=215081073
stderr.txt shows lines like this:
2019-02-03 06:49:45|52906|SiteInformat| Executing command: curl --connect-timeout 20 --max-time 120 --cacert /tmp/x509up_u2002 -sS "http://pandaserver.cern.ch:25085/cache/schedconfig/BOINC_MCORE.all.json" > /home/boinc2/BOINC_ATLAS/slots/2/queuedata.json
2019-02-03 06:49:45|52906|SiteInformat| !!WARNING!!1999!! curl command exited with code 1792

TCP Port 25085 to pandaserver.cern.ch is blocked as it is not listed in the portlist.
Seems to be a misconfigured task (or complete batch?).
ID: 37914 · Report as offensive     Reply Quote
computezrmle
Volunteer moderator
Volunteer developer
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 15 Jun 08
Posts: 2386
Credit: 222,944,101
RAC: 137,246
Message 38008 - Posted: 14 Feb 2019, 11:31:07 UTC - in response to Message 37869.  

ATLAS native again causes firewall complaints.


1.
Target-IP: 141.108.38.67
DNS: atlas-svc-07.roma1.infn.it.
Target-Port: 8080 TCP


2.
Target-IP: 148.88.67.14
DNS: py-dev.lancs.ac.uk.
Target-Port: different UDP

Today I notice the same firewall issues.
Needs to be checked by the project team.
ID: 38008 · Report as offensive     Reply Quote
David Cameron
Project administrator
Project developer
Project scientist

Send message
Joined: 13 May 14
Posts: 387
Credit: 15,314,184
RAC: 0
Message 38011 - Posted: 14 Feb 2019, 15:45:27 UTC - in response to Message 38008.  

ATLAS native again causes firewall complaints.


1.
Target-IP: 141.108.38.67
DNS: atlas-svc-07.roma1.infn.it.
Target-Port: 8080 TCP


This is an ATLAS database service but the ATLAS@Home WU should not be accessing it. I've fixed the configuration of services that ATLAS use so this one shouldn't be used again.


2.
Target-IP: 148.88.67.14
DNS: py-dev.lancs.ac.uk.
Target-Port: different UDP

Today I notice the same firewall issues.
Needs to be checked by the project team.


This is the WU sending some monitoring information which is not necessary, so I've turned this off for new WU.



TCP Port 25085 to pandaserver.cern.ch is blocked as it is not listed in the portlist.
Seems to be a misconfigured task (or complete batch?).


Maybe this was a temporary error for this particular WU? The file downloaded from pandaserver.cern.ch is a file that should be included in the WU input files - for some reason in this case it was missing and so had to be downloaded.
ID: 38011 · Report as offensive     Reply Quote
computezrmle
Volunteer moderator
Volunteer developer
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 15 Jun 08
Posts: 2386
Credit: 222,944,101
RAC: 137,246
Message 38084 - Posted: 28 Feb 2019, 18:58:22 UTC - in response to Message 38011.  

Another misconfigured ATLAS batch?

My firewall complains again:
Target-IP: 141.108.38.67
DNS: atlas-svc-07.roma1.infn.it.
Target-Port: 8080 TCP

@David Cameron
Be so kind as to check the task configuration.
ID: 38084 · Report as offensive     Reply Quote
David Cameron
Project administrator
Project developer
Project scientist

Send message
Joined: 13 May 14
Posts: 387
Credit: 15,314,184
RAC: 0
Message 38093 - Posted: 3 Mar 2019, 21:32:16 UTC - in response to Message 38084.  

Another misconfigured ATLAS batch?

My firewall complains again:
Target-IP: 141.108.38.67
DNS: atlas-svc-07.roma1.infn.it.
Target-Port: 8080 TCP

@David Cameron
Be so kind as to check the task configuration.


I asked my colleagues in Rome for more information on this server - it is not actually a database server but a monitoring service. All ATLAS tasks in the world (not only ATLAS@Home) send hardware information such as CPU model etc to this server so that the effects of different machines on the performance of ATLAS tasks can be studied. Failing to contact this service doesn't affect the results of the WU in any way so do not worry about your results and you can ignore the firewall warnings or open it to this server if you wish.
ID: 38093 · Report as offensive     Reply Quote

Message boards : ATLAS application : Firewall Complaints caused by ATLAS


©2024 CERN