All jobs failing after RE Server reboot

Highlighted
Seven Stars

All jobs failing after RE Server reboot

All our Talend jobs in Talend Integration Cloud are failing after a RE server reboot yesterday. The error that Cloud Integration Interface shows is misleading since even when there is only one job running same error is shows:

 

Deploy Failed:
Exceeded the limit of executions per engine. Run this Flow on another Remote Engine.

 

 

CPU/RAM on RE server is not pegged at all.

 

On RE Server Talend services are up as well:

talend_re.PNG

 

Is there something on the Talend RE Server that needs to brought up manually?

 

Thanks

Seven Stars

Re: All jobs failing after RE Server reboot

In Talend documentation I came across this:

 

re_start_windows.png

 

Here is the source URL:

https://help.talend.com/reader/L46WOZPYhdcRiNqKttYr3Q/225DXVffWZJJf9yXg1oLrw

 

It looks like I need to run trun executable on the Remote Engine server.

 

Any thoughts on this?

 

Thanks

Seven Stars

Re: All jobs failing after RE Server reboot

Another day of failed jobs.

 

In Talend docs - it says that I probably need to run start.bat - I guess that starts Karaf in the background.

 

Also, I have noticed that Apache Tomcat is not running on the Remote Engine server.

 

Now I am not sure what needs to be done to fix this issue - should I run trun, start.bat or run start Tomcat?

 

Any thoughts?

talend_re2.PNG

Seven Stars

Re: All jobs failing after RE Server reboot

Still not luck - all jobs executed from TIC are still failing. I see following in the Karaf log under C:\RemoteEngine-21\data\log:

 

 

2018-10-08T09:54:16,245 | INFO  | pool-32-thread-1 | RemoteHeartbeatSender            | 159 - pairing-agent - 2.1.0 | Sending heartbeat...
2018-10-08T09:54:16,386 | INFO  | pool-32-thread-1 | PairingAgent                     | 159 - pairing-agent - 2.1.0 | ACTIVE is the same as current status. No further processing.
2018-10-08T09:54:19,371 | WARN  | ActiveMQ Transport: HTTP Reader https://msg.us.cloud.talend.com:443 | FailoverTransport                | 182 - org.apache.activemq.activemq-osgi - 5.14.5 | Transport (https://msg.us.cloud.talend.com:443) failed , attempting to automatically reconnect: {}
java.io.IOException: Failed to perform GET on: https://msg.us.cloud.talend.com:443 Reason: Socket Closed
 at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:34) [182Smiley Surprisedrg.apache.activemq.activemq-osgi:5.14.5]
 at org.apache.activemq.transport.http.HttpClientTransport.run(HttpClientTransport.java:208) [182Smiley Surprisedrg.apache.activemq.activemq-osgi:5.14.5]
 at java.lang.Thread.run(Thread.java:745) [?:?]
Caused by: java.net.SocketException: Socket Closed

 

 

Seven Stars

Re: All jobs failing after RE Server reboot

Looks like issue had to do with trac.bat. It creates a runtime and needs to be running. So now we scheduled it to run every time server boots. To run it in the background you need to run the start.bat file and not trac.bat.

 

https://help.talend.com/reader/yovCMqvJzyaSSSIdrlB4FQ/W11TRd~UWUBoXI2b6iGFUA

2019 GARNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

What’s New for Talend Summer ’19

Watch the recorded webinar!

Watch Now

Self-service Talend Migration: Moving from On-Premises to the Cloud

Move from On-Premises to the Cloud by following the advice of experts

Read Now

Modern Data Engineering in the Cloud

Learn about modern data engineering in the Cloud

Watch Now

How to deploy Talend Jobs as Docker images to Amazon, Azure and Google Cloud reg...

Learn how to deploy Talend Jobs as Docker images to Amazon, Azure and Google Cloud registries

Blog