Heroku / Rails3: Heroku db:pull --> 内部服务器错误。为什么？答案

【问题标题】：Heroku / Rails3: Heroku db:pull --> Internal Server Error. Why?Heroku / Rails3: Heroku db:pull --> 内部服务器错误。为什么？
【发布时间】：2011-01-27 17:04:39
【问题描述】：

我不是特别擅长描述应用程序部署过程。（我更像是一名编码员而不是系统管理员）。但是，在将新代码推送到 Heroku 并运行数据库迁移之前，我确实需要将 Heroku 部署中的数据库备份到本地计算机。所以，我正在尝试运行 heroku db:pull。当我这样做时，我收到以下内部服务器错误：

C:\Users\Morris\railsdev[[应用程序]]>heroku db:pull

Loaded Taps v0.3.14
Auto-detected local database: sqlite://db/development.sqlite3
Warning: Data in the database 'sqlite://db/development.sqlite3' will be overwritten and will not be recoverable.
Are you sure you wish to continue? (y/n)? y
 !   Internal server error

所以，我检查了日志以获取回溯。这是我得到的：


==> cron-4139529.log (crash) 
/usr/ruby1.8.7/lib/ruby/1.8/rexml/parsers/baseparser.rb:330:in `pull'
/usr/ruby1.8.7/lib/ruby/1.8/rexml/parsers/treeparser.rb:22:in `parse'
/usr/ruby1.8.7/lib/ruby/1.8/rexml/document.rb:227:in `build'
/usr/ruby1.8.7/lib/ruby/1.8/rexml/document.rb:43:in `initialize'
/disk1/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8
/gems/xml-simple-1.0.12/lib/xmlsimple.rb:959:in `new'
/disk1/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8
/gems/xml-simple-1.0.12/lib/xmlsimple.rb:959:in `parse'
/disk1/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8
/gems/xml-simple-1.0.12/lib/xmlsimple.rb:164:in `xml_in'
/disk1/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8
/gems/xml-simple-1.0.12/lib/xmlsimple.rb:203:in `xml_in'
/disk1/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8
/bundler/gems/tumblr-oauth-baa3f24a267c/lib/tumblr/request.rb:52:in `authenticat
e'
/disk1/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8
/bundler/gems/tumblr-oauth-baa3f24a267c/lib/tumblr/user.rb:10:in `initialize'
/disk1/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/app/models/tumblog.rb
:181:in `new'
/disk1/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/app/models/tumblog.rb
:181:in `update_followers'
/disk1/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/app/models/tumblog.rb
:178:in `each'
/disk1/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/app/models/tumblog.rb
:178:in `update_followers'
/disk1/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/Rakefile:11
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/lib/rake.rb:636:in `call'
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/lib/rake.rb:636:in `execute'
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/lib/rake.rb:631:in `each'
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/lib/rake.rb:631:in `execute'
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain'
/usr/ruby1.8.7/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/lib/rake.rb:583:in `invoke'
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/lib/rake.rb:2051:in `invoke_task'
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/lib/rake.rb:2029:in `top_level'
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/lib/rake.rb:2029:in `each'
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/lib/rake.rb:2029:in `top_level'
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/lib/rake.rb:2023:in `top_level'
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/lib/rake.rb:2001:in `run'
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/lib/rake.rb:1998:in `run'
/home/slugs/804b0fd8-de4e-44aa-9961-75f718fcf3d8/mnt/.bundle/gems/ruby/1.8/gems/
rake-0.8.7/bin/rake:31
/usr/ruby1.8.7/bin/rake:19:in `load'
/usr/ruby1.8.7/bin/rake:19
...
Missing end tag for 'link' (got "head")
Line:
Position:
Last 80 unconsumed characters:
      Your application crashed.

       Examine the backtrace above this message to debug.

我应该注意到，应用程序在服务器（和本地）上运行良好，可以通过 Web 浏览器访问。有谁知道为什么我无法提取我的数据库？

【问题讨论】：

我现在已经在 Heroku 的帮助下回答了这个问题。有时候你不能责怪自己。问题出在他们头上。

标签： ruby-on-rails heroku rake

【解决方案1】：

db:pull 对于大型数据集真的很慢。只是为了将来参考，您可能希望查看他们的 pgbackups 以从 Postgres 数据库中捕获转储，而不是像 db:pull 那样逐条传输记录：

$ heroku pgbackups:capture

【讨论】：