有人能解释一下为什么这个块读取操作会抛出一个EOFError吗?在我看来,当文件被完全读取时,它就会结束这个块。我遗漏了什么?我怎么才能修好它?非常感谢。
注意:我应该指出,有时它运行良好,而在其他情况下,它抛出EOFError。在同一位置的同一文件上.
Net::FTP.open(host=ftp.address, user='********', passwd='********') do |ftp|
ftp.passive = true
files = ftp.nlst('*')
s3 = Aws::S3::Resource.new(region: 'us-east-1')
files.each do |file|
ftp.getbinaryfile(file, file, 65536) # Copies file to /tmp
UpdateVfile.loader(@company, file) # Process file from /tmp
s3_file = file + Time.zone.now.strftime("-%Y-%m-%dT%H-%M.xls")
obj = s3.bucket('mydatafeed').object(s3_file) # Build object in S3 bucket
data = ''
ftp.getbinaryfile(file, nil, 65536) do |block| <== EOFError thrown here!
data << block
end
obj.put(body: data) # Write it to S3
ftp.delete(file) # Delete the file from FTP
end
end堆栈跟踪:
An EOFError occurred in background at 2015.11.23 :
end of file reached
/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/net/ftp.rb:1112:in `readline'
-------------------------------
Backtrace:
-------------------------------
/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/net/ftp.rb:1112:in `readline'
/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/net/ftp.rb:289:in `getline'
/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/net/ftp.rb:300:in `getmultiline'
/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/net/ftp.rb:318:in `getresp'
/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/net/ftp.rb:351:in `block in sendcmd'
/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize'
/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/net/ftp.rb:349:in `sendcmd'
/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/net/ftp.rb:394:in `makepasv'
/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/net/ftp.rb:406:in `transfercmd'
/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/net/ftp.rb:490:in `block (2 levels) in retrbinary'
/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/net/ftp.rb:199:in `with_binary'
/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/net/ftp.rb:488:in `block in retrbinary'
/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize'
/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/net/ftp.rb:487:in `retrbinary'
/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/net/ftp.rb:620:in `getbinaryfile'
/app/lib/tasks/updates_vfile.rake:40:in `block (6 levels) in <top (required)>'FTP debug_mode输出:
put: TYPE A
get: 200 Command TYPE okay.
put: PASV
get: 227 Entering Passive Mode (75,101,155,12,5,165)
put: NLST *
get: 150 File status okay; about to open data connection.
get: 226 Closing data connection.
put: TYPE I
get: 200 Command TYPE okay.
put: PASV
get: 227 Entering Passive Mode (75,101,155,12,5,163)
put: RETR <filename redacted>
get: 150 File status okay; about to open data connection.
get: 226 Transfer complete.
...output from update processing
put: PASV
rake aborted!
EOFError: end of file reached发布于 2015-11-23 21:32:20
结果发现问题是FTP空闲超时。因为UpdateVfile.loader是一项长期运行的任务,所以我将FTP单独放置了太长时间,并且它使用了一个EOFError。显然,一个超时错误会比这样一个无法描述的错误要好得多,因为它给了我比没有诊断信息更糟糕的信息。
如果装载机是短的,它就能工作。对于更强烈的更新,它花了太长时间。当我更改源代码以尝试诊断和解决问题时,EOFError转移到了ftp.delete命令,这对我来说更没有意义。
我发现一些讨论暗示了这个问题。因此,在调用加载程序之前,我更改了流程以处理所有FTP工作。这是可靠的。否则,我要么必须发送定期的“保持生命”,要么找到一种修改超时时间的方法。这两件事似乎都不容易实现。
如果有人能向我解释一下为什么FTP会发出EOFError而不是超时错误,我会很高兴。这是不对的,从诊断上来说,这会把任何人引向完全错误的方向。谢谢..。
https://stackoverflow.com/questions/33872354
复制相似问题