You are viewing a plain text version of this content. The canonical link for it is here.
Posted to repository@apache.org by Dennis Lundberg <de...@apache.org> on 2014/08/21 18:00:16 UTC
repository.apache.org is unresponsive
Hi,
Depending on which part I try to access I get one of these failures:
- 503 Service Temporarily Unavailable (accessing a repository under /content/)
- 502 Proxy Error (accessing a repository under /content/)
- 500 Server Error (trying to release the repository
orgapachecreadur-1001 from staging)
I had a look at monitoring.apache.org, but it also gives an error message:
"nagiosDataNotUpToDate: NDOMy: NDO data to old (Backend ndomy_1)
NDO claims that Nagios did no status Update for more than "180"
seconds. Make sure that Nagios and ndo2db are running"
Let me know if you need additional details.
--
Dennis Lundberg
Re: repository.apache.org is unresponsive
Posted by Brian Fox <br...@sonatype.com>.
Something changed on the host which has restricted io capacity of the vm
(possibly another vm...). I'm still sorting out the details and we'll be
making changes to rsync to eliminate the bottlenecks.
On Thu, Aug 21, 2014 at 12:00 PM, Dennis Lundberg <de...@apache.org>
wrote:
> Hi,
>
> Depending on which part I try to access I get one of these failures:
> - 503 Service Temporarily Unavailable (accessing a repository under
> /content/)
> - 502 Proxy Error (accessing a repository under /content/)
> - 500 Server Error (trying to release the repository
> orgapachecreadur-1001 from staging)
>
> I had a look at monitoring.apache.org, but it also gives an error message:
>
> "nagiosDataNotUpToDate: NDOMy: NDO data to old (Backend ndomy_1)
> NDO claims that Nagios did no status Update for more than "180"
> seconds. Make sure that Nagios and ndo2db are running"
>
> Let me know if you need additional details.
>
> --
> Dennis Lundberg
>
Re: repository.apache.org is unresponsive
Posted by Brian Fox <br...@sonatype.com>.
I'm told that the disk array serving the system has multiple failed disks and is running in a degraded mode. The disks should arrive tomorrow and be installed this week. In parallel, we are working to get smart proxy hooked up to replace the rsync, which will help but will still require a final rsync to complete
--mobile
> On Aug 26, 2014, at 6:46 AM, Dennis Lundberg <de...@apache.org> wrote:
>
> Hi,
>
> The staging repo had entered some kind of locked state. On the 24th
> the staging repo was reset automatically, due to being in a
> non-responsive state. After that I was able to release it properly.
> Like others I'm now waiting for the sync to central to catch up.
>
> BTW, the reason for the failures on checksums and signatures were
> indeed due to I/O errors. This could be found by clicking on each
> activity in the tree view, which revealed more info about that
> activity, including the reason for the failure.
>
>
>> On Fri, Aug 22, 2014 at 5:32 PM, Dennis Lundberg <de...@apache.org> wrote:
>> Here is some more info about the staging repository for creadur that I
>> am trying to release. It is currently labeled as "Operation in
>> progress" and I cannot do anything with it. The Close, Promote,
>> Release and Drop buttons are all disabled.
>>
>>> On Thu, Aug 21, 2014 at 7:31 PM, Dennis Lundberg <de...@apache.org> wrote:
>>> Hi again,
>>>
>>> The server is responsive again. Thank you for that.
>>>
>>> I'm still having problems though. While trying to release the staging
>>> repository orgapachecreadur-1001 at
>>> https://repository.apache.org/content/repositories/orgapachecreadur-1001/
>>> Nexus complains that the signature and checksum validation fails. This
>>> is on the Activity tab under Activities/release. However if you look
>>> under Activities/close you can see that the same validations
>>> succeeded. Can this be related to the hardware switch in any way,
>>> which AFAICT occurred after the staging repo was closed but before I
>>> tried to release it?
>>>
>>>
>>>> On Thu, Aug 21, 2014 at 6:00 PM, Dennis Lundberg <de...@apache.org> wrote:
>>>> Hi,
>>>>
>>>> Depending on which part I try to access I get one of these failures:
>>>> - 503 Service Temporarily Unavailable (accessing a repository under /content/)
>>>> - 502 Proxy Error (accessing a repository under /content/)
>>>> - 500 Server Error (trying to release the repository
>>>> orgapachecreadur-1001 from staging)
>>>>
>>>> I had a look at monitoring.apache.org, but it also gives an error message:
>>>>
>>>> "nagiosDataNotUpToDate: NDOMy: NDO data to old (Backend ndomy_1)
>>>> NDO claims that Nagios did no status Update for more than "180"
>>>> seconds. Make sure that Nagios and ndo2db are running"
>>>>
>>>> Let me know if you need additional details.
>>>>
>>>> --
>>>> Dennis Lundberg
>>>
>>>
>>>
>>> --
>>> Dennis Lundberg
>>
>>
>>
>> --
>> Dennis Lundberg
>
>
>
> --
> Dennis Lundberg
Re: repository.apache.org is unresponsive
Posted by Dennis Lundberg <de...@apache.org>.
Hi,
The staging repo had entered some kind of locked state. On the 24th
the staging repo was reset automatically, due to being in a
non-responsive state. After that I was able to release it properly.
Like others I'm now waiting for the sync to central to catch up.
BTW, the reason for the failures on checksums and signatures were
indeed due to I/O errors. This could be found by clicking on each
activity in the tree view, which revealed more info about that
activity, including the reason for the failure.
On Fri, Aug 22, 2014 at 5:32 PM, Dennis Lundberg <de...@apache.org> wrote:
> Here is some more info about the staging repository for creadur that I
> am trying to release. It is currently labeled as "Operation in
> progress" and I cannot do anything with it. The Close, Promote,
> Release and Drop buttons are all disabled.
>
> On Thu, Aug 21, 2014 at 7:31 PM, Dennis Lundberg <de...@apache.org> wrote:
>> Hi again,
>>
>> The server is responsive again. Thank you for that.
>>
>> I'm still having problems though. While trying to release the staging
>> repository orgapachecreadur-1001 at
>> https://repository.apache.org/content/repositories/orgapachecreadur-1001/
>> Nexus complains that the signature and checksum validation fails. This
>> is on the Activity tab under Activities/release. However if you look
>> under Activities/close you can see that the same validations
>> succeeded. Can this be related to the hardware switch in any way,
>> which AFAICT occurred after the staging repo was closed but before I
>> tried to release it?
>>
>>
>> On Thu, Aug 21, 2014 at 6:00 PM, Dennis Lundberg <de...@apache.org> wrote:
>>> Hi,
>>>
>>> Depending on which part I try to access I get one of these failures:
>>> - 503 Service Temporarily Unavailable (accessing a repository under /content/)
>>> - 502 Proxy Error (accessing a repository under /content/)
>>> - 500 Server Error (trying to release the repository
>>> orgapachecreadur-1001 from staging)
>>>
>>> I had a look at monitoring.apache.org, but it also gives an error message:
>>>
>>> "nagiosDataNotUpToDate: NDOMy: NDO data to old (Backend ndomy_1)
>>> NDO claims that Nagios did no status Update for more than "180"
>>> seconds. Make sure that Nagios and ndo2db are running"
>>>
>>> Let me know if you need additional details.
>>>
>>> --
>>> Dennis Lundberg
>>
>>
>>
>> --
>> Dennis Lundberg
>
>
>
> --
> Dennis Lundberg
--
Dennis Lundberg
Re: repository.apache.org is unresponsive
Posted by Dennis Lundberg <de...@apache.org>.
Here is some more info about the staging repository for creadur that I
am trying to release. It is currently labeled as "Operation in
progress" and I cannot do anything with it. The Close, Promote,
Release and Drop buttons are all disabled.
On Thu, Aug 21, 2014 at 7:31 PM, Dennis Lundberg <de...@apache.org> wrote:
> Hi again,
>
> The server is responsive again. Thank you for that.
>
> I'm still having problems though. While trying to release the staging
> repository orgapachecreadur-1001 at
> https://repository.apache.org/content/repositories/orgapachecreadur-1001/
> Nexus complains that the signature and checksum validation fails. This
> is on the Activity tab under Activities/release. However if you look
> under Activities/close you can see that the same validations
> succeeded. Can this be related to the hardware switch in any way,
> which AFAICT occurred after the staging repo was closed but before I
> tried to release it?
>
>
> On Thu, Aug 21, 2014 at 6:00 PM, Dennis Lundberg <de...@apache.org> wrote:
>> Hi,
>>
>> Depending on which part I try to access I get one of these failures:
>> - 503 Service Temporarily Unavailable (accessing a repository under /content/)
>> - 502 Proxy Error (accessing a repository under /content/)
>> - 500 Server Error (trying to release the repository
>> orgapachecreadur-1001 from staging)
>>
>> I had a look at monitoring.apache.org, but it also gives an error message:
>>
>> "nagiosDataNotUpToDate: NDOMy: NDO data to old (Backend ndomy_1)
>> NDO claims that Nagios did no status Update for more than "180"
>> seconds. Make sure that Nagios and ndo2db are running"
>>
>> Let me know if you need additional details.
>>
>> --
>> Dennis Lundberg
>
>
>
> --
> Dennis Lundberg
--
Dennis Lundberg
Re: repository.apache.org is unresponsive
Posted by Dennis Lundberg <de...@apache.org>.
Hi again,
The server is responsive again. Thank you for that.
I'm still having problems though. While trying to release the staging
repository orgapachecreadur-1001 at
https://repository.apache.org/content/repositories/orgapachecreadur-1001/
Nexus complains that the signature and checksum validation fails. This
is on the Activity tab under Activities/release. However if you look
under Activities/close you can see that the same validations
succeeded. Can this be related to the hardware switch in any way,
which AFAICT occurred after the staging repo was closed but before I
tried to release it?
On Thu, Aug 21, 2014 at 6:00 PM, Dennis Lundberg <de...@apache.org> wrote:
> Hi,
>
> Depending on which part I try to access I get one of these failures:
> - 503 Service Temporarily Unavailable (accessing a repository under /content/)
> - 502 Proxy Error (accessing a repository under /content/)
> - 500 Server Error (trying to release the repository
> orgapachecreadur-1001 from staging)
>
> I had a look at monitoring.apache.org, but it also gives an error message:
>
> "nagiosDataNotUpToDate: NDOMy: NDO data to old (Backend ndomy_1)
> NDO claims that Nagios did no status Update for more than "180"
> seconds. Make sure that Nagios and ndo2db are running"
>
> Let me know if you need additional details.
>
> --
> Dennis Lundberg
--
Dennis Lundberg