Closed sercanaktas closed 9 years ago
What value do you currently have set for sl.api_timeout
?
It is not set, so I assume it is using the default 60 secs.
Try increasing that but given the Runtime exceptions above it looks like it may occasionally be loosing packets as well so it might be a general network issue.
Hi again,
I increased the sl.api_timeout to 500 secs and I am still getting the same errors. Though a new one is added;
Exception class: #Class:0x4277eb0 Exception message: execution expired
Is this a windows box? Seems similar to this upstream issue, see if increasing the winrm timeout helps if you are building a windows box. If not theres also the sl.provision_timeout
you can try setting.
It is CentOS
$ ./vagrant-softlayer-credentials software list -y
ERROR: Failed to perform action list on credential category software: execution expired
I started hitting this myself this morning and have never actually seen it before it, happened when my internet went down due to the snowstorm in the North East so it probably is just a general network issue.
I would like to place some 'puts' commands to see which API calls are made by vagrant-softlayer and what are their responses. Any suggestions where in which file I should do that?
Theres a few calls it puts in depending on what options you select but the general:
There may also be the joining of the load balancer if you have that configured. But the above would be the important points where it interfaces with softlayer_api
and the API itself.
Thanks I will look into it more and keep this updated
More information for you;
When I run vagrant from a linux machine, it runs without a problem. Sadly our development machines are Windows and we are using Windows Command Prompt since Cygwin has problems with softlayer. And in Windows machine I get these problems. Do you have any insight on this?
Cygwin has problems with softlayer
I havent used SL or vagrant-softlayer on Windows at all so Im not sure what you are hitting here. Other than a possible difficultly in ensuring you have all the right dependencies installed or possible issues with Cygwin -> Windows path transformations I dont see why it wouldnt work.
With the info provided above all I can tell is it looks like a general network issue, but if you want to provide further details we can reopen and try to continue troubleshoot.
Hello,
I've been encountering the following errors quite frequently since last week. It looks like it's occurring in warden.rb. I've attached a stack trace with debug flag on.
The stack trace is the same though the exception is different.
Sample stack trace below: