Reading file from SFTP server using Node.js and SSH2

前端 未结 2 1376
不知归路
不知归路 2021-02-20 05:41

I have a pretty strange problem working with read streams in Node.js. I\'m using SSH2 to create a sftp connection between me and a sftp server. I then try to create a read strea

相关标签:
2条回答
  • 2021-02-20 05:59

    If the byte size (or chunk size) is not mandatory and you just need to get the file, guess there is a much better lighter-and-faster way (yeah...the nodejs way!). This is how I use to copy a file:

    function getFile(remoteFile, localFile) {
         conn.on('ready', function () {
         conn.sftp(function (err, sftp) {
             if (err) throw err;
             var rstream = sftp.createReadStream(remoteFile);
             var wstream = fs.createWriteStream(localFile);
             rstream.pipe(wstream);
             rstream.on('error', function (err) { // To handle remote file issues
                 console.log(err.message);
                 conn.end();
                 rstream.destroy();
                 wstream.destroy();
             });
             rstream.on('end', function () {
                 conn.end();
             });
             wstream.on('finish', function () {
                 console.log(`${remoteFile} has successfully download to ${localFile}!`);
             });
         });
       }).connect(m_ssh2Credentials);
    }
    

    As an alternative, you can also try sftp.fastGet() which uses parallel reads to bring the file quickly. fastGet() provides you a way to show the progress of the download (if wanted) apart from giving a way to configure the number of parallel reads and chunk size. To know more, open this SFTPStream doc and search for fastGet.

    Here is a very quick code:

    sftp.fastGet(remoteFile, localFile, function (err) {
        if (err) throw err;
        console.log(`${remoteFile} has successfully download to ${localFile}!`);
    }
    

    HIH!

    0 讨论(0)
  • 2021-02-20 06:05

    So after a lot of investigation I finally realized that there was something wrong with the last bits of data that was transmitted in the 'data' event. From my understanding it seems to be a bug in the implementation of the read stream. I was able to get around this problem by using the more simplistic functions (open, fstat, read) in the SSH2 library. This solution works for me. Wanted to share the solution if someone else comes across the same problem.

    Working code:

    sftp.open(config.ftpPath + "/" + m_fileName, "r", function(err, fd) {
    sftp.fstat(fd, function(err, stats) {
        var bufferSize = stats.size,
            chunkSize = 16384,
            buffer = new Buffer(bufferSize),
            bytesRead = 0,
            errorOccured = false;
    
        while (bytesRead < bufferSize && !errorOccured) {
            if ((bytesRead + chunkSize) > bufferSize) {
                chunkSize = (bufferSize - bytesRead);
            }
            sftp.read(fd, buffer, bytesRead, chunkSize, bytesRead, callbackFunc);
            bytesRead += chunkSize;
        }
    
        var totalBytesRead = 0;
        function callbackFunc(err, bytesRead, buf, pos) {
            if(err) {
                writeToErrorLog("downloadFile(): Error retrieving the file.");
                errorOccured = true;
                sftp.close(fd);
            }
            totalBytesRead += bytesRead;
            data.push(buf);
            if(totalBytesRead === bufferSize) {
                m_fileBuffer = Buffer.concat(data);
                writeToLog("downloadFile(): File saved to buffer.");
                sftp.close(fd);
                m_eventEmitter.emit(' downloadFile_Completed ');
            }
        }
    })
    });   
    
    0 讨论(0)
提交回复
热议问题