Hi Jeff,

Can you attach your httpd and php log directories here?  There should be an 
error message with a better description of the reason for the failure there.

Many thanks,
Wm. Marc O'Brien
Scalr Technical Support


On Friday, January 27, 2017 at 10:37:33 AM UTC-7, Jeff Gojkovich wrote:
>
> I am sorry, I was looking at the wrong set of servers.  Sorry for the 
> confusion.  Looks like we are getting a 500 error from the requests.
>
> 127.0.0.1 (for "172.23.11.203") - - [27/Jan/2017:17:27:41 +0000] "GET 
> /api/v1beta0/account/roles/ HTTP/1.1" 500 129 "-" "python-requests/2.13.0"
>
>
> --
> Jeff
>
> On Thursday, January 26, 2017 at 6:07:56 PM UTC-7, Jeff Gojkovich wrote:
>>
>> Marc,
>>
>> The relevant section of the config file looks like this..
>>
>> app[:configuration] = {  # Add extra configuration here
>>   :scalr => {
>>     :azure => {
>>       :app_client_id => 'xxxxxx',
>>       :app_secret_key => 'xxxxx'
>>     },
>>
>>     :system => {
>>       :api => {
>>         :enabled => true,
>>         :allowed_origins => '*'
>>       },
>>     },
>>
>>     :openstack => {
>>        :instances_connection_policy => 'public'
>>     },
>>
>>
>>
>> I do not see anything in the logs that would indicate the request is even 
>> making it that far. The system is lightly used, when I try and hit the api 
>> nothing is written to the httpd or php log files.  Anything else I should 
>> look for? 
>> Does the API communicate through the same port and service as the http 
>> interface?
>>
>> --
>> Jeff
>>
>> On Thursday, January 26, 2017 at 4:14:14 PM UTC-7, Marc O'Brien wrote:
>>>
>>> Hi Jeff,
>>>
>>> Typically these types of errors are due to API failure.  Can you confirm 
>>> that you have set up APIv2 <https://api-explorer.scalr.com/> on your 
>>> Scalr server and that your workstation is contained in the allowed origins 
>>> setting?  If so, we will want to look in the Scalr server logs for errors 
>>> related to your scalr-ctl tests.  Within /opt/scalr-server/var/log you 
>>> would want to check the web error logs, as well as the php error logs.  
>>> Typically we will find something related there, but do let us know if you 
>>> have any troubles with this.  If you do, an upload of your logs here would 
>>> be useful.  Let us know if you have any questions.
>>>
>>> Many thanks,
>>> Wm. Marc O'Brien
>>> Scalr Technical Support
>>>
>>>
>>> On Thursday, January 26, 2017 at 3:44:00 PM UTC-7, Jeff Gojkovich wrote:
>>>>
>>>> Hello,
>>>>
>>>> I am trying to utilize scalr-ctl.  I have installed it successfully 
>>>> with pip and then I created a key in scalr to use in the scalr-ctl 
>>>> configure prompts, but I am having issues running any of the commands. For 
>>>> example
>>>>
>>>> $ scalr-ctl images list
>>>> Error: Server Error
>>>>
>>>>
>>>> Is there any way to make the output more verbose so that I know what is 
>>>> actually going wrong?
>>>>
>>>>
>>>> --
>>>> Jeff
>>>>
>>>

-- 
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 scalr-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to