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-16653) migrate projects-vm
Date Fri, 13 Jul 2018 15:38:00 GMT

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

Sebb commented on INFRA-16653:
------------------------------

Just found out that infod.py on hermes only accepted connects from projects-vm.a.o.
This causes failures for reporter.a.o on the new box.

I've fixed the code so it should work for projects-vm2.a.o.

However for some reason the server has not been set up to run as a reboot cron job for apmail
as might be expected so I cannot restart it.
It looks to be running under an individual infra person's login.

It now needs to be restarted to give access to the new server.
At the same time it really ought to be turned into a proper cron job so it won't get lost
on a reboot.

> migrate projects-vm
> -------------------
>
>                 Key: INFRA-16653
>                 URL: https://issues.apache.org/jira/browse/INFRA-16653
>             Project: Infrastructure
>          Issue Type: Project
>          Components: comdev
>            Reporter: Chris Lambertus
>            Priority: Major
>              Labels: pull-request-available
>
> projects-vm needs to be migrated to projects-vm2



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

Mime
View raw message