[
https://issues.apache.org/jira/browse/DISPATCH-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322516#comment-15322516
]
Jiri Danek commented on DISPATCH-224:
-------------------------------------
Command {{qdstat -g}} with default config succeeds for me if I build and run
the Ubuntu docker image from dispatch repo (in {{dockerfiles}} directory). The
same for the Fedora docker image in the repo. The only cyrus-sasl package from
your list that is missing in the Fedora docker image is cyrus-sasl-scram. Even
after I install this, the command succeeds. Then I tried modifying Dockerfile
to instal it before compilation and even then it works.
{noformat}
$ docker build -f Dockerfile-fedora -t qpid-dispatch-fedora .
$ docker run -it --rm qpid-dispatch-fedora bash
# qdrouterd &
# qdstat -g
Router Statistics
attr value
===========================
Mode standalone
Area 0
Router Id Router.A
Address Count 0
Link Count 0
Node Count 0
# rpm -qa "cyrus*"
cyrus-sasl-scram-2.1.26-25.2.fc23.x86_64
cyrus-sasl-2.1.26-25.2.fc23.x86_64
cyrus-sasl-devel-2.1.26-25.2.fc23.x86_64
cyrus-sasl-gssapi-2.1.26-25.2.fc23.x86_64
cyrus-sasl-md5-2.1.26-25.2.fc23.x86_64
cyrus-sasl-plain-2.1.26-25.2.fc23.x86_64
cyrus-sasl-lib-2.1.26-25.2.fc23.x86_64
{noformat}
> Default installed configuration fails without error message.
> ------------------------------------------------------------
>
> Key: DISPATCH-224
> URL: https://issues.apache.org/jira/browse/DISPATCH-224
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
> Affects Versions: 0.5
> Reporter: Alan Conway
> Assignee: Ted Ross
> Priority: Critical
> Fix For: 0.7.0
>
>
> A simple test of a default install of dispatch in /usr/local does not work:
> {code}
> $ make install
> $ qdrouterd&
> $ qdstat -g
> ConnectionException: Connection amqp://0.0.0.0:amqp/$management disconnected
> {code}
> The exception gives no hint why we were disconnected, and the router log file
> has no entries at all regarding the disconnection. The actual cause is a SASL
> rejection due to invalid configuration. There are several issues that need
> fixing:
> - The router log should show an error if SASL cant find/parse its config file.
> - The router log should show an error if a connection is rejected for
> security reasons.
> - The client exception should indicate that the disconnect was caused by a
> security problem.
> - The router should look for SASL configuration under its install prefix
> since that is where it is installed.
> - The default router configuration needs to be updated to either be
> functional or clearly NON functional.
> Question is is what should the default configuration allow? IMO it should at
> least allow you to use the tools shipped with qdrouterd to verify that it is
> running and working.
> The alternative is don't ship a default config at all. In that case the
> router should fail to start at all with a clear message "you must configure
> me first, see $prefix/share/doc/qdrouter/config-examples." We can provide a
> sample "qdrouterd-insecure.conf" to get developers started quickly without
> forcing them to learn SASL first. We can add other example configs for
> different scenarios as we go.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
