Both the nodes are up now.
On Friday, July 14, 2017, 3:41:54 PM PDT, Daniel Pono Takamori
wrote:
lares doesn't respond to ping or ssh, and orcus seems to have sshd
running but won't let me in and hangs when I try to connect.
Could we get a powercycle when you have a chance please.
Thanks a mil
I am unable to revive the node remotely. Asked our siteops to have a look.
On Thursday, February 2, 2017, 6:32:16 AM PST, Pono Takamori
wrote:Hey Rajiv,
Looks like asf916 didn't come back up from a reboot. Would you mind nudging it?
Thanks a bunch,
-Pono
rebooted asf908 and proserpina and they are up now.
I don't have access to jenkins master and don't manage builds.
From: Andrew Bayer
To: Rajiv Chittajallu
Cc: "builds@apache.org"
Sent: Tuesday, September 15, 2015 5:43 AM
Subject: Please reboot asf908 and prosper
asf909 is up.
On Monday, August 24, 2015, 11:59, Rajiv Chittajallu
wrote:
Unable to get asf909 up from remote. Will ask siteops.
Rest of the nodes are working.
From: Andrew Bayer
To: Rajiv Chittajallu
Cc: "builds@apache.org"
Sent: Monday, August 24, 2015 11:08 A
Unable to get asf909 up from remote. Will ask siteops.
Rest of the nodes are working.
From: Andrew Bayer
To: Rajiv Chittajallu
Cc: "builds@apache.org"
Sent: Monday, August 24, 2015 11:08 AM
Subject: Please reboot Y! slaves
Hi Rajiv -
The following Jenkins slave
Using google public dns should be fine.
Removed yahoo in colo resolver, 67.195.2.197 which is accessible from hosted
apache nodes. DHCPD configs is also updated to issue revolvers as
8.8.8.8/8.8.4.4 .
-rajive
From: Andrew Bayer
To: "builds@apache.org"
Cc: Keith
[
https://issues.apache.org/jira/browse/BUILDS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332470#comment-14332470
]
Rajiv Chittajallu commented on BUILDS-55:
-
lares and orcus were stuck with
[
https://issues.apache.org/jira/browse/BUILDS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332470#comment-14332470
]
Rajiv Chittajallu edited comment on BUILDS-55 at 2/23/15 1:3
[
https://issues.apache.org/jira/browse/BUILDS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312939#comment-14312939
]
Rajiv Chittajallu commented on BUILDS-55:
-
stuck in:
{noformat}
[11154983.52
[
https://issues.apache.org/jira/browse/BUILDS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312802#comment-14312802
]
Rajiv Chittajallu commented on BUILDS-55:
-
checking
> ssh connection fai
/etc/security/limits.conf is only used by pam_sessions. Limits are set for
processes, based on this configs, only if an session is initiated via a
process (login/sudo/ssh etc) that uses PAM. Processes started by upstart,
or manually (including root) would only inherit parent limits, what ever
that
David,
Ulimits are set on process startup. I think Jenkins slaves are started via
ssh, if PAM is used, pam_limits would set them based on
/etc/security/limits.conf. Host reboot is not required. For child process
should inherit parent by default.
Looking at sshd_config, UsePAM is no
---
#
12 matches
Mail list logo
