Re: Pipeline script from SCM - Git Issue

2024-08-12 Thread Mk 
 I have updated the "Configure the host key verification strategy from 
"Manage Jenkins" >> "Security" >> "Git Host Key Verification 
Configuration", now working as expected. Thanks. 

On Monday, August 12, 2024 at 2:44:19 PM UTC+5:30 Mk wrote:

> Hi Team,
>
>  
>
> *My Environment:-*
>
> Jenkins Master version - 2.462.1 LTS
>
> Git plugin Version - 5.3.0 
>
> Job Type – Pipeline
>
>  
>
> *Problem Description:-*
>
>  
>
> I have configured a Pipeline job. In the Pipeline definition section, I 
> selected "*Pipeline script from SCM*." However, I'm encountering the 
> following error.
>
>  
>
> *SCM: Git*
>
> *Repository URL:  g...@github.com:testorg/test-abc.git*
>
>  
>
> Failed to connect to repository : Command "git ls-remote -h -- 
> g...@github.com:testorg/test-abc.git HEAD" returned status code 128:
> stdout: 
> stderr: Host key verification failed. 
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
> *Script Path: Jenkinsfile*
>
>  
>
> *Console Output:*
>
>  
>
> Started by user Admin
>
> hudson.plugins.git.GitException: Command "git fetch --tags --force 
> --progress --prune -- origin +refs/heads/main:refs/remotes/origin/main" 
> returned status code 128:
>
> stdout: 
>
> stderr: Host key verification failed.
>
> fatal: Could not read from remote repository.
>
>  
>
> Please make sure you have the correct access rights
>
> and the repository exists.
>
>  
>
>at PluginClassLoader for 
> git-client//org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2846)
>
>at PluginClassLoader for 
> git-client//org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2185)
>
>at PluginClassLoader for 
> git-client//org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:635)
>
>at PluginClassLoader for 
> git//jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:406)
>
>at PluginClassLoader for 
> scm-api//jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:219)
>
>at PluginClassLoader for 
> workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:126)
>
>at PluginClassLoader for 
> workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:73)
>
>at PluginClassLoader for 
> workflow-job//org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:311)
>
>at 
> hudson.model.ResourceController.execute(ResourceController.java:101)
>
>at hudson.model.Executor.run(Executor.java:446)
>
> Finished: FAILURE
>
>  
>
> I suspect there might be an issue with the plugin side, but I'm not 
> entirely sure. Could you please assist me in resolving this?
>
>  
>

-- 
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/e0cdf7b0-3279-449e-93f0-67688d7389f5n%40googlegroups.com.

Pipeline script from SCM - Git Issue

2024-08-12 Thread Mk 
 

Hi Team,

 

*My Environment:-*

Jenkins Master version - 2.462.1 LTS

Git plugin Version - 5.3.0 

Job Type – Pipeline

 

*Problem Description:-*

 

I have configured a Pipeline job. In the Pipeline definition section, I 
selected "*Pipeline script from SCM*." However, I'm encountering the 
following error.

 

*SCM: Git*

*Repository URL:  g...@github.com:testorg/test-abc.git*

 

Failed to connect to repository : Command "git ls-remote -h -- 
g...@github.com:testorg/test-abc.git HEAD" returned status code 128:
stdout: 
stderr: Host key verification failed. 
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

*Script Path: Jenkinsfile*

 

*Console Output:*

 

Started by user Admin

hudson.plugins.git.GitException: Command "git fetch --tags --force 
--progress --prune -- origin +refs/heads/main:refs/remotes/origin/main" 
returned status code 128:

stdout: 

stderr: Host key verification failed.

fatal: Could not read from remote repository.

 

Please make sure you have the correct access rights

and the repository exists.

 

   at PluginClassLoader for 
git-client//org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2846)

   at PluginClassLoader for 
git-client//org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2185)

   at PluginClassLoader for 
git-client//org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:635)

   at PluginClassLoader for 
git//jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:406)

   at PluginClassLoader for 
scm-api//jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:219)

   at PluginClassLoader for 
workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:126)

   at PluginClassLoader for 
workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:73)

   at PluginClassLoader for 
workflow-job//org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:311)

   at 
hudson.model.ResourceController.execute(ResourceController.java:101)

   at hudson.model.Executor.run(Executor.java:446)

Finished: FAILURE

 

I suspect there might be an issue with the plugin side, but I'm not 
entirely sure. Could you please assist me in resolving this?

 

-- 
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/b30e9e56-f1bd-4247-849f-fa74ef33956dn%40googlegroups.com.

Re: Pipeline script step looking script inside job@tmp path

2023-06-06 Thread Mk 
 sh '$WORKSPACE/script.sh' solved the problem. 

On Tuesday, June 6, 2023 at 4:17:12 PM UTC+5:30 Mk wrote:

> I'm using Jenkins - 2.375.2 and both Jenkinsfile and script.sh files are 
> in my github repository. 
>
> My Jenkinsfile (Declarative Pipeline) content as follows,
> pipeline {
> agent any
>
> stages {
> stage('Checkout') {
> steps {
> git url: 'g...@github.com:org/repository.git'
> }
> }
> 
> stage('Script') {
> steps {
> sh 'script.sh' 
> }
> }
> } 
>
> Any idea why my job goes to below path and looking for script? 
> + myscript.sh 
> /home/user/jenkins/workspace/My_JOB_1@tmp/durable-942e10b9/script.sh: 1: 
> /home/user/jenkins/workspace/My_JOB_1@tmp/durable-942e10b9/script.sh: 
> myscript.sh: not found
>
> I have my script inside this path /home/user/jenkins/workspace/My_JOB_1 
> path. 
> Not sure why it has created jobname with @tmp and looking script in that 
> path.
>
> Any advise to fix this problem would be helpful.
>

-- 
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/7b51799a-6452-4e4b-9766-af5ae9ce7043n%40googlegroups.com.

Pipeline script step looking script inside job@tmp path

2023-06-06 Thread Mk 
I'm using Jenkins - 2.375.2 and both Jenkinsfile and script.sh files are in 
my github repository. 

My Jenkinsfile (Declarative Pipeline) content as follows,
pipeline {
agent any

stages {
stage('Checkout') {
steps {
git url: 'g...@github.com:org/repository.git'
}
}

stage('Script') {
steps {
sh 'script.sh' 
}
}
} 

Any idea why my job goes to below path and looking for script? 
+ myscript.sh 
/home/user/jenkins/workspace/My_JOB_1@tmp/durable-942e10b9/script.sh: 1: 
/home/user/jenkins/workspace/My_JOB_1@tmp/durable-942e10b9/script.sh: 
myscript.sh: not found

I have my script inside this path /home/user/jenkins/workspace/My_JOB_1 
path. 
Not sure why it has created jobname with @tmp and looking script in that 
path.

Any advise to fix this problem would be helpful.

-- 
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/1ff73bc3-4afc-4c73-acf1-3e1b19b2614an%40googlegroups.com.

LDAP Manager DN Query

2022-04-26 Thread Mk 
 

*Jenkins Version - Jenkins 2.319.1 *

*LDAP Plugin version – 2.9*

Our LDAP authentication working fine. However our IT-Department very often 
changing the Manager DN configured user’s CN path.

 For example, Currently our Manager DN section configured like below

* CN=MyUser,CN=Users,DC=mydomain,DC=com*

Is it possible to use like *mydomain\MyUser *in Manager DN section?

-- 
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/18fbe692-71d2-41e2-b011-d69a30db7e84n%40googlegroups.com.

Re: HTTP Status 403 – Forbidden error

2021-02-18 Thread Mk 

Thanks Mark. I have uninstalled the *MultiSCM plugin* and restarted the 
service. However still i am experiencing the same problem*. *Under *Manage 
Jenkins* --> *Configure Systems* section post any modification if i click 
save button it fails. Now from systems log i can below error message.

Feb 19, 2021 10:56:05 AM WARNING hudson.security.csrf.CrumbFilter doFilter
No valid crumb was included in request for /jenkins/configSubmit by 
vasanth.guru. Returning 403.

The account i am using has Admin privilege.
On Friday, February 19, 2021 at 10:31:23 AM UTC+5:30 Mark Waite wrote:

> That null pointer exception seems likely to have been caused by one of the 
> plugins that was updated.  Since it is mentioning LibraryConfiguration, 
> SCMRetriever, and MultiSCM, you might first look at the 
> workflow-cps-global-lib and the multiple-scms plugin to see if either of 
> them were recently upgraded.
>
> The MultipleSCMs plugin has been deprecated.  Jenkins Pipeline is the 
> better way to implement multiple SCM support from within a single job.
>
> Mark Waite
>
> On Thu, Feb 18, 2021 at 9:47 PM Mk  wrote:
>
>>
>> Hello Jenkins Community team,
>>
>> I am using *Jenkins - 2.263.1(LTS)* deployed through tomcat.
>>
>> I have upgraded few of the plugins yesterday since then i am facing 
>> following issue whenever i modify any settings under *Manage Jenkins* 
>> --> *Configure Systems* section if i click save button. it takes few 
>> mins and throws the below error.
>>
>> HTTP Status 403 – Forbidden
>> Type Status Report
>> Message No valid crumb was included in the request
>> Description The server understood the request but refuses to authorize it.
>> Apache Tomcat/9.0.30
>>
>> From jenkins systems log below message shown.
>>
>> Feb 18, 2021 7:52:13 AM WARNING hudson.ExpressionFactory2$JexlExpression 
>> evaluate
>>
>> Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in 
>> /jenkins/configure. Reason: java.lang.NullPointerException: Descriptor list 
>> is null for context 'class hudson.model.Hudson' in thread 'Handling GET 
>> /jenkins/configure from 206.25.26.27 : http-nio-8080-exec-2 
>> Jenkins/configure.jelly GlobalLibraries/config.jelly 
>> LibraryConfiguration/config.jelly SCMRetriever/DescriptorImpl/config.jelly 
>> MultiSCM/DescriptorImpl/config.jelly'
>> java.lang.NullPointerException: Descriptor list is null for context 
>> 'class hudson.model.Hudson' in thread 'Handling GET /jenkins/configure from 
>> 206.25.26.27 : http-nio-8080-exec-2 Jenkins/configure.jelly 
>> GlobalLibraries/config.jelly LibraryConfiguration/config.jelly 
>> SCMRetriever/DescriptorImpl/config.jelly 
>> MultiSCM/DescriptorImpl/config.jelly'
>> at 
>> hudson.model.DescriptorVisibilityFilter.apply(DescriptorVisibilityFilter.java:73)
>> at hudson.Functions.filterDescriptors(Functions.java:2122)
>> at sun.reflect.GeneratedMethodAccessor308.invoke(Unknown Source)
>> at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>>
>> Under *Configure Global security --> CSRF Protection -->Enable proxy 
>> compatibility*(Enabled). Still same problem persists. Therefore please 
>> help me to solve this issue.
>>
>> Thanks in advance.
>>
>> -- 
>> 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/5813788e-3157-45f5-b2d4-f906b3ce8228n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/5813788e-3157-45f5-b2d4-f906b3ce8228n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/916407dc-b449-41f8-a52a-ced5a7f32932n%40googlegroups.com.

Re: HTTP Status 403 – Forbidden error

2021-02-18 Thread Mk 
Thanks Mark. I have uninstalled the *MultiSCM plugin* and restarted the 
service. However still i am experiencing the same problem*. (**Manage 
Jenkins* --> *Configure Systems* section post any modification if i click 
save button it fails). Now from systems log i can below above errors 
disappeared.

Feb 19, 2021 10:56:05 AM WARNING hudson.security.csrf.CrumbFilter doFilter
No valid crumb was included in request for /jenkins/configSubmit by 
vasanth.guru. Returning 403.

On Friday, February 19, 2021 at 10:31:23 AM UTC+5:30 Mark Waite wrote:

> That null pointer exception seems likely to have been caused by one of the 
> plugins that was updated.  Since it is mentioning LibraryConfiguration, 
> SCMRetriever, and MultiSCM, you might first look at the 
> workflow-cps-global-lib and the multiple-scms plugin to see if either of 
> them were recently upgraded.
>
> The MultipleSCMs plugin has been deprecated.  Jenkins Pipeline is the 
> better way to implement multiple SCM support from within a single job.
>
> Mark Waite
>
> On Thu, Feb 18, 2021 at 9:47 PM Mk  wrote:
>
>>
>> Hello Jenkins Community team,
>>
>> I am using *Jenkins - 2.263.1(LTS)* deployed through tomcat.
>>
>> I have upgraded few of the plugins yesterday since then i am facing 
>> following issue whenever i modify any settings under *Manage Jenkins* 
>> --> *Configure Systems* section if i click save button. it takes few 
>> mins and throws the below error.
>>
>> HTTP Status 403 – Forbidden
>> Type Status Report
>> Message No valid crumb was included in the request
>> Description The server understood the request but refuses to authorize it.
>> Apache Tomcat/9.0.30
>>
>> From jenkins systems log below message shown.
>>
>> Feb 18, 2021 7:52:13 AM WARNING hudson.ExpressionFactory2$JexlExpression 
>> evaluate
>>
>> Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in 
>> /jenkins/configure. Reason: java.lang.NullPointerException: Descriptor list 
>> is null for context 'class hudson.model.Hudson' in thread 'Handling GET 
>> /jenkins/configure from 206.25.26.27 : http-nio-8080-exec-2 
>> Jenkins/configure.jelly GlobalLibraries/config.jelly 
>> LibraryConfiguration/config.jelly SCMRetriever/DescriptorImpl/config.jelly 
>> MultiSCM/DescriptorImpl/config.jelly'
>> java.lang.NullPointerException: Descriptor list is null for context 
>> 'class hudson.model.Hudson' in thread 'Handling GET /jenkins/configure from 
>> 206.25.26.27 : http-nio-8080-exec-2 Jenkins/configure.jelly 
>> GlobalLibraries/config.jelly LibraryConfiguration/config.jelly 
>> SCMRetriever/DescriptorImpl/config.jelly 
>> MultiSCM/DescriptorImpl/config.jelly'
>> at 
>> hudson.model.DescriptorVisibilityFilter.apply(DescriptorVisibilityFilter.java:73)
>> at hudson.Functions.filterDescriptors(Functions.java:2122)
>> at sun.reflect.GeneratedMethodAccessor308.invoke(Unknown Source)
>> at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>>
>> Under *Configure Global security --> CSRF Protection -->Enable proxy 
>> compatibility*(Enabled). Still same problem persists. Therefore please 
>> help me to solve this issue.
>>
>> Thanks in advance.
>>
>> -- 
>> 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/5813788e-3157-45f5-b2d4-f906b3ce8228n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/5813788e-3157-45f5-b2d4-f906b3ce8228n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/3f23087f-d1cd-4fbb-9a6b-30d4bf96dafbn%40googlegroups.com.

HTTP Status 403 – Forbidden error

2021-02-18 Thread Mk 

Hello Jenkins Community team,

I am using *Jenkins - 2.263.1(LTS)* deployed through tomcat.

I have upgraded few of the plugins yesterday since then i am facing 
following issue whenever i modify any settings under *Manage Jenkins* --> 
*Configure 
Systems* section if i click save button. it takes few mins and throws the 
below error.

HTTP Status 403 – Forbidden
Type Status Report
Message No valid crumb was included in the request
Description The server understood the request but refuses to authorize it.
Apache Tomcat/9.0.30

>From jenkins systems log below message shown.

Feb 18, 2021 7:52:13 AM WARNING hudson.ExpressionFactory2$JexlExpression 
evaluate

Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in 
/jenkins/configure. Reason: java.lang.NullPointerException: Descriptor list 
is null for context 'class hudson.model.Hudson' in thread 'Handling GET 
/jenkins/configure from 206.25.26.27 : http-nio-8080-exec-2 
Jenkins/configure.jelly GlobalLibraries/config.jelly 
LibraryConfiguration/config.jelly SCMRetriever/DescriptorImpl/config.jelly 
MultiSCM/DescriptorImpl/config.jelly'
java.lang.NullPointerException: Descriptor list is null for context 'class 
hudson.model.Hudson' in thread 'Handling GET /jenkins/configure from 
206.25.26.27 : http-nio-8080-exec-2 Jenkins/configure.jelly 
GlobalLibraries/config.jelly LibraryConfiguration/config.jelly 
SCMRetriever/DescriptorImpl/config.jelly 
MultiSCM/DescriptorImpl/config.jelly'
at 
hudson.model.DescriptorVisibilityFilter.apply(DescriptorVisibilityFilter.java:73)
at hudson.Functions.filterDescriptors(Functions.java:2122)
at sun.reflect.GeneratedMethodAccessor308.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)

Under *Configure Global security --> CSRF Protection -->Enable proxy 
compatibility*(Enabled). Still same problem persists. Therefore please help 
me to solve this issue.

Thanks in advance.

-- 
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/5813788e-3157-45f5-b2d4-f906b3ce8228n%40googlegroups.com.

hostPathVolume not mounting on Kubernetes pods(Dynamic Jenkins Agent)

2020-12-04 Thread Mk 
*Environment: *
Jenkins - Version 2.235.5  (LTS) 
Kubernetes Jenkins Plugin - 1.27.7 
 

*K8s-Master & Worker Server Details:- *
OS - CentOS Linux release 7.9.2009 (Core) & Kernal - 
3.10.0-1160.6.1.el7.x86_64 
Docker Version - 19.03.12 
Client Version: v1.19.0 
Server Version: v1.19.0 

I am trying to mount a *hostPathVolume *through Jenkins Kubernetes-plugin 
*podTemplate 
*and when the pod gets kicked off via Jenkins master the path of my K8s 
worker not getting mounted on K8s pods(Jenkins Agent). 

I have the below podTemplate 

podTemplate(containers: [ 
containerTemplate(name: 'build', image: 'alpine/git', ttyEnabled: true, 
command: 'cat'), 
containerTemplate(name: 'test', image: 'maven:3.3.9-jdk-8-alpine', command: 
'cat', ttyEnabled: true), 
], 
volumes: [ 
hostPathVolume(mountPath: '/home/jenkins', hostPath: 
'/test-vol/abc/workspace'), 
] 
) { 
node ("jenkins-node") { 
stage('Code Checkout') { 
checkout([$class: 'GitSCM', branches: [[name: '*/master']], 
doGenerateSubmoduleConfigurations: false, extensions: [[$class: 
'CloneOption', depth: 0, noTags: false, reference: '', shallow: false, 
timeout: 120]], submoduleCfg: [], userRemoteConfigs: [[url: 
'ssh://userid@gerrit-server:29418/abc/repository']]]) 
} 
} 
node(POD_LABEL) { 
stage('Build') { 
container('build') { 
sh label: '', script: '''cd /home/jenkins/Jenkins_Job/project/src/ 
mvn clean install''' 
} 
stage('Test') { 
container('test') { 
sh label: '', script: '''cd /home/jenkins/Jenkins_Job/project/src/ 
mvn test''' 
} 
} 
} 
} 
} 
I expect the volume to be mounted in my pod, I have tried with *K8s v1.19.4* 
and *Kubernetes Jenkins Plugin - 1.27.0* but same result. Not sure what is 
causing the problem on *CentOS-7.9* K8s. Whereas the same is working 
perfectly on *CentOS - 8.2.2004 (Core) & 4.18.0-193.14.2.el8_2.x86_64 
kernal. *

-- 
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/73c67b12-bea5-4e9b-b51a-0acf83f1bd76n%40googlegroups.com.

Re: Jenkins Integration with LDAP - Testing Connection Fails

2020-09-01 Thread Mk 
I have fixed it. Each time when we change/update the *"Display Name LDAP 
attribute" *value in LDAP configuration section, We need to delete the user 
from people category and need to login. Post that it displays the 
configured settings.

On Wednesday, September 2, 2020 at 9:57:31 AM UTC+5:30, Mk wrote:
>
> Team, Is it possible to display only *First name + Sur-name* in Jenkins?
>
>
> On Friday, August 28, 2020 at 9:56:39 AM UTC+5:30, Mk wrote:
>>
>> Dear Team,
>>
>> Now our LDAP Authentication working fine. I have question regarding 
>> "*Display 
>> Name LDAP attribute*: *displayname*" i have configured like this and for 
>> all logged in users, The display name shown as like below which is too 
>> lengthy/long.
>>
>> First-Name/Sur-Name/Team-Name/Location/Title/Company-Name
>>
>> Would like to display only *First-Name + Sur-Name*. For this i tried to 
>> change Display Name LDAP attribute: with name such as *givenName, cn* & *sn 
>> *but none of them are worked. So is it possible to display only *First 
>> name + Sur-name* in Jenkins for logged-in users?
>>
>> On Sunday, August 23, 2020 at 10:37:42 AM UTC+5:30, Mk wrote:
>>>
>>> Hi Jeremy,
>>>
>>> Even LDAP Login slowness issue also resolved with below configuration.
>>>
>>> Group membership filter - (memberOf={0})
>>>
>>> Enable cache
>>> Cache size - 200
>>> Cache TTL - 30min
>>>
>>> Now everything working as excepted, But would like to know that 
>>> currently i am running* root DN* as *empty *and *enabled - Allow blank 
>>> rootDN* in plugin section. Is this is fine?
>>>
>>> On Saturday, August 22, 2020 at 11:55:37 AM UTC+5:30, Mk wrote:
>>>>
>>>> Hi Jeremy,
>>>>
>>>> I have tried by keeping the *root DN* as *empty *and enabled the* tick 
>>>> mark - Allow blank rootDN. *now my test connection is successful but 
>>>> took around *4mins* to show the successful result. Below is the 
>>>> configuration used.
>>>>
>>>> root DN - Allow blank rootDN
>>>>
>>>> User search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>>> User search filter: sAMAccountName={0}
>>>> Group search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>>> Group search filter: (&(objectclass=group)(cn={0}))
>>>> Group membership
>>>>   Group membership filter - (&(objectCategory=group)(member:1.2.
>>>> 840.113556.1.4.1941:={0}))
>>>> Manager DN: CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>>> Manager Password: password
>>>> Display Name LDAP attribute: displayname
>>>> Email Address LDAP attribute: mail
>>>>
>>>> Now how to figureout the login performace issue? Another thing keeping 
>>>> the *root DN* empty does not an issue?
>>>>
>>>>
>>>> On Saturday, August 22, 2020 at 10:00:55 AM UTC+5:30, Mk wrote:
>>>>>
>>>>> Hi Jeremy, Thanks for the reply. Actually *ldapsearch* command on 
>>>>> jenkins master server terminal works. Below is the response. 
>>>>>
>>>>> ldapsearch -x -h ad-ldap-server.com -p 389 -D 
>>>>> "CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com"  -b 
>>>>> "OU=Users,OU=Division,OU=Team,DC=domain,DC=com" 
>>>>> "(sAMAccountName=jenkins)" -W
>>>>> Enter LDAP Password:
>>>>> # extended LDIF
>>>>> #
>>>>> # LDAPv3
>>>>> # base  with scope 
>>>>> subtree
>>>>> # filter: (sAMAccountName=jenkins)
>>>>> # requesting: ALL
>>>>> #
>>>>>
>>>>> # search result
>>>>> search: 2
>>>>> result: 0 Success
>>>>>
>>>>> # numResponses: 2
>>>>> # numEntries: 1
>>>>>
>>>>> Since i am getting reponse so seems i have permission to query the 
>>>>> AD(LDAP) server.
>>>>>
>>>>> Also tried *Login name case sensitivity* & *Group name case 
>>>>> sensitivity* - Both with *Case sensitive* & *Case insensitive *but 
>>>>> still same result. 
>>>>>
>>>>>
>>>>>
>>>>> On Friday, August 21, 2020 at 11:44:56 PM UTC+5:30, jeremy mordkoff 
>>>>> wrote:
>>>>>>
>>

Re: Jenkins Integration with LDAP - Testing Connection Fails

2020-09-01 Thread Mk 
Team, Is it possible to display only *First name + Sur-name* in Jenkins?


On Friday, August 28, 2020 at 9:56:39 AM UTC+5:30, Mk wrote:
>
> Dear Team,
>
> Now our LDAP Authentication working fine. I have question regarding "*Display 
> Name LDAP attribute*: *displayname*" i have configured like this and for 
> all logged in users, The display name shown as like below which is too 
> lengthy/long.
>
> First-Name/Sur-Name/Team-Name/Location/Title/Company-Name
>
> Would like to display only *First-Name + Sur-Name*. For this i tried to 
> change Display Name LDAP attribute: with name such as *givenName, cn* & *sn 
> *but none of them are worked. So is it possible to display only *First 
> name + Sur-name* in Jenkins for logged-in users?
>
> On Sunday, August 23, 2020 at 10:37:42 AM UTC+5:30, Mk wrote:
>>
>> Hi Jeremy,
>>
>> Even LDAP Login slowness issue also resolved with below configuration.
>>
>> Group membership filter - (memberOf={0})
>>
>> Enable cache
>> Cache size - 200
>> Cache TTL - 30min
>>
>> Now everything working as excepted, But would like to know that currently 
>> i am running* root DN* as *empty *and *enabled - Allow blank rootDN* in 
>> plugin section. Is this is fine?
>>
>> On Saturday, August 22, 2020 at 11:55:37 AM UTC+5:30, Mk wrote:
>>>
>>> Hi Jeremy,
>>>
>>> I have tried by keeping the *root DN* as *empty *and enabled the* tick 
>>> mark - Allow blank rootDN. *now my test connection is successful but 
>>> took around *4mins* to show the successful result. Below is the 
>>> configuration used.
>>>
>>> root DN - Allow blank rootDN
>>>
>>> User search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>> User search filter: sAMAccountName={0}
>>> Group search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>> Group search filter: (&(objectclass=group)(cn={0}))
>>> Group membership
>>>   Group membership filter - (&(objectCategory=group)(member:1.2.
>>> 840.113556.1.4.1941:={0}))
>>> Manager DN: CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>> Manager Password: password
>>> Display Name LDAP attribute: displayname
>>> Email Address LDAP attribute: mail
>>>
>>> Now how to figureout the login performace issue? Another thing keeping 
>>> the *root DN* empty does not an issue?
>>>
>>>
>>> On Saturday, August 22, 2020 at 10:00:55 AM UTC+5:30, Mk wrote:
>>>>
>>>> Hi Jeremy, Thanks for the reply. Actually *ldapsearch* command on 
>>>> jenkins master server terminal works. Below is the response. 
>>>>
>>>> ldapsearch -x -h ad-ldap-server.com -p 389 -D 
>>>> "CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com"  -b 
>>>> "OU=Users,OU=Division,OU=Team,DC=domain,DC=com" 
>>>> "(sAMAccountName=jenkins)" -W
>>>> Enter LDAP Password:
>>>> # extended LDIF
>>>> #
>>>> # LDAPv3
>>>> # base  with scope 
>>>> subtree
>>>> # filter: (sAMAccountName=jenkins)
>>>> # requesting: ALL
>>>> #
>>>>
>>>> # search result
>>>> search: 2
>>>> result: 0 Success
>>>>
>>>> # numResponses: 2
>>>> # numEntries: 1
>>>>
>>>> Since i am getting reponse so seems i have permission to query the 
>>>> AD(LDAP) server.
>>>>
>>>> Also tried *Login name case sensitivity* & *Group name case 
>>>> sensitivity* - Both with *Case sensitive* & *Case insensitive *but 
>>>> still same result. 
>>>>
>>>>
>>>>
>>>> On Friday, August 21, 2020 at 11:44:56 PM UTC+5:30, jeremy mordkoff 
>>>> wrote:
>>>>>
>>>>> sounds like the user is valid but not a member of any groups. Is that 
>>>>> possible? 
>>>>>
>>>>>
>>>>>
>>>>> On Thursday, August 20, 2020 at 1:28:21 PM UTC-4 Mk wrote:
>>>>>
>>>>>> Hi Team,
>>>>>>
>>>>>> I am trying to configure LDAP(AD) Authentication in our Jenkins, 
>>>>>> Below is my configuration settings, But test LDAP connection is failing.
>>>>>>
>>>>>> Environment:-
>>>>>> Jenkins Version - 2.235.5(LTS)
>>>>>> LDAP Plugin - 1.24
>>>>>>
>>>>>>

Re: K8s jenkins dynamic agent fails & shows - tcpSlaveAgentListener error

2020-08-30 Thread Mk 


Team, It was an kubernetes DNS resolution issue. With the help of following 
link - 
https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/ 
created (*dnsutils.yaml*) pod and found that my K8s cluster pods was 
returning following error "*connection timed out; no servers could be 
reached"* for below command.


kubectl exec -i -t dnsutils -- nslookup kubernetes.default


So i have uninstalled and re-installed *Kubernetes version - v1.19.0*. Now 
everything working fine.  Thanks.!!!


On Friday, August 28, 2020 at 10:16:45 AM UTC+5:30, Mk wrote:
>
> Dear Team,
>
> I have *Jenkins Master* &* K8s-Master* running on same server(*CentOS-8*), 
> Configured Jenkins *Kubernetes Plugin version - 1.26.4* But while running 
> pipeline job i always getting an error, Below is K8s cluster jenkins agent 
> pod log.
>
> [root@K8s-Master /]# kubectl logs -f pipeline-test-33-sj6tl-r0clh-g559d -c 
> jnlp
>
> Aug 08, 2020 8:37:21 AM hudson.remoting.jnlp.Main createEngine
> INFO: Setting up agent: pipeline-test-33-sj6tl-r0clh-g559d
> Aug 08, 2020 8:37:21 AM hudson.remoting.jnlp.Main$CuiListener 
> INFO: Jenkins agent is running in headless mode.
> Aug 08, 2020 8:37:21 AM hudson.remoting.Engine startEngine
> INFO: Using Remoting version: 4.3
> Aug 08, 2020 8:37:21 AM org.jenkinsci.remoting.engine.WorkDirManager 
> initializeWorkDir
> INFO: Using /home/jenkins/agent/remoting as a remoting work directory
> Aug 08, 2020 8:37:21 AM org.jenkinsci.remoting.engine.WorkDirManager 
> setupLogging
> INFO: Both error and output logs will be printed to 
> /home/jenkins/agent/remoting
> Aug 08, 2020 8:37:21 AM hudson.remoting.jnlp.Main$CuiListener status
> INFO: Locating server among [http://jenkins-serverjenkins/]
> Aug 08, 2020 8:37:41 AM hudson.remoting.jnlp.Main$CuiListener error
>
> SEVERE: Failed to connect to 
> http://jenkins-server/jenkins/tcpSlaveAgentListener/: jenkins-server
> java.io.IOException: Failed to connect to 
> http://jenkins-serverjenkins/tcpSlaveAgentListener/: jenkins-server
> at 
> org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:217)
> at hudson.remoting.Engine.innerRun(Engine.java:693)
> at hudson.remoting.Engine.run(Engine.java:518)
> Caused by: java.net.UnknownHostException: jenkins-server
> at 
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:607)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
> at sun.net.www.http.HttpClient.(HttpClient.java:242)
> at sun.net.www.http.HttpClient.New(HttpClient.java:339)
> at sun.net.www.http.HttpClient.New(HttpClient.java:357)
> at 
> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1226)
> at 
> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1162)
> at 
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1056)
> at 
> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:990)
> at 
> org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:214)
>
>
> ... 2 more
>
>
> Below settings configuration already enabled glocal security section.
>
> Manage Jenkins --> Configure Global Security --> Agents Random [Enabled]
>
>
>
> [image: 1.png]
>
>
>
>
> I am successfully able to communicate from my Jenkins to the K8s master 
> cluster(Verified in Jenkins Cloud section).
>
> Even in K8s master server all the namespace pods are running. *Flannel 
> CNI installed*, Not sure what is causing problem with agent provisioning 
> through Jenkins.
>
> Would appreciate any suggestions.
>

-- 
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/b0e419c3-c06a-4052-b5cd-64609b038d55o%40googlegroups.com.

Re: K8s jenkins dynamic agent fails & shows - tcpSlaveAgentListener error

2020-08-29 Thread Mk 


Hi Richard, 

 

Thanks for the reply. Sorry i didn't give my environment details before. 
Please find my environment details below.

 

*Server:-1*

*Jenkins Master & Kubernetes Cluster Master Server Environment (Both 
deployed in same physical server).*

*OS - Centos-8.2*

*Jenkins Version - Jenkins 2.235.3 (Deployed through Tomcat Apache) - 
Jenkins not on K8s cluster.*

*Jenkins Kubernetes Plugin version - 1.26.4*

*Jenkins URL - http://jenkins-server/jenkins/ 
<http://jenkins-server/jenkins/>*

 

kubectl version --short
Client Version: v1.18.8
Server Version: v1.18.8


*Server:-2*

*Kubernetes Worker-Node Server Environment:-*

*OS - Centos-8.2*


K8s-Worker Node I am referring my Kubernetes cluster node(Currently i have 
single K8s-Worker-Node) and my Jenkins master pod template doesn't have any 
namespace (it is just empty) in my Jenkins cloud configuration section GUI.


Earlier my */etc/hosts* file in both server was like below. Addtionally i 
tried adding the following (*jenkins-server.company.domain.com* & 
*k8s-node-1.company.domain.com*)


127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4

::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

75.76.77.5  jenkins-server

75.76.77.6  k8s-node-1

 
Since from my *K8s-Worker-Node* server getting response through *curl *commands 
to Jenkins master. so i feel it looks there is no issue with Kubernetes 
Jenkins plugin confiugration. it would be mostly DNS resolution issue with 
Kubernetes cluster. 

In my K8s Master server all namespaces pods are running. Also below is my 
K8s master & Worker node's */etc/resolv.conf* file. For K8s DNS resolving 
any other configuration required?

# cat /etc/resolv.conf
# Generated by NetworkManager

nameserver 61.62.63.41
nameserver 61.62.63.42

What are configuration that I need to do to resolve this problem? Please 
help me. Thanks.


On Saturday, August 29, 2020 at 2:36:06 PM UTC+5:30, Richard Bywater wrote:
>
> What is the K8s-Worker node that you are referring to? You didn't mention 
> that in the first email so I'm not sure where that fits in. Also which 
> entries did you actually put into the /etc/hosts file as you don't say what 
> it looked like before.
>
> I'm fairly new to K8s myself but my main question would be whether or not 
> you have a service defined in the namespace fronting the Jenkins master 
> called 'jenkins-server'?
>
> Richard.
>
> On Fri, 28 Aug 2020 at 18:29, Mk > wrote:
>
>> Further tried by adding below entries in */etc/hosts* file on both 
>> *Jenkins/K8s 
>> Master* and* K8s-Worker* node system as well. But still result is same.
>>
>> # cat /etc/hosts
>> 127.0.0.1   localhost localhost.localdomain localhost4 
>> localhost4.localdomain4
>> ::1 localhost localhost.localdomain localhost6 
>> localhost6.localdomain6
>>
>> 75.76.77.5  jenkins-server jenkins-server.company.domain.com
>> 75.76.77.6  k8s-node-1 k8s-node-1.company.domain.com
>>
>>
>> *Executed below on K8s-Worker node.*
>>
>> #  curl -I http://jenkins-server/jenkins/tcpSlaveAgentListener/
>> HTTP/1.1 200
>> Server: nginx/1.14.1
>> Date: Fri, 28 Aug 2020 06:13:34 GMT
>> Content-Type: text/plain;charset=UTF-8
>> Connection: keep-alive
>> Cache-Control: private
>> Expires: Thu, 01 Jan 1970 00:00:00 GMT
>> X-Content-Type-Options: nosniff
>> X-Hudson-JNLP-Port: 40021
>> X-Jenkins-JNLP-Port: 40021
>> X-Instance-Identity: 
>> MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnkgz8Av2x8R9R2KZDzWm1K11O01r7VDikW48rCNQlgw
>> /pUeNSPJu9pv7kH884tOE65GkMepNdtJcOFQFtY1qZ0sr5y4GF5TOc7+U/
>> TqfwULt60r7OQlKcrsQx/jJkF0xLjR+xaJ64WKnbsl0AiZhd8/
>> ynk02UxFXKcgwkEP2PGpGyQ1ps5t/
>> yj6ueFiPAHX2ssK8aI7ynVbf3YyVrtFOlqhnTy11mJFoLAZnpjYRCJsrX5z/
>> xciVq5c2XmEikLzMpjFl0YBAsDo7JL4eBUwiBr64HPcSKrsBBB9oPE4oI6GkYUCAni8uOLfzoNr9B1eImaETYSdVPdSKW
>> /ez/OeHjQIDAQAB
>> X-Jenkins-Agent-Protocols: JNLP4-connect, Ping
>> X-Remoting-Minimum-Version: 3.14
>>
>> # curl http://jenkins-server:40021/
>> Jenkins-Agent-Protocols: JNLP4-connect, Ping
>> Jenkins-Version: 2.235.3
>> Jenkins-Session: 4455fd45
>> Client: 75.76.77.6
>> Server: 75.76.77.5
>> Remoting-Minimum-Version: 3.14
>>
>>
>>
>>
>> On Friday, August 28, 2020 at 10:16:45 AM UTC+5:30, Mk wrote:
>>>
>>> Dear Team,
>>>
>>> I have *Jenkins Master* &* K8s-Master* running on same server(*CentOS-8*), 
>>> Configured Jenkins *Kubernetes Plugin version - 1.26.4* But while 
>>> running pipeline job i always getting an error, Below is K8s cluster 
>>> jenkins agent pod log.

Re: Failed to connect to http://jenkins.build-env.svc.cluster.local:8080/tcpSlaveAgentListener/: jenkins.build-env.svc.cluster.local

2020-08-28 Thread Mk 
Hi Pbasan,

Now i too facing the same problem. I am using CentOS-8 (Jenkins & K8s) 
running in same server. But Jenkins running separately(Not running on K8s 
cluster).  My error as follows.

SEVERE: Failed to connect to 
http://jenkins-server/jenkins/tcpSlaveAgentListener/: jenkins-server
java.io.IOException: Failed to connect to 
http://jenkins-serverjenkins/tcpSlaveAgentListener/: jenkins-server
at 
org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:217)
at hudson.remoting.Engine.innerRun(Engine.java:693)
at hudson.remoting.Engine.run(Engine.java:518)
Caused by: java.net.UnknownHostException: jenkins-server


Please share the fix, it would be helpful. Thanks.

On Tuesday, November 21, 2017 at 4:34:58 PM UTC+5:30, WANG, YAN-HONG wrote:
>
> In my case, we run Jenkins also in K8S. So Jenkins expose with K8S service.
>
> 2017-11-21 11:38 GMT+01:00 >:
>
>> Yes we installed Jenkins separately (not on K8s cluster).
>>
>> On Tuesday, November 21, 2017 at 1:22:55 PM UTC+5:30, YAN-HONG WANG wrote:
>>>
>>> You use Jenkins, but *not using as a service?*
>>>
>>> *Or?*
>>>
>>> 2017-11-21 8:50 GMT+01:00 YAN-HONG WANG :
>>>
 Hi Basanta,

 Because the DNS mechanism seem are different in Ubuntu and CentOS.
 If using CentOS, and install K8S by default way maybe not a problem.

 But, in Ubuntu. I need to add nameserver into 
 /etc/resolvconf/resolv.conf.d/head or /etc/resolvconf/resolv.conf.d/tail.
 And then 'resolvconf -u' update /etc/resolv.conf. So kubeadm will also 
 add my nameserver into K8S.

 That's my environment condition.

 Hope this help you.

 Hong


 Am Dienstag, 21. November 2017 06:06:27 UTC+1 schrieb 
 pbasan...@gmail.com:
>
> Hi Hong,
>
> Here is the detail of the Environment 
> Installed k8s and Jenkins on the one Master server (Linux) and the 
> jobs are running on Master.(with out slave nodes)
> But when we tried on 1 Master and 2 slave nodes , the jobs are failing 
> with error 
> =
> Nov 16, 2017 6:22:51 AM hudson.remoting.jnlp.Main$CuiListener error
> SEVERE: Failed to connect to 
> http://slc13pef.us.oracle.com:8080/tcpSlaveAgentListener/: 
> slc13pef.us.oracle.com
> java.io.IOException: Failed to connect to 
> http://slc13pef.us.oracle.com:8080/tcpSlaveAgentListener/: 
> slc13pef.us.oracle.com
> at 
> org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:161)
> at hudson.remoting.Engine.innerRun(Engine.java:495)
> at hudson.remoting.Engine.run(Engine.java:447)
> Caused by: java.net.UnknownHostException: slc13pef.us.oracle.com
> ==
> Here we installed Jenkins and not using as a service.
> Regards,
> Basanta
>
> On Tuesday, November 21, 2017 at 10:01:24 AM UTC+5:30, 
> pbasan...@gmail.com wrote:
>>
>> Hi Hong,
>> We are using Linux machine 
>> But i think the issue reported on this thread is nothing to do with 
>> Operating System.
>> Regards,
>> Basanta
>>
>> On Monday, November 20, 2017 at 9:13:08 PM UTC+5:30, YAN-HONG WANG 
>> wrote:
>>>
>>> Hello,
>>>
>>> Do you use Ubuntu machine to be your base?
>>>
>>> Hong
>>>
>>> Am Montag, 20. November 2017 12:14:02 UTC+1 schrieb 
>>> pbasan...@gmail.com:

 Hi Hong,
 We are hitting the Same error as mentioned above .. Can you please 
 share the steps followed to resolve this error.
 =
 Nov 16, 2017 6:22:51 AM hudson.remoting.jnlp.Main$CuiListener error
 SEVERE: Failed to connect to 
 http://slc13pef.us.oracle.com:8080/tcpSlaveAgentListener/: 
 slc13pef.us.oracle.com
 java.io.IOException: Failed to connect to 
 http://slc13pef.us.oracle.com:8080/tcpSlaveAgentListener/: 
 slc13pef.us.oracle.com
 at 
 org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:161)
 at hudson.remoting.Engine.innerRun(Engine.java:495)
 at hudson.remoting.Engine.run(Engine.java:447)
 Caused by: java.net.UnknownHostException: slc13pef.us.oracle.com
  
 ==
 Regards,
 Basanta


 On Thursday, October 12, 2017 at 5:40:36 PM UTC+5:30, YAN-HONG WANG 
 wrote:
>
> Hello Carlos,
>
> I fixed problem already.
> Thanks.
>
> Hong
>
> Am Dienstag, 10. Oktober 2017 14:26:47 UTC+2 schrieb YAN-HONG WANG:
>>
>> Hello Carlos,
>>
>> In containerTemplate, I define one container "worker".
>>
>> ---

Re: K8s jenkins dynamic agent fails & shows - tcpSlaveAgentListener error

2020-08-27 Thread Mk 
Further tried by adding below entries in */etc/hosts* file on both *Jenkins/K8s 
Master* and* K8s-Worker* node system as well. But still result is same.

# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

75.76.77.5  jenkins-server jenkins-server.company.domain.com
75.76.77.6  k8s-node-1 k8s-node-1.company.domain.com


*Excuted below on K8s-Worker node.*

#  curl -I http://jenkins-server/jenkins/tcpSlaveAgentListener/
HTTP/1.1 200
Server: nginx/1.14.1
Date: Fri, 28 Aug 2020 06:13:34 GMT
Content-Type: text/plain;charset=UTF-8
Connection: keep-alive
Cache-Control: private
Expires: Thu, 01 Jan 1970 00:00:00 GMT
X-Content-Type-Options: nosniff
X-Hudson-JNLP-Port: 40021
X-Jenkins-JNLP-Port: 40021
X-Instance-Identity: 
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnkgz8Av2x8R9R2KZDzWm1K11O01r7VDikW48rCNQlgw
/pUeNSPJu9pv7kH884tOE65GkMepNdtJcOFQFtY1qZ0sr5y4GF5TOc7+U/
TqfwULt60r7OQlKcrsQx/jJkF0xLjR+xaJ64WKnbsl0AiZhd8/
ynk02UxFXKcgwkEP2PGpGyQ1ps5t/
yj6ueFiPAHX2ssK8aI7ynVbf3YyVrtFOlqhnTy11mJFoLAZnpjYRCJsrX5z/
xciVq5c2XmEikLzMpjFl0YBAsDo7JL4eBUwiBr64HPcSKrsBBB9oPE4oI6GkYUCAni8uOLfzoNr9B1eImaETYSdVPdSKW
/ez/OeHjQIDAQAB
X-Jenkins-Agent-Protocols: JNLP4-connect, Ping
X-Remoting-Minimum-Version: 3.14

# curl http://jenkins-server:40021/
Jenkins-Agent-Protocols: JNLP4-connect, Ping
Jenkins-Version: 2.235.3
Jenkins-Session: 4455fd45
Client: 75.76.77.6
Server: 75.76.77.5
Remoting-Minimum-Version: 3.14




On Friday, August 28, 2020 at 10:16:45 AM UTC+5:30, Mk wrote:
>
> Dear Team,
>
> I have *Jenkins Master* &* K8s-Master* running on same server(*CentOS-8*), 
> Configured Jenkins *Kubernetes Plugin version - 1.26.4* But while running 
> pipeline job i always getting an error, Below is K8s cluster jenkins agent 
> pod log.
>
> [root@K8s-Master /]# kubectl logs -f pipeline-test-33-sj6tl-r0clh-g559d -c 
> jnlp
>
> Aug 08, 2020 8:37:21 AM hudson.remoting.jnlp.Main createEngine
> INFO: Setting up agent: pipeline-test-33-sj6tl-r0clh-g559d
> Aug 08, 2020 8:37:21 AM hudson.remoting.jnlp.Main$CuiListener 
> INFO: Jenkins agent is running in headless mode.
> Aug 08, 2020 8:37:21 AM hudson.remoting.Engine startEngine
> INFO: Using Remoting version: 4.3
> Aug 08, 2020 8:37:21 AM org.jenkinsci.remoting.engine.WorkDirManager 
> initializeWorkDir
> INFO: Using /home/jenkins/agent/remoting as a remoting work directory
> Aug 08, 2020 8:37:21 AM org.jenkinsci.remoting.engine.WorkDirManager 
> setupLogging
> INFO: Both error and output logs will be printed to 
> /home/jenkins/agent/remoting
> Aug 08, 2020 8:37:21 AM hudson.remoting.jnlp.Main$CuiListener status
> INFO: Locating server among [http://jenkins-serverjenkins/]
> Aug 08, 2020 8:37:41 AM hudson.remoting.jnlp.Main$CuiListener error
>
> SEVERE: Failed to connect to 
> http://jenkins-server/jenkins/tcpSlaveAgentListener/: jenkins-server
> java.io.IOException: Failed to connect to 
> http://jenkins-serverjenkins/tcpSlaveAgentListener/: jenkins-server
> at 
> org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:217)
> at hudson.remoting.Engine.innerRun(Engine.java:693)
> at hudson.remoting.Engine.run(Engine.java:518)
> Caused by: java.net.UnknownHostException: jenkins-server
> at 
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:607)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
> at sun.net.www.http.HttpClient.(HttpClient.java:242)
> at sun.net.www.http.HttpClient.New(HttpClient.java:339)
> at sun.net.www.http.HttpClient.New(HttpClient.java:357)
> at 
> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1226)
> at 
> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1162)
> at 
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1056)
> at 
> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:990)
> at 
> org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:214)
>
>
> ... 2 more
>
>
> Below settings configuration already enabled glocal security section.
>
> Manage Jenkins --> Configure Global Security --> Agents Random [Enabled]
>
>
>
> [image: 1.png]
>
>
>
>
> I am successfully able to communicate from my Jenkins to the K8s ma

K8s jenkins dynamic agent fails & shows - tcpSlaveAgentListener error

2020-08-27 Thread Mk 
Dear Team,

I have *Jenkins Master* &* K8s-Master* running on same server(*CentOS-8*), 
Configured Jenkins *Kubernetes Plugin version - 1.26.4* But while running 
pipeline job i always getting an error, Below is K8s cluster jenkins agent 
pod log.

[root@K8s-Master /]# kubectl logs -f pipeline-test-33-sj6tl-r0clh-g559d -c jnlp

Aug 08, 2020 8:37:21 AM hudson.remoting.jnlp.Main createEngine
INFO: Setting up agent: pipeline-test-33-sj6tl-r0clh-g559d
Aug 08, 2020 8:37:21 AM hudson.remoting.jnlp.Main$CuiListener 
INFO: Jenkins agent is running in headless mode.
Aug 08, 2020 8:37:21 AM hudson.remoting.Engine startEngine
INFO: Using Remoting version: 4.3
Aug 08, 2020 8:37:21 AM org.jenkinsci.remoting.engine.WorkDirManager 
initializeWorkDir
INFO: Using /home/jenkins/agent/remoting as a remoting work directory
Aug 08, 2020 8:37:21 AM org.jenkinsci.remoting.engine.WorkDirManager 
setupLogging
INFO: Both error and output logs will be printed to /home/jenkins/agent/remoting
Aug 08, 2020 8:37:21 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [http://jenkins-serverjenkins/]
Aug 08, 2020 8:37:41 AM hudson.remoting.jnlp.Main$CuiListener error

SEVERE: Failed to connect to 
http://jenkins-server/jenkins/tcpSlaveAgentListener/: jenkins-server
java.io.IOException: Failed to connect to 
http://jenkins-serverjenkins/tcpSlaveAgentListener/: jenkins-server
at 
org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:217)
at hudson.remoting.Engine.innerRun(Engine.java:693)
at hudson.remoting.Engine.run(Engine.java:518)
Caused by: java.net.UnknownHostException: jenkins-server
at 
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:607)
at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
at sun.net.www.http.HttpClient.(HttpClient.java:242)
at sun.net.www.http.HttpClient.New(HttpClient.java:339)
at sun.net.www.http.HttpClient.New(HttpClient.java:357)
at 
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1226)
at 
sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1162)
at 
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1056)
at 
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:990)
at 
org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:214)


... 2 more


Below settings configuration already enabled glocal security section.

Manage Jenkins --> Configure Global Security --> Agents Random [Enabled]



[image: 1.png]




I am successfully able to communicate from my Jenkins to the K8s master 
cluster(Verified in Jenkins Cloud section).

Even in K8s master server all the namespace pods are running. *Flannel CNI 
installed*, Not sure what is causing problem with agent provisioning 
through Jenkins.

Would appreciate any suggestions.

-- 
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/7100644f-f843-4726-8627-9e889ac89484o%40googlegroups.com.

Re: Jenkins Integration with LDAP - Testing Connection Fails

2020-08-27 Thread Mk 
Dear Team,

Now our LDAP Authentication working fine. I have question regarding "*Display 
Name LDAP attribute*: *displayname*" i have configured like this and for 
all logged in users, The display name shown as like below which is too 
lengthy/long.

First-Name/Sur-Name/Team-Name/Location/Title/Company-Name

Would like to display only *First-Name + Sur-Name*. For this i tried to 
change Display Name LDAP attribute: with name such as *givenName, cn* & *sn 
*but none of them are worked. So is it possible to display only *First name 
+ Sur-name* in Jenkins for logged-in users?

On Sunday, August 23, 2020 at 10:37:42 AM UTC+5:30, Mk wrote:
>
> Hi Jeremy,
>
> Even LDAP Login slowness issue also resolved with below configuration.
>
> Group membership filter - (memberOf={0})
>
> Enable cache
> Cache size - 200
> Cache TTL - 30min
>
> Now everything working as excepted, But would like to know that currently 
> i am running* root DN* as *empty *and *enabled - Allow blank rootDN* in 
> plugin section. Is this is fine?
>
> On Saturday, August 22, 2020 at 11:55:37 AM UTC+5:30, Mk wrote:
>>
>> Hi Jeremy,
>>
>> I have tried by keeping the *root DN* as *empty *and enabled the* tick 
>> mark - Allow blank rootDN. *now my test connection is successful but 
>> took around *4mins* to show the successful result. Below is the 
>> configuration used.
>>
>> root DN - Allow blank rootDN
>>
>> User search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>> User search filter: sAMAccountName={0}
>> Group search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>> Group search filter: (&(objectclass=group)(cn={0}))
>> Group membership
>>   Group membership filter - (&(objectCategory=group)(member:1.2.
>> 840.113556.1.4.1941:={0}))
>> Manager DN: CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>> Manager Password: password
>> Display Name LDAP attribute: displayname
>> Email Address LDAP attribute: mail
>>
>> Now how to figureout the login performace issue? Another thing keeping 
>> the *root DN* empty does not an issue?
>>
>>
>> On Saturday, August 22, 2020 at 10:00:55 AM UTC+5:30, Mk wrote:
>>>
>>> Hi Jeremy, Thanks for the reply. Actually *ldapsearch* command on 
>>> jenkins master server terminal works. Below is the response. 
>>>
>>> ldapsearch -x -h ad-ldap-server.com -p 389 -D 
>>> "CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com"  -b 
>>> "OU=Users,OU=Division,OU=Team,DC=domain,DC=com" 
>>> "(sAMAccountName=jenkins)" -W
>>> Enter LDAP Password:
>>> # extended LDIF
>>> #
>>> # LDAPv3
>>> # base  with scope subtree
>>> # filter: (sAMAccountName=jenkins)
>>> # requesting: ALL
>>> #
>>>
>>> # search result
>>> search: 2
>>> result: 0 Success
>>>
>>> # numResponses: 2
>>> # numEntries: 1
>>>
>>> Since i am getting reponse so seems i have permission to query the 
>>> AD(LDAP) server.
>>>
>>> Also tried *Login name case sensitivity* & *Group name case sensitivity* 
>>> - Both with *Case sensitive* & *Case insensitive *but still same 
>>> result. 
>>>
>>>
>>>
>>> On Friday, August 21, 2020 at 11:44:56 PM UTC+5:30, jeremy mordkoff 
>>> wrote:
>>>>
>>>> sounds like the user is valid but not a member of any groups. Is that 
>>>> possible? 
>>>>
>>>>
>>>>
>>>> On Thursday, August 20, 2020 at 1:28:21 PM UTC-4 Mk wrote:
>>>>
>>>>> Hi Team,
>>>>>
>>>>> I am trying to configure LDAP(AD) Authentication in our Jenkins, Below 
>>>>> is my configuration settings, But test LDAP connection is failing.
>>>>>
>>>>> Environment:-
>>>>> Jenkins Version - 2.235.5(LTS)
>>>>> LDAP Plugin - 1.24
>>>>>
>>>>>
>>>>> Server - ldap://ad-ldap-server.com
>>>>> root DN: DC=domain,DC=com
>>>>> User search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>>>> User search filter: sAMAccountName={0}
>>>>> Group search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>>>> Group search filter: (&(objectclass=group)(cn={0}))
>>>>> Group membership
>>>>>   Group membership filter - 
>>>>> (&(objectCategory=group)(member:1.2.840.113556.1.4.1941:={0}))
>>>>> Manager DN: CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>>>> Manager Password: password
>>>>> Display Name LDAP attribute: displayname
>>>>> Email Address LDAP attribute: mail
>>>>>
>>>>>
>>>>> Error Message:-
>>>>>
>>>>> [image: 1.png]
>>>>>
>>>>> Please let me know what is missing in my configuration?. Any help 
>>>>> would be appreciated.
>>>>>
>>>>

-- 
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/3976221a-c5e1-4045-a5be-4d0d9e423069o%40googlegroups.com.

Re: Jenkins Integration with LDAP - Testing Connection Fails

2020-08-22 Thread Mk 
Hi Jeremy,

Even LDAP Login slowness issue also resolved with below configuration.

Group membership filter - (memberOf={0})

Enable cache
Cache size - 200
Cache TTL - 30min

Now everything working as excepted, But would like to know that currently i 
am running* root DN* as *empty *and *enabled - Allow blank rootDN* in 
plugin section. Is this is fine?

On Saturday, August 22, 2020 at 11:55:37 AM UTC+5:30, Mk wrote:
>
> Hi Jeremy,
>
> I have tried by keeping the *root DN* as *empty *and enabled the* tick 
> mark - Allow blank rootDN. *now my test connection is successful but took 
> around *4mins* to show the successful result. Below is the configuration 
> used.
>
> root DN - Allow blank rootDN
>
> User search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
> User search filter: sAMAccountName={0}
> Group search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
> Group search filter: (&(objectclass=group)(cn={0}))
> Group membership
>   Group membership filter - (&(objectCategory=group)(member:1.2.
> 840.113556.1.4.1941:={0}))
> Manager DN: CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com
> Manager Password: password
> Display Name LDAP attribute: displayname
> Email Address LDAP attribute: mail
>
> Now how to figureout the login performace issue? Another thing keeping the 
> *root 
> DN* empty does not an issue?
>
>
> On Saturday, August 22, 2020 at 10:00:55 AM UTC+5:30, Mk wrote:
>>
>> Hi Jeremy, Thanks for the reply. Actually *ldapsearch* command on 
>> jenkins master server terminal works. Below is the response. 
>>
>> ldapsearch -x -h ad-ldap-server.com -p 389 -D 
>> "CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com"  -b 
>> "OU=Users,OU=Division,OU=Team,DC=domain,DC=com" 
>> "(sAMAccountName=jenkins)" -W
>> Enter LDAP Password:
>> # extended LDIF
>> #
>> # LDAPv3
>> # base  with scope subtree
>> # filter: (sAMAccountName=jenkins)
>> # requesting: ALL
>> #
>>
>> # search result
>> search: 2
>> result: 0 Success
>>
>> # numResponses: 2
>> # numEntries: 1
>>
>> Since i am getting reponse so seems i have permission to query the 
>> AD(LDAP) server.
>>
>> Also tried *Login name case sensitivity* & *Group name case sensitivity* 
>> - Both with *Case sensitive* & *Case insensitive *but still same result. 
>>
>>
>>
>> On Friday, August 21, 2020 at 11:44:56 PM UTC+5:30, jeremy mordkoff wrote:
>>>
>>> sounds like the user is valid but not a member of any groups. Is that 
>>> possible? 
>>>
>>>
>>>
>>> On Thursday, August 20, 2020 at 1:28:21 PM UTC-4 Mk wrote:
>>>
>>>> Hi Team,
>>>>
>>>> I am trying to configure LDAP(AD) Authentication in our Jenkins, Below 
>>>> is my configuration settings, But test LDAP connection is failing.
>>>>
>>>> Environment:-
>>>> Jenkins Version - 2.235.5(LTS)
>>>> LDAP Plugin - 1.24
>>>>
>>>>
>>>> Server - ldap://ad-ldap-server.com
>>>> root DN: DC=domain,DC=com
>>>> User search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>>> User search filter: sAMAccountName={0}
>>>> Group search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>>> Group search filter: (&(objectclass=group)(cn={0}))
>>>> Group membership
>>>>   Group membership filter - 
>>>> (&(objectCategory=group)(member:1.2.840.113556.1.4.1941:={0}))
>>>> Manager DN: CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>>> Manager Password: password
>>>> Display Name LDAP attribute: displayname
>>>> Email Address LDAP attribute: mail
>>>>
>>>>
>>>> Error Message:-
>>>>
>>>> [image: 1.png]
>>>>
>>>> Please let me know what is missing in my configuration?. Any help would 
>>>> be appreciated.
>>>>
>>>

-- 
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/7d05dc28-3945-4fcb-965b-637bd4c723c7o%40googlegroups.com.

Re: Jenkins Integration with LDAP - Testing Connection Fails

2020-08-21 Thread Mk 
Hi Jeremy,

I have tried by keeping the *root DN* as *empty *and enabled the* tick mark 
- Allow blank rootDN. *now my test connection is successful but took around 
*4mins* to show the successful result. Below is the configuration used.

root DN - Allow blank rootDN

User search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
User search filter: sAMAccountName={0}
Group search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
Group search filter: (&(objectclass=group)(cn={0}))
Group membership
  Group membership filter - (&(objectCategory=group)(member:1.2.
840.113556.1.4.1941:={0}))
Manager DN: CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com
Manager Password: password
Display Name LDAP attribute: displayname
Email Address LDAP attribute: mail

Now how to figureout the login performace issue? Another thing keeping the 
*root 
DN* empty does not an issue?


On Saturday, August 22, 2020 at 10:00:55 AM UTC+5:30, Mk wrote:
>
> Hi Jeremy, Thanks for the reply. Actually *ldapsearch* command on jenkins 
> master server terminal works. Below is the response. 
>
> ldapsearch -x -h ad-ldap-server.com -p 389 -D 
> "CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com"  -b 
> "OU=Users,OU=Division,OU=Team,DC=domain,DC=com" "(sAMAccountName=jenkins)" 
> -W
> Enter LDAP Password:
> # extended LDIF
> #
> # LDAPv3
> # base  with scope subtree
> # filter: (sAMAccountName=jenkins)
> # requesting: ALL
> #
>
> # search result
> search: 2
> result: 0 Success
>
> # numResponses: 2
> # numEntries: 1
>
> Since i am getting reponse so seems i have permission to query the 
> AD(LDAP) server.
>
> Also tried *Login name case sensitivity* & *Group name case sensitivity* 
> - Both with *Case sensitive* & *Case insensitive *but still same result. 
>
>
>
> On Friday, August 21, 2020 at 11:44:56 PM UTC+5:30, jeremy mordkoff wrote:
>>
>> sounds like the user is valid but not a member of any groups. Is that 
>> possible? 
>>
>>
>>
>> On Thursday, August 20, 2020 at 1:28:21 PM UTC-4 Mk wrote:
>>
>>> Hi Team,
>>>
>>> I am trying to configure LDAP(AD) Authentication in our Jenkins, Below 
>>> is my configuration settings, But test LDAP connection is failing.
>>>
>>> Environment:-
>>> Jenkins Version - 2.235.5(LTS)
>>> LDAP Plugin - 1.24
>>>
>>>
>>> Server - ldap://ad-ldap-server.com
>>> root DN: DC=domain,DC=com
>>> User search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>> User search filter: sAMAccountName={0}
>>> Group search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>> Group search filter: (&(objectclass=group)(cn={0}))
>>> Group membership
>>>   Group membership filter - 
>>> (&(objectCategory=group)(member:1.2.840.113556.1.4.1941:={0}))
>>> Manager DN: CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>>> Manager Password: password
>>> Display Name LDAP attribute: displayname
>>> Email Address LDAP attribute: mail
>>>
>>>
>>> Error Message:-
>>>
>>> [image: 1.png]
>>>
>>> Please let me know what is missing in my configuration?. Any help would 
>>> be appreciated.
>>>
>>

-- 
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/3f90c60f-155c-4107-8fc1-4a9c44782f0bo%40googlegroups.com.

Re: Jenkins Integration with LDAP - Testing Connection Fails

2020-08-21 Thread Mk 
Hi Jeremy, Thanks for the reply. Actually *ldapsearch* command on jenkins 
master server terminal works. Below is the response. 

ldapsearch -x -h ad-ldap-server.com -p 389 -D 
"CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com"  -b 
"OU=Users,OU=Division,OU=Team,DC=domain,DC=com" "(sAMAccountName=jenkins)" -
W
Enter LDAP Password:
# extended LDIF
#
# LDAPv3
# base  with scope subtree
# filter: (sAMAccountName=jenkins)
# requesting: ALL
#

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1

Since i am getting reponse so seems i have permission to query the AD(LDAP) 
server.

Also tried *Login name case sensitivity* & *Group name case sensitivity* - 
Both with *Case sensitive* & *Case insensitive *but still same result. 



On Friday, August 21, 2020 at 11:44:56 PM UTC+5:30, jeremy mordkoff wrote:
>
> sounds like the user is valid but not a member of any groups. Is that 
> possible? 
>
>
>
> On Thursday, August 20, 2020 at 1:28:21 PM UTC-4 Mk wrote:
>
>> Hi Team,
>>
>> I am trying to configure LDAP(AD) Authentication in our Jenkins, Below is 
>> my configuration settings, But test LDAP connection is failing.
>>
>> Environment:-
>> Jenkins Version - 2.235.5(LTS)
>> LDAP Plugin - 1.24
>>
>>
>> Server - ldap://ad-ldap-server.com
>> root DN: DC=domain,DC=com
>> User search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>> User search filter: sAMAccountName={0}
>> Group search base: OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>> Group search filter: (&(objectclass=group)(cn={0}))
>> Group membership
>>   Group membership filter - 
>> (&(objectCategory=group)(member:1.2.840.113556.1.4.1941:={0}))
>> Manager DN: CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com
>> Manager Password: password
>> Display Name LDAP attribute: displayname
>> Email Address LDAP attribute: mail
>>
>>
>> Error Message:-
>>
>> [image: 1.png]
>>
>> Please let me know what is missing in my configuration?. Any help would 
>> be appreciated.
>>
>

-- 
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/07d7b887-2990-4949-bf37-5dd8e482111co%40googlegroups.com.

Re: Loading certain view tabs takes forever

2013-04-04 Thread MK 
I am facing similar issues with views, tried it with different view types, 
like filtered or all. The log does not tell anything, removing the progress 
bar column plugin was not of success.

Even with new views I now face this issue.

Markus

On Thursday, April 26, 2012 3:07:23 PM UTC+2, pgweiss wrote:
>
> I don't understand why this should be, but it happens to me quite 
> often: I click a view tab and wait many, many, seconds for it to be 
> loaded. This doesn't happen for the main view, nor does it happen for 
> all the views, but in my case, it happens with a view that I use quite 
> regularly.  There is nothing particularly special about the view: it 
> is a view defined by checking off a bunch of jobs, rather than a 
> regexp. The regexp views seem to load faster. 
>
> Any thoughts? 
>
> -P 
>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.