Hi joshmckin,
thank you very much for the support.
I have tried to replicate the problem locally but I have found no
error yet.
I'm thinking a way to save the log realtime so I can parse it
searching for the problem; the "advance" logging addon is out of my
budget.
On 20 Lug, 15:58, joshmckin wro
Hi,
some users are informing me that my application sometimes pop up an
Application Error:
--
Application Error
An error occurred in the application and your page could not be
served. Please try again in a few moments.
If you are the application owner, check your logs for details.
--
I'm
Yes, quite *sad*.
In this cases the only solution is to have a backup hosting/server and
do a DNS change. I "solved" this way.
On 21 Apr, 21:19, chris wrote:
> We created a custom error page and are seeing the heroku generic instead of
> our prettiness. Sad...
--
You received this message becau
x27;
/usr/ruby1.8.7/lib/ruby/1.8/openssl/buffering.rb:170:in `do_write'
/usr/ruby1.8.7/lib/ruby/1.8/openssl/buffering.rb:192:in `write'
The same error happens in local and using the Heroku console too.
Any tip please?
Regards,
Daniele
--
You received this message beca
Same thoughts here.
The support request is not as fast as other providers I use. I didn't
have critical issue (except for a problem to a primary key of the
database, not set correctly during a push, that I solved myself) but
I'm a little scared about the fact to stay offline with a slow support
res
Thank you very much Jacob.
On Sep 16, 7:05 pm, Jacob Vorreuter wrote:
> The backlog too deep response is served once a request spends 15 seconds
> queued up waiting for a backend. Once the wait queue reaches a length of 50
> requests, backlog too deep responses are served immediately.
--
You
blem phase I get a lot of these
messages while the git repo was not probably accessible. So I will
prefer an iframe/ajax solution in this case too.
Daniele
On Sep 15, 7:19 pm, Mike Abner wrote:
> Why have a separate branch? Heroku can just tell us where to put them
> in the folder hiera
The queue is a numeric value you can see in the
HTTP_X_HEROKU_QUEUE_DEPTH header.
Of course it depends on the number of requests.. but I need to know
the max length after which we get the error page.
On Sep 15, 9:18 pm, Teng Siong Ong wrote:
> it depends on how long your processing time for each
As subject, what is the limit above which appears the error "backlog
too deep"?
--
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+unsubsc
can check for the domain existence and switch to
a plain txt message if it is not set.
I'd love to get feedback on these ideas by Heroku guys. Thank you.
Daniele
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to thi
+1 for the unbranded page
A simple solution for more personalization without the need to access
any preferences could be to have a full page iframe inside the
heroku's error page pointing to http://error..
So every application can have an error page/backup application to
handle the down.
A js ca
sob... :)
Thank you for the reply.
On 23 Mag, 02:16, Oren Teich wrote:
> That's wrong. I'll fix the docs. The only way to flush varnish right
> now is to do a fresh git push.
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group,
a bug? Any experience about that?
Regards,
Daniele
--
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.c
+1 for EU datacenter :)
On 24 Mar, 02:38, Morten Bagai wrote:
> Thank for the comments. We continue to see strong interest in the Heroku
> platform from European users,
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send ema
+1
Really nice feature!
On 15 Mar, 18:57, Mike Doel wrote:
> I imagine we're not alone in having both a staging and production environment
> up on heroku. We frequently use heroku db:pull to grab the production
> database and will occasionally put it up to our staging environment with
> hero
On 15 Mar, 01:13, Mike wrote:
> That's a really good idea on having a controller take the upload into
> temp. Is there a size limit on the temp directory?
I don't know, sorry.
> Or a time limit on
> how long a dyno can be locked to a single upload before being
> restarted?
"Request Length: 3
This is an hard step and depend by the size of default dataset (?).
Just an idea (I've not tested it):
* Create a controller for the update with an upload field.
* Upload a DB with the basic dataset only. The file will update in
the /temp dir.
* Find out you postgres config reading the config/dat
For the import part if it has not to be "atomic" you could create
another app and use it to feed via a web service the data on the
production database while the main app is live.
To download only the main dataset create a boundle, animate it on a
new application, delete the huge data with a migrat
tem... is not supported on Heroku :P
So locally I tested a global var and it did its work. Yes I know it is
not a best practice.
Any other ideas?
Thank you for your time.
On 10 Mar, 17:25, Carl Fyffe wrote:
> Daniele,
>
> My apologies for coming across rude, it was not my intention,
act as a filter before every
request. So what I need it to keep a moderate size array in memory,
read and write it *quickly*.
Any suggestion are welcome.
On 10 Mar, 16:38, Chris wrote:
> Daniele,
> If you really need a global variable to be accessible across servers
> then memcached
Yes Carl, you tone is quite rude. And perhaps you reply to the wrong
person.
By the way I need the global variable for other uses, caching is not a
problem for me.
On 10 Mar, 15:51, Carl Fyffe wrote:
> These kinds of questions crack me up. I am going to try to adress this
> without sounding rude,
Any news about that?
On 9 Mar, 09:18, Daniele wrote:
> Yes I know that.
> But with on a single dyno app and 10 concurrent users I should always
> have a queue of 9. Right?
> I used a 1 sec dummy action to eliminate eventual ab delays that will
> empty the queue faster.
--
Yo
So a global variable $xx is not shared in the cloud?!
On 10 Mar, 06:49, Oren Teich wrote:
> I don't have a good answer for your question, but note there is no guarantee
> that your requests will be served from the same physical machine - we'll
> move the dyno around as demanded by the cloud.
-
Yes I know that.
But with on a single dyno app and 10 concurrent users I should always
have a queue of 9. Right?
I used a 1 sec dummy action to eliminate eventual ab delays that will
empty the queue faster.
On 9 Mar, 00:49, Oren Teich wrote:
> the queue is the list of what is waiting.
> Requests
t;]}"
end
end
So I lunch ab against it:
ab -c 10 -t 60 http://myapp.heroku.com/visitme/test
With a concurrency of 10 I should get a queue of 10, right?
Instead, while response times are correctly about 10 secs, the queue
is always at 5 or lower value. How can that be possibile?
Regards,
Thank you Oren
On 8 Mar, 19:34, Oren Teich wrote:
> it's based on what you have set. Set dynos to 2 for an hour, and you'll pay
> $0.05. Set it to 2 for 30 minutes, and you'll pay $0.025. We don't
> currently auto-scale.
--
You received this message because you are subscribed to the Google G
Hi all,
from docs I read "subsequent dynos cost $0.05 per hour, prorated to
the second".
So I will pay dynos for effective seconds usage?
Thank you in advance.
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send email to her..
Of course I mean locked-in in a soft way :P Perhaps the wrong term,
sorry for my bad english
I'm used to think in the old server way, so for example I was unable
to grasp how to implement an hight availability setup with a secondary
server. But thinking about that the remote connection should not b
Hi Oren,
thank you for the "official" reply :)
RDS is not a solution because I only need to import some data. Then I
love Postgres :)
By the way I'm a little scared about been locked-in in the future too.
I think that a way to connect from the outside (with an IP firewall
policy too) could be a nic
Thanks Carl but this is not a viable solution because I have to push
data while the app is running. I cannot stop it to backup - modify -
restore
On 4 Mar, 21:32, Carl Fyffe wrote:
> Not sure if this meets your needs or not:
> http://blog.heroku.com/archives/2009/3/18/push_and_pull_databases_to_
our local mssql db, read stuff into memory, and
> then push the data to your remote app via the ActiveResource objects.
>
> Cheers,
>
> -Roy
>
>
>
>
>
> On Thu, Mar 4, 2010 at 12:25 PM, Daniele wrote:
> > Hi Roy,
> > actually I have a rake task
Hi Roy,
actually I have a rake task in my RoR app that connect to a remote
MSSQL database and import data. This task use dbi with a quite complex
system configuration.
Because I cannot use it on Heroku it could be nice to setup the Heroku
database as remote one on a second installation so I can use
Hi,
I have to connect to the Heroku database from a remote location, is it
possibile?
Regards,
Daniele
--
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 g
33 matches
Mail list logo
