8 Replies Latest reply on Oct 14, 2015 4:10 PM by lcarlson

    FTP Voyager Scheduler hangs when connecting to F5

    lcarlson

      I'm setting up the FTP Voyager Scheduler to download backup files from our F5's. It works on some, with this log message:

      [12] Tue 13Oct15 12:05:04 - (Task: f5-internal-01_backup) - Execution successfully completed.

       

      [07] Tue 13Oct15 12:05:07 - SSH_MSG_DISCONNECT: reason code 11; description: Disconnection initiated by user.

       

      But fails on 4 out of 6 with this log message:

       

      [07] Tue 13Oct15 14:05:48 - SSH_MSG_DISCONNECT: reason code 11; description: Disconnection initiated by user.

       


      [13] Tue 13Oct15 14:07:24 - (Action: "/var/local/ucs" to "C:\SFTP_Root\f5-internal-03") - Action was aborted.


      [12] Tue 13Oct15 14:07:24 - (Task: f5-internal-03_backup) - Execution was aborted.


      [07] Tue 13Oct15 14:07:24 - SSH_MSG_DISCONNECT: reason code 11; description: Disconnection initiated by user.

      The last message is from having to cancel the task, as it just sits at "Executing". The only difference is the F5 OS version, the ones that work are 11.2.0 and the ones that fail are 11.6.0, anyone see this before?

        • Re: FTP Voyager Scheduler hangs when connecting to F5
          josh.d

          Can you pull files normally (i.e. interactively) from all of them?

            • Re: FTP Voyager Scheduler hangs when connecting to F5
              josh.d

              Could this be related?:

               

              ID 223651An SSH File Transfer Protocol (SFTP) client might emit an error message containing 'Received message too long' when the user is unprivileged and may not use SFTP. This occurs when using a user with insufficient privileges uses SFTP. 'Received message too long' posted for SFTP client when the user is unprivileged. This is a known issue with SSH. For more information, see 2.9 - sftp/scp fails at connection, but ssh is OK, available here: http://www.openssh.com/faq.html#2.9. The user must be authorized to use SFTP/SCP.

               

              AskF5 | Release Note: BIG-IP LTM and TMOS 11.6.0

              • Re: FTP Voyager Scheduler hangs when connecting to F5
                lcarlson

                Yes, everything works fine using SFTP manually, just not with the Scheduler.

                  • Re: FTP Voyager Scheduler hangs when connecting to F5
                    lcarlson

                    Here is the latest log output, which has the "real path" statements, which the nodes that work never show:

                     

                    [07] Wed 14Oct15 06:51:31 - SSH_MSG_DISCONNECT: reason code 11; description: Disconnection initiated by user.

                     


                    [03] Wed 14Oct15 06:54:24 - Getting "real path" name to keep connection alive (KEEP ALIVE)


                    [07] Wed 14Oct15 06:54:24 - SSH_FXP_REALPATH: translating path: .


                    [08] Wed 14Oct15 06:54:24 - SSH_FXP_NAME: translated path: /root


                    [03] Wed 14Oct15 06:57:24 - Getting "real path" name to keep connection alive (KEEP ALIVE)


                    [07] Wed 14Oct15 06:57:24 - SSH_FXP_REALPATH: translating path: .


                    [08] Wed 14Oct15 06:57:24 - SSH_FXP_NAME: translated path: /root


                    [03] Wed 14Oct15 07:00:24 - Getting "real path" name to keep connection alive (KEEP ALIVE)


                    [07] Wed 14Oct15 07:00:24 - SSH_FXP_REALPATH: translating path: .


                    [08] Wed 14Oct15 07:00:24 - SSH_FXP_NAME: translated path: /root


                    [03] Wed 14Oct15 07:03:25 - Getting "real path" name to keep connection alive (KEEP ALIVE)


                    [07] Wed 14Oct15 07:03:25 - SSH_FXP_REALPATH: translating path: .


                    [08] Wed 14Oct15 07:03:25 - SSH_FXP_NAME: translated path: /root


                    [08] Wed 14Oct15 07:05:25 - SSH_MSG_DISCONNECT: reason code: 0; description: Timeout, your session not responding.


                    [04] Wed 14Oct15 07:05:25 - The server has unexpectedly closed the connection.

                     

                    At this point, the Scheduler sticks at "Executing" and never completes the task.