I am trying to use node-red and openwhisk together so I can invoke openwhisk actions from node-red. I am using node-red-node-openwhisk (https://www.npmjs.com/package/node-red-node-openwhisk) for that.
I am using openwhisk outside of the bluemix locally with vagrant. I am trying to make this work according to this tutorial:
https://github.com/kpavel/openwhisk-light
but it seems impossible since I am ok until this comand
wsk action --apihost http://localhost:3000 invoke owl-test -r -p mykey myval
that I get this:
{
"error": {
"code": 4767018,
"error": "The supplied authentication is invalid"
},
"message": "GET https://openwhisk.ng.bluemix.net/api/v1/namespaces/_/actions/owl-test Returned HTTP 401 (Unauthorized) --> \"The supplied authentication is invalid\"",
"name": "OpenWhiskError",
"statusCode": 401
}
Also I cannot set the openwhisk node to work on my node-red environment because whatever apihost I am using I am getting errors.
Any suggestions?
There might be, or have been, a bug with setting the API host via a CLI parameter. It may also be necessary to run this before running your wsk action command:
wsk property set --apihost http://localhost:3000
https://github.com/apache/incubator-openwhisk-cli/issues/131
Related
I have an azure function which has this code:
run = Run.get_context()
ws = Workspace.from_config('config.json',auth=MsiAuthentication()) if not hasattr(run, 'experiment') else run.experiment.workspace
This works when I test the function locally using func start
but when I build docker image for the azure function and run the docker, it gives following error:
Message: Failed to connect to MSI. Please make sure MSI is configured correctly.
Get Token request returned http error: 400, reason: Bad Request
InnerException None
ErrorResponse
{
"error": {
"message": "Failed to connect to MSI. Please make sure MSI is configured correctly.\nGet Token request returned http error: 400, reason: Bad Request"
}
}
The identity configuration for azure function has the required roles:
Or, is there any other authentication method that I should use?
I want to add application in IIS. I have EC2 instance on AWS Amazon - Windows 2019 Server Base. I want to add application to my folder created in wwwroot folder. When I press test I get error:
Authorization Cannot verify access to path (C:\inetpub\wwwroot\myapp)
Authentication is ok
I was looking in the Internet and I've installed everything in IIS.
And when I go to my website http://localhost/myapp/ I have error:
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Detailed Error Information:
Module IIS Web Core
Notification BeginRequest
Handler Not yet determined
Error Code 0x8007000d
Config Error
Config File \\?\C:\inetpub\wwwroot\myapp\web.config
Requested URL http://localhost:80/myapp/
Physical Path C:\inetpub\wwwroot\myapp\
Logon Method Not yet determined
Logon User Not yet determined
I've resolved the error. It was the problem with certificate for Identity server. I had to add certificate and configuration for that in appsettings.json:
"IdentityServer": {
"Key": {
"Type": "File",
"FilePath": "Certificates\\certificatefile.pfx",
"Password": "mypsw"
},
"Clients": {
"FtblrApp": {
"Profile": "IdentityServerSPA"
}
}
},
Now it works
Can hyperledger-fabric get the peer node running status without entering the docker container? If so, how should I get it?
In docker-compose file, for peer service add following env variable. (You may add a different port for different services)
- CORE_OPERATIONS_LISTENADDRESS=0.0.0.0:9440
expose the port(You may expose port number as per availability). Export different port for different peer
ports:
- 9440:9440
Once all services up hit the following path for specific service(As per port defined)
curl -X GET localhost:9440/healthz
You will get a following response if the service is running.
{
"status": "OK",
"time": "2009-11-10T23:00:00Z"
}
If service is not available, you will get the following response.
{
"status": "Service Unavailable",
"time": "2009-11-10T23:00:00Z",
"failed_checks": [
{
"component": "docker",
"reason": "failed to connect to Docker daemon: invalid endpoint"
}
]
}
The Operations Service might be what you are looking for, the simple check is for "Health" and the more complex check is to look the "metrics".
It is covered in the Fabric docs.
I'm trying to deploy a small Node.js server to a Linux EC2 on AWS. This server uses the AWS JavaScript SDK. The ~/.aws/credentials and ~/.aws/config are properly filled out. Everything works when I run the server by node index.js or npm start, but if I run it using systemd, I get the following response:
{ message: 'Could not load credentials from any providers',
retryable: false,
time: 2018-07-23T20:12:59.057Z,
code: 'CredentialsError' }
For some systems ~ becomes / when run from a service. This means the path is /.aws/credentials. For your system try copying "~/.aws" to "/root/.aws". Then try copying to "/.aws". One of these will work.
You can also use a json file and specify that when creating your client.
Create the file "/mysite/aws_config.json" with the following contents:
{
"accessKeyId": "YOUR_ACCESS_KEY_ID",
"secretAccessKey": "YOUR_SECRET_ACCESS_KEY",
"region": "YOUR_REGION"
}
Then load the credentials with this statement:
AWS.config.loadFromPath('/mysite/aws_config.json');
This way you can keep your site's configuration in one directory.
There are many methods to specify credentials. The AWS documentation for node.js SDK has lots more.
When I try PUTing my Foxx service in ArangoDB I get this error:
{
"error": true,
"code": 404,
"errorNum": 404,
"errorMessage": "unknown path '/_api/foxx/service?teardown=false&setup=true&legacy=false&mount=/upload&name=upload&version=1&development=true&manifest={%20%20%22engines%22:%20{%20%20%20%20%22arangodb%22:%20%22^3.0.0%22%20%20},%20%20%22main%22:%20%22index.js%22,%20%20%22scripts%22:%20{%20%20%20%20%22setup%22:%20%22scripts/setup.js%22%20%20}}'"
}
This is a call from Postman and within Postman it is a copy/paste from a working call to an other server. That is why this confuses me.
Also, using the Web Interface, I can upload this fine.
What does this error message mean exactly?
Arango: 3.0.12
Log stays empty.
This was probably a bug in Arango. I run CentOS7 and there is more than 1 (!!) repo at arangodb.com for CentOS7, also probably a bug. After reinstalling the repo for CentOS7 the software upgraded, completely destroyed SSL but the deployment is working now :)