Hi Daniel, lsst-dbdev2 was reinstalled recently after the system disk crash, I guess this explains new host key. I have impression that they tried to restore user home directories from failed disk, but some files/directories could be unreadable, so your ~/.ssh directory may be gone now. I looked at user's directories and all of them have .ssh dirs except for you (bad luck I guess). lsst-dbdev6 had issues with the disk as well mid-December, I notified sysadmins but have not heard anything since then, it could have been rebuilt as well if you see new host key. lsst-dbdev1 rejects me too, not sure what's going on there. Cheers, Andy Daniel L. Wang wrote on 2015-01-05: > Hey there, > > I'm having some issues logging into some of the lsst-dbdev machines we > are using at NCSA and was wondering if any of you had the same issues or > had performed some "maintenance" that others should know about. > > Specifically, > lsst-dbdev1 : rejects my SSH public key > lsst-dbdev2 : rejects my SSH public key, and has an unrecognized (new?) > host key > lsst-dbdev{3,4,5} : these work fine. > lsst-dbdev6 : accepts my SSH public key, but has an unrecognized (new?) > host key > > Any ideas? I sent an email to the sysadmins at ncsa about it, but if you > know of something, then perhaps they don't need to look into it. > > Thanks, > -Daniel > > ######################################################################## > Use REPLY-ALL to reply to list > > To unsubscribe from the QSERV-L list, click the following link: > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the QSERV-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1