Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
X xcache-config
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Docker-in-Docker (DinD) capabilities of public runners deactivated. More info

  • Escape European project @ CC
  • xcache-config
  • Issues
  • #2

Closed
Open
Created Feb 25, 2021 by MUSSET Paul@pmussetMaintainer

HTTPS access to eulake when XCache is XRootD 5.1

When the XCache is on XRootD 5.1, it's impossible to do file transfer from the EOS instance at CERN (EULAKE)

According to Elvin (EOS dev) and Andy (XRootD dev), it could come from known bugs (https://github.com/xrootd/xrootd/issues/1399 and ). Both have corrective patch which needs to be deploy on EOS (https://github.com/xrootd/xrootd/commit/d74e7a8af67e83fad14c3cbf08a58843f897b957 and https://github.com/xrootd/xrootd/pull/1408 or https://github.com/xrootd/xrootd/pull/1412).

If it the one about range, Wei Yang advise to start the server with the environment variable XRDCLHTTP_AVOIDRANAGE set to 1

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking