Ok, I'm pretty sure that this is being triggered in the UI by asking
for all nodes. If i specify and environment and this request nodes
everything is quick and displays properly. If i change environment to
'none' it will eventually time out.
On Thu, Jun 28, 2012 at 3:31 PM, Chris < "> > wrote:
> Maybe. But i dont see anything wrong happening there either. When I
> make a request agains /nodes everything seems to work fine. Its a
> little slow, but never times out. As you can see here
>
> merb : chef-server-webui : worker (port 4040) ~ Started request
> handling: Thu Jun 28 15:26:56 -0700 2012
> merb : chef-server-webui : worker (port 4040) ~ Routed to:
> {"format"=>nil, "action"=>"index", "controller"=>"nodes"}
> merb : chef-server-webui : worker (port 4040) ~ Params:
> {"format"=>nil, "action"=>"index", "controller"=>"nodes"}
> merb : chef-server-webui : worker (port 4040) ~
> {:dispatch_time=>38.045792, :action_time=>38.04534,
> :after_filters_time=>1.5e-05, :before_filters_time=>9.544411}
>
>
> On Thu, Jun 28, 2012 at 3:20 PM, AJ Christensen < "> > wrote:
>> CouchDB?
>>
>> --AJ
>>
>> On 29 June 2012 10:11, Chris < "> > wrote:
>>> Hi chefs!
>>>
>>> A few of my users have been complaining about timeouts from the UI. I
>>> have yet to repro this myself, but i did happen to catch the webui log
>>> while someone was complaining they were having issues.
>>>
>>> heres the log output
>>> http://pastie.org/4167984
>>>
>>> its not obvious to me why its returning nil on the nodes controller
>>> and any subsequent requests to the UI work just fine. anyone have any
>>> ideas?
>>>
>>>
>>> --
>>> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
>>> permitted by applicable law.
>
>
>
> --
> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
> permitted by applicable law.
--
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Archive powered by MHonArc 2.6.16.