Checked the log on my end and it appears that the initial login attempt was
successful:
Jul 20 06:27:44 sshd[2695]: Connection from 63.246.20.112 port 59463
Jul 20 06:27:47 sshd[2695]: Failed publickey for archiva from
63.246.20.112 port
59463 ssh2
Jul 20 06:27:47 sshd[2695]: Failed publickey for archiva from
63.246.20.112 port
59463 ssh2
Jul 20 06:27:47 sshd[2695]: Found matching DSA key:
e7:18:65:db:2a:22:b4:92:9d:c7:6a:a9:ae:1a:03:a8
Jul 20 06:27:47 sshd[2696]: Postponed publickey for archiva from 63.246.20.112
port 59463 ssh2
Jul 20 06:27:47 sshd[2695]: Found matching DSA key:
e7:18:65:db:2a:22:b4:92:9d:c7:6a:a9:ae:1a:03:a8
Jul 20 06:27:47 sshd[2695]: Accepted publickey for archiva from 63.246.20.112
port 59463 ssh2
Jul 20 06:27:47 sshd[2695]: pam_unix(sshd:session): session opened for user
archiva by (uid=0)
Jul 20 06:27:50 sshd[2697]: Connection closed by 63.246.20.112
Jul 20 06:27:50 sshd[2697]: Closing connection to 63.246.20.112
Jul 20 06:27:50 sshd[2695]: pam_unix(sshd:session): session closed for user
archiva
All subsequent attempts, however, are failing with the following log entry:
Jul 20 17:16:25 sshd[6615]: Connection from 63.246.20.112 port 37653
Jul 20 17:16:26 sshd[6615]: Invalid user archiva from 63.246.20.112
Jul 20 17:16:26 sshd[6616]: input_userauth_request: invalid user archiva
Jul 20 17:16:26 sshd[6616]: Connection closed by 63.246.20.112
Jul 20 21:24:26 sshd[8056]: Connection from 63.246.20.112 port 41556
Jul 20 21:24:27 sshd[8056]: Invalid user archiva from 63.246.20.112
Jul 20 21:24:27 sshd[8057]: input_userauth_request: invalid user archiva
Jul 20 21:24:27 sshd[8057]: Connection closed by 63.246.20.112
It appears as though the client deamon may be configured with a leading
space in
user name, i.e. " archiva"? How do we manage this from here, should I reopen
the original jira issue?
Todd
Quoting "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>:
--- Some repositories were not synchronized ---
groupId: org.bluestemsoftware
Error:
Permission denied (publickey,gssapi-with-mic).
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: unexplained error (code 255) at io.c(453) [receiver=2.6.9]
Error synchronizing metadata. Exit code: 255
groupId: org.parancoe
Error:
ssh: connect to host maven2.parancoe.org port 22: Connection refused
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at
io.c(453) [receiver=2.6.9]
Error synchronizing metadata. Exit code: 12
This is an automated email, do not respond.Contact the owners at
[email protected]
