there's a comment to one of the answers that mentions thread safety.
changing the environments\production.rb file
config.threadsafe!
to
config.threadsafe! unless $rails_rake_task
appears to have fixed my problem. Thx for your replies.
On Apr 27, 11:10 am, Jeff Schmitz wrote:
> The link you p
Nope. Interesting that the line in http.rb is
if use_ssl?
s.connect # it's this line
end
So something b0rken.
K.
---
http://blitz.io
http://twitter.com/pcapr
http://labs.mudynamics.com
On Wed, Apr 27, 2011 at 8:09 PM, Wes Gamble wrote:
> Does "heroku logs --tail" work on
Does "heroku logs --tail" work on 1.8?
W
On 4/27/11 9:46 PM, kowsik wrote:
$ heroku logs --source heroku --tail
/usr/local/lib/ruby/1.8/net/http.rb:586: [BUG] Bus Error
ruby 1.8.7 (2008-05-31 patchlevel 0) [i686-darwin9.8.0]
Abort trap
???
ruby 1.9 works.
K.
---
http://blitz.io
http://twitt
$ heroku logs --source heroku --tail
/usr/local/lib/ruby/1.8/net/http.rb:586: [BUG] Bus Error
ruby 1.8.7 (2008-05-31 patchlevel 0) [i686-darwin9.8.0]
Abort trap
???
ruby 1.9 works.
K.
---
http://blitz.io
http://twitter.com/pcapr
http://labs.mudynamics.com
On Wed, Apr 27, 2011 at 2:01 PM, Chris
I was able to get it fixed.. not sure why but when I reinstalled the
the bundle and pushed it up to heroku it worked correctly. Nokogiri
was also having some issue, so I reinstalled it.
On Apr 27, 8:29 pm, Aaron Mills wrote:
> I am getting a lot of strange errors on one of my apps. For example:
>
I am getting a lot of strange errors on one of my apps. For example:
heroku rake db:migrate
rake aborted!
could not translate host name
"ec2-50-16-226-121.compute-1.amazonaws.com" to address: Name or
service not known
Also I am getting 500 error codes when I try and pull up any of the
pages, and
Sweet
--
Christian Hjalmarsson
27 apr 2011 kl. 22:50 skrev David Dollar :
> We've just released version 2.0 of the Heroku client. While most of the
> changes are behind the scenes, a few new things you'll notice include:
>
> * The help system has been completely revamped, including help for in
We've just released version 2.0 of the Heroku client. While most of the changes
are behind the scenes, a few new things you'll notice include:
* The help system has been completely revamped, including help for individual
commands.
* All commands now have namespaces for organizational purposes.
The link you provided was about eager loading, not thread safety.
The only way I can make it jive with your earlier message is that the
require of Authlogic from Event is failing
maybe you can run with --trace?
On Wed, Apr 27, 2011 at 10:17 AM, Daz wrote:
> After more searching, I have finall
The nginx docs here note that gzip_http_version defaults to 1.1:
http://wiki.nginx.org/HttpGzipModule#gzip_http_version
Which might explain the behavior on Heroku. And this blog post
mentions nginx config for using CloudFront, specifically setting
gzip_http_version to 1.0:
http://www.nomitor.com
After more searching, I have finally come across this:
http://stackoverflow.com/questions/4300240/rails-3-rake-task-cant-find-model-in-production
- which provided the hint that the problem is actually due to having
the production environment configured to be thread safe. Since the
cron would work p
That's a good review of EBS issues, thanks for the link.
On Tue, Apr 26, 2011 at 10:41 PM, kowsik wrote:
> On Tue, Apr 26, 2011 at 8:31 PM, Wes Gamble wrote:
> > On 4/26/11 10:07 PM, kowsik wrote:
> >>
> >> On Tue, Apr 26, 2011 at 8:01 PM, Wes Gamble wrote:
> >>>
> >>> I would like to understa
Confused how Authlogic, usually found in a controller, could be a part of
this.
Event.send_reminders is not using authentication, is it?
On Tue, Apr 26, 2011 at 10:33 PM, Darren Bereska wrote:
> I'm running a Rails 3 app using Authlogic 2.1.6. I've added a cron task
> that will not execute. It
I'm running a Rails 3 app using Authlogic 2.1.6. I've added a cron task that
will not execute. It errors out with this:
$ heroku rake cron
(in /app)
start sending reminder emails
rake aborted!
uninitialized constant Object::Event
/usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2482:in `const_missing'
/app/l
It seems like Heroku's nginx may be set to issue a gzipped response
only for HTTP/1.1 requests. In my quick tests, a 1.0 request with an
"Accept-Encoding: deflate, gzip" header gets an uncompressed response,
but the same request under 1.1 gets gzipped content.
Unfortunately, Amazon CloudFront, whi
15 matches
Mail list logo
