From: Miklos S. <mi...@sz...> - 2007-11-19 11:40:43
|
> I am trying to find a solution for a problem we have delivering large > files to vendors. The problem is, we use AWS - EC2 to package up are > files -- wich can range from 10 - 40GB -- then they go to a bridged > server that connects to our vendors. Unfortunately, AWS does not offer > static IP's, and our vendors require an IP to allow us access through > the FW. > > I decided to give SSHFS a shot.. and it seems to work fine, except it > randomly hangs. Is it possible that it's just a server variable I'm > missing in the ssh config? Or is this just a dumb thing to do > entirely. > > To recap a bit, my AWS instances build these large packages, and push > them to my bridged server which I have mounted to our vendors file > system via sshfs. > > Here is a list of my setup. > > OS - RHEL4 > KERNEL - 2.6.9-55.ELsmp #1 SMP x86_64 > > SSHFS version 1.8 > FUSE library version: 2.7.1 > fusermount version: 2.7.1 > using FUSE kernel interface version 7.8 > > > On the AWS side, in the ssh_config I do have ServerAliveInterval 15 as > well as on my bridged server. Very interesting. This is not a known issue, although there have been reports of similar hangs, which we didn't manage to track down completely. Can you help with debugging this? It might take a few iterations. The first thing to try is to enable debugging in the sshfs client with: sshfs -odebug,sshfs_debug ... 2> /tmp/sshfs.log The other thing is, IIRC sftp-server was suspected to play a part in these hangs. So a strace might be useful. After mounting sshfs on the client you can start strace on the sever: strace -o /tmp/sftp-server.strace -p `pidof sftp-server` Thanks, Miklos |