任务单 #38037

without acces with rsync

开放日期: 2018-03-13 11:22 最后更新: 2020-11-25 08:18

报告人:
属主:
类型:
状态:
关闭
里程碑:
(无)
优先:
9 - Highest
严重性:
9 - Highest
处理结果:
Fixed
文件:
Vote
Score: 1
100.0% (1/1)
0.0% (0/1)

Details

Hi, I already generated my sshkey and put in account in osdn; but running rsync, scp, and sftp; i do not have acces... "Connection closed by 210.128.165.62 port 22"

任务单历史 (3/14 Histories)

2018-03-13 11:22 Updated by: davidva
  • New Ticket "without acces with rsync" created
2018-03-13 12:26 Updated by: sugi
评论

Hello,

I connot find your access from server logs. Would you please run following command and paste the output?

ssh -vvv davidva@storage.osdn.net
2018-03-13 13:37 Updated by: sugi
评论

Thank you!

Hmm... It seems the connection closed unexpectedly before recieving server publickey. It may be hard to investigate.

I have increase log level to max on server side temporarily. Would you please try again and tell the time you run the command to me?

I'm sorry for bothering you.

2018-03-13 16:09 Updated by: sugi
评论

Thank you.

I have checked server log. On server side, your connection just seems to be closed by client.

In this case, it's hard to identify the cause. At present, I can just suggest you to connect from another host or network.

BTW, can you connect to another host on OSDN?

Please try with shell server;

ssh davidva@shell.osdn.net

If you can connect to shell server, rsync files to shell server, then rsync again to storage server from shell sever with *ssh agent forwarding* (or, set new key pair to copy between shell server to storage server).

2018-03-14 03:57 Updated by: davidva
评论

Reply To sugi

Thank you. I have checked server log. On server side, your connection just seems to be closed by client. In this case, it's hard to identify the cause. At present, I can just suggest you to connect from another host or network. BTW, can you connect to another host on OSDN? Please try with shell server; {{{ ssh davidva@shell.osdn.net }}} If you can connect to shell server, rsync files to shell server, then rsync again to storage server from shell sever with *ssh agent forwarding* (or, set new key pair to copy between shell server to storage server).

Well, I can connect to shell server; also I made new ssh keys, but...

ssh-keygen -t rsa

ssh-keygen -t dsa

ssh-keygen -t ecdsa

ssh-keygen -f ~/.ssh/identity

Now, I can make directories, but I can't upload nothing...

My test...

Now with "ssh -vvv davidva@storage.osdn.net"

https://gist.githubusercontent.com/kuboosoft/feb52cb216663e1c7daf8c63447dbd55/raw/b2539478ed4e9d337020075fb2c17c2583d40b1c/log3

(Edited, 2018-03-14 10:49 Updated by: davidva)
2018-03-14 12:43 Updated by: sugi
评论

Please test with rsync to shell.osdn.net by following command?

rsync -av  /some/sorce/path davidva@shell.osdn.net:transfer-test/

In our system, shell.osdn.net and storage.osdn.net uses different network.

If you success to transfer for shell and fail for storage, the problem likely to be caused by our network connected with storage server.

If you fail to send files to both server in similar error, your ISP or network path may be something wrong, maybe.

(Edited, 2018-03-14 12:44 Updated by: sugi)
2018-03-14 13:18 Updated by: sugi
评论

No problem. It's correct behavior that fails to write "transfer-test/" on storage server. (Use davidva@storage.osdn.net:/storage/groups/u/un/unitedrpms/29/x86_64/ for storage.)

Anyway, your transfer for shell server is success...

Would you please try again with stoarge server in current condition?

rsync -av x86_64/ davidva@storage.osdn.net:/storage/groups/u/un/unitedrpms/29/x86_64/

2018-03-14 14:15 Updated by: None
评论

Reply To sugi

No problem. It's correct behavior that fails to write "transfer-test/" on storage server. (Use davidva@storage.osdn.net:/storage/groups/u/un/unitedrpms/29/x86_64/ for storage.) Anyway, your transfer for shell server is success... Would you please try again with stoarge server in current condition? {{{ rsync -av x86_64/ davidva@storage.osdn.net:/storage/groups/u/un/unitedrpms/29/x86_64/ }}}

Ok, same "broken pipe" ...

https://gist.githubusercontent.com/kuboosoft/4f25c877f7caf8070e0fd351f373635e/raw/b3d5f708f7a2a691c7589e2c801b5d0e9ef5de6e/log6

2018-03-14 15:53 Updated by: sugi
评论

OK, Thanks.

I prepared new route to connect storage server for now.

Please use another host name "storage-in.osdn.net" (instead of storage.osdn.net) like

rsync -av x86_64/ davidva@storage-in.osdn.net:/storage/groups/u/un/unitedrpms/29/x86_64/

When you connect with new name "storage-in.osdn.net", you will use same network as shell server which seems have no problem, currently.

We may switch storage server's netwrok in future.

Anyway, please try with "storage-in.osdn.net".

2018-03-14 17:03 Updated by: davidva
评论

Thanks thanks very much! @sugi with the change to "storage-in.osdn.net" works without problem :)

https://gist.githubusercontent.com/kuboosoft/95b2814abfe515ef08344481f219ac41/raw/95b60058a52c9499b47ce230543c09b08786254a/log7

Please give us updates with the changes in future, thank you very much for your patience :)

2020-11-25 08:18 Updated by: sado
  • 处理结果 Update from to Fixed
  • 状态 Update from 开启 to 关闭

Attachment File List

No attachments

编辑

You are not logged in. I you are not logged in, your comment will be treated as an anonymous post. » 登录名