We are having an uncommon (maybe 1 out 60 executions) but fatal issue with processes not being able to obtain gpg locks. It affects long running processes. gpg is waiting on the lock which is held by some process, but it stops waiting and fails after about six seconds. It seems to only be occurring on Alma Linux servers that have been recently upgraded from CentOS. Please could you look into this at the earliest since this is affecting all our servers upgraded to Alma Linux.
Thanks,
Arshad
The behavior is different between the old and the new versions. gpg-agent, the backend exits with the shell closing in the old version. But, if I start it with the new version, it stays running unless explicitly closed. I wonder if this means that we should run gpg-agent on all servers?
Also, the option to use standard sockets triggers a warning message with the new version of gpg-agent
Thanks,
Arshad
Are you seriously using version 2.0 which had its EOL of 6 years ago? Libgcrypt 1.5 EOF was even a year earlier. Sorry, I won't look into that.
Apologies! That was from the CentOS Server. Below are the current details
for the recently upgraded Alma Linux servers. Will upgrading to the most
recent version fix the issue?
gpg (GnuPG) 2.2.20
libgcrypt 1.8.5
Copyright (C) 2020 Free Software Foundation, Inc.
Thanks,
Arshad
Since 2.2.20 we had these items in the NEWS
I am not sure whether this is related to your issue but it should be worth to try 2.2.42 (or the soon to be released 2.2.43 with just a few minor updates). In general I would of course suggest to switch to 2.4.4 which has a lot of improvements over 2.2.