Thanks!

momentarily, this issue dissipated yesterday.  it is back this morning. The 
only thing that i have been able to do in order to get this working is to 
adjust the security groups on the ELB that sits in front of scalr.  When i 
add an OUTBOUND ALLOW ALL rule, things just tart working, again...

Things continue to work even after i remove this rule.  I suspect this is 
because the roles are cached in the UI layer or possibly on the scalr side 
of things? 

The only theory i have, that is semi supported by the facts is that the 
hosted chef service that we use is rate limiting the API requests (we have 
a *lot* of roles / cookbooks!) and when i toggle ELB changes, amazon gives 
me a new EIP, which is not on the hosted chef 'watch' list, and things 
therefore work.


But it's purely speculation.

*sigh*.  I guess i'll just be happy that it's working for now, and i'll 
keep an eye out for the updated scalr release which fixes the chef-client 
approach!


-K

On Friday, July 17, 2015 at 4:59:40 AM UTC-7, DicsyDel wrote:
>
> Hi Karl, 
>
> I'm 100% sure. Here is the code: 
>
> https://github.com/Scalr/scalr/blob/master/app/src/Scalr/UI/Controller/Services/Chef.php#L17-L67
>  
>
> As you can see we're making N+1 API calls where N is number of your 
> recipes/roles in new version it's always 1 API call. 
>
> Regards, 
> Igor 
>
> On 16 July 2015 at 18:34,  <[email protected] <javascript:>> 
> wrote: 
> > Igor, are you sure this problem is due to Scalr's chef server 
> > communications? 
> > 
> > I ran log rotate, verified a clean log, and then attempted to load roles 
> > again.  Here's what i got: 
> > 
> > 
> > [Thu Jul 16 17:30:54.713194 2015] [proxy_http:error] [pid 8746] 
> (70007)The 
> > timeout specified has expired: [client 172.16.0.162:60914] AH01102: 
> error 
> > reading status line from remote server 127.0.0.1:6270, referer: 
> > https://scalr.CORP-tools.com/ 
> > [Thu Jul 16 17:30:54.713272 2015] [proxy:error] [pid 8746] [client 
> > 172.16.0.162:60914] AH00898: Error reading from remote server returned 
> by 
> > /services/chef/xListRoles, referer: https://scalr.CORP-tools.com/ 
> > 
> > 
> > 
> > 
> > Can you point me to the source code that manages the Scalr / Chef 
> > interactions or describe the workflow so i can continue to dig in? 
> > 
> > 
> > 
> > On Wednesday, July 15, 2015 at 3:46:10 PM UTC-7, DicsyDel wrote: 
> >> 
> >> Karl, 
> >> 
> >> This issue is related to how scalr is querying chef server. In current 
> >> opensource version scalr working with Chef server in a very 
> >> inefficient way and making to many API calls what leads to timeout in 
> >> UI if you have many chef roles or recipes. 
> >> 
> >> Right now we're preparing new OS release (will be available within the 
> >> next day or two) where this issue is fixed. 
> >> 
> >> If you cannot wait, just try to clean up your chef server and remove 
> >> unused chef roles. 
> >> 
> >> Regards, 
> >> Igor 
> >> 
> >> 
> >> 
> >> On 15 July 2015 at 22:42,  <[email protected]> wrote: 
> >> >> I've found something else that's rather interesting... 
> >> > 
> >> > 
> >> > root@scalr01:/opt/scalr-server/var/log/httpd# grep xListRoles *.log 
> >> > <snip> 
> >> > web.proxy.error.log:[Wed Jul 15 19:33:24.215302 2015] [proxy:error] 
> [pid 
> >> > 30341] [client 172.16.0.227:47228] AH00898: Error reading from 
> remote 
> >> > server 
> >> > returned by /services/chef/xListRoles, referer: 
> >> > https://scalr.CORP-tools.com/ 
> >> > web.proxy.error.log:[Wed Jul 15 19:45:37.132377 2015] [proxy:error] 
> [pid 
> >> > 1908] [client 172.16.0.162:36630] AH00898: Error reading from remote 
> >> > server 
> >> > returned by /services/chef/xListRoles, referer: 
> >> > https://scalr.CORP-tools.com/ 
> >> > web.proxy.error.log:[Wed Jul 15 19:52:23.847080 2015] [proxy:error] 
> [pid 
> >> > 3802] [client 172.16.0.162:36798] AH00898: Error reading from remote 
> >> > server 
> >> > returned by /services/chef/xListRoles, referer: 
> >> > https://scalr.CORP-tools.com/ 
> >> > web.proxy.error.log:[Wed Jul 15 19:54:07.965805 2015] [proxy:error] 
> [pid 
> >> > 4019] [client 172.16.0.162:36867] AH00898: Error reading from remote 
> >> > server 
> >> > returned by /services/chef/xListRoles, referer: 
> >> > https://scalr.CORP-tools.com/ 
> >> > web.proxy.error.log:[Wed Jul 15 21:23:24.401372 2015] [proxy:error] 
> [pid 
> >> > 23723] [client 172.16.0.227:49529] AH00898: Error reading from 
> remote 
> >> > server 
> >> > returned by /services/chef/xListRoles, referer: 
> >> > https://scalr.CORP-tools.com/ 
> >> > web.proxy.error.log:[Wed Jul 15 21:25:30.352198 2015] [proxy:error] 
> [pid 
> >> > 25370] [client 172.16.0.227:49592] AH00898: Error reading from 
> remote 
> >> > server 
> >> > returned by /services/chef/xListRoles, referer: 
> >> > https://scalr.CORP-tools.com/ 
> >> > web.proxy.error.log:[Wed Jul 15 22:10:13.261980 2015] [proxy:error] 
> [pid 
> >> > 3867] [client 172.16.0.162:40255] AH00898: Error reading from remote 
> >> > server 
> >> > returned by /services/chef/xListRoles, referer: 
> >> > https://scalr.CORP-tools.com/ 
> >> > web.proxy.error.log:[Wed Jul 15 22:29:21.214358 2015] [proxy:error] 
> [pid 
> >> > 10538] [client 172.16.0.227:51190] AH00898: Error reading from 
> remote 
> >> > server 
> >> > returned by /services/chef/xListRoles, referer: 
> >> > https://scalr.CORP-tools.com/ 
> >> > 
> >> > 
> >> > 
> >> > 
> >> > Every browser that I use to configure my farm will have the same 
> error, 
> >> > and 
> >> > within a second or two of the error being generated on the browser, i 
> >> > see a 
> >> > new entry in the log file shown above. 
> >> > 
> >> > I am researching further: 
> >> > 
> >> > 
> >> > 
> http://serverfault.com/questions/538086/proxyerror-ah00898-error-during-ssl-handshake-with-remote-server
>  
> >> > 
> >> > 
> >> > 
> >> > -- 
> >> > You received this message because you are subscribed to the Google 
> >> > Groups 
> >> > "scalr-discuss" group. 
> >> > To unsubscribe from this group and stop receiving emails from it, 
> send 
> >> > an 
> >> > email to [email protected]. 
> >> > For more options, visit https://groups.google.com/d/optout. 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "scalr-discuss" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to [email protected] <javascript:>. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to