Istio Primary Remote multi cluster error - unsupported service type ExternalName - amazon-eks

I followed here.
In next step(verify the installation),
When I create deployment in cluster2(remote cluster), sidecar injector not working like below...
kubectl get event -n sample
LAST SEEN TYPE REASON OBJECT MESSAGE
42m Warning FailedCreate replicaset/helloworld-v2-79bf565586 Error creating: Internal error occurred: failed calling webhook "namespace.sidecar-injector.istio.io": failed to call webhook: Post "https://istiod.istio-system.svc:443/inject/cluster/cluster2/net/network1?timeout=10s": unsupported service type "ExternalName"
2m45s Warning FailedCreate replicaset/helloworld-v2-79bf565586 Error creating: Internal error occurred: failed calling webhook "namespace.sidecar-injector.istio.io": failed to call webhook: Post "https://istiod.istio-system.svc:443/inject/cluster/cluster2/net/network1?timeout=10s": unsupported service type "ExternalName"
53m Normal ScalingReplicaSet deployment/helloworld-v2 Scaled up replica set helloworld-v2-79bf565586 to 1
41m Normal ScalingReplicaSet deployment/helloworld-v2 Scaled up replica set helloworld-v2-79bf565586 to 1
Is this issue about firewalld ? (I used AWS EKS v1.24)
When I searched something about this, Other people's message is context deadline exceeded in here...
Can anybody help me? :(
Search Internet, and re install istio at all...

Related

node js api in hyperledger fabric

2022-09-14T07:37:21.040Z - error: [DiscoveryResultsProcessor]: parseDiscoveryResults[User] - Channel:mychannel received discovery error:failed constructing descriptor for chaincodes:<name:"User" >
Failed to submit transaction: Error: DiscoveryService: User error: failed constructing descriptor for chaincodes:<name:"User" >
when I hit API from post man i receive this error
This error usually comes when the chaincode name given is wrong. Make sure the chaincode('User' in this case) is committed to channel mychannel before sending transactions using SDK.

Unable to instantiate the chaincode in muticloud setup

I am trying to achieve the multicloud architecture. My network has 2 peers, 1 orderer and a webclient. This network is in Azure. I am trying to add a peer from Google Cloud Platform to the channel of Azure. For this, I created a crypto-config for 3rd peer from Azure webclient. But in the crypto-config, I made the changes like peers in Azure have their own certificates while for the 3rd peer, I placed the newly created certificates. Now I can install, instantiate, invoke and do queries in the peers(1 and 2). And I can install the chaincodes in 3rd peer. But I am unable to instantiate the chaincodes.
Getting the following error: Error: could not assemble transaction, err proposal response was not successful, error code 500, msg error starting container: error starting container: Post http://unix.sock/containers/create?name=dev-(CORE_PEER_ID)-documentCC-1: dial unix /var/run/docker.sock: connect: permission denied
Can anyone guide me on this.
Note: All the peers, orderer, webclient are running in different vm(s)
#soundarya
It doesn’t matter how many places your solution is deployed
The problem is you are running docker by using sudo command try to add docker to sudo group
Below block will help you out
https://www.digitalocean.com/community/questions/how-to-fix-docker-got-permission-denied-while-trying-to-connect-to-the-docker-daemon-socket
To learn more concept about docker.sock
You can refer to my answer in another Can anyone explain docker.sock

Labview Instrument Error: A service request has not been received for the session

I'm trying to get a Labview VI working. However, I'm getting an error on the KE6485 Multi-read sub-VI with the error "Driver Status: (Hex 0xBFFF004A) Error - A service request has not been received for the session". Does anyone have a suggestion on steps I could take to fix this?

spring-xd-1.3.1.RELEASE-yarn, submit error

If anyone has seen this issue before, please help me.
Here is my steps.
And, do I need to start from opt/spring-xd-1.3.1/xd/bin/xd-admin and xd-container before running below commands from opt/spring-xd-1.3.1.RELEASE-yarn/bin/
Thank you in advance.
bin/xd-yarn push
bin/xd-yarn submit => having below error.
Error executing a spring application; nested exception is org.springframework.yarn.YarnSystemException: Failed on local exception: java.io.IOException: com.google.protobuf.InvalidProtocolBufferException: Protocol message end-group tag did not match expected tag.; Host Details : local host is:

WSO2-ESB-4.8.1-ERROR - AbstractPersistenceManager Unable to handle service initialization. Resource does not exist at path

I'm trying to run WSO2ESB manager node sh /home/ec2-user/wso2esb-4.8.1/bin/wso2server.sh -Dsetup. But get this errors in log:
[2015-05-18 12:04:26,644] ERROR - AbstractPersistenceManager Unable to
handle service initialization. Service: echo
org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException:
Resource does not exist at path
/_system/config/repository/transports/https/listener
[2015-05-18 12:04:26,651] ERROR - DeploymentInterceptor Exception
occurred while handling service update event. {super-tenant}
org.wso2.carbon.core.persistence.PersistenceException: Unable to
handle service initialization. Service: echo
Caused by:
org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException:
Resource does not exist at path
/_system/config/repository/transports/https/listener
It seems like either you have not configured the database settings or registry has not mounted properly. Please refer to this for more information.