Skip to main content

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 #8152 Could not dump ssh keys for user
    Actions
    Infos
    #8152
    DarkByte (darkbyte)
    2021-01-04 13:23
    2015-06-17 12:48
    8177
    Details
    Could not dump ssh keys for user
    Hello, i have CentOS 6.6 with last update (today) and latest version of Tuleap (thanks for this fabulous forge)

    My problem is, when i add my SSH key on my account.
    in administration i can see :

    SystemEvent_EDIT_SSH_KEYS root ERROR 2 user: #102 2015-05-09 01:45:28 2015-05-09 01:59:01 2015-05-09 01:59:01 Could not dump ssh keys for user FooUser

    And gitolite don't work.

    Do you have any idae why i have this problem ?
    Thanks you

    P.S : i have exactly the same problem with Tuleap appliance 8.2
    Clean install. Tuleap seems worked. but i get "Could not dump ssh keys for user admin"

    P.S 2 : https://tuleap.net/plugins/forumml/message.php?group_id=101&topic=33132&list=1
    SCM/Git
    8.2
    CentOS 6
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2021-01-04
    Attachments
    Artifact links
    Empty
    Empty
    References
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2021-01-04 13:23
    No news in the last 3 years, I'm going to close.
    • Status changed from Waiting for information to Closed
    • Close date set to 2021-01-04
    User avatar
    Thomas Gerbet (tgerbet)2017-12-07 10:18
    There has been a lot of improvements in this area since 2 years ago through request #9970 and request #10242.

    Unless you are running a Tuleap instance that you haven't upgraded in 2 years (which you really should not do) it's unlikely you hit the same issue.

    Did you check the error message of your system event? Did you check the logfiles?
    User avatar
    Manuel Vacelet (vaceletm)2015-07-03 11:54
    There is likely to have a bug somewhere but we don't have time to troubleshoot this one ATM.
    User avatar
    DarkByte (darkbyte)2015-07-03 11:15
    Do you need another informations ? I have the same problem in Tuleap 8.3
    User avatar
    DarkByte (darkbyte)2015-06-19 16:49
    I have found another error in /var/log/codendi/codendi_syslog

    2015-06-19T16:41:02+02:00 [info] Processing event #5 SystemEvent_EDIT_SSH_KEYS(102::)
    2015-06-19T16:41:02+02:00 [error] User darkbyte has no uid/gid
    User avatar
    DarkByte (darkbyte)2015-06-17 18:19
    last edited by: DarkByte (darkbyte) 2015-06-17 18:21
    Thanks for your help
    1/ 'service codendi restart' change nothing

    2/ $homedir_prefix are good

    3/ ll /home are good

    4/ ll /home/users are NOT good (problem is here)
    i get 'total 0' in fresh install.
    I think it should have at least 'admin' here
    User avatar
    dylan bowden (dylan)2015-06-17 17:45
    Before anything run
    service codendi restart

    if that's not enough, open
    /etc/codendi/conf/local.inc and look for the value of $homedir_prefix- this should give you a folder path such as "/home/users".
    Then you'll need to check the permissions of this path, in particular who has write access, using a command such as "ll".

    Typically, you should have
    # ll /home
    -> drwxrwx--x 42 codendiadm codendiadm 4096 Jun 12 03:36 users

    # ll /home/users
    -> drwxr-x--x 3 admin admin 4096 Aug 26 2014 admin
    -> ...
    User avatar
    DarkByte (darkbyte)2015-06-17 15:18
    Hi,
    i've found this error in '/var/log/codendi/codendi_syslog' :
    Unable to create user home ssh directory for admin
    Unable to create user home ssh directory for darkbyte

    /var/log/codendi/git_syslog doesn't exist
    User avatar
    dylan bowden (dylan)2015-06-17 14:36
    Hi,
    could you tell if there's anything in the logs when this event is run.

    /var/log/codendi/codendi_syslog
    /var/log/codendi/git_syslog
    • Status changed from New to Waiting for information