Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Talend Cloud AWS EU Scheduled Outage: Starting Tues 26 May 21:00 CEST with expected completion Wed 27 May 01:00 CEST
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Connection error in Talend Cloud Pipeline Designer

I have created a new Database connection in Talend Cloud Pipeline Designer. When clicking the check connection, it is showing the error as

 0683p000009M9MS.png                                                     

For all the connections it is showing the same error. Kindly give some solutions to solve this. Its urgent.

Thanks in advance.

Labels (3)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

Hello @Sanjaytha,

 

Thanks for using Talend Pipeline Designer.

 

I assume you set up a Remote Engine for Pipelines. If this is not the case, please let me know.

 

Where did you deploy your Remote Engine for Pipelines ? Did you restart the machine where your Remote Engine for Pipelines is running ?

In fact this error can happen when the Remote Engine containers are restarted automatically when the machine restarts. It is better to restart the Remote Engine for Pipelines with the script associated (the one you used to start it the first time).

 

To solve your issue, can you stop your Remote Engine for Pipelines and restart it with the provided script ?

 

./pipeline-remote-engine.sh stop
if you are on a Unix system (use the bat if on Windows)
 
And then:
 
./pipeline-remote-engine.sh start
 if you are on a Unix system (use the bat if on Windows)
 
A good way to avoid this issue is to create a service to stop and start your Remote Engine gracefully with your machine.
 
Best regards,
 
Thibaut

View solution in original post

2 Replies
Anonymous
Not applicable
Author

Hello @Sanjaytha,

 

Thanks for using Talend Pipeline Designer.

 

I assume you set up a Remote Engine for Pipelines. If this is not the case, please let me know.

 

Where did you deploy your Remote Engine for Pipelines ? Did you restart the machine where your Remote Engine for Pipelines is running ?

In fact this error can happen when the Remote Engine containers are restarted automatically when the machine restarts. It is better to restart the Remote Engine for Pipelines with the script associated (the one you used to start it the first time).

 

To solve your issue, can you stop your Remote Engine for Pipelines and restart it with the provided script ?

 

./pipeline-remote-engine.sh stop
if you are on a Unix system (use the bat if on Windows)
 
And then:
 
./pipeline-remote-engine.sh start
 if you are on a Unix system (use the bat if on Windows)
 
A good way to avoid this issue is to create a service to stop and start your Remote Engine gracefully with your machine.
 
Best regards,
 
Thibaut
Anonymous
Not applicable
Author

I am running Remote engine for Pipeline in a Linux Remote Desktop machine.

I have stopped the service and started again. Now its working.

Thank you.