Sorry,
it's dead again. So fixing the stuck slave is up to ASF INFRA. Maybe its
something like wrong Java version. Without any logfiles its impossible
to guess.
Uwe
Am 26.06.2024 um 22:39 schrieb Uwe Schindler:
Hi,
looks like killing the stuck slave process ("sudo pkill -9 -u
jenkins") helped lucene-solr-2 to recover.
Uwe
Am 26.06.2024 um 16:30 schrieb Jason Gerlowski:
Hi Uwe
Thanks for the context! A few follow-up questions for you (or anyone
else that can answer):
1. What's the hostname for lucene-solr-1? Maybe my Jenkins knowledge
is lacking, but I can't find the full hostname exposed anywhere in
Jenkins, and I'd like to try SSH-ing in. (I'm hoping it might "just
work" as I have a SSH key set up through id.apache.org and am on the
Lucene PMC.)
2. AFAICT from its page in Jenkins
(https://ci-builds.apache.org/computer/lucene%2Dsolr%2D2/),
lucene-solr-2 has been "down" for some time. Does anyone know why
this is?
3. Is there a particular reason why we have project-managed VMs,
instead of using INFRA-managed nodes?
4. You mention that the VMs are only owned by the Lucene PMC. Is that
mostly a historical accident (i.e. because the Solr PMC didn't
technically exist at the time the VMs were created)? Or is there some
conceptual reason the VMs should continue to be owned by Lucene PMC
only?
Best,
Jason
On Wed, Jun 26, 2024 at 5:30 AM Uwe Schindler <u...@thetaphi.de> wrote:
Hi,
yes e.g., I have access to that machine and can issue a reboot. The two
machines are VMs specifically owned by the Lucene PMC (not Solr as far
as I remeber), but they were created before the split of projects.
Some people have direct access, not sure how this is managed. Basically
to get access you need to place a SSH key in id.apache.org -- and I
think you need to be in the correct PMC.
P.S.: I sometimes also run "apt update && apt dist-upgrade" to keep it
uptodate (but not recently).
Uwe
Am 25.06.2024 um 20:20 schrieb Jason Gerlowski:
Hey all,
Sending this email to discuss the ASF Jenkins' 'lucene-solr-1' worker
node, which both Lucene and Solr use to run builds.
While investigating a recent issue with some Solr builds, I asked
INFRA to restart 'lucene-solr-1'. They were happy to oblige (and I'm
now unblocked), but in the process they mentioned that 'lucene-solr-1'
was a "project run VM" and that someone in the project should have the
requisite access and permissions. [1] [2]
This was all a surprise to me, so I wanted to follow up here with a
few questions.
1. Is it true that our projects run or manage this VM in some way?
2. If so, does anyone remember the context around how or why this came
about? (As opposed to using one of the "standard" Jenkins build
machines that INFRA provides...)
3. Who all can access the box? How are credentials managed? (My
suspicion is that no one currently active on the Solr lists is able to
access the box, which seems worth remedying...)
Best,
Jason
[1] https://lists.apache.org/thread/g0y0ohczdctv0v5fn8sqv4t0j4y6hp68
[2] https://the-asf.slack.com/archives/CBX4TSBQ8/p1719318685682309
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
