I am trying to create a Serverless API backend using the AWS console but o matter which options I choose I always get the same build error
Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: cdk synth > ../template-export.yml. Reason: exit status 1
Is anyone able to shed any light on this?
Related
I had instal mlrun with kubernates, i had tried the to execute the 02-model training tutorial code in jupyter-lab, so everything works fine till model serving, then i tried to deploy the serving function then it shows as error listed bellow :
Failed to deploy. Details:
Error - the server could not find the requested resource
...//nuclio/pkg/platform/kube/functionres/lazy.go:757
Call stack:
Failed to create resource
...//nuclio/pkg/platform/kube/functionres/lazy.go:757
Failed to create/update HPA
...//nuclio/pkg/platform/kube/functionres/lazy.go:230
Failed to create/update function
.../platform/kube/controller/nucliofunction.go:213
2023-01-17 18:42:53,721 [error] Nuclio function failed to deploy: {'function_state': 'error'}
error in nuclio.. please help me regarding this
I am using terraform on my Mac system, and terraform apply results with below error
Error: command "bash" failed with no error message
on ssm.tf line 7, in data "external" "ssm-dynamic-general":
7: data "external" "ssm-dynamic-general" {
However there is nothing wrong in ssm.tf file, same runs perfectly fine in my another system.
Can some one please let me know what i am missing here?
You might have done what I accidentally did: not follow the external program protocol:
https://www.terraform.io/docs/providers/external/data_source.html#external-program-protocol
In my particular case, I failed to send the errors that were coming from my program to standard error. Instead, those errors were going to standard out.
That's why Terraform wasn't able to report on those errors.
So if you send any and all errors from your program to standard error using > &2, you should be able to see those errors when you run terraform plan.
I am having problems trying to deploy the rest server with persistence storage (mongo db) I ge this message when deploying the rest server:
docker logs -f rest
[2018-03-12 00:01:13] PM2 log: Launching in no daemon mode
[2018-03-12 00:01:14] PM2 log: Starting execution sequence in -fork mode- for app name:composer-rest-server id:0
[2018-03-12 00:01:14] PM2 log: App name:composer-rest-server id:0 online
WARNING: NODE_APP_INSTANCE value of '0' did not match any instance config file names.
WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
Discovering types from business network definition ...
Connection fails: Error: Error trying to ping. Error: Error trying to query business network. Error: REQUEST_TIMEOUT
It will be retried for the next request.
Exception: Error: Error trying to ping. Error: Error trying to query business network. Error: REQUEST_TIMEOUT
Error: Error trying to ping. Error: Error trying to query business network. Error: REQUEST_TIMEOUT
at _checkRuntimeVersions.then.catch (/home/composer/.npm-global/lib/node_modules/composer-rest-server/node_modules/composer-connector-hlfv1/lib/hlfconnection.js:699:34)
at
at process._tickDomainCallback (internal/process/next_tick.js:228:7)
[2018-03-12 00:07:03] PM2 log: App [composer-rest-server] with id [0] and pid [14], exited with code [1] via signal [SIGINT]
I am using composer v.18
is there any work around to fix this error. when I run the composer-rest- server alone it work. but if I try to add the mongodb it does not work
I'm trying to use Bash to run aws-cli devicefarm schedule-run to run instrumentation testing:
TEST_STRUCTURE=type\=INSTRUMENTATION,testPackageArn=$TESTS_UPLOAD_ARN
aws devicefarm schedule-run --project-arn $PROJECT_ARN --app-arn $APP_UPLOAD_ARN --device-pool-arn $DEVICE_POOL_ARN --test $TEST_STRUCTURE
But keep receiving an error:
A client error (ArgumentException) occurred when calling the ScheduleRun operation: Missing or unprocessed resources.
How can I resolve this error, I'm not sure what values I am not passing correctly...
I'm using protractor with jasmine framework to run my automation scripts. The test is failing with the following error:
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
Warning: Tests failed, protractor exited with code: 3 Use --force to continue.
while trying to get attribute value of an element.
But, I'm able to perform clicks and verifyElementPresent kind of actions for the same web element..
Could any one please help me out of this how to overcome this error.
Thanks in advance..