remote: Sending to redis to log activity and send commit notification emails remote: Emitting a message to the fedmsg bus. remote: * Publishing information for 1 commits remote: 2018-01-22 16:45:12,769 [ERROR] pagure.lib.notify: Error sending fedmsg remote: Traceback (most recent call last): remote: File "/usr/lib/python2.7/site-packages/pagure/lib/notify.py", line 52, in fedmsg_publish remote: fedmsg.publish(*args, **kwargs) remote: File "/usr/lib/python2.7/site-packages/fedmsg/__init__.py", line 81, in _wrapper remote: return func(*args, **kw) remote: File "/usr/lib/python2.7/site-packages/fedmsg/__init__.py", line 93, in publish remote: return __local.__context.publish(topic, msg, **kw) remote: File "/usr/lib/python2.7/site-packages/fedmsg/core.py", line 313, in publish remote: msg = fedmsg.crypto.sign(msg, **self.c) remote: File "/usr/lib/python2.7/site-packages/fedmsg/crypto/__init__.py", line 207, in sign remote: return _implementation.sign(message, **config) remote: File "/usr/lib/python2.7/site-packages/fedmsg/crypto/x509.py", line 76, in _m2crypto_sign remote: "%s/%s.key" % (ssldir, certname)) remote: File "/usr/lib64/python2.7/site-packages/M2Crypto/RSA.py", line 350, in load_key remote: bio = BIO.openfile(file) remote: File "/usr/lib64/python2.7/site-packages/M2Crypto/BIO.py", line 186, in openfile remote: return File(open(filename, mode)) remote: IOError: [Errno 13] Permission denied: '/etc/pki/fedmsg/shell-pkgs02.phx2.fedoraproject.org.key' To ssh://pkgs.fedoraproject.org/rpms/libxcrypt 2d090ad..1478266 master -> master
Do you see this traceback all the time? Or was it a one-off?
Is it still happening?
@kevin that was one-off..
ok. Might have been some weirdness like the playbook was deploying a new key or the like...
Lets just close this for now, but please do let us know if it happens again.
Metadata Update from @kevin: - Issue close_status updated to: Insufficient data - Issue status updated to: Closed (was: Open)
I actually get email with this error every once in a while, so this may still happen, I'm just not clear under which circumstances.
FTR this got reported as well in https://pagure.io/fedora-infrastructure/issue/6736 and fixed by fixing the permission of the file on the filesystem