I am using terraform to create my architecture.
Adding the following rows on the resource ecs_task_definitions
“runtimePlatform”: {
“operatingSystemFamily”: “LINUX”,
“cpuArchitecture”: “ARM64”
},
The task does not run. This is the error
STOPPED (CannotPullContainerError: inspect image has been retried 1 time(s): failed to resolve ref "********.dkr.ecr.eu-central-1.amazonaws.com/ecr-repo-prod:latest": **********.dkr.ecr.eu-central-1.amazonaws.com/ecr-repo-prod:latest: not found)
Do you know where is the problem?
Related
Error: Deploying program failed: Error processing Instruction 1: custom program error: 0x1
There was a problem deploying: Output { status: ExitStatus(unix_wait_status(256)), stdout: "", stderr: "" }.
What is this error about? How do I fix it?
I have set the config url to the devnet, and I have already airdropped into my wallet sufficient funds to deploy on the devnet.
Found out that the "custom program error: 0x1" error message is another variation of the Insufficient Funds error. Solved this by airdropping my wallet significantly more SOL. To deploy an NFT with Metadata (using Anchor and Metaplex) my transaction used ~4 SOL, far more than I expected.
I am trying to setup pcf in Ubuntu20. While i am setting up it, its notable to create and found
x509: certificate has expired or is not yet valid
Here are deploy bash log file as follows. Can someone help me out ?
deploy-bosh.log
Starting registry... Finished (00:00:00)
Uploading stemcell 'bosh-warden-boshlite-ubuntu-xenial-go_agent/170.16'... Skipped [Stemcell already uploaded] (00:00:00)
Started deploying
Deleting VM '654e6637-3333-4879-a5a7-26a6066585ab'... Finished (00:00:14)
Creating VM for instance 'bosh/0' from stemcell '211465a3-381f-4fdd-83ba-9591803442f9'... Finished (00:00:05)
Waiting for the agent on VM '7091e293-6518-4008-b337-cbbf2d273eae' to be ready... Failed (00:00:04)
Failed deploying (00:00:23)
Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)
Deploying:
Creating instance 'bosh/0':
Waiting until instance is ready:
Post https://mbus:<redacted>#10.144.0.2:6868/agent: x509: certificate has expired or is not yet valid
Exit code 1
When registering an Amazon SSM Agent, it registers successfully in the SSM Managed Instances console, but the connection shows "Connection Lost".
When I try to start the service manually, I get the following error:
Error occurred fetching the seelog config file path: open /etc/amazon/ssm/seelog.xml: no such file or directory
Initializing new seelog logger
New Seelog Logger Creation Complete
2020-12-09 10:20:01 ERROR error occurred when starting amazon-ssm-agent: failed to start message bus, failed to start health channel: failed to listen on the channel: ipc:///var/lib/amazon/ssm/ipc/health, address in use
How exactly do I solve this? I've tried to restart the service a few times but no luck.
I was able to fix this issue by stopping the agent and purging the /var/lib/amazon/ssm/ipc directory
service amazon-ssm-agent stop
rm -rf /var/lib/amazon/ssm/ipc
service amazon-ssm-agent start
I am new to blockchain platforms and eris. trying to get a private blockchain up and running in my Mac OS from here
https://monax.io/docs/tutorials/getting-started/
all went fine until deployment of a smart contract. While performing "eris pkgs do" command, getting below error.
Performing action. This can sometimes take a wee while
Error connecting to node (tcp://chain:46657) to get chain id: Post http://chain:46657: dial tcp 198.105.244.228:46657: getsockopt: connection refused
Could not perform pkg action service: Could not perform pkg action: Container interactive-73d789a8-4693-4a4c-bcf2-ae2005a12d23 exited with status 1
update:
I am now able to get past this error. Followed the Mona tutorial for docker machines.
This took me to the compiler error (error scenario 6 in getting started session).
Now getting below error. the IP address is taken from the active machine by issuing command "docker-machine ls".
GinguVjs-MacBook-Pro:idi ginguvj$ eris pkgs do --chain simplechain --address $addr --compiler 192.168.99.101:2376
Performing action. This can sometimes take a wee while
Executing Job defaultAddr
Executing Job setStorageBase
Executing Job deployStorageK
failed to send HTTP request Post 192.168.99.101:2376: unsupported protocol scheme ""
Error compiling contracts: Compilers error:
Post 192.168.99.101:2376: unsupported protocol scheme ""
Could not perform pkg action service: Could not perform pkg action: Container interactive-671e81dc-4a1b-4e1e-b1ad-b51d955297b1 exited with status 1
GinguVjs-MacBook-Pro:idi ginguvj$
The compilation issue was resolved by adding a "-z" to the end.
"eris pkgs do --chain simplechain --address $addr -z"
I have started to receive a 402 error when accessing my CoreOS cluster. It has been working fine up until a day ago. Anybody has any ideas why I'm receiving this error? I am using the stable channel on EC2.
$ fleetctl list-machines
E0929 09:43:14.823081 00979 fleetctl.go:151] error attempting to check latest fleet version in Registry: 402: Standby Internal Error () [0]
Error retrieving list of active machines: 402: Standby Internal Error () [0]
In this case etcd does not currently have quorum. The "Standby Internal Error" signifies that the node is attempting to act as a standby but is failing to redirect you to the active node. Repairing the etcd issue will fix the problem. Check on the status of etcd by running:
journalctl -u etcd.service on each of the nodes should give you the information that you need to repair etcd in this case.