www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (INFRA-10031) cannot access /mnt/asf-maven-central-mirror: Transport endpoint is not connected
Date Wed, 22 Jul 2015 03:14:04 GMT

     [ https://issues.apache.org/jira/browse/INFRA-10031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Lambertus resolved INFRA-10031.
-------------------------------------
    Resolution: Fixed

Unmounted then ran 

/usr/local/bin/riofs --uid=0 --gid=0 --config=/etc/riofs.conf.xml -o ro,allow_other asf-maven-central-mirror
/mnt/asf-maven-central-mirror/

Seems to be OK now.


> cannot access /mnt/asf-maven-central-mirror: Transport endpoint is not connected
> --------------------------------------------------------------------------------
>
>                 Key: INFRA-10031
>                 URL: https://issues.apache.org/jira/browse/INFRA-10031
>             Project: Infrastructure
>          Issue Type: Bug
>            Reporter: Hervé Boutemy
>            Assignee: Chris Lambertus
>            Priority: Critical
>
> issue that was closed in INFRA-9636 reappeared a few days after it was manually fixed
by [~abayer]
> hboutemy@maven-central-mirror-us-east:~$ ls /mnt/ 
> ls: cannot access /mnt/asf-maven-central-mirror: Transport endpoint is not connected

> ls: cannot access /mnt/tmp: Transport endpoint is not connected 
> asf-maven-central-mirror lost+found riofs tmp 
> I put this issue as Critical since I suppose the maven central copy is failing, but I
can't really tell...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message