Qpidd service always down

Support
1

Hi, I have problem running katello/foreman as well as capsule server with
qpidd service always seems to be down, here is the status check on katello
server:
mongod (pid 22674) is running…
qdrouterd (pid 23006) is running…

tomcat6 (pid 23366) is running… [ OK ]
celery init v10.0.
Using config script: /etc/default/pulp_workers
node reserved_resource_worker-0 (pid 24285) is running…
node reserved_resource_worker-1 (pid 24308) is running…
node reserved_resource_worker-2 (pid 24339) is running…
node reserved_resource_worker-3 (pid 24424) is running…
node reserved_resource_worker-4 (pid 24467) is running…
node reserved_resource_worker-5 (pid 24498) is running…
node reserved_resource_worker-6 (pid 24532) is running…
node reserved_resource_worker-7 (pid 24622) is running…
foreman-proxy (pid 313) is running…
celery init v10.0.
Using configuration: /etc/default/pulp_workers, /etc/default/pulp_celerybeat
pulp_celerybeat (pid 24733) is running.
elasticsearch (pid 23740) is running…
celery init v10.0.
Using config script: /etc/default/pulp_resource_manager
node resource_manager (pid 23686) is running…
httpd (pid 25191) is running…
dynflow_executor is running.
dynflow_executor_monitor is running.
Some services failed: qpidd

And this is the output from capsule server:
mongod (pid 25931) is running…
qdrouterd (pid 28093) is running…

foreman-proxy (pid 27625) is running…
celery init v10.0.
Using configuration: /etc/default/pulp_workers, /etc/default/pulp_celerybeat
pulp_celerybeat (pid 26381) is running.
celery init v10.0.
Using config script: /etc/default/pulp_workers
node reserved_resource_worker-0 (pid 26810) is running…
node reserved_resource_worker-1 (pid 26835) is running…
node reserved_resource_worker-2 (pid 26864) is running…
node reserved_resource_worker-3 (pid 26894) is running…
celery init v10.0.
Using config script: /etc/default/pulp_resource_manager
node resource_manager (pid 26576) is running…
httpd (pid 28008) is running…
Some services failed: qpidd

where I can check the log to find the root cause

2

I saw some log saying that qpidd needs an encrypted connections, is there
anything wrong with the configuration? here is the log:
Dec 10 00:49:21 capsule qpidd[26086]: 2015-12-10 00:49:21 [Security] error
Rejected un-encrypted connection.
Dec 10 00:49:22 capsule qpidd[26086]: 2015-12-10 00:49:22 [Protocol] error
Connection qpid.127.0.0.1:5672-127.0.0.1:44268 closed by error:
connection-forced: Connection must be encrypted.(320)

··· On Thursday, December 10, 2015 at 4:51:06 PM UTC+8, sinux shen wrote: > > Hi, I have problem running katello/foreman as well as capsule server with > qpidd service always seems to be down, here is the status check on katello > server: > mongod (pid 22674) is running... > qdrouterd (pid 23006) is running... > > tomcat6 (pid 23366) is running... [ OK ] > celery init v10.0. > Using config script: /etc/default/pulp_workers > node reserved_resource_worker-0 (pid 24285) is running... > node reserved_resource_worker-1 (pid 24308) is running... > node reserved_resource_worker-2 (pid 24339) is running... > node reserved_resource_worker-3 (pid 24424) is running... > node reserved_resource_worker-4 (pid 24467) is running... > node reserved_resource_worker-5 (pid 24498) is running... > node reserved_resource_worker-6 (pid 24532) is running... > node reserved_resource_worker-7 (pid 24622) is running... > foreman-proxy (pid 313) is running... > celery init v10.0. > Using configuration: /etc/default/pulp_workers, > /etc/default/pulp_celerybeat > pulp_celerybeat (pid 24733) is running. > elasticsearch (pid 23740) is running... > celery init v10.0. > Using config script: /etc/default/pulp_resource_manager > node resource_manager (pid 23686) is running... > httpd (pid 25191) is running... > dynflow_executor is running. > dynflow_executor_monitor is running. > Some services failed: qpidd > > And this is the output from capsule server: > mongod (pid 25931) is running... > qdrouterd (pid 28093) is running... > > foreman-proxy (pid 27625) is running... > celery init v10.0. > Using configuration: /etc/default/pulp_workers, > /etc/default/pulp_celerybeat > pulp_celerybeat (pid 26381) is running. > celery init v10.0. > Using config script: /etc/default/pulp_workers > node reserved_resource_worker-0 (pid 26810) is running... > node reserved_resource_worker-1 (pid 26835) is running... > node reserved_resource_worker-2 (pid 26864) is running... > node reserved_resource_worker-3 (pid 26894) is running... > celery init v10.0. > Using config script: /etc/default/pulp_resource_manager > node resource_manager (pid 26576) is running... > httpd (pid 28008) is running... > Some services failed: qpidd > > where I can check the log to find the root cause > >
3

> I saw some log saying that qpidd needs an encrypted connections, is
> there anything wrong with the configuration? here is the log:
> Dec 10 00:49:21 capsule qpidd[26086]: 2015-12-10 00:49:21 [Security]
> error Rejected un-encrypted connection.
> Dec 10 00:49:22 capsule qpidd[26086]: 2015-12-10 00:49:22 [Protocol]
> error Connection qpid.127.0.0.1:5672-127.0.0.1:44268 closed by error:
> connection-forced: Connection must be encrypted.(320)
>

Its a known issue that qpidd on el6 always reports that it is down, you
are using el6 right?

Are you seeing any actual issues or just concerned based on the status
output? Those errors may indicate a problem (possibly with an external
capsule?) but it would be easier if we knew what if anything was not
actually working.

-Justin

··· On 12/10/2015 03:52 AM, sinux shen wrote:

On Thursday, December 10, 2015 at 4:51:06 PM UTC+8, sinux shen wrote:

Hi, I have problem running katello/foreman as well as capsule
server with qpidd service always seems to be down, here is the
status check on katello server:
mongod (pid  22674) is running...
qdrouterd (pid 23006) is running...

tomcat6 (pid 23366) is running... [  OK  ]
celery init v10.0.
Using config script: /etc/default/pulp_workers
node reserved_resource_worker-0 (pid 24285) is running...
node reserved_resource_worker-1 (pid 24308) is running...
node reserved_resource_worker-2 (pid 24339) is running...
node reserved_resource_worker-3 (pid 24424) is running...
node reserved_resource_worker-4 (pid 24467) is running...
node reserved_resource_worker-5 (pid 24498) is running...
node reserved_resource_worker-6 (pid 24532) is running...
node reserved_resource_worker-7 (pid 24622) is running...
foreman-proxy (pid  313) is running...
celery init v10.0.
Using configuration: /etc/default/pulp_workers,
/etc/default/pulp_celerybeat
pulp_celerybeat (pid 24733) is running.
elasticsearch (pid  23740) is running...
celery init v10.0.
Using config script: /etc/default/pulp_resource_manager
node resource_manager (pid 23686) is running...
httpd (pid  25191) is running...
dynflow_executor is running.
dynflow_executor_monitor is running.
Some services failed: qpidd

And this is the output from capsule server:
mongod (pid  25931) is running...
qdrouterd (pid 28093) is running...

foreman-proxy (pid  27625) is running...
celery init v10.0.
Using configuration: /etc/default/pulp_workers,
/etc/default/pulp_celerybeat
pulp_celerybeat (pid 26381) is running.
celery init v10.0.
Using config script: /etc/default/pulp_workers
node reserved_resource_worker-0 (pid 26810) is running...
node reserved_resource_worker-1 (pid 26835) is running...
node reserved_resource_worker-2 (pid 26864) is running...
node reserved_resource_worker-3 (pid 26894) is running...
celery init v10.0.
Using config script: /etc/default/pulp_resource_manager
node resource_manager (pid 26576) is running...
httpd (pid  28008) is running...
Some services failed: qpidd

where I can check the log to find the root cause

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

4

Yes, I am using RHEL6,

Actually, it works as what we excepted, we use the system as our content manager, puppet master as well as subscription manager, everything seem good, it’s just the out output that gave us some concerts. I don’t know what’s wrong and what was impacted.

-Sinux

··· > On Dec 11, 2015, at 13:19, Justin Sherrill wrote: > > On 12/10/2015 03:52 AM, sinux shen wrote: >> I saw some log saying that qpidd needs an encrypted connections, is there anything wrong with the configuration? here is the log: >> Dec 10 00:49:21 capsule qpidd[26086]: 2015-12-10 00:49:21 [Security] error Rejected un-encrypted connection. >> Dec 10 00:49:22 capsule qpidd[26086]: 2015-12-10 00:49:22 [Protocol] error Connection qpid.127.0.0.1:5672-127.0.0.1:44268 closed by error: connection-forced: Connection must be encrypted.(320) >> > > Its a known issue that qpidd on el6 always reports that it is down, you are using el6 right? > > Are you seeing any actual issues or just concerned based on the status output? Those errors may indicate a problem (possibly with an external capsule?) but it would be easier if we knew what if anything was not actually working. > > -Justin > >> >> On Thursday, December 10, 2015 at 4:51:06 PM UTC+8, sinux shen wrote: >> Hi, I have problem running katello/foreman as well as capsule server with qpidd service always seems to be down, here is the status check on katello server: >> mongod (pid 22674) is running... >> qdrouterd (pid 23006) is running... >> >> tomcat6 (pid 23366) is running... [ OK ] >> celery init v10.0. >> Using config script: /etc/default/pulp_workers >> node reserved_resource_worker-0 (pid 24285) is running... >> node reserved_resource_worker-1 (pid 24308) is running... >> node reserved_resource_worker-2 (pid 24339) is running... >> node reserved_resource_worker-3 (pid 24424) is running... >> node reserved_resource_worker-4 (pid 24467) is running... >> node reserved_resource_worker-5 (pid 24498) is running... >> node reserved_resource_worker-6 (pid 24532) is running... >> node reserved_resource_worker-7 (pid 24622) is running... >> foreman-proxy (pid 313) is running... >> celery init v10.0. >> Using configuration: /etc/default/pulp_workers, /etc/default/pulp_celerybeat >> pulp_celerybeat (pid 24733) is running. >> elasticsearch (pid 23740) is running... >> celery init v10.0. >> Using config script: /etc/default/pulp_resource_manager >> node resource_manager (pid 23686) is running... >> httpd (pid 25191) is running... >> dynflow_executor is running. >> dynflow_executor_monitor is running. >> Some services failed: qpidd >> >> And this is the output from capsule server: >> mongod (pid 25931) is running... >> qdrouterd (pid 28093) is running... >> >> foreman-proxy (pid 27625) is running... >> celery init v10.0. >> Using configuration: /etc/default/pulp_workers, /etc/default/pulp_celerybeat >> pulp_celerybeat (pid 26381) is running. >> celery init v10.0. >> Using config script: /etc/default/pulp_workers >> node reserved_resource_worker-0 (pid 26810) is running... >> node reserved_resource_worker-1 (pid 26835) is running... >> node reserved_resource_worker-2 (pid 26864) is running... >> node reserved_resource_worker-3 (pid 26894) is running... >> celery init v10.0. >> Using config script: /etc/default/pulp_resource_manager >> node resource_manager (pid 26576) is running... >> httpd (pid 28008) is running... >> Some services failed: qpidd >> >> where I can check the log to find the root cause >> >> -- >> You received this message because you are subscribed to the Google Groups "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com . >> To post to this group, send email to foreman-users@googlegroups.com . >> Visit this group at http://groups.google.com/group/foreman-users . >> For more options, visit https://groups.google.com/d/optout . > > > -- > You received this message because you are subscribed to the Google Groups "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com . > To post to this group, send email to foreman-users@googlegroups.com . > Visit this group at http://groups.google.com/group/foreman-users . > For more options, visit https://groups.google.com/d/optout .