•  
      request #8922 gitolite : user NOT in sudoers
    Infos
    #8922
    Jérôme Oufella (jero)
    2016-03-02 18:33
    2016-03-02 01:05
    9030
    Details
    gitolite : user NOT in sudoers

    Looking at our servers mail log, I noticed the following messages on the servers inbox:

     myserver000 : Mar 17:15:15 : gitolite : user NOT in sudoers ; TTY=unknown ; PWD=/var/lib/tuleap/gitolite/repositories/projectname/repo.git ; USER=codendiadm ; COMMAND=/usr/share/codendi/src/utils/php-launcher.sh /usr/share/codendi/plugins/git/hooks/post-receive.php /var/lib/tuleap/gitolite/repositories/projectname/repo.git

    Should there be a sudoers entry normally?

    Empty
    8.11
    CentOS 6
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Declined
    2016-03-02
    Attachments
    Empty
    References
    References list is empty

    Follow-ups

    User avatar
    Jérôme Oufella (jero)2016-03-02 18:16

    Sorry for the noise Manuel, I realized the server config was likely broken by an external system, post installation of tuleap, breaking the inclusion of the sudoers.d subdirectory. This is a non-issue.


    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Jérôme Oufella (jero)2016-03-02 01:07

    Tuleap version info:

    # rpm -qf /usr/share/codendi/src/utils/php-launcher.sh
    tuleap-8.11.99.80-1.el6.noarch

    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Jérôme Oufella (jero)2016-03-02 01:06
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Jérôme Oufella (jero)2016-03-02 01:05
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes