Qpid
  1. Qpid
  2. QPID-2216

Error for missing ssl-cert-db option reports wrong option name

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 0.6
    • Fix Version/s: 0.11
    • Component/s: C++ Broker
    • Labels:
      None
    • Environment:

      Linux

      Description

      On Linux, trying to run the broker with the ssl module, but forgetting the ssl-cert-db option, yields:

      2009-11-24 18:48:18 info SSL plugin not enabled, you must set --qpid-ssl-cert-db to enable it.

      Two problems:
      1. It's an 'info' message, so is not visible with default logging level set; I added -t to see this.
      2. the option that must be set is -ssl-cert-db, not --qpid-ssl-cert-db (-help reports it correctly)

        Activity

        Steve Huston created issue -
        Hide
        Carl Trieloff added a comment -

        Flip it to Notice ??

        Carl.

        Show
        Carl Trieloff added a comment - Flip it to Notice ?? Carl.
        Hide
        Gordon Sim added a comment -

        I've fixed the second point. I'm not sure about the first point, I don't think we have a consistently agreed and understood approach to log levels. On one hand (as the module will always be loaded in a default installation), always having that message reported adds noise and confusion, on the other hand when someone is trying to configure it they may not think to turn on info level logging for ssl.

        Show
        Gordon Sim added a comment - I've fixed the second point. I'm not sure about the first point, I don't think we have a consistently agreed and understood approach to log levels. On one hand (as the module will always be loaded in a default installation), always having that message reported adds noise and confusion, on the other hand when someone is trying to configure it they may not think to turn on info level logging for ssl.
        Hide
        Steve Huston added a comment -

        I see your point, Gordon, but if a module is loading but can't do anything useful, I think it's a good idea to let the user know that. If there's a problem logged, the user can decide to a) fix it, b) avoid loading a module they won't use, c) ignore it.

        Show
        Steve Huston added a comment - I see your point, Gordon, but if a module is loading but can't do anything useful, I think it's a good idea to let the user know that. If there's a problem logged, the user can decide to a) fix it, b) avoid loading a module they won't use, c) ignore it.
        Gordon Sim made changes -
        Field Original Value New Value
        Fix Version/s 0.11 [ 12316272 ]
        Gordon Sim made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Justin Ross made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        467d 17h 58m 1 Gordon Sim 07/Mar/11 18:21
        Resolved Resolved Closed Closed
        875d 32m 1 Justin Ross 29/Jul/13 19:54

          People

          • Assignee:
            Unassigned
            Reporter:
            Steve Huston
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development