[katello 2.2 RC2] enable qpid dispatch router on katello server

Support
1

Hi,

By default my install doesn't seem to have the qpid dispatch router running
on port 5647, the qpid config deployed seems to only have:

ls /etc/qpid/
qpidc.conf qpidd.conf

Is there any documentation on how to enable this service on the
katello-server? Right now my katello-agent continues to try connect to port
5647 but fails as there's nothing listening on that port.

Thanks.

2

>
> Hi,
>
> By default my install doesn't seem to have the qpid dispatch router
> running on port 5647, the qpid config deployed seems to only have:
>
> ls /etc/qpid/
> qpidc.conf qpidd.conf
>
> Is there any documentation on how to enable this service on the
> katello-server? Right now my katello-agent continues to try connect to port
> 5647 but fails as there's nothing listening on that port.
>

It's installed and enabled by the katello-installer. Maybe the service
crashed? There's an open issue about it segfaulting under load, but I don't
have it handy. We're working on getting new diispatcher packages with the
fix.

The service is called qdrouterd, make sure its there and running.

Thanks

··· On Saturday, April 4, 2015 at 2:56:46 AM UTC+2, Andrew Lau wrote: >
3

I also don't have qdrouterd running on a fresh install. I didn't realize it
was needed until I tried to add a katello-agent and it couldn't communicate
back to the master.

··· On Friday, April 3, 2015 at 6:56:46 PM UTC-6, Andrew Lau wrote: > > Hi, > > By default my install doesn't seem to have the qpid dispatch router > running on port 5647, the qpid config deployed seems to only have: > > ls /etc/qpid/ > qpidc.conf qpidd.conf > > Is there any documentation on how to enable this service on the > katello-server? Right now my katello-agent continues to try connect to port > 5647 but fails as there's nothing listening on that port. > > Thanks. >
4

>
>
>
>>
>> Hi,
>>
>> By default my install doesn't seem to have the qpid dispatch router
>> running on port 5647, the qpid config deployed seems to only have:
>>
>> ls /etc/qpid/
>> qpidc.conf qpidd.conf
>>
>> Is there any documentation on how to enable this service on the
>> katello-server? Right now my katello-agent continues to try connect to port
>> 5647 but fails as there's nothing listening on that port.
>>
>
> It's installed and enabled by the katello-installer. Maybe the service
> crashed? There's an open issue about it segfaulting under load, but I don't
> have it handy. We're working on getting new diispatcher packages with the
> fix.
>
> The service is called qdrouterd, make sure its there and running.
>

I can't find any reference to qdrouterd in my running processes or in
/etc/init.d/ is it started by the qpidd script and where could I find the
logs?

··· On Sunday, 5 April 2015 10:58:39 UTC+10, Stephen Benjamin wrote: > On Saturday, April 4, 2015 at 2:56:46 AM UTC+2, Andrew Lau wrote:

Thanks

5

Hi,

Very strange, I'm not sure how you could end up with a 2.2 installation
without qpid dispatch router installed.

@Andrew - Dispatch router is it's own software, and configured in
/etc/qpid-dispatch. Do you have that?

Could one of you open an issue on Redmine so can look at this? Uploading
some 'foreman-debug' would be helpful too.

··· On Sunday, April 5, 2015 at 10:12:30 PM UTC+2, Scott Seekamp wrote: > > I also don't have qdrouterd running on a fresh install. I didn't realize > it was needed until I tried to add a katello-agent and it couldn't > communicate back to the master. > > On Friday, April 3, 2015 at 6:56:46 PM UTC-6, Andrew Lau wrote: >> >> Hi, >> >> By default my install doesn't seem to have the qpid dispatch router >> running on port 5647, the qpid config deployed seems to only have: >> >> ls /etc/qpid/ >> qpidc.conf qpidd.conf >> >> Is there any documentation on how to enable this service on the >> katello-server? Right now my katello-agent continues to try connect to port >> 5647 but fails as there's nothing listening on that port. >> >> Thanks. >> >
6

I don't have any file at /etc/qpid-dispatch
I've opened a bug at Bug #10023: qpid-dispatch isn't deployed with katello 2.2 - Katello - Foreman

··· On 6 April 2015 at 08:12, Stephen Benjamin wrote:

Hi,

Very strange, I’m not sure how you could end up with a 2.2 installation
without qpid dispatch router installed.

@Andrew - Dispatch router is it’s own software, and configured in
/etc/qpid-dispatch. Do you have that?

Could one of you open an issue on Redmine so can look at this? Uploading
some ‘foreman-debug’ would be helpful too.

On Sunday, April 5, 2015 at 10:12:30 PM UTC+2, Scott Seekamp wrote:

I also don’t have qdrouterd running on a fresh install. I didn’t realize
it was needed until I tried to add a katello-agent and it couldn’t
communicate back to the master.

On Friday, April 3, 2015 at 6:56:46 PM UTC-6, Andrew Lau wrote:

Hi,

By default my install doesn’t seem to have the qpid dispatch router
running on port 5647, the qpid config deployed seems to only have:

ls /etc/qpid/
qpidc.conf qpidd.conf

Is there any documentation on how to enable this service on the
katello-server? Right now my katello-agent continues to try connect to port
5647 but fails as there’s nothing listening on that port.

Thanks.

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/qnOWgcaiVCA/unsubscribe.
To unsubscribe from this group and all its topics, 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.

7

> I don't have any file at /etc/qpid-dispatch
> I've opened a bug at Bug #10023: qpid-dispatch isn't deployed with katello 2.2 - Katello - Foreman

Hey - looks like we dropped the ball on this, and the dispatch router
stuff didn't make the installer in the RC, so a bunch of things are
broken :frowning: It'll make the next release of 2.2.

Thanks for letting us know about it.

··· On Mon, Apr 06, 2015 at 10:26:23AM +1000, Andrew Lau wrote:

On 6 April 2015 at 08:12, Stephen Benjamin stephen@bitbin.de wrote:

Hi,

Very strange, I’m not sure how you could end up with a 2.2 installation
without qpid dispatch router installed.

@Andrew - Dispatch router is it’s own software, and configured in
/etc/qpid-dispatch. Do you have that?

Could one of you open an issue on Redmine so can look at this? Uploading
some ‘foreman-debug’ would be helpful too.

On Sunday, April 5, 2015 at 10:12:30 PM UTC+2, Scott Seekamp wrote:

I also don’t have qdrouterd running on a fresh install. I didn’t realize
it was needed until I tried to add a katello-agent and it couldn’t
communicate back to the master.

On Friday, April 3, 2015 at 6:56:46 PM UTC-6, Andrew Lau wrote:

Hi,

By default my install doesn’t seem to have the qpid dispatch router
running on port 5647, the qpid config deployed seems to only have:

ls /etc/qpid/
qpidc.conf qpidd.conf

Is there any documentation on how to enable this service on the
katello-server? Right now my katello-agent continues to try connect to port
5647 but fails as there’s nothing listening on that port.

Thanks.

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/qnOWgcaiVCA/unsubscribe.
To unsubscribe from this group and all its topics, 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.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

8

Will we be able to add it to existing installs later without requiring a
reinstall? Or are we able to manually add it now?

··· On 7 April 2015 at 03:53, Stephen Benjamin wrote:

On Mon, Apr 06, 2015 at 10:26:23AM +1000, Andrew Lau wrote:

I don’t have any file at /etc/qpid-dispatch
I’ve opened a bug at Bug #10023: qpid-dispatch isn’t deployed with katello 2.2 - Katello - Foreman

Hey - looks like we dropped the ball on this, and the dispatch router
stuff didn’t make the installer in the RC, so a bunch of things are
broken :frowning: It’ll make the next release of 2.2.

Thanks for letting us know about it.

On 6 April 2015 at 08:12, Stephen Benjamin stephen@bitbin.de wrote:

Hi,

Very strange, I’m not sure how you could end up with a 2.2 installation
without qpid dispatch router installed.

@Andrew - Dispatch router is it’s own software, and configured in
/etc/qpid-dispatch. Do you have that?

Could one of you open an issue on Redmine so can look at this?
Uploading

some ‘foreman-debug’ would be helpful too.

On Sunday, April 5, 2015 at 10:12:30 PM UTC+2, Scott Seekamp wrote:

I also don’t have qdrouterd running on a fresh install. I didn’t
realize

it was needed until I tried to add a katello-agent and it couldn’t
communicate back to the master.

On Friday, April 3, 2015 at 6:56:46 PM UTC-6, Andrew Lau wrote:

Hi,

By default my install doesn’t seem to have the qpid dispatch router
running on port 5647, the qpid config deployed seems to only have:

ls /etc/qpid/
qpidc.conf qpidd.conf

Is there any documentation on how to enable this service on the
katello-server? Right now my katello-agent continues to try connect
to port

5647 but fails as there’s nothing listening on that port.

Thanks.

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit

https://groups.google.com/d/topic/foreman-users/qnOWgcaiVCA/unsubscribe.

To unsubscribe from this group and all its topics, 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.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/qnOWgcaiVCA/unsubscribe.
To unsubscribe from this group and all its topics, 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.