[ 
https://issues.apache.org/jira/browse/QPID-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552275#comment-14552275
 ] 

ASF subversion and git services commented on QPID-6548:
-------------------------------------------------------

Commit 1680550 from [~aconway] in branch 'qpid/trunk'
[ https://svn.apache.org/r1680550 ]

QPID-6548: SYSV init scripts do not work properly wiht SSL-only broker.

Previously the broker was writing a PID file with the port number as a suffix.
This was confusing the tools when using SSL and no explicit port, as the actual
listening port is 5671 but qpidd -c was looking for 5672.

This commit introduces a simple --pidfile option which writes the pid exactly
where you tell it with no frills. The original port-pidfile setup is over
complex and not really necessary, it can be deprecated at some future time.

> SYSV init scripts do not work properly wiht SSL-only broker.
> ------------------------------------------------------------
>
>                 Key: QPID-6548
>                 URL: https://issues.apache.org/jira/browse/QPID-6548
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: 0.32
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>             Fix For: 0.33
>
>
> Install in default /usr and /etc locations, configure for SSL only. Try to 
> use the SYSV service scripts. Servivce start starts the broker but reports 
> and error, service status and stop commands don't work at all.
> {noformat}
>     aconway@mrg33 usr (trunk)$ sudo service qpidd start
>     Starting Qpid AMQP daemon: ^[[60G[^[[0;32m  OK  ^[[0;39m]
>     2015-05-19 14:59:42 [Unspecified] notice Broker is not running: Cannot 
> open lock file /home/qpidd/.qpidd/qpidd.5672.pid: No such file or directory
>     aconway@mrg33 usr (trunk)$ sudo service qpidd status
>     qpidd dead but pid file exists
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to