IC5Notice: We have upgraded developerWorks Community to the latest version of IBM Connections. For more information, read our upgrade FAQ.
Topic
  • 8 replies
  • Latest Post - ‏2012-11-01T20:27:19Z by Jeffreo
Jeffreo
Jeffreo
8 Posts

Pinned topic Linux:: Message Broker V8 cannot create Default Configuration

‏2012-10-22T15:45:15Z |
I'm using Linux RedHat CentOS. All installations of Message Broker V8 have went smoothly, including all its underlying dependencies. However, I'm unable to create a Default Configuration (using the wizard). Getting the following error:

Task: Creating the default broker MB8BROKER and the queue manager MB8QMGR failed. If you can manually fix the issues that caused this task to fail, do so and then click Retry.

The .metadata log states:

SEVERE: Could not create the broker.
...
BIP8011E: Unable to create the component configuration data.

Anyone else encounter this? Thanks for any info.
Updated on 2012-11-01T20:27:19Z at 2012-11-01T20:27:19Z by Jeffreo
  • Jeffreo
    Jeffreo
    8 Posts

    Re: Linux:: Message Broker V8 cannot create Default Configuration

    ‏2012-10-23T13:09:55Z  
    Has anyone had success setting up the Message Broker Default Configuration on Linux x86-64 platform? Anyone out there? IBM?

    Do I perhaps need to install DB2?
  • fjb_saper
    fjb_saper
    122 Posts

    Re: Linux:: Message Broker V8 cannot create Default Configuration

    ‏2012-10-25T08:30:40Z  
    • Jeffreo
    • ‏2012-10-23T13:09:55Z
    Has anyone had success setting up the Message Broker Default Configuration on Linux x86-64 platform? Anyone out there? IBM?

    Do I perhaps need to install DB2?
    Not enough information.
    What user are you running this stuff under and what is the user's primary group?
  • Jeffreo
    Jeffreo
    8 Posts

    Re: Linux:: Message Broker V8 cannot create Default Configuration

    ‏2012-10-25T13:40:42Z  
    • fjb_saper
    • ‏2012-10-25T08:30:40Z
    Not enough information.
    What user are you running this stuff under and what is the user's primary group?
    User is "root". (It's a test system.)

    Primary group is "root". Also has groups "mqm" and "mqbrkrs".

    Like written earlier, all installations to this point went great, including all of Msg Broker's underlying dependencies. I did the same on Windows, but did not encounter said problem at the MB Default Config stage.

    Your input is appreciated.
  • antonpiatek
    antonpiatek
    31 Posts

    Re: Linux:: Message Broker V8 cannot create Default Configuration

    ‏2012-10-25T14:01:12Z  
    • Jeffreo
    • ‏2012-10-25T13:40:42Z
    User is "root". (It's a test system.)

    Primary group is "root". Also has groups "mqm" and "mqbrkrs".

    Like written earlier, all installations to this point went great, including all of Msg Broker's underlying dependencies. I did the same on Windows, but did not encounter said problem at the MB Default Config stage.

    Your input is appreciated.
    Even on a test system running as root is very dangerous and quiet bad.
    I'm not sure MQ or Broker will work as root, as I'm sure it has never been tested and some things are often coded to explicitly reject access from root for this reason.

    You would be much better off with a new user in the mqm and mqbrkrs groups (which gives it full access to MQ and Broker anyway)
  • Jeffreo
    Jeffreo
    8 Posts

    Re: Linux:: Message Broker V8 cannot create Default Configuration

    ‏2012-10-25T14:28:30Z  
    Even on a test system running as root is very dangerous and quiet bad.
    I'm not sure MQ or Broker will work as root, as I'm sure it has never been tested and some things are often coded to explicitly reject access from root for this reason.

    You would be much better off with a new user in the mqm and mqbrkrs groups (which gives it full access to MQ and Broker anyway)
    I ran the MB Default Config with a non-root user and got the same results/errors. The user also has the two required mq* groups.

    Attached is the DefaultConfigurationWizard.log.

    Thank you in advance.
  • Jeffreo
    Jeffreo
    8 Posts

    Re: Linux:: Message Broker V8 cannot create Default Configuration

    ‏2012-10-31T15:44:20Z  
    • Jeffreo
    • ‏2012-10-25T14:28:30Z
    I ran the MB Default Config with a non-root user and got the same results/errors. The user also has the two required mq* groups.

    Attached is the DefaultConfigurationWizard.log.

    Thank you in advance.
    IBM,
    I have been unable to evaluate the Message Broker V8 on Linux because of this error. This is a game-changer because another product may be required to accomplish what my organization requires. Perhaps I can receive some help in this matter so I can actually evaluate this IBM product. Thanks, IBM, in advance.

    Sincerely,
    Getting Concerned
  • antonpiatek
    antonpiatek
    31 Posts

    Re: Linux:: Message Broker V8 cannot create Default Configuration

    ‏2012-10-31T16:08:12Z  
    • Jeffreo
    • ‏2012-10-31T15:44:20Z
    IBM,
    I have been unable to evaluate the Message Broker V8 on Linux because of this error. This is a game-changer because another product may be required to accomplish what my organization requires. Perhaps I can receive some help in this matter so I can actually evaluate this IBM product. Thanks, IBM, in advance.

    Sincerely,
    Getting Concerned
    First, consider your choice of OS - CentOS is not a supported platform for WebSphere Message Broker. That said, I don't think that is the cause.

    From your log:
    Collected output from task >
    Stdout: [Failed to open file /var/mqsi/common/log/utility.mqsilist.trace.bin.0 with error Permission denied
    Failed to open file /var/mqsi/common/log/utility.mqsilist.userTrace.bin.0 with error Permission denied
    BIP1281I: No brokers have been defined on this machine.

    It looks like your experiment with root has messed up all the permissions. Please run the following from a root shell with the broker environment.
    rm -rf /var/mqsi
    mkdir /var/mqsi
    mqsicreateworkpath /var/mqsi

    Then log out from root and try your default configuration again as a normal user.
  • Jeffreo
    Jeffreo
    8 Posts

    Re: Linux:: Message Broker V8 cannot create Default Configuration

    ‏2012-11-01T20:27:19Z  
    First, consider your choice of OS - CentOS is not a supported platform for WebSphere Message Broker. That said, I don't think that is the cause.

    From your log:
    Collected output from task >
    Stdout: [Failed to open file /var/mqsi/common/log/utility.mqsilist.trace.bin.0 with error Permission denied
    Failed to open file /var/mqsi/common/log/utility.mqsilist.userTrace.bin.0 with error Permission denied
    BIP1281I: No brokers have been defined on this machine.

    It looks like your experiment with root has messed up all the permissions. Please run the following from a root shell with the broker environment.
    rm -rf /var/mqsi
    mkdir /var/mqsi
    mqsicreateworkpath /var/mqsi

    Then log out from root and try your default configuration again as a normal user.
    Anton,
    I followed your post. And I had to reinstall the MB Runtime as the non-root user. And MB worked! I verified it using the Pager example. Thank you! This restores my confidence.