[JIRA] (JENKINS-53856) Fix error during snapshotting "unable to access '/root/.config/git/attributes': Permission denied"
Title: Message Title Baptiste Mathus updated JENKINS-53856 Jenkins / JENKINS-53856 Fix error during snapshotting "unable to access '/root/.config/git/attributes': Permission denied" Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53856) Fix error during snapshotting "unable to access '/root/.config/git/attributes': Permission denied"
Title: Message Title Baptiste Mathus updated JENKINS-53856 Jenkins / JENKINS-53856 Fix error during snapshotting "unable to access '/root/.config/git/attributes': Permission denied" Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53856) Fix error during snapshotting "unable to access '/root/.config/git/attributes': Permission denied"
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53856
Fix error during snapshotting "unable to access '/root/.config/git/attributes': Permission denied"
Change By:
Baptiste Mathus
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:{noformat}instance_1 | info: [snapshotting] stdout: '[master 6894d0d] UL4->UL5 Snapshot after downloads completed, before Jenkins restartinstance_1 | 2 files changed, 2 insertions(+), 1 deletion(-)instance_1 | 'instance_1 | error: [snapshotting] stderr: 'warning: unable to access '/root/.config/git/attributes': Permission deniedinstance_1 | warning: unable to access '/root/.config/git/attributes': Permission denied{noformat}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: * {noformat}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 764instance_1 | npm ERR! path /root/.npm/_logsinstance_1 | npm ERR! code EACCESinstance_1 | npm ERR! errno -13instance_1 | npm ERR! syscall scandirinstance_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 userinstance_1 | npm ERR! instance_1 | npm ERR! If you believe this might be a permissions issue, please double-check theinstance_1 | npm ERR! permissions of the file and its containing directories, or try runninginstance_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{noformat}
[JIRA] (JENKINS-53856) Fix error during snapshotting "unable to access '/root/.config/git/attributes': Permission denied"
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-53856
Fix error during snapshotting "unable to access '/root/.config/git/attributes': Permission denied"
Change By:
Baptiste Mathus
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 :{noformat}instance_1 | info: [snapshotting] stdout: '[master 6894d0d] UL4->UL5 Snapshot after downloads completed, before Jenkins restartinstance_1 | 2 files changed, 2 insertions(+), 1 deletion(-)instance_1 | 'instance_1 | error: [snapshotting] stderr: 'warning: unable to access '/root/ . config/git/attributes': Permission deniedinstance_1 | warning: unable to access '/root/.config/git/attributes': Permission denied{noformat}I think we just need to set HOME for the evergreen-client. Since supervisord only changes setuid.I'm pretty sure it would also fix the node related error in the go:{noformat}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 764instance_1 | npm ERR! path /root/.npm/_logsinstance_1 | npm ERR! code EACCESinstance_1 | npm ERR! errno -13instance_1 | npm ERR! syscall scandirinstance_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 userinstance_1 | npm ERR! instance_1 | npm ERR! If you believe this might be a permissions issue, please double-check theinstance_1 | npm ERR! permissions of the file and its containing directories, or try runninginstance_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{noformat}
[JIRA] (JENKINS-53856) Fix error during snapshotting "unable to access '/root/.config/git/attributes': Permission denied"
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-53856 Fix error during snapshotting "unable to access '/root/.config/git/attributes': Permission denied" Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53856) Fix error during snapshotting "unable to access '/root/.config/git/attributes': Permission denied"
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53856 Fix error during snapshotting "unable to access '/root/.config/git/attributes': Permission denied" Issue Type: Bug Assignee: R. Tyler Croy Components: evergreen Created: 2018-10-01 15:44 Labels: evergreen Priority: Minor Reporter: Baptiste Mathus 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. Add Comment
[JIRA] (JENKINS-53856) Fix error during snapshotting "unable to access '/root/.config/git/attributes': Permission denied"
Title: Message Title Baptiste Mathus started work on JENKINS-53856 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
