infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-15908) Cannot update hermes:/var/qmail/badrcptto
Date Fri, 26 Jan 2018 01:02:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-15908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16340379#comment-16340379
] 

Sebb commented on INFRA-15908:
------------------------------

OK thanks!

[BTW, I suggested the root cron update because I had thought that it was a root cron job that
checked in the changes, but I see now the check-ins are done by an apmail cron job.]


> Cannot update hermes:/var/qmail/badrcptto
> -----------------------------------------
>
>                 Key: INFRA-15908
>                 URL: https://issues.apache.org/jira/browse/INFRA-15908
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Mailing Lists
>            Reporter: Sebb
>            Assignee: Gavin
>            Priority: Major
>
> Cannot update hermes:/var/qmail/badrcptto
> Using apmail credentials:
> Updating '/var/qmail/control':
> svn: E000013: Can't move '/var/qmail/control/.svn/tmp/svn-XppDSv' to '/var/qmail/control/.svn/pristine/f4/f45610f44796265a7a2041f9bb9f083a42c13a3c.svn-base':
Permission denied
> This has worked in the past.
> It looks like the problem is that the pristine/f4 directory has been used by root to
commit some of the changes that are made locally.
> A possible fix would be to update the root cron to revert ownership back to apmail after
any commits.
> N.B. for now I have updated the file locally



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message