Description of problem: $ fedmsg-logger --message="This is a message." Version-Release number of selected component: fedmsg-0.7.6-2.fc20 Additional info: reporter: libreport-2.2.0 cmdline: /usr/bin/python /usr/bin/fedmsg-logger '--message=This is a message.' executable: /usr/bin/fedmsg-logger kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: core.py:82:__init__:KeyError: 'relay_inbound' Traceback (most recent call last): File "/usr/bin/fedmsg-logger", line 9, in <module> load_entry_point('fedmsg==0.7.6', 'console_scripts', 'fedmsg-logger')() File "/usr/lib/python2.7/site-packages/fedmsg/commands/logger.py", line 114, in logger return command.execute() File "/usr/lib/python2.7/site-packages/fedmsg/commands/__init__.py", line 96, in execute return self.run() File "/usr/lib/python2.7/site-packages/fedmsg/commands/logger.py", line 101, in run fedmsg.init(**self.config) File "/usr/lib/python2.7/site-packages/fedmsg/__init__.py", line 59, in init __local.__context = fedmsg.core.FedMsgContext(**config) File "/usr/lib/python2.7/site-packages/fedmsg/core.py", line 82, in __init__ config['endpoints'][name] = config[name] KeyError: 'relay_inbound' Local variables in innermost frame: self: <fedmsg.core.FedMsgContext object at 0x26cae90> config: {'zmq_strict': False, 'topic': 'log', 'zmq_enabled': True, 'io_threads': 1, 'crl_location': 'https://fedoraproject.org/fedmsg/crl.pem', 'print_config': False, 'zmq_linger': 1000, 'routing_policy': {'org.fedoraproject.prod.announce.announcement': ['announce-lockbox.phx2.fedoraproject.org']}, 'ssldir': '/etc/pki/fedmsg', 'zmq_tcp_keepalive_cnt': 3, 'environment': 'dev', 'cert_prefix': 'shell', 'zmq_tcp_keepalive_intvl': 5, 'topic_prefix': 'org.fedoraproject', 'zmq_tcp_keepalive': 1, 'ca_cert_cache_expiry': 0, 'timeout': 2, 'ca_cert_cache': '/var/run/fedmsg/ca.crt', 'sign_messages': False, 'zmq_tcp_keepalive_idle': 60, 'config_filename': None, 'active': True, 'topic_prefix_re': 'org\\.fedoraproject\\.(dev|stg|prod)', 'persistent_store': None, 'crypto_validate_backends': ['x509'], 'modname': 'logger', 'high_water_mark': 0, 'logging': {'loggers': {'fedmsg': {'handlers': ['console'], 'propagate': False, 'level': 'INFO'}, 'moksha': {'handlers': ['console'], 'propagate': False, 'level': 'INFO'}}, 'version': 1, 'handlers': {'console': {'formatter': 'bare', 'class': 'logging.StreamHandler', 'stream': 'ext://sys.stdout', 'level': 'INFO'}}, 'formatters': {'bare': {'datefmt': '%Y-%m-%d %H:%M:%S', 'format': '[%(asctime)s][%(name)10s %(levelname)7s] %(message)s'}}}, 'name': 'relay_inbound', 'ca_cert_location': 'https://fedoraproject.org/fedmsg/ca.crt', 'json_input': False, 'validate_signatures': False, 'certnames': {}, 'logger_message': 'This is a message.', 'post_init_sleep': 0.5, 'crypto_backend': 'x509', 'routing_nitpicky': False, 'endpoints': {'fedora-infrastructure': ['tcp://hub.fedoraproject.org:9940']}, 'crl_cache_expiry': 10, 'crl_cache': '/var/run/fedmsg/crl.pem'} name: 'relay_inbound' method: 'connect'
Created attachment 890060 [details] File: backtrace
Created attachment 890061 [details] File: environ
This produces a nicer error message upstream now: https://github.com/fedora-infra/fedmsg/pull/269 It should be fixed in the 0.9.2 release (pending).