I am trying to launch a task in my local minikube by using spring cloud stream which is using my custom source to post a TaskLaunchRequest message to TaskLauncherSink module (spring-cloud-starter-stream-sink-task-launcher-kubernetes). I am not seeing any exception but unable to launch a task when this stream deployed and running.
Initially got connection refused error in sink module with the config server url http://localhost:8888. But, now I have disabled that in my sink module by adding a property spring.cloud.config.enabled=false in bootstrap.properties.
No exception right now but not able to launch the task. Could you please help me to resolve this issue?
Related
I am getting the below error whilst running my Python Azure Function on the local machine in VSCode.
For clarification the message is:
The listener for function 'Functions.IoT_Data-Handler' was unable to
start. Microsoft.Azure.EventHubs.Processor: Encountered error while
fetching the list of EventHub PartitionIds. System.Private.CoreLib: A
connection attempt failed because the connected party did not properly
respond after a period of time, or established connection failed
because connected host has failed to respond.
This error has never occurred before in the time I have started using VSCode for Azure functions (since last September). The only thing that has changed recently is that I now deploy this function within an Azure Function premium resource, but really that should not matter in the dev environment.
For information, this function is hooked up to an Azure IoT-Hub endpoint and is simply reading and processing the uplink data before saving it to an Azure SQL database.
Can anyone offer any advice?
Check if my below findings help to fix your issue:
As #PeterBons said, check the connection string given correctly in the local.settings.json:
Whatever the Event Hub Endpoint/IoT Hub Endpoint Connection String given in the file local.settings.json, that property name should be mapped in the function.json file.
Try replacing the IoT Hub Connection String without the consumer group name as mentioned in this GitHub Issue #5512
I found similar issues in the SO 1 & 2 which will be helpful to fix your issue.
I'am submitting a connector to kafka. The connector created is sftp connector. Now when the password is wrong the connector sends back success response when the connector fails. The password is wrong response is not given at that time. This is a single scenario there could be mutliple scenarios like this. Now when I use the <host>/connectors/<connector-name>/status, I get the error saying failed to establish connection. But this endpoint has a little delay. If I'am immediately trying after creating the connector, I may not get any response(404).
What is the proper way of handling this using the status api call.Is there any delay that needs to be used before firing this API. Or can it be handled while submitting the connector to API?
When you create the connector, it naturally needs to load the JAR(s) responsible for the tasks, then distribute the tasks to actually start the connector code (which is responsible for connecting to the SFTP server with the connection details).
Therefore, the delay is natural, and there's no way to know your connection details are incorrect unless you try to use them before launching the connector.
I have created an application in IBM cloud - using the Node-Red starter. The app has been running with no errors for 2 weeks.
I have installed an additional node:"node-red-dashboard":"2.9.6", by adding this in the package.json file.
When deploying within Node-Red, the app crashes with error "Cannot connect to server".
Then, the page is no longer reachable with error "500 Error: Failed to establish a backside connection".
I have tried to restart the app, which allows it to run, again until I deploy again.
This could be an intermittent problem with the toolchain or possibly due to the extra memory requirement placed on the build with the additional node.
Is there a reason why you have not used the manage palette option to install the new nodes?
If you are still getting the error, try increasing the memory allocated to node-red in the manifest.yml file, or try removing the additional node to get node-red to rebuild.
I have kie workbench and kie execution server.
Execution server is runnig on
http://localhost:7080/kie-server/
and I can check its availability via request to services/rest/server/.
Also I have a workbench, running on
http://localhost:8080/kie-wb
and I can work with it via UI (direct REST calls cause unauthorized response).
I want to register new server with a container and set as endpoint my execution server on 7080 port.
However in workbench via scanner it's unable to find any endpoint - so it seems my execution server is unable to connect to workbench
I start it with these parameters
D:\installed\apache-tomcat-7.0.52-Copy\bin>set JAVA_OPTS= -Dorg.kie.server.persistence.dialect=oorg.hibernate.dialect.H2Dialect -Dorg.kie.server.persistence.ds=jdbc/jbpmB
-Dorg.kie.server.controller=http://localhost:8080/kie-wb/rest/controller -Dorg.kie.server.id=first-kie-server
Where I set workbench controller as localhost:8080/kie-wb.
What's the problem?
I am using 6.3 versions for both workbench and server.
The problem is solved.
The culprit was me. Accidentally I used snapshot of execution server artifact. And it wasn't trying to connect to controller.
When I used the proper artifact it started to work fine.
I'm running into an error using the migration utility after installing v1.0.1.006. I have previously used v1.0.1.001 to migrate a sandbox/test project with success. I attempted to use the .001 version to migrate the full project but ran into the Processing blocked problem. The recommendation was to update to the .006 version.
Now after running for 30-60 minutes, I get the following error:
com.opshub.eai.metadata.MetadataException: OpsHub-014371: Could not instantiate metadata implementation for xxx to xxx| TFS Source 1409181936489 ALM TFS 1409181936495, due to ; nested exception is: java.net.SocketTimeoutExeption: Read timed out.
Restarting the app appears to make the process resume, only to have the same error repeat after another 30-60 minutes. As a side-note, the Work Item never shows me a count like it did in version .001, it just says Running.
Connection refused error is logged continuously on your instance. From the logs it looks like your background services are not running properly.
Have you installed anything on port 8989 or 9090. Port 9090 is service port for tfs/vso side communications, but as per the logs service is not running or not responding properly. Also from the utility ui logs we captured that background opshub server service also not working.
Can you please make sure following things.
"OpsHub Visual Studio Online Migration Utility" is configured as
Manual service and not running before you start migration utility
This service will be automatically started by migration utility, it
will also spawn process of tfs proxy on 9090 port.
Port 8989 and 9090 is free and no other processes are occupying it
during migration utility execution.
Regards,
OpsHub Support