Runtime log file "\log\tesb.log" never updated

[URWITEU]

Hello,

I have a Talend runtime that seems to be working correctly. However, the log file tesb.log has not been updated for a month now.

Could you please tell me what I need to check? Additionally, I have restarted it, but it doesn't change anything. Thank you.

Regards.

[Xiaodi_Shi]

Hello,

Could you please indicate on which Talend Runtime build version you got this issue? Is your Runtime connected with a Remote Engine? Is the pax logging configuration file getting overridden?

Best regards

Sabrina

[URWITEU]

Hello

Could you please indicate on which Talend Runtime build version you got this issue?
=> "8.0.1.R2023-10-RT_Platform_2"

Is your Runtime connected with a Remote Engine?
=> Yes it is :

Is the pax logging configuration file getting overridden?
=> The content of the file org.ops4j.pax.logging.cfg :

log4j2.appender.DSRunnerLogCollector.reconnectionDelayMillis = 120000
log4j2.appender.DSRunnerLogCollector.host = localhost
log4j2.appender.DSRunnerLogCollector.layout.type = JsonLayout
log4j2.rootLogger.appenderRef.Socket.ref = DSRunnerLogCollector
log4j2.appender.DSRunnerLogCollector.port = 7789
log4j2.appender.DSRunnerLogCollector.layout.properties = true
log4j2.appender.DSRunnerLogCollector.layout.compact = true
log4j2.appender.DSRunnerLogCollector.type = Socket
log4j2.appender.DSRunnerLogCollector.name = DSRunnerLogCollector
log4j2.appender.DSRunnerLogCollector.layout.locationInfo = true

Thanks.

[Xiaodi_Shi]

Hello,

I suspect your Runtime and RE are on same server, however they can't communicate with each other. When RE and Runtime are both running, the RE will hookup/connect to the Runtime using the jmx.url specified in org.talend.ipaas.rt.dsrunner.talendruntime.client.cfg and this is when Runtime's org.ops4j.pax.logging.cfg is updated with those DSRunnerLogCollector

4:37

and this is when Runtime's org.ops4j.pax.logging.cfg is updated with those DSRunnerLogCollector

Is your Runtime configured to listen to same port or jmx.url is pointing to your current Runtime?

Best regards

Sabrina

[URWITEU]

Hello,

Thank you for your response. To be honest, we used this server to install a second Runtime in order to create documentation for our Production department to install our production Runtimes. However, we made sure to remove this second Runtime using the uninstallation procedure. Since then, the log file of the first Runtime is no longer being updated.

However, the org.talend.ipaas.rt.dsrunner.talendruntime.client.cfg file of the Remote Engine seems to correctly redirect to the first Runtime:

talendruntime.jmx.url=service:jmx:rmi://localhost:44444/jndi/rmi://localhost:1099/karaf-trun

In Runtime, the org.apache.karaf.management.cfg file includes the following values: 44444 and 1099

Best regards,

Etienne

[Xiaodi_Shi]

Hello,

I met an issue before that some hosts may not accept the default value 0.0.0.0 (bind to all available interfaces) for hosts (org.apache.karaf.management.cfg) - in this case you may have to change them to 127.0.0.1.

It is recommend you should create a support case through support cycle with priority so that we could give you a remote assistance.

https://community.qlik.com/t5/Official-Support-Articles/How-to-contact-Qlik-Support/ta-p/1837529

Best regards

Sabrina

[URWITEU]

Hello,

It is already 127.0.0.1. Ok I will open a support case.

Regards,

Etienne