Re: Database importing very slow
Thanks for replying. Yes, taps is the latest version. Initially it wouldn't work because of a known issue with Ruby 1.9.1 but it works fine when I used 1.8.7. The taps version number is 0.3.9. The database has 11 tables all of which were generated according to Rails defaults and as such all have an integer primary key. I also confirmed this through directly querying the database in postgres. My database eventually uploaded overnight taking 8 hours (~0.5 kbps!). After uploading my app didn't work so I suspect it didn't upload properly (although I can't prove this). Perhaps I'll try Heroku support directly. On Jun 25, 4:34 am, Oren Teich o...@heroku.com wrote: Are you running the latest version of taps (sudo gem update taps)? Is the primary key on your table an integer? http://blog.heroku.com/archives/2010/4/21/supporting_big_data_part_1/ On Thu, Jun 24, 2010 at 4:25 AM, Brad oconnor.b...@gmail.com wrote: Oops, I didn't say how slow. So far it's been 2 hours. It looks like it'll be at least another hour. On Jun 24, 9:23 pm, Brad oconnor.b...@gmail.com wrote: I'm trying to upload my development database to my heroku app (via heroku db:push) but finding it very slow. My database is not huge - 11 tables, about 57000 records, 13MB diskspace but is taking hours to upload. I don't even know where to start with investigating this. The connection at my end is fine for any other activities. Surely heroku can't be this slow. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Can't use memcache with my application
I'm not sure if this is a related issue or not, but heroku have an example
app of Rails 3b4 with memcached here:
http://github.com/heroku-examples/r3b4-memcache-heroku
However, if we flip it to memcached-northscale we start seeing :
/Users/neil/Dropbox/code/r3b4-memcache-heroku/config/environments/production.rb:29:
uninitialized constant Memcached (NameError)
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application.rb:55:in
`class_eval'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application.rb:55:in
`configure'
from
/Users/neil/Dropbox/code/r3b4-memcache-heroku/config/environments/production.rb:1
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application/bootstrap.rb:10:in
`require'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application/bootstrap.rb:10
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/initializable.rb:25:in
`instance_exec'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/initializable.rb:25:in
`run'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/initializable.rb:55:in
`run_initializers'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/initializable.rb:54:in
`each'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/initializable.rb:54:in
`run_initializers'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application.rb:119:in
`initialize!'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application.rb:81:in
`send'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application.rb:81:in
`method_missing'
from /Users/neil/Dropbox/code/r3b4-memcache-heroku/config/environment.rb:5
from config.ru:3:in `require'
from config.ru:3
from /Library/Ruby/Gems/1.8/gems/rack-1.1.0/lib/rack/builder.rb:46:in
`instance_eval'
from /Library/Ruby/Gems/1.8/gems/rack-1.1.0/lib/rack/builder.rb:46:in
`initialize'
from config.ru:1:in `new'
from config.ru:1
This might be a non-issue, but we thought it worth pointing out differences
between the two gems.
Neil
On Thu, Jun 24, 2010 at 5:39 PM, Sean Lynch se...@literati.org wrote:
Hi, Eki.
This is a side-effect of Fauna's throwing exceptions for errors that would
just show up as misses in memcache-client. I've fixed this and it's in
testing in a gem called memcached-northscale. You still use require
'Memcached', just use memcached-northscale instead of memcached in your
gem.
Once I get feedback that it a) solves the problem and b) doesn't cause
other problems, I'll get it incorporated into Fauna.
Thanks!
-Sean
On Jun 24, 2010, at 3:46 AM, Eki wrote:
Hi guys ,
I'm trying to use memcached with my application , I followed the
official instructions to do so but still not working ,
the error msg is something like this :
Memcached::ServerIsMarkedDead (Key
{country_x_y_z=127.0.0.1:11211:8}):
memcached (0.19.7) lib/memcached/memcached.rb:609:in
`check_return_code'
memcached (0.19.7) lib/memcached/memcached.rb:515:in `get'
memcached (0.19.7) lib/memcached/rails.rb:39:in `get'
app/controllers/prayer_times_controller.rb:9:in `index'
/home/heroku_rack/lib/static_assets.rb:9:in `call'
/home/heroku_rack/lib/last_access.rb:25:in `call'
/home/heroku_rack/lib/date_header.rb:14:in `call'
thin (1.0.1) lib/thin/connection.rb:80:in `pre_process'
thin (1.0.1) lib/thin/connection.rb:78:in `catch'
thin (1.0.1) lib/thin/connection.rb:78:in `pre_process'
thin (1.0.1) lib/thin/connection.rb:57:in `process'
thin (1.0.1) lib/thin/connection.rb:42:in `receive_data'
eventmachine (0.12.6) lib/eventmachine.rb:240:in `run_machine'
eventmachine (0.12.6) lib/eventmachine.rb:240:in `run'
thin (1.0.1) lib/thin/backends/base.rb:57:in `start'
thin (1.0.1) lib/thin/server.rb:150:in `start'
thin (1.0.1) lib/thin/controllers/controller.rb:80:in `start'
thin (1.0.1) lib/thin/runner.rb:173:in `send'
thin (1.0.1) lib/thin/runner.rb:173:in `run_command'
thin (1.0.1) lib/thin/runner.rb:139:in `run!'
thin (1.0.1) bin/thin:6
/usr/local/bin/thin:20:in `load'
/usr/local/bin/thin:20
Rendering /disk1/home/slugs/212292_698e4ed_e2ba/mnt/public/500.html
(500 Internal Server Error)
Any help will b highly appreciated .
Hope to hear from you soon guys .
Cheers
Eki
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com
.
For
Location of Amazon servers used by Heroku
Just wondering if heroku uses a particular set of amazon servers, e.g East Coast, West Coast, Europe etc. Are there any plans to make this user selectable? This may matter to me as latency may be an issue for my app (still need to do more deployment/testing to see how much of an issue). I'd particularly be interested in the Singapore/Asia servers at this point in time. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Deployment Planning and general safeguards
Arron, Could you share those rake tasks? Be interested in checking them out cheers, john On Jun 23, 5:58 am, Arron Washington l33t...@gmail.com wrote: Nobody? OK, I'll share what I do. :3 For an important project hosted on Heroku (that I don't want to go down), I tend to wrap everything up in rake tasks that handle deployment, caching assets on Amazon S3/Cloudfront, etc. As part of these tasks, I also include the ability to roll back to a previous (or arbitrary) Git commit. I use the 'git' gem to handle these commands internally, and since there's always an official repo that isn't hosted by Heroku, it's safe to nuke the Heroku repositories using the '--force' flag when required. Once the tasks are developed and the app is live, nobody is allowed to do a raw `git push` to the Heroku remotes anymore. We keep our environments/staging.rb as close to our environments/ production.rb as possible. Deploy tasks also capture a Heroku bundle for each deploy, but I think the Heroku bundles also take a snapshot of the database -- data is generally not something we're willing to use during an emergency recovery, so we don't use the bundles. They're there just in case. On Jun 18, 7:49 pm, Neil Middleton neil.middle...@gmail.com wrote: Following on partly from my earlier email about support: We have an app that we've deployed a production and staging environment for. The idea being that all deployments go via staging prior to production as a way of testing that Heroku is happy to spin up and 'accept' our application (config is nearly always the issue). Question is, what steps do people do to prevent themselves from ending up with a production app that's failing to start? I know some users are pushing a large amount of traffic where downtime is unacceptable, so what do you do to protect yourself? How do you recover if things go bad? For anyone to trust something as different as Heroku, I think you have to know how to get back to a working state asap without outside intervention where possible. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Location of Amazon servers used by Heroku
Hi Brad, Our services are currently located in US East. We have discussed offering Heroku in a second geographic region, but we don't have any specific plans or a timetable for doing this. Europe would likely be our second region. Matt On Fri, Jun 25, 2010 at 4:49 AM, Brad oconnor.b...@gmail.com wrote: Just wondering if heroku uses a particular set of amazon servers, e.g East Coast, West Coast, Europe etc. Are there any plans to make this user selectable? This may matter to me as latency may be an issue for my app (still need to do more deployment/testing to see how much of an issue). I'd particularly be interested in the Singapore/Asia servers at this point in time. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- Matthew Soldo Heroku, Inc (415) 323-0003 http://www.linkedin.com/in/mattsoldo @mattsoldo -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Location of Amazon servers used by Heroku
+100 for Europe Neil On Fri, Jun 25, 2010 at 4:31 PM, Matthew Soldo m...@heroku.com wrote: Hi Brad, Our services are currently located in US East. We have discussed offering Heroku in a second geographic region, but we don't have any specific plans or a timetable for doing this. Europe would likely be our second region. Matt On Fri, Jun 25, 2010 at 4:49 AM, Brad oconnor.b...@gmail.com wrote: Just wondering if heroku uses a particular set of amazon servers, e.g East Coast, West Coast, Europe etc. Are there any plans to make this user selectable? This may matter to me as latency may be an issue for my app (still need to do more deployment/testing to see how much of an issue). I'd particularly be interested in the Singapore/Asia servers at this point in time. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- Matthew Soldo Heroku, Inc (415) 323-0003 http://www.linkedin.com/in/mattsoldo @mattsoldo -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Permission Denied (publickey)
I just did heroku create I did that for the first time, so it'd upload the public key automatically; it uploaded successfully. Now, when I do git push heroku master it says: Permission denied (publickey) fatal: The remote end hung up unexpectedly -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
error pushing to heroku
hi, i'm getting an error when pushing to heroku using rails 3 beta 4. i've managed to deploy before using it but for some reason i'm getting a strange error now. I'm on os x, snow leopard. I've been using rvm with both 1.9.2 preview and head, i also just reverted back to the system ruby 1.8.7 -p254 but they all give me the same error: -- git push heroku master Counting objects: 334, done. Delta compression using up to 2 threads. Compressing objects: 100% (285/285), done. Writing objects: 100% (310/310), 48.73 KiB, done. Total 310 (delta 119), reused 0 (delta 0) - Heroku receiving push - Rails app detected - Gemfile detected, running Bundler Unresolved dependencies detected; Installing... . . INSTALLS/BUNDLES ALL THE GEMS AND EVERYTHING WORKS FINE UNTILL HERE: . . Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed. Locking environment /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/package/ tar_input.rb:49:in `initialize': not in gzip format (Zlib::GzipFile::Error) from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/package/ tar_input.rb:49:in `new' . . MORE STACK TRACE HERE: . . error: hooks/pre-receive exited with error code 1 To g...@heroku.com:hostelizer.git ! [remote rejected] master - master (pre-receive hook declined) error: failed to push some refs to 'g...@heroku.com:hostelizer.git' -- Any ideas would be gr8 as i'm not a guru with ruby/rails. Cheers. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
db:pull throws exception from taps
I am having the same problem discussed in this thread: http://groups.google.com/group/heroku/browse_thread/thread/20e036163a9e5ee0/92f0f6e9e021c2a0?lnk=gstq=taps+_load, but the solution of uninstalling and re-installing sqlite3-ruby did not help. Taps throws an exception here: Error encountered loading data, wrote the data chunk to dump. 20810.dat | ETA: --:--:-- /home/lsiden/.rvm/gems/ruby-1.9.1-p378/gems/taps-0.3.9/lib/taps/ data_stream.rb:187:in `load': class DateTime needs to have method `_load' (TypeError) from /home/lsiden/.rvm/gems/ruby-1.9.1-p378/gems/taps-0.3.9/lib/taps/ data_stream.rb:187:in `parse_encoded_data' from /home/lsiden/.rvm/gems/ruby-1.9.1-p378/gems/taps-0.3.9/lib/taps/ data_stream.rb:130:in `fetch_remote' from /home/lsiden/.rvm/gems/ruby-1.9.1-p378/gems/taps-0.3.9/lib/taps/ operation.rb:286:in `block in pull_data_from_table' from /home/lsiden/.rvm/gems/ruby-1.9.1-p378/gems/taps-0.3.9/lib/taps/ operation.rb:279:in `loop' from /home/lsiden/.rvm/gems/ruby-1.9.1-p378/gems/taps-0.3.9/lib/taps/ operation.rb:279:in `pull_data_from_table' Is this something I should post to the taps forum or #irc? -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Please help on rack-rewrite
j...@home ~/work/voteforpoetry $ heroku config
SITE_URL = voteforpoetry.com
j...@home ~/work/voteforpoetry $ heroku domains
Domain names for voteforpoetry.heroku.com:
voteforpoetry.com
www.voteforpoetry.com
http://github.com/jtrupiano/rack-rewrite/issues/#issue/7
## Gemfile
gem 'rack-rewrite', '1.0.0'
## config/environments/production.rb (fails)
config.gem 'rack-rewrite', '1.0.0'
require 'rack/rewrite'
config.middleware.insert_before(Rack::Lock, Rack::Rewrite) do
r301 %r{.*}, http://#{ENV['SITE_URL']}$, :if = Proc.new { |
rack_env|
rack_env['SERVER_NAME'] != ENV['SITE_URL']
}
end
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
git push heroku resets database each time
Each time I push my app to heroku, I notice that the database has been reset (emptied). Is this because I have environment=test set? Or is it because my git refspec forces non-fast-forward pushes? Or is there some other reason that I don't know about. This could be a show-stopper when I deploy my app and it starts to gather real data. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Permission Denied (publickey)
I just did heroku create I did that for the first time, so it'd upload the public key automatically; it uploaded successfully. Now, when I do git push heroku master it says: Permission denied (publickey) fatal: The remote end hung up unexpectedly I don't know what's wrong. But I can change my public key with Heroku. How can change that? -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Can't use memcache with my application
Just pushed an update for the northscale gem:
http://github.com/heroku-examples/r3b4-memcache-heroku/commit/4fbc4f15dfa9f375b30325a62d9311a87cf07e7b
Oren
On Fri, Jun 25, 2010 at 4:11 AM, Neil Middleton neil.middle...@gmail.comwrote:
I'm not sure if this is a related issue or not, but heroku have an example
app of Rails 3b4 with memcached here:
http://github.com/heroku-examples/r3b4-memcache-heroku
However, if we flip it to memcached-northscale we start seeing :
/Users/neil/Dropbox/code/r3b4-memcache-heroku/config/environments/production.rb:29:
uninitialized constant Memcached (NameError)
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application.rb:55:in
`class_eval'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application.rb:55:in
`configure'
from
/Users/neil/Dropbox/code/r3b4-memcache-heroku/config/environments/production.rb:1
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application/bootstrap.rb:10:in
`require'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application/bootstrap.rb:10
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/initializable.rb:25:in
`instance_exec'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/initializable.rb:25:in
`run'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/initializable.rb:55:in
`run_initializers'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/initializable.rb:54:in
`each'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/initializable.rb:54:in
`run_initializers'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application.rb:119:in
`initialize!'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application.rb:81:in
`send'
from
/Library/Ruby/Gems/1.8/gems/railties-3.0.0.beta4/lib/rails/application.rb:81:in
`method_missing'
from /Users/neil/Dropbox/code/r3b4-memcache-heroku/config/environment.rb:5
from config.ru:3:in `require'
from config.ru:3
from /Library/Ruby/Gems/1.8/gems/rack-1.1.0/lib/rack/builder.rb:46:in
`instance_eval'
from /Library/Ruby/Gems/1.8/gems/rack-1.1.0/lib/rack/builder.rb:46:in
`initialize'
from config.ru:1:in `new'
from config.ru:1
This might be a non-issue, but we thought it worth pointing out differences
between the two gems.
Neil
On Thu, Jun 24, 2010 at 5:39 PM, Sean Lynch se...@literati.org wrote:
Hi, Eki.
This is a side-effect of Fauna's throwing exceptions for errors that would
just show up as misses in memcache-client. I've fixed this and it's in
testing in a gem called memcached-northscale. You still use require
'Memcached', just use memcached-northscale instead of memcached in your
gem.
Once I get feedback that it a) solves the problem and b) doesn't cause
other problems, I'll get it incorporated into Fauna.
Thanks!
-Sean
On Jun 24, 2010, at 3:46 AM, Eki wrote:
Hi guys ,
I'm trying to use memcached with my application , I followed the
official instructions to do so but still not working ,
the error msg is something like this :
Memcached::ServerIsMarkedDead (Key
{country_x_y_z=127.0.0.1:11211:8}):
memcached (0.19.7) lib/memcached/memcached.rb:609:in
`check_return_code'
memcached (0.19.7) lib/memcached/memcached.rb:515:in `get'
memcached (0.19.7) lib/memcached/rails.rb:39:in `get'
app/controllers/prayer_times_controller.rb:9:in `index'
/home/heroku_rack/lib/static_assets.rb:9:in `call'
/home/heroku_rack/lib/last_access.rb:25:in `call'
/home/heroku_rack/lib/date_header.rb:14:in `call'
thin (1.0.1) lib/thin/connection.rb:80:in `pre_process'
thin (1.0.1) lib/thin/connection.rb:78:in `catch'
thin (1.0.1) lib/thin/connection.rb:78:in `pre_process'
thin (1.0.1) lib/thin/connection.rb:57:in `process'
thin (1.0.1) lib/thin/connection.rb:42:in `receive_data'
eventmachine (0.12.6) lib/eventmachine.rb:240:in `run_machine'
eventmachine (0.12.6) lib/eventmachine.rb:240:in `run'
thin (1.0.1) lib/thin/backends/base.rb:57:in `start'
thin (1.0.1) lib/thin/server.rb:150:in `start'
thin (1.0.1) lib/thin/controllers/controller.rb:80:in `start'
thin (1.0.1) lib/thin/runner.rb:173:in `send'
thin (1.0.1) lib/thin/runner.rb:173:in `run_command'
thin (1.0.1) lib/thin/runner.rb:139:in `run!'
thin (1.0.1) bin/thin:6
/usr/local/bin/thin:20:in `load'
/usr/local/bin/thin:20
Rendering /disk1/home/slugs/212292_698e4ed_e2ba/mnt/public/500.html
(500 Internal Server Error)
Any help will b highly appreciated .
Hope to hear from you soon guys .
Cheers
Eki
--
You received this message because you are subscribed to the Google
Groups Heroku group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
Re: git push heroku resets database each time
It's because you have your enviornment set. That's a rails feature. Production doesn't do that. On Fri, Jun 25, 2010 at 12:22 AM, lsiden lsi...@gmail.com wrote: Each time I push my app to heroku, I notice that the database has been reset (emptied). Is this because I have environment=test set? Or is it because my git refspec forces non-fast-forward pushes? Or is there some other reason that I don't know about. This could be a show-stopper when I deploy my app and it starts to gather real data. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
App Failed to Start -- JSON BUG?
Hi all, We're having intermittent errors with our preliminary app (http:// fromus.heroku.com). Occasionally we're getting an App Failed to Start screen (e.g., on the home screen), but then on reload the page will load fine. It's very intermittent and unpredictable. I have copied the error log below, and it there's a JSON bug reported... Does anyone know what this is? Or have any advice how I can figure it out? We're planning to launch within the next week, and we need to make sure this is running smoothly first. Thanks, Brett App failed to start Check out the troubleshooting section on our Documentation site. Original Error ** [NewRelic] New Relic RPM Agent 2.12.3 Initialized: pid = 3298 ** [NewRelic] Agent Log found in /disk1/home/slugs/184992_3ae2c09_5807/ mnt/log/newrelic_agent.log /disk1/home/slugs/184992_3ae2c09_5807/mnt/app/helpers/ application_helper.rb:103: warning: parenthesize argument(s) for future version Thin web server (v1.0.1 codename ?) Maximum connections set to 1024 Listening on 0.0.0.0:47491, CTRL+C to stop ** [NewRelic] Connected to NewRelic Service at collector5.newrelic.com: 80 /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/ active_support/json/encoding.rb:18: [BUG] object allocation during garbage collection phase ruby 1.8.6 (2008-08-11) [x86_64-linux] -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
