From pierre at freepascal.org  Sun Aug 31 09:05:21 2025
From: pierre at freepascal.org (Pierre Muller)
Date: Sun, 31 Aug 2025 09:05:21 +0200
Subject: Unable to access unstable10s and unstable10x on login.opencsw.org
 test machine
Message-ID: <f1dfefd8-bb4b-408e-949c-0d4e9c7e7bf2@freepascal.org>

   Hi,

   I am unable to ssh into unstable10x or unstable10s
from login.opencsw.org into which I can ssh without trouble.

   According to time stamps inside my logs directory,
it seems that this access stopped working around August 21.
as the corn job I use to test Free Pascal on Solaris
uses also this ssh access to run a script on those machines.

   Could someone please try to look into this issue?

Thanks in advance,

Pierre Muller
Free Pascal core team member

From dam at opencsw.org  Sun Aug 31 12:04:59 2025
From: dam at opencsw.org (Dagobert Michelsen)
Date: Sun, 31 Aug 2025 12:04:59 +0200
Subject: Unable to access unstable10s and unstable10x on login.opencsw.org
 test machine
In-Reply-To: <f1dfefd8-bb4b-408e-949c-0d4e9c7e7bf2@freepascal.org>
References: <f1dfefd8-bb4b-408e-949c-0d4e9c7e7bf2@freepascal.org>
Message-ID: <EABBFFE8-E5D3-4278-AA2A-47A1B99BEBFF@opencsw.org>

Hi Pierre,

> Am 31.08.2025 um 09:05 schrieb Pierre Muller via buildfarm <buildfarm at lists.opencsw.org>:
>  I am unable to ssh into unstable10x or unstable10s
> from login.opencsw.org into which I can ssh without trouble.
> 
>  According to time stamps inside my logs directory,
> it seems that this access stopped working around August 21.
> as the corn job I use to test Free Pascal on Solaris
> uses also this ssh access to run a script on those machines.
> 
>  Could someone please try to look into this issue?


The home directory is NFS mounted on all machine, the default connfiguration is that you have a local
ssh private key in .ssh and the public key in authorized keys and then it should work immediately.
I would suspect your ssh configuration on login which looks mighty complex to me and I don?t want
to tinker with that. SSH is trying to use id_ed25519 which seems not be in your authorized_keys.
If you have further troubles please let me know.


Best regards

  ? Dago

-- 
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.opencsw.org/pipermail/buildfarm/attachments/20250831/ee83831c/attachment-0001.html>

From pierre at freepascal.org  Sun Aug 31 22:39:51 2025
From: pierre at freepascal.org (Pierre Muller)
Date: Sun, 31 Aug 2025 22:39:51 +0200
Subject: Unable to access unstable10s and unstable10x on login.opencsw.org
 test machine
In-Reply-To: <EABBFFE8-E5D3-4278-AA2A-47A1B99BEBFF@opencsw.org>
References: <f1dfefd8-bb4b-408e-949c-0d4e9c7e7bf2@freepascal.org>
 <EABBFFE8-E5D3-4278-AA2A-47A1B99BEBFF@opencsw.org>
Message-ID: <7a06685c-850c-45c9-a834-244970428044@freepascal.org>



Le 31/08/2025 ? 12:04, Dagobert Michelsen a ?crit?:
> Hi Pierre,
> 
>> Am 31.08.2025 um 09:05 schrieb Pierre Muller via buildfarm <buildfarm at lists.opencsw.org>:
>> ?I am unable to ssh into unstable10x or unstable10s
>> from login.opencsw.org into which I can ssh without trouble.
>>
>> ?According to time stamps inside my logs directory,
>> it seems that this access stopped working around August 21.
>> as the corn job I use to test Free Pascal on Solaris
>> uses also this ssh access to run a script on those machines.
>>
>> ?Could someone please try to look into this issue?
> 
> The home directory is NFS mounted on all machine, the default connfiguration is that you have a local
> ssh private key in .ssh and the public key in authorized keys and then it should work immediately.
> I would suspect your ssh configuration on login which looks mighty complex to me and I don?t want
> to tinker with that. SSH is trying to use?id_ed25519 which seems not be in your authorized_keys.
> If you have further troubles please let me know.

  You are completely right, this is completely my own fault...

   I modified the ~/.ssh/config file,
and didn't add the needed entries for the unstableXYZ machines...

Thank you and sorry for the noise,

Pierre