You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by "Kevin A. McGrail" <ke...@mcgrail.com> on 2015/01/05 22:50:12 UTC
Fwd: [jira] [Closed] (INFRA-8525) Solaris1 is not launching the slave
agent causing builds on Jenkins that depend on it to hang
FYI that we appear back online with Jenkins.
regards,
KAM
-------- Forwarded Message --------
Subject: [jira] [Closed] (INFRA-8525) Solaris1 is not launching the
slave agent causing builds on Jenkins that depend on it to hang
Date: Sun, 4 Jan 2015 08:59:34 +0000 (UTC)
From: Gavin (JIRA) <ji...@apache.org>
To: kmcgrail@apache.org
[ https://issues.apache.org/jira/browse/INFRA-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin closed INFRA-8525.
------------------------
Resolution: Fixed
Slave back up, seems to be doing ok.
> Solaris1 is not launching the slave agent causing builds on Jenkins that depend on it to hang
> ---------------------------------------------------------------------------------------------
>
> Key: INFRA-8525
> URL: https://issues.apache.org/jira/browse/INFRA-8525
> Project: Infrastructure
> Issue Type: Bug
> Components: Jenkins
> Reporter: Kevin A. McGrail
> Assignee: Gavin
>
> There do not appear to be any open tickets but solars1 appears to be unreachable so that Jenkins just hangs for builds depending on it.
> https://builds.apache.org/computer/solaris1/
> Specifically for https://builds.apache.org/job/SpamAssassin-trunk/, it appears our last working build was Build #9644 (May 21, 2014 2:11:19 AM) and we've received no notices that they were hung.
> However, I noticed if you look at INFRA-6597, you'll note that Stevo Slavic added a comment - 20/May/14 15:16 saying the issue was back which was diskspace related for that ticket. Perhaps /tmp is full?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Fwd: [jira] [Closed] (INFRA-8525) Solaris1 is not launching the
slave agent causing builds on Jenkins that depend on it to hang
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 1/7/2015 5:59 AM, Axb wrote:
> great!
> Thanks
>
> Axb
>
> PS: Hope you find time to get ruleqa back to normal operation.
Fingers crossed, I believe it's spinning up now. Give it a day and let
me know what you see.
Re: Fwd: [jira] [Closed] (INFRA-8525) Solaris1 is not launching the
slave agent causing builds on Jenkins that depend on it to hang
Posted by Axb <ax...@gmail.com>.
great!
Thanks
Axb
PS: Hope you find time to get ruleqa back to normal operation.
On 01/05/2015 10:50 PM, Kevin A. McGrail wrote:
> FYI that we appear back online with Jenkins.
>
> regards,
> KAM
>
>
> -------- Forwarded Message --------
> Subject: [jira] [Closed] (INFRA-8525) Solaris1 is not launching the
> slave agent causing builds on Jenkins that depend on it to hang
> Date: Sun, 4 Jan 2015 08:59:34 +0000 (UTC)
> From: Gavin (JIRA) <ji...@apache.org>
> To: kmcgrail@apache.org
>
>
>
> [
> https://issues.apache.org/jira/browse/INFRA-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Gavin closed INFRA-8525.
> ------------------------
> Resolution: Fixed
>
> Slave back up, seems to be doing ok.
>
>> Solaris1 is not launching the slave agent causing builds on Jenkins
>> that depend on it to hang
>> ---------------------------------------------------------------------------------------------
>>
>>
>> Key: INFRA-8525
>> URL: https://issues.apache.org/jira/browse/INFRA-8525
>> Project: Infrastructure
>> Issue Type: Bug
>> Components: Jenkins
>> Reporter: Kevin A. McGrail
>> Assignee: Gavin
>>
>> There do not appear to be any open tickets but solars1 appears to be
>> unreachable so that Jenkins just hangs for builds depending on it.
>> https://builds.apache.org/computer/solaris1/
>> Specifically for https://builds.apache.org/job/SpamAssassin-trunk/, it
>> appears our last working build was Build #9644 (May 21, 2014 2:11:19
>> AM) and we've received no notices that they were hung.
>> However, I noticed if you look at INFRA-6597, you'll note that Stevo
>> Slavic added a comment - 20/May/14 15:16 saying the issue was back
>> which was diskspace related for that ticket. Perhaps /tmp is full?
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>
>
>
>