Development for LHC@home

[Once again, I can't post to the main project!]
[Hmm, maybe it doesn't like my emoticons!!]

Is anyone else having their tasks fail after just a few minutes due to a failure to contact the CMS-Factory? It's happening increasingly for me, but 've not seen it for a few other volunteers I've studied -- and no-one else is complaining at the moment!

2024-09-10 06:01:15 (12611): Guest Log: [INFO] Testing connection to EOSCMS
2024-09-10 06:01:15 (12611): Guest Log: [INFO] Testing connection to CMS-Factory
2024-09-10 06:01:30 (12611): Guest Log: [DEBUG] Status run 1 of up to 3: 1
2024-09-10 06:01:53 (12611): Guest Log: [DEBUG] Status run 2 of up to 3: 1
2024-09-10 06:02:23 (12611): Guest Log: [DEBUG] Status run 3 of up to 3: 1
...
2024-09-10 06:02:23 (12611): Guest Log: libnsock nsock_trace_handler_callback(): Callback: CONNECT ERROR [Network is unreachable (101)] for EID 16 [2001:1458:d00:17::13:80]
2024-09-10 06:02:23 (12611): Guest Log: Ncat: Network is unreachable.
2024-09-10 06:02:23 (12611): Guest Log: [ERROR] Could not connect to vocms0205.cern.ch on port 80

I'm having some real problems with a new security regime at my institution, so this could possibly be a manifestation of that.😒

---

Factory has been on vocms0205.cern.ch in the past but was recently moved to vocms0204.cern.ch.
The CMS VM still includes a check for vocms0205 (called by bootstrap).

Laurence created a patch to replace that check without the need to distribute a completely new vdi/app version.
Looks like that patch doesn't always work reliable on your machine - reason unknown.


Best long term solution would be to create a fresh vdi with a simplified bootstrap (outsourced network checks).

I'm having some real problems with a new security regime at my institution, so this could possibly be a manifestation of that.

I don't think so.
The test fails simply because vocms0205.cern.ch doesn't exist any more.