Re: Cannot start slave on IBM i due to java.io.EOFException

2019-06-16 Thread Ivan Fernandez Calvo
> Could you enable verbose loggin for the package "hudson.remoting"? FINE log level should enough see how at https://github.com/jenkinsci/remoting/blob/master/docs/logging.md Which version os SSH do you use? execute `ssh -V` -- You received this message because you are subscribed to the Goog

Re: Cannot start slave on IBM i due to java.io.EOFException

2019-06-16 Thread Thomas R
Enabling "Master Access Control" (Enable Agent → Master Access Control) and removing the '-text parameter did not help: [06/16/19 22:10:24] [SSH] Starting agent process: cd "/home/Raddatz/jenkins" && /QOpenSys/usr/bin/java -Dfile.encoding=ISO8859_1 -Xms256M -Xmx256M -jar remoting.jar -workDi

Re: Cannot start slave on IBM i due to java.io.EOFException

2019-06-16 Thread Thomas R
Changing Java propertis Xms and Xms (trouble shooting guide) did not help: [06/16/19 21:52:55] [SSH] Starting agent process: cd "/home/Raddatz/jenkins" && /QOpenSys/usr/bin/java -Dfile.encoding=ISO8859_1 -Xms256M -Xmx256M -jar remoting.jar -workDir /home/Raddatz/jenkins/work Slave JVM has ter

Re: Cannot start slave on IBM i due to java.io.EOFException

2019-06-16 Thread Thomas R
I forgot to mention that I start the Jenkins server with the following command: "c:\Program Files\IBM\SDP_096\jdk\bin\java.exe" -jar jenkins-2.164.3.war --httpPort=9090 The Java version number is: C:\Users\traddatz>"c:\Program Files\IBM\SDP_096\jdk\bin\java.exe" -version java version "1.8.0_18

Re: Cannot start slave on IBM i due to java.io.EOFException

2019-06-16 Thread Thomas R
There are only the following files: a) \\ghentw.gfd.de\home\Raddatz\jenkins\remoting.jar b) \\ghentw.gfd.de\home\Raddatz\jenkins\work\remoting\logs\remoting.log.0 (0-bytes = empty) The "cd "/home/Raddatz/jenkins" && /QIBM/ProdData/Java400/bin/java -Dfile.encoding=ISO8859_1 -jar remoting.jar

Cannot start slave on IBM i due to java.io.EOFException

2019-06-16 Thread Ivan Fernandez Calvo
I've found it, is a remoting option to use base64 to encode the comunication, I've never use it, it is not needed https://github.com/jenkinsci/remoting/blob/005dd67af809881ff0c79992583661fa2cde4229/src/main/java/hudson/remoting/Launcher.java#L130 -- You received this message because you are subs

Cannot start slave on IBM i due to java.io.EOFException

2019-06-16 Thread Ivan Fernandez Calvo
Another question, what is the use of ‘-text’ option you pass to the JVM? I did no find it on the Oracle JDK either on the IBM JDK -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it

Cannot start slave on IBM i due to java.io.EOFException

2019-06-16 Thread Ivan Fernandez Calvo
Which JDK do you use on the Jenkins master? Did you try to execute the following command manually on the agent? cd "/home/Raddatz/jenkins" && /QIBM/ProdData/Java400/bin/java -Dfile.encoding=ISO8859_1 -jar remoting.jar -workDir /home/raddatz/jenkins/work -text check the directory /home/raddatz/

Pipeline - production - input in the stage

2019-06-16 Thread zakyn
Hello, I would like to ask you for your help. I am trying to declare this workflow: - user has to choose param - dev, test, prod - when use dev - copy deploy-01.txt - when use test - copy deploy-02.txt - when use prodution - user has to write password - when it is correct then - copy both files.

Cannot start slave on IBM i due to java.io.EOFException

2019-06-16 Thread Thomas R
Hi all, I am new to Jenkins and I am lost. The problem is that I cannot start a Jenkins slave on an IBM i (former: AS/400, iSeries, etc.) due to a java.io.EOFException. The log file and the console output does not contain anything meaningful to me. Jenkins version: 2.164.3 (same problem with

SCM option no more available in 'Trigger/call builds on other project' after upgrading

2019-06-16 Thread Jyc Zuan
Hi, I'm new to the group, I'm not sure if this topic has been already discussed in the past. With Jenkins 1.582 in Add build step the "Trigger/call builds on other projects" has a checkbox "Build triggered projects only if there is SCM changes" but after upgrading to 2.164.3 this option is n