Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-59250

fatal: Authentication failed for jenkins

    Details

    • Similar Issues:

      Description

       
       Good morning guys, I have a problem building my pipeline in jenkins, sometimes some jobs returning authentication error and sometimes they are working.
       

       

      Started by upstream project "PIPELINE_OI" build number 35 originally caused by:
       
      {{Started by user Administrador Jenkins OI[EnvInject] - Loading node environment variables.Building in workspace /var/lib/jenkins/workspace/TRUNK/AUDITORIA J14/poi-auditoria-commons-j14
      using credential dbebfd81-9cc5-4693-ad12-5b7f0e7dc845Cloning the remote Git repositoryCloning repository https://innersource.accenture.com/scm/pmoi/auditoria-vj14_poi-auditoria-commons-j14.git> git init /var/lib/jenkins/workspace/TRUNK/AUDITORIA J14/poi-auditoria-commons-j14 # timeout=10Fetching upstream changes from https://innersource.accenture.com/scm/pmoi/auditoria-vj14_poi-auditoria-commons-j14.git> git --version # timeout=10using GIT_ASKPASS to set credentials > git fetch --tags --progress https://innersource.accenture.com/scm/pmoi/auditoria-vj14_poi-auditoria-commons-j14.git +refs/heads/:refs/remotes/origin/*ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "git fetch --tags --progress https://innersource.accenture.com/scm/pmoi/auditoria-vj14_poi-auditoria-commons-j14.git +refs/heads/:refs/remotes/origin/*" returned status code 128:

      stdout:
      stderr: fatal: Authentication failed for 'https://innersource.accenture.com/scm/pmoi/auditoria-vj14_poi-auditoria-commons-j14.git/'

      at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042)
      at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761)
      at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72)
      at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442)
      at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:655)
      at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1152)
      at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192)
      at hudson.scm.SCM.checkout(SCM.java:504)
      at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
      at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
      at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
      at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
      at hudson.model.Run.execute(Run.java:1816)
      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
      at hudson.model.ResourceController.execute(ResourceController.java:97)
      at hudson.model.Executor.run(Executor.java:429)
      ERROR: Error cloning remote repo 'origin'
      [WS-CLEANUP] Deleting project workspace...
      [WS-CLEANUP] Deferred wipeout is used...
      [WS-CLEANUP] done
      Finished: FAILURE}}

       

      sometimes passed, and sometimes returning this authentication error.

        Attachments

          Activity

          victor_silva Victor Silva created issue -
          victor_silva Victor Silva made changes -
          Field Original Value New Value
          Description Started by upstream project "PIPELINE_OI" build number 35 originally caused by:
           
          {{Started by user Administrador Jenkins OI[EnvInject] - Loading node environment variables.Building in workspace /var/lib/jenkins/workspace/TRUNK/AUDITORIA J14/poi-auditoria-commons-j14
          using credential dbebfd81-9cc5-4693-ad12-5b7f0e7dc845Cloning the remote Git repositoryCloning repository https://innersource.accenture.com/scm/pmoi/auditoria-vj14_poi-auditoria-commons-j14.git> git init /var/lib/jenkins/workspace/TRUNK/AUDITORIA J14/poi-auditoria-commons-j14 # timeout=10Fetching upstream changes from https://innersource.accenture.com/scm/pmoi/auditoria-vj14_poi-auditoria-commons-j14.git> git --version # timeout=10using GIT_ASKPASS to set credentials > git fetch --tags --progress https://innersource.accenture.com/scm/pmoi/auditoria-vj14_poi-auditoria-commons-j14.git +refs/heads/*:refs/remotes/origin/*ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "git fetch --tags --progress https://innersource.accenture.com/scm/pmoi/auditoria-vj14_poi-auditoria-commons-j14.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:

          stdout:
          stderr: fatal: Authentication failed for 'https://innersource.accenture.com/scm/pmoi/auditoria-vj14_poi-auditoria-commons-j14.git/'

          at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042)
          at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761)
          at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72)
          at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442)
          at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:655)
          at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1152)
          at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192)
          at hudson.scm.SCM.checkout(SCM.java:504)
          at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
          at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
          at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
          at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
          at hudson.model.Run.execute(Run.java:1816)
          at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
          at hudson.model.ResourceController.execute(ResourceController.java:97)
          at hudson.model.Executor.run(Executor.java:429)
          ERROR: Error cloning remote repo 'origin'
          [WS-CLEANUP] Deleting project workspace...
          [WS-CLEANUP] Deferred wipeout is used...
          [WS-CLEANUP] done
          Finished: FAILURE}}
           
           Good morning guys, I have a problem building my pipeline in jenkins, sometimes some jobs returning authentication error and sometimes they are working.
           

           

          Started by upstream project "PIPELINE_OI" build number 35 originally caused by:
            
           {{Started by user Administrador Jenkins OI[EnvInject] - Loading node environment variables.Building in workspace /var/lib/jenkins/workspace/TRUNK/AUDITORIA J14/poi-auditoria-commons-j14
           using credential dbebfd81-9cc5-4693-ad12-5b7f0e7dc845Cloning the remote Git repositoryCloning repository [https://innersource.accenture.com/scm/pmoi/auditoria-vj14_poi-auditoria-commons-j14.git]> git init /var/lib/jenkins/workspace/TRUNK/AUDITORIA J14/poi-auditoria-commons-j14 # timeout=10Fetching upstream changes from [https://innersource.accenture.com/scm/pmoi/auditoria-vj14_poi-auditoria-commons-j14.git]> git --version # timeout=10using GIT_ASKPASS to set credentials > git fetch --tags --progress [https://innersource.accenture.com/scm/pmoi/auditoria-vj14_poi-auditoria-commons-j14.git] +refs/heads/*:refs/remotes/origin/*ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "git fetch --tags --progress [https://innersource.accenture.com/scm/pmoi/auditoria-vj14_poi-auditoria-commons-j14.git] +refs/heads/*:refs/remotes/origin/*" returned status code 128:

          stdout:
           stderr: fatal: Authentication failed for 'https://innersource.accenture.com/scm/pmoi/auditoria-vj14_poi-auditoria-commons-j14.git/'

          at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042)
           at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761)
           at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72)
           at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442)
           at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:655)
           at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1152)
           at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192)
           at hudson.scm.SCM.checkout(SCM.java:504)
           at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
           at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
           at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
           at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
           at hudson.model.Run.execute(Run.java:1816)
           at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
           at hudson.model.ResourceController.execute(ResourceController.java:97)
           at hudson.model.Executor.run(Executor.java:429)
           ERROR: Error cloning remote repo 'origin'
           [WS-CLEANUP] Deleting project workspace...
           [WS-CLEANUP] Deferred wipeout is used...
           [WS-CLEANUP] done
           Finished: FAILURE}}

           

          sometimes passed, and sometimes returning this authentication error.
          Hide
          markewaite Mark Waite added a comment -

          This is probably best answered through the Jenkins user mailing list or the Jenkins chat channels. Alternately, if you're running a CloudBees product, you could open a CloudBees support ticket.

          Intermittent failures typically involve investigations of several possible causes, looking for hints in log files and elsewhere which will explain the intermittent failure:

          • Are there log entries on the git server at about the same time which hint at an overload condition?
          • Are there authentication log entries on an LDAP or active directory or other server which might get more details on why the credentials were rejected?
          • Are there more details logs on the Jenkins server which might hint at global issues (low memory, etc.) which might cause the problem?
          • Are the authentication failures specific to a single agent or a subset of agents?

          All those topics are best addressed in the mailing list or the chat channels.

          Show
          markewaite Mark Waite added a comment - This is probably best answered through the Jenkins user mailing list or the Jenkins chat channels. Alternately, if you're running a CloudBees product, you could open a CloudBees support ticket. Intermittent failures typically involve investigations of several possible causes, looking for hints in log files and elsewhere which will explain the intermittent failure: Are there log entries on the git server at about the same time which hint at an overload condition? Are there authentication log entries on an LDAP or active directory or other server which might get more details on why the credentials were rejected? Are there more details logs on the Jenkins server which might hint at global issues (low memory, etc.) which might cause the problem? Are the authentication failures specific to a single agent or a subset of agents? All those topics are best addressed in the mailing list or the chat channels.
          markewaite Mark Waite made changes -
          Status Open [ 1 ] Fixed but Unreleased [ 10203 ]
          Resolution Not A Defect [ 7 ]
          markewaite Mark Waite made changes -
          Status Fixed but Unreleased [ 10203 ] Closed [ 6 ]

            People

            • Assignee:
              markewaite Mark Waite
              Reporter:
              victor_silva Victor Silva
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: