Setting up eucalyptus cloud on my laptop has become a nightmare for me.
When I run the command euca-describe-availability-zones, it shows up as expected. It shows all free/max values correctly. However, when I run euca-run-instance it says that no resources av.
How can this be fixed?
you are not giving enough information to really understand what the problem is. If you check on the sticky post at http://open.eucalyptus.com/forums/eucalyptus-support-0 for generic info needed. In your case, can you post the output of euca-describe-availability-zones verbose (ran with the admin credentials) and the output of euca-describe-addresses (again with admin credentials)?
cheers
graziano
Related
I know a similar question has been asked (link), but the response didn't work for me.
TLDR: I keep running into errors when trying to authenticate Google Cloud Storage in RStudio. I'm not sure what is going wrong and would love advice.
I have downloaded both the GCS_AUTH_FILE (created a service account with service admin privileges'--downloaded the key associated with the service account) and also downloaded GAR_CLIENT_WEB_JSON by creating a OAuth 2.0 Client ID and downloading that associated JSON file.
I've tried authenticating my Google Cloud Storage in several ways and hit different errors.
Way 1-automatic setup:
gcs_setup()
Then I select any one of the options, and get the error: Error in if (file.exists(local_file)) { : argument is of length zero And that error happens no matter which of the three options I select.
Way 2 - basic, following manual setup instructions from the package:
Sys.setenv("GCS_DEFAULT_BUCKET" = "my-default-bucket",
"GCS_AUTH_FILE" = "/fullpath/to/service-auth.json")
gcs_auth()
In this case, GCS_AUTH_FILE is the file that I mentioned at the beginning of this post, and the GCS_DEFAULT_BUCKET is the name of the bucket. When I run the first line, it seems to be working (nothing goes awry and it runs just fine), but when I run gcs_auth() I get taken to a web browser page that states:
"Authorization Error
Error 400: invalid_request
Missing required parameter: client_id"
Way 3: Following the method from the post that I linked above
This way involves manually setting the .Renviron file w/ the GCS_AUTH_FILE and GAR__CLIENT_WEB_JSON locations, and then running gar_auth(). And yet again, I get the exact same error as in Way 2.
Any ideas about what could be going wrong? Thanks for your help. I wasn't sure how to put in totally reproducible code in this case, so if there is a way I should do that, please let me know.
I was using Bing Custom Search API for the past week with no problems thanks to the free trial, but today, I tried upgrading to the S1 plan, since the API was sending error messages. I tried regenerating the key as well, but despite doing both of these things, I was still getting errors and unable to use the API.
However, I was able to make calls using: https://www.customsearch.ai/applications, where I was able to use my API key to test endpoints and get the results I expected. What baffles me is that my nodejs code which hasn't been modified aside from the subscription key should still work with the upgraded plan, but it doesn't.
I should be able to help here. Let us do little bit of troubleshooting once:
First go to https://www.customsearch.ai/applications -> click on your instance name ->Click on "Production" tab on top -> Try making API call on this page by providing Query and Subscription key you got. If this works, go to the next step.
On the page mentioned above you would have seen Custom Configuration ID and Subscription Key. Make sure those two are same in your node.js code. Ideally this should work.
If it still doesn't work, please share your error code so that I can get better understanding of the error you are getting.
Since I installed munin and enabled alerts, it has been intermittently sending me this for four of my hard drives:
WARNINGs: smartctl_exit_status is 4.00 (outside range [:1]).
The munin documentation says:
The ignoreexit parameter can be useful to exclude some bits in smartctl exit code, which is a bit mask described in its main page, from consideration.
So I added the following to /etc/munin/plugin-conf.d/munin-node:
[smart_sdg;smart_sdh;smart_sdi;smart_sdj]
env.ignoreexit 4
(Note that this corresponds with the four drives sending the alerts.)
Alas, the alerts keep coming. I can't make them stop and I don't understand why. Is my config location wrong? Am I doing the configuration wrong? Why isn't this working? Any help?
It turns out that I had an old version of Munin and it doesn't support the env.ignoreexit parameters. I grabbed the latest version of the plugin from Munin's repository and it seems to work.
This was a fun exploration. I wish Munin threw errors when you gave it configurations it didn't recognize, but alas.
I'm getting the following the error message in my content delivery logging:
com.tridion.smarttarget.utils.AmbientDataHelper - can't find defined
trigger-types in claim store (check if your smarttarget cartridge is up and running)
I've checked out my smarttarget_conf.xml and have confirmed the web services are up and running. The one that is failing (or returns a 404 via broswer) is the following:
<Endpoint>http://servername:8180/fredhopper/config/trigger-types</Endpoint>
But having read through the documentation and the forum, i'm under the impression this is correct and that the url doesn't respond to GET requests.
So I'm assuming everything is set up correctly, in my smarttarget_conf.xml, I'm hoping is anyone has some pointers for me to have a look into to resolve this issue.
Thanks in advance.
Solution
The issue here is that my trigger-types.xml file was not correctly formed on the FAS (Fredhopper server). I'm giving Jeremy the winning answer below as he spotted my issue behind the scenes.
Thanks Jeremy - I hope anyone reading this up-votes your answer
The port of my local SmartTarget instance is 8180, not 8080. Perhaps this is the same for you?
I am getting the following exception when trying to run the MakeCall example code:
com.skype.NotAttachedException
at com.skype.Utils.convertToSkypeException(Utils.java:36)
at com.skype.Skype.setDebug(Skype.java:116)
at com.skype.sample.MakeCall.main(MakeCall.java:26)
Caused by: com.skype.connector.NotAttachedException
at com.skype.connector.Connector.assureAttached(Connector.java:580)
at com.skype.connector.Connector.addConnectorListener(Connector.java:604)
at com.skype.connector.Connector.addConnectorListener(Connector.java:591)
at com.skype.connector.Connector.setDebug(Connector.java:209)
at com.skype.Skype.setDebug(Skype.java:114)
... 1 more
Now, I have not provided any sort of API credentials, so I kind of expect it to fail. My question then, is how do I provide whatever credentials necessary to attach my connector? The documentation on Skype4Java seems pretty slim.
After not getting any tips here, I have cross-posted this question on the Skype community forum as well.
Had same thing, went on Skype->Options->Advance->Manage Other Programs access to Skype...selected
Java.exe from the list and set option to allow. Working perfect now.
If you have the dbus dependency installed, then make sure to start skype on the command line with the "--use-system-dbus".
https://developer.skype.com/Docs/ApiDoc/src#Linux
Once skype is running and you then start the java program, you'll be prompted to allow your java program to access skype.