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

2019-06-17 Thread Thomas R
Your help was most welcome. Thank you very much for that. Most likely I will 
contact IBM support, now. Maybe they can help. At least it seems that it is not 
directly a Jenkins problem. 

Again, thank you. 

Thomas. 

-- 
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, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4b57f05a-3694-4169-8d6a-5da364589500%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2019-06-17 Thread Ivan Fernandez Calvo
I run out of ideas, I could be some configuration option in 
/etc/ssh/sshd_config but I am not sure

-- 
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, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/cf3f8004-b6f5-4b86-9f38-301a6c312660%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2019-06-17 Thread Thomas R
Sure I can. Here is the result of the commands executed from a Windows Bash 
shell:

traddatz@CNDEA041500 MINGW64 ~
$ ssh raddatz@10.200.36.33 echo "OK"
raddatz@10.200.36.33's password:
OK

traddatz@CNDEA041500 MINGW64 ~
$ ssh -t raddatz@10.200.36.33 echo "OK"
raddatz@10.200.36.33's password:
OK
Connection to 10.200.36.33 closed.

traddatz@CNDEA041500 MINGW64 ~
$ ssh -T raddatz@10.200.36.33 echo "OK"
raddatz@10.200.36.33's password:
OK

traddatz@CNDEA041500 MINGW64 ~
$ ssh raddatz@10.200.36.33 ssh -V
raddatz@10.200.36.33's password:
OpenSSH_6.9p1, OpenSSL 1.0.2r  26 Feb 2019

traddatz@CNDEA041500 MINGW64 ~
$



Am Montag, 17. Juni 2019 15:41:38 UTC+2 schrieb Ivan Fernandez Calvo:
>
> Can you execute a command on a remote ssh session on the agent? something 
> like the following commands `ssh USER@JENKINS_AGENT echo "OK"`, `ssh -t 
> USER@JENKINS_AGENT echo "OK"`, `ssh -T USER@JENKINS_AGENT echo "OK"`
>

-- 
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, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/201538fa-4748-4d10-97f5-16933e88b581%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2019-06-17 Thread Ivan Fernandez Calvo
Can you execute a command on a remote ssh session on the agent? something 
like the following commands `ssh USER@JENKINS_AGENT echo "OK"`, `ssh -t 
USER@JENKINS_AGENT echo "OK"`, `ssh -T USER@JENKINS_AGENT echo "OK"`

-- 
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, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/040a01e6-492d-487b-944e-b353d4a1e349%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2019-06-17 Thread Thomas R
The SSH version on the IBM i server, that is where the slave should run, is:

> ssh -V
  OpenSSH_6.9p1, OpenSSL 1.0.2r  26 Feb 2019
  $

Enabling logging on the slave did not help. All I get is an empty log file 
'remoting.log.0', when using the following logger configuration file:

# Configuration file that controls the slave logging ... if we pass in a JVM
# arg -Djava.util.logging.config.file=jenkins-slave.logging.properties

# Send output to file as well as console.
handlers=java.util.logging.FileHandler, java.util.logging.ConsoleHandler

# Log everything equally
java.util.logging.FileHandler.level=ALL
java.util.logging.ConsoleHandler.level=ALL
java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter
java.util.logging.SimpleFormatter.format=%1$tFT%1$tT.%1$tL%1$tz %4$s %2$s: 
%5$s%6$s%n

# On the filesystem, we keep up to 9 logs of 10meg each.
java.util.logging.FileHandler.pattern=jenkins-slave.%g.log
java.util.logging.FileHandler.encoding=UTF-8
java.util.logging.FileHandler.limit=10485760
java.util.logging.FileHandler.count=9
java.util.logging.FileHandler.append=false

# Log everything ...
.level= ALL
hudson.remoting.level=FINE


This is who I specified the logger configuration of the slave:

Source agent hash is D2D1A740134BD20D6F0855B356344342. Installed agent hash is 
D2D1A740134BD20D6F0855B356344342
Verified agent jar. No update is necessary.
Expanded the channel window size to 4MB
[06/17/19 13:24:16] [SSH] Starting agent process: cd "/home/Raddatz/jenkins" && 
/QOpenSys/usr/bin/java -Dfile.encoding=ISO8859_1   -jar remoting.jar -workDir 
/home/Raddatz/jenkins/work -loggingConfig jenkins-slave.logging.properties

Slave JVM has terminated. Exit code=1
[06/17/19 13:24:41] Launch failed - cleaning up connection
[06/17/19 13:24:41] [SSH] Connection closed.


Thomas.


Am Sonntag, 16. Juni 2019 22:35:53 UTC+2 schrieb 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 Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/52ba48af-53d1-42bd-aae0-80a0f92b77f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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 Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a7d68260-36e8-468f-a1dd-4b1a4df1581a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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 -workDir /home/Raddatz/jenkins/work

Slave JVM has terminated. Exit code=1



Thomas.


Am Sonntag, 16. Juni 2019 20:41:42 UTC+2 schrieb 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 subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7fb1ce21-a6d3-41d7-8903-c777946711f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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 terminated. Exit code=1


Also enabling


Am Sonntag, 16. Juni 2019 21:27:35 UTC+2 schrieb 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 -workDir 
> /home/raddatz/jenkins/work -text" command produces the following output, 
> when being executed from Qshell on the host:
>
> > cd "/home/Raddatz/jenkins" && /QIBM/ProdData/Java400/bin/java 
> -Dfile.encoding=ISO8859_1 -jar remoting.jar -workDir   
>  /home/raddatz/jenkins/work -text  
> 
>   Running in text mode
>  
>   Jun 16, 2019 9:18:52 PM org.jenkinsci.remoting.engine.WorkDirManager 
> initializeWorkDir   
>   INFO: Using /home/raddatz/jenkins/work/remoting as a remoting work 
> directory 
>   Both error and output logs will be printed to 
> /home/raddatz/jenkins/work/remoting
> 
>   WARNING: Are you running agent from an interactive console?  
> 
>   If so, you are probably using it incorrectly.
> 
>   See https://wiki.jenkins.io/display/JENKINS/Launching+agent+from+console  
>
>   <===[JENKINS REMOTING 
> CAPACITY]===>rO0ABXNyABpodWRzb24ucmVtb3RpbmcuQ2FwYWJpbGl0eQABAgABSgAEbWFza3hwAf4=<===[HUDSO
>   N TRANSMISSION BEGINS]===>  
>  
>
> It also produces an empty 'remoting.log.0'.
>
> There are no hs_err_pid files in folder /home/raddatz/jenkis and any 
> deeper folder.
>
> I am going to check the troubleshooting page , now.
>
> Thank you for your quick reply.
>
> Thoma.s
>
> Am Sonntag, 16. Juni 2019 20:18:27 UTC+2 schrieb 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/jenkins and /home/raddatz/jenkins/work 
>> for log files or hs_err_pid files
>>
>> Finally check the troubleshooting guide 
>> https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/TROUBLESHOOTING.md#troubleshooting
>>
>>

-- 
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, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fdfdc2db-3cb6-4114-b6f3-dff53fa07202%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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_181"
Java(TM) SE Runtime Environment (build 8.0.5.20 - 
pwa6480sr5fp20-20180802_01(SR5 FP20))
IBM J9 VM (build 2.9, JRE 1.8.0 Windows 7 amd64-64-Bit Compressed 
References 20180731_393394 (JIT enabled, AOT enabled)
OpenJ9   - bd23af8
OMR  - ca1411c
IBM  - 98805ca)
JCL - 20180719_01 based on Oracle jdk8u181-b12


Thomas.


Am Sonntag, 16. Juni 2019 20:18:27 UTC+2 schrieb 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/jenkins and /home/raddatz/jenkins/work 
> for log files or hs_err_pid files
>
> Finally check the troubleshooting guide 
> https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/TROUBLESHOOTING.md#troubleshooting
>
>

-- 
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, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/583d3be8-b933-4916-8865-66085a899ffa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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 -workDir 
/home/raddatz/jenkins/work -text" command produces the following output, 
when being executed from Qshell on the host:

> cd "/home/Raddatz/jenkins" && /QIBM/ProdData/Java400/bin/java 
-Dfile.encoding=ISO8859_1 -jar remoting.jar -workDir   
 /home/raddatz/jenkins/work -text  

  Running in text mode  
   
  Jun 16, 2019 9:18:52 PM org.jenkinsci.remoting.engine.WorkDirManager 
initializeWorkDir   
  INFO: Using /home/raddatz/jenkins/work/remoting as a remoting work 
directory 
  Both error and output logs will be printed to 
/home/raddatz/jenkins/work/remoting

  WARNING: Are you running agent from an interactive console?  

  If so, you are probably using it incorrectly.

  See https://wiki.jenkins.io/display/JENKINS/Launching+agent+from+console  
   
  <===[JENKINS REMOTING 
CAPACITY]===>rO0ABXNyABpodWRzb24ucmVtb3RpbmcuQ2FwYWJpbGl0eQABAgABSgAEbWFza3hwAf4=<===[HUDSO
  N TRANSMISSION BEGINS]===>
   

It also produces an empty 'remoting.log.0'.

There are no hs_err_pid files in folder /home/raddatz/jenkis and any deeper 
folder.

I am going to check the troubleshooting page , now.

Thank you for your quick reply.

Thoma.s

Am Sonntag, 16. Juni 2019 20:18:27 UTC+2 schrieb 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/jenkins and /home/raddatz/jenkins/work 
> for log files or hs_err_pid files
>
> Finally check the troubleshooting guide 
> https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/TROUBLESHOOTING.md#troubleshooting
>
>

-- 
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, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/22674b9a-441b-49a2-9e52-37078cf1fbc1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.