SFTP CL 5.8 File size Issue??

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf SFTP CL 5.8 File size Issue??

  • Creator
    Topic
  • #52800
    Mike Wilson
    Participant

      I am trying to use the built in SFTP protocol in CL 5.8.  I have been successful sending single HL7 messages.  I need to write the entire days messages out to a file and then send it at the end of day.  If I do this I get:

      “Detailed error:Failed sending data to the peer Curl errCode:55 Curl error: Failed sending data to the peer”.  

      The file is about 1MB.  If I cut the file down to under 15K it sends with no problem…..  Anybody have any ideas or experience with this?  

      Thanks in Advance!

    Viewing 12 reply threads
    • Author
      Replies
      • #75505
        Mike Wilson
        Participant

          Update:  The vendor is using MOVEit DMZ…

        • #75506
          Jim Kosloskey
          Participant

            Mike,

            If you do SFTP from the command line can you send the large file?

            If not, perhaps he other side is limiting the file size.

            email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

          • #75507
            Mike Wilson
            Participant

              I should have said that earlier.  I can send Large files to the other side with other SFTP clients..  just not the CL built in.

            • #75508
              Mike Wilson
              Participant

                I also did the send from the command line using curl and I got the same message as I did in the engine.

              • #75509
                Jim Kosloskey
                Participant

                  Mike,

                  If you turn up the engine noise is there more information in the process log?

                  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

                • #75510
                  Mike Wilson
                  Participant

                    I turned the EOconfig all the way up and the only relevant part I can find is:

                    About to connect() to 139.177.214.97 port 22 (#0)

                    *   Trying 139.177.214.97… * connected

                    * Connected to 139.177.214.97 (139.177.214.97) port 22 (#0)

                    * SSH authentication methods available: publickey,password

                    * Using ssh public key file C:Usershciuser/.ssh/id_dsa.pub

                    * Using ssh private key file C:Usershciuser/.ssh/id_dsa

                    * SSH public key authentication failed: Unable to open public key file

                    * Initialized password authentication

                    * Authentication complete

                    * Sending quote commands

                    * rm command failed: No such file or directory

                    * Connection #0 to host 139.177.214.97 left intact

                    [pd  :pdtd:INFO/1:mckesson_sftp_brmc:11/11/2011 16:06:25] Set driver status to PD_STATUS_UP

                    [fset:init:DBUG/0:mckesson_sftp_brmc:11/11/2011 16:06:25] fcDoNetworkStuff:  mode=5

                    * About to connect() to 139.177.214.97 port 22 (#0)

                    *   Trying 139.177.214.97… * connected

                    * Connected to 139.177.214.97 (139.177.214.97) port 22 (#0)

                    * SSH authentication methods available: publickey,password

                    * Using ssh public key file C:Usershciuser/.ssh/id_dsa.pub

                    * Using ssh private key file C:Usershciuser/.ssh/id_dsa

                    * SSH public key authentication failed: Unable to open public key file

                    * Initialized password authentication

                    * Authentication complete

                    * Closing connection #0

                    * Failed sending data to the peer

                    [fset:wrte:ERR /0:mckesson_sftp_brmc:11/11/2011 16:06:27] Error while trying to write bradfordADT.hl7.

                                            Detailed error:Failed sending data to the peer

                                              Curl errCode:55 Curl error: Failed sending data to the peer

                    [pd  :pdtd:INFO/1:mckesson_sftp_brmc:11/11/2011 16:06:27] Set driver status to PD_STATUS_OPENING

                    [pd  :pdtd:INFO/1:mckesson_sftp_brmc:11/11/2011 16:06:29] Set driver status to PD_STATUS_ERROR

                    [pd  :pdtd:INFO/1:mckesson_sftp_brmc:11/11/2011 16:06:29] [0.0.8075314] Writing message failed

                  • #75511
                    Jim Kosloskey
                    Participant

                      Mike,

                      Does the highlighted entry from the log look like an issue?

                      * Using ssh private key file C:Usershciuser/.ssh/id_dsa

                      <span style="color: red]* SSH public key authentication failed”>

                      * Initialized password authentication

                      * Authentication complete

                      * Closing connection #0

                      * Failed sending data to the peer

                      email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

                    • #75512
                      Mike Wilson
                      Participant

                        Jim,

                        I dont think authentication is an issue.  I dont have any keys installed.  Just username and password authentication which is working.  If  that was a problem I would think I couldnt send any files.. which is not the case.

                      • #75513
                        Kevin Scantlan
                        Participant

                          When you send the sftp manually, are you manually typing in the password?  I know that if you want to do sftp from a script without it prompting for a password, you must user public/private key authentication.  That may be the same from CL 5.8 .

                        • #75514
                          Mike Wilson
                          Participant

                            Guys,

                            If authentication was an issue I would think I couldnt send any files at all.  I can send some files..

                            Mike

                          • #75515
                            Jim Kosloskey
                            Participant

                              Mike,

                              Since I am not on 5.8 unfortunately I cannot experiment to help you.

                              email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

                            • #75516
                              Kevin Scantlan
                              Participant

                                If I manually type in “sftp” with userid and IP address, sftp will first try to authenticate using a public/private key match.  It will do RSA type first, then look for DSA.  If it cannot authenticate (keys don’t match or don’t exist), will then prompt for a password to be manually inputed (authentication via a password).  When I write a script and use sftp, I must use key authentication since there is no way using sftp to automatically have the password inputed.  

                                I do not know how CL5.8 works, but I suspect it works in the same fashion as using a script.

                                You would be able to send files manually via sftp using a password, but you may not be able to use Cloverleaf without key authentication.

                                Anyway, that’s my best guess w/o knowing CL5.8 .

                              • #75517
                                David Barr
                                Participant

                                  Kevin Scantlan wrote:

                                  When I write a script and use sftp, I must use key authentication since there is no way using sftp to automatically have the password inputed.

                              Viewing 12 reply threads
                              • The forum ‘Cloverleaf’ is closed to new topics and replies.