Created attachment 1096022 [details]
foreman-debug

Description of problem:
During sync on new capsule, the qdrouterd on Satellite server terminated with error:
Nov 17 11:41:33 satellite6-ops kernel: qdrouterd[30362]: segfault at 30 ip 000000304081b26c sp 00007fef887e2338 error 4 in libqpid-proton.so.2.0.0[3040800000+4d000]

How reproducible:
Trigger the capsule sync:
hammer -u abraverm capsule content synchronize --id 10

Actual results:
The error above in Satellite /var/log/messages and connection error in Capsule:
Nov 18 11:35:16 vm-18-115 pulp: pulp.server.async.scheduler:ERROR: could not connect to localhost:27017: [Errno 111] Connection refused
Nov 18 11:35:16 vm-18-115 pulp: pulp.server.db.connection:ERROR: find_one operation failed on pulp_database.users
Nov 18 11:35:16 vm-18-115 mongod: about to fork child process, waiting until server is ready for connections.
Nov 18 11:35:21 vm-18-115 pulp: celery.worker.consumer:ERROR: (29502-28288) consumer: Cannot connect to qpid://capsule-ops.eng.lab.tlv.redhat.com:5671//: [Errno 104] Connection reset by peer.
Nov 18 12:00:44 vm-18-115 goferd: [ERROR][worker-0] gofer.messaging.adapter.proton.connection:106 - connect: proton+amqps://satellite6-ops.rhev-ci-vms.eng.rdu2.redhat.com:5647, failed: Connection amqps://satellite6-ops.rhev-ci-vms.eng.rdu2.redhat.com:5647 disconnected


Expected results:
service qdrouterd is running

Additional Info:
The Capsule is new deployment. Satellite is an upgrade from 6.0