Closed
Bug 745102
Opened 13 years ago
Closed 13 years ago
seabld's key isn't properly set in symbolpush.mozilla.org from cn-sea-qm-win2k3-01.nl.mozilla.org
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: ewong, Assigned: Callek)
Details
In cn-sea-qm-win2k3-01.nl.mozilla.org, if I open a moz-build
prompt and do |ssh -l seabld symbolpush.mozilla.org|, I get the
following:
The authenticity of host 'symbolpush.mozilla.org (63.245.216.248)' can't be established.
RSA key fingerprint is a5:91:7c:be:5f:b2:3e:99:59:42:40:44:39:12:d4:49.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'symbolpush.mozilla.org,63.245.216.248' (RSA) to the
list of known hosts.
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
|
||
Updated•13 years ago
|
Assignee: server-ops → ashish
|
|
||
Updated•13 years ago
|
Severity: blocker → critical
|
|
||
Comment 1•13 years ago
|
||
I'm unable to access cn-sea-qm-win2k3-01.nl.mozilla.org via nl-vpn. Assigning to :Callek to investigate.
Assignee: ashish → bugspam.Callek
|
Assignee | |
Comment 2•13 years ago
|
||
This was a misnomer,
it WFM (and had seabld's buildbot console stuck asking us to accept the RSA key for the host)
I suspect that buildbt's issue, coupled with SeaMonkey's administrator account not having the seabld key in its .ssh folder (since ewong didn't use -i to try logging in) was the issue.
I restarted the host just now anyway.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
|
||
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•