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

Fix error during snapshotting "unable to access '/root/.config/git/attributes': Permission denied"

    Details

    • Similar Issues:
    • Sprint:
      Evergreen - Milestone 2

      Description

      Though this is apparently not stopping anything from working, this is annoying and distracting as I'm testing the rollback and going through quite a lot of logs many times:

      instance_1  | info: [snapshotting] stdout: '[master 6894d0d] UL4->UL5 Snapshot after downloads completed, before Jenkins restart
      instance_1  |  2 files changed, 2 insertions(+), 1 deletion(-)
      instance_1  | '
      instance_1  | error: [snapshotting] stderr: 'warning: unable to access '/root/.config/git/attributes': Permission denied
      instance_1  | warning: unable to access '/root/.config/git/attributes': Permission denied
      

      I think we just need to set HOME for the evergreen-client. Since supervisord only changes setuid.

      Update: oh BTW I'm pretty sure it would also fix the node related error in the go:

      instance_1  | 2018-10-01 15:34:35,827 INFO exited: evergreen-client (exit status 243; not expected)
      instance_1  | 2018-10-01 15:34:36,832 INFO spawned: 'evergreen-client' with pid 764
      instance_1  | npm ERR! path /root/.npm/_logs
      instance_1  | npm ERR! code EACCES
      instance_1  | npm ERR! errno -13
      instance_1  | npm ERR! syscall scandir
      instance_1  | npm ERR! Error: EACCES: permission denied, scandir '/root/.npm/_logs'
      instance_1  | npm ERR!  { [Error: EACCES: permission denied, scandir '/root/.npm/_logs']
      instance_1  | npm ERR!   stack:
      instance_1  | npm ERR!    'Error: EACCES: permission denied, scandir \'/root/.npm/_logs\'',
      instance_1  | npm ERR!   errno: -13,
      instance_1  | npm ERR!   code: 'EACCES',
      instance_1  | npm ERR!   syscall: 'scandir',
      instance_1  | npm ERR!   path: '/root/.npm/_logs' }
      instance_1  | npm ERR! 
      instance_1  | npm ERR! The operation was rejected by your operating system.
      instance_1  | npm ERR! It is likely you do not have the permissions to access this file as the current user
      instance_1  | npm ERR! 
      instance_1  | npm ERR! If you believe this might be a permissions issue, please double-check the
      instance_1  | npm ERR! permissions of the file and its containing directories, or try running
      instance_1  | npm ERR! the command again as root/Administrator (though this is not recommended).
      instance_1  | glob error { [Error: EACCES: permission denied, scandir '/root/.npm/_logs']
      instance_1  |   stack:
      instance_1  |    'Error: EACCES: permission denied, scandir \'/root/.npm/_logs\'',
      instance_1  |   errno: -13,
      instance_1  |   code: 'EACCES',
      instance_1  |   syscall: 'scandir',
      instance_1  |   path: '/root/.npm/_logs' }
      instance_1  | 
      instance_1  | > evergreen-client@1.0.0 client /evergreen/client
      

        Attachments

          Issue Links

            Activity

            There are no comments yet on this issue.

              People

              • Assignee:
                batmat Baptiste Mathus
                Reporter:
                batmat Baptiste Mathus
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: