Re: Error override with tSSH - Qlik Community

flipflip · ‎2023-03-09

Good morning,

I use Talend Open Studio 8.0.20211109_1610 on my PC which is under Fedora 37 with the Java Zulu18.

I don't use Taled every day but it was walking.Today I create a new job with just a SSH connection to a server and when I launch the job I have the error.

Démarrage du Job waitCde à 14:54 09/03/2023.

[statistics] connecting to socket on port 3720

[statistics] connected

Exception in component tSSH_1 (waitCde)

java.io.StreamCorruptedException: Overriding the global section with a specific one at line 3: Host *

at org.apache.sshd.client.config.hosts.HostConfigEntry.readHostConfigEntries(HostConfigEntry.java:854)

at org.apache.sshd.client.config.hosts.HostConfigEntry.readHostConfigEntries(HostConfigEntry.java:796)

at org.apache.sshd.client.config.hosts.HostConfigEntry.readHostConfigEntries(HostConfigEntry.java:790)

at org.apache.sshd.client.config.hosts.HostConfigEntry.readHostConfigEntries(HostConfigEntry.java:777)

at org.apache.sshd.client.config.hosts.ConfigFileHostEntryResolver.reloadHostConfigEntries(ConfigFileHostEntryResolver.java:104)

at org.apache.sshd.client.config.hosts.DefaultConfigFileHostEntryResolver.reloadHostConfigEntries(DefaultConfigFileHostEntryResolver.java:83)

at org.apache.sshd.client.config.hosts.ConfigFileHostEntryResolver.resolveEffectiveResolver(ConfigFileHostEntryResolver.java:89)

at org.apache.sshd.client.config.hosts.ConfigFileHostEntryResolver.resolveEffectiveHost(ConfigFileHostEntryResolver.java:59)

at org.apache.sshd.client.SshClient.connect(SshClient.java:471)

at org.apache.sshd.client.session.ClientSessionCreator.connect(ClientSessionCreator.java:60)

at org.apache.sshd.client.session.ClientSessionCreator.connect(ClientSessionCreator.java:43)

at pim.waitcde_0_1.waitCde.tSSH_1Process(waitCde.java:436)

at pim.waitcde_0_1.waitCde.runJobInTOS(waitCde.java:1652)

at pim.waitcde_0_1.waitCde.main(waitCde.java:1472)

[statistics] disconnected

For tests the connection is carried out with username and password.

I tested the connection from a terminal with the same information and no problem.

To push further I tried with a TSCPGetFile or even TSCPConnection component and the problem and the same.I also tested with an old job that walked before and the same.

I don't understand where the problem comes from?

Anonymous · ‎2023-03-10

Hello,

What we can see now is you are using Java Zulu18 which is not list in the compatible java environments.

https://help.talend.com/r/en-US/8.0/installation-guide-windows/compatible-java-environments

In the documentation we provide a list of java environments that are supported, in the sense that we do provide an SLA and technical support for them. This doesn't mean other (non-listed) java environments will not work but simply we won't necessarily be equipped to help you with any issue you may face with them.

Best regards

Sabrina

flipflip · ‎2023-03-10

Hello, thank you for your response.

On this page it is indicated: OpenJDK (recommended Distribution: Zulu)

Several months ago, when I started using Open Studio I immediately installed the Zulu version but I don't remember what version and it is likely that it is updated during aSystem up to date.

On my machine I have three other versions of Java installed:

$ sudo alternatives --config java

Il existe 4 programmes qui fournissent « java ».

Sélection Commande

-----------------------------------------------

1 /usr/lib/jvm/zulu18/bin/java

* 2 java-17-openjdk.x86_64 (/usr/lib/jvm/java-17-openjdk-17.0.6.0.10-1.fc37.x86_64/bin/java)

+ 3 java-11-openjdk.x86_64 (/usr/lib/jvm/java-11-openjdk-11.0.18.0.10-1.fc37.x86_64/bin/java)

4 /usr/lib/jvm/zulu11/bin/java

Tapez « Entrée » pour garder la sélection courante [+] ou saisissez le numéro de sélection : 4

$ java --version

openjdk 11.0.18 2023-01-17 LTS

OpenJDK Runtime Environment Zulu11.62+17-CA (build 11.0.18+10-LTS)

OpenJDK 64-Bit Server VM Zulu11.62+17-CA (build 11.0.18+10-LTS, mixed mode)

I tested by setting it by default (I relaunched Open Studio between each change) and I checked that it was taken into account in the open studio configuration.

Before posting my answer I tested with all the versions of Java present on my machine.

Unfortunately the problem is still present.

Philippe.

Anonymous · ‎2023-03-10

Hello,

Could you please post the studio log file here which will be helpful for us to address your issue?

You will find it here: <studio-root>/configuration/xxxxxxxx.log

and the workspace log file: <workspace-root>/.metadata/.log

Best regards

Sabrina

flipflip · ‎2023-03-10

Hello,

In the directory: <studio-root>/configuration/xxxxxxxx.log I do not have a log file.

<workspace-root>/.metadata/.log

!ENTRY org.talend.platform.logging 1 0 2023-03-10 10:24:58.610

!MESSAGE 2023-03-10 10:24:58,609 INFO org.eclipse.m2e.core.internal.project.WorkspaceClassifierResolverManager - Resolving P/PIM_ROUTINES: org.example.pim.code:routines:8.0.1 with classifier to /PIM_ROUTINES/target/classes

!ENTRY org.talend.platform.logging 1 0 2023-03-10 10:24:58.778

!MESSAGE 2023-03-10 10:24:58,778 INFO org.talend.designer.core.runprocess.Processor - Ligne de commande : /usr/lib/jvm/zulu11/bin/java -Xms256M -Xmx1024M -Dfile.encoding=UTF-8 -Dtalend.component.manager.m2.repository=/home/xxxxx/Téléchargements/TOS_DI-20211109_1610-V8.0.1/configuration/.m2/repository -Dencryption.keys.file=/home/xxxxx/Téléchargements/TOS_DI-20211109_1610-V8.0.1/configuration/studio.keys -cp /home/xxxxx/Téléchargements/TOS_DI-20211109_1610-V8.0.1/workspace/PIM/poms/jobs/process/waitcde_0.1/target/classpath.jar: pim.waitcde_0_1.waitCde --context=Default --stat_port=3667 "$@"

!ENTRY org.talend.platform.logging 1 0 2023-03-10 10:28:34.879

!MESSAGE 2023-03-10 10:28:34,879 INFO org.talend.designer.runprocess.maven.MavenJavaProcessor - build, threadParam: -T 1C

!ENTRY org.talend.platform.logging 1 0 2023-03-10 10:28:34.882

!MESSAGE 2023-03-10 10:28:34,881 INFO org.eclipse.m2e.core.internal.project.ProjectConfigurationManager - Update started

!ENTRY org.talend.platform.logging 1 0 2023-03-10 10:28:35.057

!MESSAGE 2023-03-10 10:28:35,056 INFO org.eclipse.m2e.core.internal.project.WorkspaceClassifierResolverManager - Resolving P/PIM_ROUTINES: org.example.pim.code:routines:8.0.1 with classifier to /PIM_ROUTINES/target/classes

!ENTRY org.talend.platform.logging 1 0 2023-03-10 10:28:35.245

!MESSAGE 2023-03-10 10:28:35,244 INFO org.eclipse.m2e.jdt.internal.AbstractJavaProjectConfigurator - Adding source folder /PIM_WAITCDE_0.1/src/main/java

!ENTRY org.talend.platform.logging 1 0 2023-03-10 10:28:35.245

!MESSAGE 2023-03-10 10:28:35,245 INFO org.eclipse.m2e.jdt.internal.AbstractJavaProjectConfigurator - Adding resource folder /PIM_WAITCDE_0.1/src/main/resources

!ENTRY org.talend.platform.logging 1 0 2023-03-10 10:28:35.248

!MESSAGE 2023-03-10 10:28:35,248 INFO org.eclipse.m2e.jdt.internal.AbstractJavaProjectConfigurator - Adding source folder /PIM_WAITCDE_0.1/src/test/java

!ENTRY org.talend.platform.logging 1 0 2023-03-10 10:28:35.249

!MESSAGE 2023-03-10 10:28:35,248 INFO org.eclipse.m2e.jdt.internal.AbstractJavaProjectConfigurator - Adding resource folder /PIM_WAITCDE_0.1/src/test/resources

!ENTRY org.talend.platform.logging 1 0 2023-03-10 10:28:35.320

!MESSAGE 2023-03-10 10:28:35,319 INFO org.eclipse.m2e.core.internal.project.ProjectConfigurationManager - Update completed: 0 sec

!ENTRY org.talend.platform.logging 1 0 2023-03-10 10:28:36.046

!MESSAGE 2023-03-10 10:28:36,046 INFO org.eclipse.m2e.core.internal.project.WorkspaceClassifierResolverManager - Resolving P/PIM_ROUTINES: org.example.pim.code:routines:8.0.1 with classifier to /PIM_ROUTINES/target/classes

!ENTRY org.talend.platform.logging 1 0 2023-03-10 10:28:36.226

!MESSAGE 2023-03-10 10:28:36,225 INFO org.talend.designer.core.runprocess.Processor - Ligne de commande : /usr/lib/jvm/zulu11/bin/java -Xms256M -Xmx1024M -Dfile.encoding=UTF-8 -Dtalend.component.manager.m2.repository=/home/xxxxx/Téléchargements/TOS_DI-20211109_1610-V8.0.1/configuration/.m2/repository -Dencryption.keys.file=/home/xxxxx/Téléchargements/TOS_DI-20211109_1610-V8.0.1/configuration/studio.keys -cp /home/xxxxx/Téléchargements/TOS_DI-20211109_1610-V8.0.1/workspace/PIM/poms/jobs/process/waitcde_0.1/target/classpath.jar: pim.waitcde_0_1.waitCde --context=Default --stat_port=3876 "$@"

Anonymous · ‎2023-03-10

Hello,

Could you please show us the full error log?

Best regards

Sabrina

flipflip · ‎2023-03-10

oups 🙂 Complete log since the launch of TOS, loading of the project, opening of the job, launch of the job and closure of TOS

*** Part 1 ***

!SESSION 2023-03-10 11:05:47.754 -----------------------------------------------

eclipse.buildId=unknown

java.version=11.0.18

java.vendor=Azul Systems, Inc.

BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=fr

Command-line arguments: -os linux -ws gtk -arch x86_64

!ENTRY org.eclipse.compare.win32 4 0 2023-03-10 11:05:49.398

!MESSAGE FrameworkEvent ERROR

!STACK 0

org.osgi.framework.BundleException: Could not resolve module: org.eclipse.compare.win32 [4]

Unresolved requirement: Require-Capability: eclipse.platform; filter:="(osgi.os=win32)"

at org.eclipse.osgi.container.Module.start(Module.java:463)

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1849)

at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1842)

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1783)

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1747)

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1669)

at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)

at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)

at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)

!ENTRY org.eclipse.jdt.launching.macosx 4 0 2023-03-10 11:05:49.401

!MESSAGE FrameworkEvent ERROR

!STACK 0

org.osgi.framework.BundleException: Could not resolve module: org.eclipse.jdt.launching.macosx [19]

Unresolved requirement: Require-Capability: eclipse.platform; filter:="(osgi.os=macosx)"