Good morning,
We upgraded to 3.3 last week and everything was working great until this morning when all requests have started to fail. When I look at the service_errors it looks like timeout errors but we have not made any changes in the past week after the upgrade. Any suggestions?
Good morning,
We upgraded to 3.3 last week and everything was working great until this morning when all requests have started to fail. When I look at the service_errors it looks like timeout errors but we have not made any changes in the past week after the upgrade. Any suggestions?
--
You received this message because you are subscribed to the Google Groups "Umlaut" group.
To unsubscribe from this group and stop receiving emails from it, send an email to umlaut-softwa...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Great to hear that it is not just a local issue.
Scot,
Have you tried changing sfx_timeout? Based on the sfx.rb the default timeout is set to 8 s which may be causing the issue. I made this change earlier this morning and have not seen the error again – yet. I increased the value to 60 s which seems high but will work for testing.
From: Scot Thomas Dalton [mailto:st...@nyu.edu]
Sent: Monday, July 21, 2014 9:02 AM
To: Poulter, Dale
Cc: umlaut-...@googlegroups.com
Subject: [External] Re: [umlaut] Umlaut sfx service fails with timeout
Hi Dale,
So something doesn't seem right there, because an Umlaut upgrade should
not cause your SFX to respond any slower than it did before! And your SFX really ought not to take 120 seconds to respond -- are you actually having to wait up to 2 minutes for your Umlaut page with SFX results to display?
In addition to being a pretty terrible experience for your users, I think that's also going to result in a pretty unstable app, if it's blocking that long before returning results.
Scot, did you figure out anything else about this?
Dale, can you let me know what version of Umlaut you were using previously, and what version you upgraded to? Maybe file a Github ticket on this? If you give me your exact umlaut_services.yml file (and maybe your Gemfile.lock too), I can maybe try to reproduce on my end.
Jonathan
On 8/18/14 9:35 AM, Poulter, Dale wrote:
We are still having this issue but we were able to at least mask the
issue by increasing the sfx_timeout to 120 so everything is ok right
now. We will probably move back to the delivered menu shortly with a
few customizations.
-Dale
-----Original Message----- From: Jonathan Rochkind
[mailto:roch...@jhu.edu] Sent: Monday, August 18, 2014 8:30 AM To:
Poulter, Dale; umlaut-software@googlegroups.com Subject: Re: [umlaut]
Umlaut sfx service fails with timeout
Hi Dale, I'm afraid I was away on summer vacation, just returned. Are
you still having this problem? Did you downgrade to an earlier
version of Umlaut in the meantime?
Jonathan
On 7/21/14 9:28 AM, Dale Poulter wrote:
Good morning,
We upgraded to 3.3 last week and everything was working great
until this morning when all requests have started to fail. When I
look at the service_errors it looks like timeout errors but we have
not made any changes in the past week after the upgrade. Any
suggestions?
-- You received this message because you are subscribed to the
Google Groups "Umlaut" group. To unsubscribe from this group and
stop receiving emails from it, send an email to
umlaut-software+unsubscribe@googlegroups.com
<mailto:umlaut-software+unsub...@googlegroups.com>. For more
options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Umlaut" group.
To unsubscribe from this group and stop receiving emails from it, send an email to umlaut-software+unsubscribe@googlegroups.com.