Error message when logging in via SSH

Discussion in 'General' started by RossCK, Jan 4, 2019.

  1. RossCK

    RossCK New Member

    When logging into the server via a ssh user created through ISPConfig 3 i get the following error in the syslog. I recently became aware of this after installing OSSEC. Why is this happening and how do I fix it?

    systemd[12057]: gpgconf: running /usr/bin/gpg-agent failed (exitcode=2): General error
    systemd[12057]: gpgconf: fatal error (exit status 1)


    Here is the full showing of the login activity

    Jan 4 17:19:22 box systemd[1]: Created slice User Slice of web2.
    Jan 4 17:19:22 box systemd[1]: Starting User Manager for UID 5005...
    Jan 4 17:19:22 box systemd[1]: Started Session 24 of user web2.
    Jan 4 17:19:22 box systemd[2915]: gpgconf: running /usr/bin/gpg-agent failed (exitcode=2): General error
    Jan 4 17:19:22 box systemd[2915]: gpgconf: fatal error (exit status 1)
    Jan 4 17:19:22 box systemd[2915]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
    Jan 4 17:19:22 box systemd[2915]: Listening on GnuPG cryptographic agent and passphrase cache.
    Jan 4 17:19:22 box systemd[2915]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
    Jan 4 17:19:22 box systemd[2915]: Reached target Timers.
    Jan 4 17:19:22 box systemd[2915]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
    Jan 4 17:19:22 box systemd[2915]: Reached target Paths.
    Jan 4 17:19:22 box systemd[2915]: Listening on GnuPG network certificate management daemon.
    Jan 4 17:19:22 box systemd[2915]: Reached target Sockets.
    Jan 4 17:19:22 box systemd[2915]: Reached target Basic System.
    Jan 4 17:19:22 box systemd[1]: Started User Manager for UID 5005.
    Jan 4 17:19:22 box systemd[2915]: Reached target Default.
    Jan 4 17:19:22 box systemd[2915]: Startup finished in 57ms.
     
    RossCK, Jan 4, 2019
    #1
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    gpg-agent is not used nor configured by ispconfig, so it's probably an ossec issue.
     
    till, Jan 4, 2019
    #2
  3. RossCK

    RossCK New Member

    Thanks. I thought they might be related as OSSEC is just reporting the issue from the log. Back to the drawing board...
     
    RossCK, Jan 4, 2019
    #3
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Most likely gpg-agent wants to have some kind of config for that user, try to find out what it needs and then try adding that for the user.
     
    till, Jan 4, 2019
    #4
    RossCK likes this.
  5. RossCK

    RossCK New Member

    Thanks. I'll take a look at that. I do not get the same error when logging in via root. I have the server allowing only pubkeys, which i am putting into the created ssh users in the ISPConfig CP. There is a .gnupg directory in the root, so I think you may be right. Thanks for the tip!
     
    RossCK, Jan 4, 2019
    #5
  6. Oren

    Oren New Member

    Hi, I encountered with the same issue while trying to login with AD login credentials (which i couldn't find a solution yet).
    can you please share your solution?

    my machine:
    gpg-agent (GnuPG) 2.2.4
    libgcrypt 1.8.1
     
    Oren, Sep 5, 2019
    #6

Share This Page