Hi Nick, Thanks a lot for your reply. What you say makes sense. Even a long time after the file transfer has finished, I cannot connect to the server. One conclusion would be that the operation might have crashed both SSH and SNMP. Guess, I should make sure that SSH and SNMP are monitored and use a less resource-hungry way of transferring the files.
sam On Jun 30, 12:29 pm, Nickolas Toursky <[email protected]> wrote: > HiSam, > > Most likely, SSH and SNMP were locked out due to high server load > since transferring files using scp is a resource-hungry operation. > Try using '-l' option to limit transfer bandwidth or choose another > way to transfer file. > > Nick > > > > On Fri, Jun 26, 2009 at 10:08 PM,SamZurcher<[email protected]> wrote: > > > Hi guys, > > > On a custom x86_64 role, I have been running into the problem that > > both SSH and SNMP stop working although I can ping the machine. The > > only way to get access to the machine is to issue the reboot command. > > From the analysis of the scalr log files, it looks like SSH and SNMP > > stop working while I'm transferring a file of more than 600MB using > > scp. > > > Has anybody experienced failure of SSH and SNMP? If so, have you > > related the failure to the transfer of a file with scp? Or have you > > found a different reason? > > > Best, > >sam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
