git clone impossible while slave is connecte

[cd]

Hello,

I have an "interesting" problem. I have a server running jenkins (linux) and a slave for running jobs (linux). When the slave is NOT connected then i can clone repos. BUT when the slave is connected, either from the master or the slave, then the job i stuck at "cloning into...". Any suggestions?

I have looked at the settings in /etc/ssh/... but cannot find anything unusual...

/chris

[Mark Waite]

You might try proving that the problem is specific to the slave by modifying the job definition to force it to run on only on the master node.  In the job configuration page for that job there is a field which iwll allow you to restrict which nodes can run the job.  Place "master" into that field (without the quotes), save the job configuration, and run it again.

If that works, then change the value in the field to "!master" (not master - without the quotes).  That should then force the job to run on the slave.  If you have more than one slave, then you'll need to list the specific slave name rather than the !master syntax.

Once you've shown that the problem is on the slave and not the master, then you probably want to compare the configuration of the master and the slave.

One scenario I've seen that was similar to your described symptoms was due to my having granted additional permissions to the jenkins user on the master nodle which I did not grant to the jenkins user on the slave nodes.  In my case, I needed to add the private key of the jenkins user on the master node as a credential (in "Manage Credentials"), then use that credential in the configuration of the git plugin.

Mark Waite 

--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/87c886d2-4046-48bb-9004-ced3937fc4de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[cd]

The job has been running on the master for a couple of month. Due to heavy load we have added a slave. When I run on the slave I specify the job to run on the slave specifically. I have tried both using credential passed from the master and adding credentials on the slave. When the connection between the slave and the master is up then I cannot even ssh from the slave to the master. Very strange...

[cd]

...and even if I disconnect i persists, the only way I have found to solve it is reboot...