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]===>rO0ABXNyABpodWRzb24ucmVtb3RpbmcuQ2FwYWJpbGl0eQAAAAAAAAABAgABSgAEbWFza3hwAAAAAAAAAf4=<===[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 [email protected].
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.

Reply via email to