MX 3.9.1 build 3096 Errors

[astroed]

After installing build 3096 I'm getting a lot of errors (see below). I've attached the MXdiags folder.
Thanks, Ed

MXdiags.zip

Normal running
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'Renci.SshNet.SftpClient'.
at Renci.SshNet.BaseClient.CheckDisposed()
at Renci.SshNet.BaseClient.Disconnect()
at CumulusMX.Cumulus.DoFTPLogin()
at CumulusMX.Cumulus.DoHTMLFiles()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
Press Enter to terminate

[mcrossley]

OK, it shouldn't have done that, but it did recover from the error.

You seem to have a problem with your SFTP server, it keeps disconnecting the active session, then refusing the reconnection request. Looking at the last log file, the first time it happened, the server did eventually accept the connection and the SFTP worked again for a while. Then the sessions were disconnected by the server again and it refused all reconnection attempts until the end of the log file.

[astroed]

I have been having issues with my Internet Service Provider. My internet would go through periods when it suddenly lost connection, a few minutes (or seconds) later it would suddenly pop back on. This behavior would repeat throughout the day. This behavior has been an issue for several weeks and supposedly was fixed yesterday. This issue was not causing problems with Cumulus MX in prior builds. It wasn't until I updated to 3096 did the problem appear. I noticed the errors occurred again last night. As you indicated, most of the time it recovers.
Ed

[ConligWX]

just a guess, are you using the ftp user account for anything else other than cumulus?

[astroed]

Yes, I'm using GRLevel3 software to FTP radar images to my web site using the same user account.

[saratogaWX]

Make sure that both CumulusMX and GRLevel3 use passive FTP to your site. If you're using active FTP (port 21 only), then only one connection is allowed at a time.

[astroed]

I have passive FTP set for GRLevel3 and CumulusMX FTP is set to port 22 with the FTP protocol set to SFTP.
I experimented yesterday by closing GRLevel3 to stop it from uploading files. After 24 hours CumulusMX had generated two sets of errors which indicates GRLevel3 is not the issue. CumulusMX did recover from the errors and continued to upload files.

[mcrossley]

So GRLevel3 is using FTP and Cumulus is using SFTP (SSH file transfer). Two different protocols.

I don't know what else to say other than the remote server is disconnecting your sessions, then refusing the new connections when Cumulus tries to reconnect. After a while it accepts the connection and the transfers resume.

Can you try using good old slow FTP (or FTPS) for the uploads and see if that is any more stable?

[saratogaWX]

GRLevel3 can only do FTP (not SFTP nor FTPS). I agree with Mark, you should use FTP (port 21) Passive for both GRLevel3 and CumulusMX uploads.

[astroed]

When I tried both good old FTP and FTPS in CumulusMX, FTP stopped working. I now recalled that I was having FTP problems several months ago and had contacted my web hosting service (BlueHost). They had made some changes in their FTP requirements which I'm guessing were for security reasons. They had me modify the Cumulus FTP settings to port 22 and FTPS at which point FTP in CumulusMX started working again. It had been working fine until until I installed the latest CumulusMX build. Also, I don't see a way to the change port setting in GRlevel3. As I stated previously, GRlevel3 doesn't seem to be causing the issue since I disabled it for 24 hours and the CumulusMX errors still occasionally occurred.

I can live with this problem since it only occurs once or twice a day and connection is always reestablished after a brief delay. Let me know if there is anything else you want me to try.

Thanks everyone for helping me with this issue!

Ed