Skip to main content

Tuleap Community Edition development and releases are no longer public. You have until September 30th to download packages and sources in Tuleap project. You can contact the team if you need further assistance.

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #13338 gitolite setup broken on fresh Tuleap 11 (CentOS 7)
    Infos
    #13338
    Marc Lijour (marclijour)
    2025-11-17 16:33
    2019-04-27 11:57
    14464
    Details
    gitolite setup broken on fresh Tuleap 11 (CentOS 7)

    I noticed recurring SYSTEM_CHECK errors in the logs.

    /var/lib/gitolite/.ssh/authorized_keys is empty. In order to retrieve a file with the gitolite admin public key, run the script : /usr/share/tuleap/plugins/git/bin/recreate_authorized_keys.sh

    There are several problems in this script:

    • /etc/init.d/codendi doesn't exist (do we mean service tuleap stop/start instead?)

    • public_key=$($CAT /home/codendiadm/.ssh/id_rsa_gl-adm.pub) has several problems:
      • there is no /home/codendiadm 
      • instead /etc/passwd refers to /var/lib/tuleap as the home dir of user codendiadm
      • but there are no .ssh directory there, and no public key either
    • gitolite appears in /var/lib/gitolite and /var/lib/gitolite3 (which is it?)
    • file /usr/bin/gl-auth-command doesn't exist
    • file  /var/lib/codendi/gitolite/admin doesn't exist

    To test Git, I created a repo in one of the projects. The repo is stuck in the creation queue.

    What's missing to get Git to work?

    SCM/Git
    11.0
    EL7 (CentOS|RHEL)
    • [ ] enhancement
    • [ ] internal improvement
    Manuel Vacelet (vaceletm), Lyderic Dubut (ldubut)
    Stage
    Empty
    Waiting for information
    Empty
    Attachments
    Empty
    References
    Referenced by request #13338

    Artifact

    request #11862 gitolite setup broken
    Display settings

    Follow-ups

    User avatar
    Ahmed KALLEL (ahmedkallel)2025-11-17 16:33

    fatal: not a git repository: '/var/lib/tuleap/gitolite/admin/.git' fatal: not a git repository (or any of the parent directories): .git

    User avatar
    Ahmed KALLEL (ahmedkallel)2025-11-17 16:21

    FATAL: errors found but logfile could not be created FATAL: /var/lib/gitolite/.gitolite/logs/gitolite-2025-11.log: Permission denied FATAL: cli gitolite setup --pubkey /tmp/id_rsa_gl-adm.pub

    User avatar
    Alejandro Gay (gayalejandro)2020-03-24 15:05
    Clean install have the same issue in a Centos 7, repositories can't be created, the system_check fails, returning this error /var/lib/gitolite/.ssh/authorized_keys is empty. In order to retrieve a file with the gitolite admin public key, run the scrip .... and when you run the script has errors
    User avatar
    Nicholas Geoffrion (neehasa)2019-05-30 14:43
    Hi,
    I'm having a similar issue and I've done some digging with my colleagues:

    If you look at the content of /var/log/tuleap/git_syslog, you can see that there are some errors with admin permissions.
    This is a fresh install with import from pre CentOS 7.
    Currently, I can push and pull existing repos but not create new ones.


    ```
    2019-05-30T14:38:25+02:00 [20620] [error] [SystemEventProcessor] An error happened during execution of post actions: Command execution failure: /opt/rh/sclo-git212/root/usr/bin/git --work-tree='/var/lib/tuleap/gitolite/admin' --git-dir='/var/lib/tuleap/gitolite/admin/.git' push --porcelain origin master (return value: 128):
    Permission denied, please try again.
    Permission denied, please try again.
    Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
    fatal: Could not read from remote repository.

    Please make sure you have the correct access rights
    and the repository exists.
    ```
    User avatar
    Thomas Gerbet (tgerbet)2019-05-03 09:07
    Hi,

    Yes the error message is not correct and the suggestions can not work on recent instances. It needs to be updated.

    I have I'm however not able to reproduce your issue on a fresh install. Is this something you always reproduce? If yes, can you give the steps to reproduce it?
    • Status changed from New to Waiting for information