When I use distcc, it fail with message below:
dcc_writex warning: failed to write: Transport endpoint is not connected
This is not happend at every time, does anybody has idea on this?
Related
The error states that :"Exception User-Unhandled
Microsoft.Azure.EventHubs.Processor.EventProcessorConfigurationException: 'Encountered error while fetching the list of EventHub Partitionids'
Inner Exception
SocketException: A connection attempt failed because the connected party did not properly respond after a va period of time, or established connection failed because connected host has failed to respond."
First time I am not getting this exception after clearing the cache and restarting my laptop . Post that same issue occurs . Is there any way to check on this ?
To resolve this Exception User-Unhandled Microsoft.Azure.EventHubs.Processor.EventProcessorConfigurationException: 'Encountered error while fetching the list of EventHub Partitionids' Inner Exception SocketException: A connection attempt failed because the connected party did not properly respond after a va period of time, or established connection failed because connected host has failed to respond." error, try the following way:
As suggested by MayankBargali, check whether the required port is open or not.
Make sure to open ports 443/5671/5672
You can use the PortQry tool to query your eventhub namespace on these ports to confirm if these are blocked or not.
References: Microsoft.Azure.EventHubs.Processor: Encountered error while fetching the list of EventHub PartitionIds and In Azure Eventhub reciever giving "Encountered error while fetching the list of EventHub PartitionIds" error
I have a basic Pulsar app, and when I try to connect to Pulsar, I get this exception:
2021-03-10 14:38:26.107 WARN 7 --- [r-client-io-1-1]
o.a.pulsar.client.impl.ConnectionPool : Failed to open connection
to my-pulsar-server-ms-tls.domain.com:6651 :
io.netty.channel.ConnectTimeoutException: connection timed out:
my-pulsar-server-ms-tls.domain.com/10.80.13.38:6651 2021-03-10
14:38:26.212 WARN 7 --- [al-listener-3-1]
o.a.pulsar.client.impl.PulsarClientImpl : [topic:
persistent://myTenant/myNamespace/myTopic]
Could not get connection while getPartitionedTopicMetadata -- Will try
again in 100 ms
My Pulsar client is pretty basic:
PulsarClient.builder()
.serviceUrl(serviceUrl)
.authentication(AuthenticationFactory.token(authToken))
.tlsTrustCertsFilePath(serverCertificateFilePath.toString())
.enableTlsHostnameVerification(false)
.allowTlsInsecureConnection(false)
.build();
The producer is also pretty basic and looks like this:
pulsarClient.newProducer(Schema.STRING)
.topic(topic)
.create();
I've verified that the token and TLS cert are correct. I've also tried connecting a consumer from this same environment and got a similar exception, and I know that others with the same code are able to connect to the same Pulsar cluster from other environments. What is the issue?
Your connection is getting blocked by a firewall or network issue.
Verify that you can establish a connection to your endpoint my-pulsar-server-ms-tls.domain.com:6651 from your environment.
If you're able to run a network packet dump (like tcpdump), that should make it obvious if you're not able to establish a connection.
You can also try running curl my-pulsar-server-ms-tls.domain.com:6651, and if you get back some html, that means you were able to reach the server. However, if you get Could not resolve host, then you were blocked by the network configuration (such as a missing route) or firewall.
I was following the Creating Your Private Network tutorial.
I have a running the bootnode in my local machine, and I want a new participant from AWS to join in my network. But somehow, i keep getting 0 peers.
I added the logs RUST_LOG=debug and found this:
2021-08-04 02:06:40.563 DEBUG tokio-runtime-worker libp2p_dns: Dialing /ip4/130.105.xxx.xxx/tcp/30333/p2p/12D3KooxxxNr
2021-08-04 02:06:40.563 DEBUG tokio-runtime-worker libp2p_tcp: dialing 130.105.xxx.xxx:30333
2021-08-04 02:06:40.563 DEBUG tokio-runtime-worker libp2p_swarm: Connection attempt to PeerId("12D3KooxxxNr") via "/ip4/130.105.xxx.xxx/tcp/30333/p2p/12D3KooxxxNr" failed with Transport(Other(Custom { kind: Other, error: Timeout })). Attempts remaining: 2.
2021-08-04 02:06:40.563 DEBUG tokio-runtime-worker libp2p_kad::behaviour: Last remaining address '/ip4/130.105.xxx.xxx/tcp/30333/p2p/12D3KooxxxNr' of peer '12D3KooxxxNr' is unreachable: Pending connection: Transport error: Timeout has been reached.
I read it somewhere, that it takes 5 minutes to connect.
How do I increase the timeout period?
I think your local machine doesn't have a public IP address.
I recommend you to set your AWS as the bootnode then connect from your local machine.
Upon using the DataFacotry Connector to Snowflake, I consistently get the error message below. Does anyone have any idea how to fix this?
I am using an Azure-managed Integration Runtime.
ERROR [HY000] [Microsoft][Snowflake] (4) REST request for URL
https://xxxxxxx.east-us-2.azure.snowflakecomputing.com.snowflakecomputing.com:443/session/v1/login-request?requestId=2fb149b1-5f57-47ad-a471-8a8db718336c&request_guid=25dcec4f-f680-4f18-b018-363084843708&databaseName=DEMO_DB&warehouse=COMPUTE_WH failed: CURLerror (curl_easy_perform() failed) - code=60 msg='SSL peer
certificate or SSH remote key was not OK'.
ERROR [HY000] [Microsoft][Snowflake] (4) REST request for URL
https://xxxxxxx.east-us-2.azure.snowflakecomputing.com.snowflakecomputing.com:443/session/v1/login-request?requestId=2fb149b1-5f57-47ad-a471-8a8db718336c&request_guid=25dcec4f-f680-4f18-b018-363084843708&databaseName=DEMO_DB&warehouse=COMPUTE_WH failed: CURLerror (curl_easy_perform() failed) - code=60 msg='SSL peer
certificate or SSH remote key was not OK'.
Activity ID: 376547c0-6604-454d-b881-544cb6e7811a.
Probably not a good idea, from a security perspective, to leave your account id visible like this.
Anyway, the issue is probably that you have mis-configured your connection as snowflake.com is repeated: ...snowflakecomputing.com.snowflakecomputing.com
I am trying to set autoAck to false while reading from azure service bus queue, which I am connecting using amqp. Below is the code.
from("amqp:queue:testqueue?autoAck=false&concurrentConsumers=1")
But I am getting an error msg:
Failed to create route route1: Route(route1)[[From[amqp:queue:testqueue?autoAck=false&concu... because of Failed to resolve endpoint: amqp://queue:testqueue?autoAck=false&concurrentConsumers=1 due to: Failed to resolve endpoint: amqp://queue:testqueue?autoAck=false&concurrentConsumers=1 due to: There are 1 parameters that couldn't be set on the endpoint. Check the uri if the parameters are spelt correctly and that they are properties of the endpoint. Unknown parameters=[{autoAck=false}]
I am trying to process the messages from the service bus queue but don't want them to be removed till the time processing is not complete.
I finally found the answer, in order to remove the messages from the queue only when a consumer has accepted the message and acknowledged that it was successfully processed, you need to add "acknowledgementModeName" to the route
from("amqp:queue:testqueue?acknowledgementModeName=CLIENT_ACKNOWLEDGE&concurrentConsumers=1")
For more clarification visit this page http://camel.apache.org/jms.html