Wow - thanks for digging in Matt - that's crazy :P
I added the 'net-dns' gem to my rails app and it seems to be doing
much better on Heroku :)
thank you so much for the help!
On Apr 4, 9:21 am, Matthew Todd wrote:
> > Unfortunately, I get the exact same connection error message
> > from Heroku
Could anyone that was running into this issue please try the latest pre-release
heroku/taps gems:
gem install heroku taps --pre
and let me know if you're still running into issues?
I just pushed them up so you may need to wait a few minutes for them to show up
in the index. The versions you're
Yep, it worked with my previous heroku gem version: 1.9.14
Thanks :)
On Monday, April 4, 2011 at 9:26 PM, David Dollar wrote:
> Sorry, forgot to mention that you will need to roll back to heroku version
> 1.19.1 as well.
>
> Cheers,
> David
>
> On Apr 4, 2011, at 2:23 PM, Ciprian Dunareanu w
Sorry, forgot to mention that you will need to roll back to heroku version
1.19.1 as well.
Cheers,
David
On Apr 4, 2011, at 2:23 PM, Ciprian Dunareanu wrote:
> Unfortunately that doesn't work for me:
> Your taps gem is out of date (v0.3.22 or higher required).
>
> Are you using an older heroku
Unfortunately that doesn't work for me:
Your taps gem is out of date (v0.3.22 or higher required).
Are you using an older heroku gem?
Regards.
--
Ciprian Dunareanu
Sent with Sparrow
On Monday, April 4, 2011 at 9:21 PM, kbjerring wrote:
> Great!
>
> Taps 0.3.21 certainly works.
>
> On Apr 4,
Great!
Taps 0.3.21 certainly works.
On Apr 4, 8:16 pm, David Dollar wrote:
> I'm working on a permanent solution. In the meantime you can roll back to
> taps 0.3.21.
>
> On Apr 4, 2011, at 2:13 PM, kbjerring wrote:
>
>
>
>
>
>
>
> > I have just seen the exact same error
> > (Using Taps-0.3.22)
I'm working on a permanent solution. In the meantime you can roll back to taps
0.3.21.
On Apr 4, 2011, at 2:13 PM, kbjerring wrote:
> I have just seen the exact same error
> (Using Taps-0.3.22)
>
> Alas, I have found no solution yet :(
>
> On Apr 4, 8:05 pm, Francois wrote:
>> wondering if an
I have just seen the exact same error
(Using Taps-0.3.22)
Alas, I have found no solution yet :(
On Apr 4, 8:05 pm, Francois wrote:
> wondering if anyone has encountered the following error before when
> using heroku db:pull ?
>
> Saving session to pull_201104041103.dat..
> !!! Caught Server Exce
Having the same problem with Taps v0.3.22
Regards.
On Apr 4, 9:06 pm, David Dollar wrote:
> What version of the taps gem are you using?
>
> On Apr 4, 2011, at 2:05 PM, Francois wrote:
>
>
>
>
>
>
>
> > wondering if anyone has encountered the following error before when
> > using heroku db:pull ?
What version of the taps gem are you using?
On Apr 4, 2011, at 2:05 PM, Francois wrote:
> wondering if anyone has encountered the following error before when
> using heroku db:pull ?
>
> Saving session to pull_201104041103.dat..
> !!! Caught Server Exception
> HTTP CODE: 500
> Taps Server Error:
wondering if anyone has encountered the following error before when
using heroku db:pull ?
Saving session to pull_201104041103.dat..
!!! Caught Server Exception
HTTP CODE: 500
Taps Server Error: unexpected nil
- thanks
F
--
You received this message because you are subscribed to the Google Gro
> Unfortunately, I get the exact same connection error message
> from Heroku when using an IP that dig has no problem connecting to
> (e.g. Google's public DNS server 8.8.8.8):
I just dug some more --
Turns out the Errno::ECONNREFUSED has nothing to do with the nameserver you're
querying. For so
very nice catch as well - but also works just fine on Heroku ..
>> puts `dig +tcp www.abc.com @8.8.8.8`
; <<>> DiG 9.6-ESV-R3 <<>> +tcp www.abc.com @8.8.8.8
;; global options: +cmd
;; Got answer:
...
On Apr 4, 8:58 am, kowsik wrote:
> dig uses udp by default. But from your error, it appears tha
dig uses udp by default. But from your error, it appears that Dnsruby
might be using tcp. Maybe try
dig +tcp www.abc.com @8.8.8.8
K.
---
http://blitz.io
http://twitter.com/pcapr
On Mon, Apr 4, 2011 at 8:24 AM, craayzie wrote:
> Thanks for replying Matt and good catch on the nameserver IP - it w
Collections are very small (a few thousand items). We're definitely
indexing. If I were hosting my own Mongo, I would have looked at admin
numbers, but this is in MongoHQ. Mostly I am looking at where to start
and how - all I got is New Relic flagging some transactions (not
much).
Thx
dB.
On Apr
Thanks for replying Matt and good catch on the nameserver IP - it was
a typo. Unfortunately, I get the exact same connection error message
from Heroku when using an IP that dig has no problem connecting to
(e.g. Google's public DNS server 8.8.8.8):
>> res = Dnsruby::Resolver.new({:nameserver => "8
All:
Thanks for the replies. I tried Jeff's syntax:
if Time.now.wday == 1
and it worked perfectly. Thanks!
I'll check into the other ideas, including Simpleworker. Thanks!!!
ps...I'm on Rails 3.0.3dont know what Ruby I'm on. Thx.
On Mar 31, 1:45 pm, Chris Hanks wrote:
> Oh, you must
Hi, Craayzie --
> >> res = Dnsruby::Resolver.new({:nameserver => ["68.87.76.182"]})
> >> ret = res.query("www.abc.com")
> Errno::ECONNREFUSED: Connection refused - connect(2)
For what it's worth, I just tried running `dig` in a Heroku console.
Querying the nameserver you mentioned didn't work:
I am getting this error:
Errno::EAFNOSUPPORT: Address family not supported by protocol -
socket2
usrruby19.2libruby1.9.1nethttprb:644:in initialize
usrruby19.2libruby1.9.1nethttprb:644:in open
usrruby19.2libruby1.9.1nethttprb:644:in block in connect
usrruby19.2libru
For some reason Heroku is complaining of not being able to establish a
TCP connection when I issue a DNS query w/ Dnsruby::Resolver but I'm
not sure how to debug it further. Any guidance would be really
appreciated.
If I try to manually establish the TCP connection to the nameserver in
question it
20 matches
Mail list logo
