New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
obssigner: "Invalid RPC response" #6233
Comments
I have no idea where the rest of this thread went... anyway, someone had suggested to debug it with just the
If I issue gpg and then sign, everything works:
So now gpg-agent has the passphrase cached/key unlocked and /usr/bin/sign completes. After some time, gpg-agent closes the key, and /usr/bin/sign no longer works. So it looks like sign/obssignd fails to give the passphrase to gpg(-agent) properly. |
Seems like a gpg regression, ignoring both --passphrase-file and --passphrase-fd (which bssign uses).
|
I'm closing this here as this is an obs-sign issue. |
(If and when obssigner and signd are running on the same machine), I happen to observe this in
/srv/obs/log/signer.log
:Packages are stuck in "signing" state. signer and/or signd falls on its feet and just dies with that IPC reponse thing. It means nothing me nothing, the error reporting is really bad.
(It would also make sense to prefix log messages by PID/TID to distinguish the different subworkers.)
obs-server-2.10~alpha.20181112T153317.f792cbbaa-lp150.6662.1.noarch
obs-signd-2.5.2-lp150.1.1.x86_64
The text was updated successfully, but these errors were encountered: