Created On:  07 April 2011


  • Product Name: VisiBroker
  • Product Version: 8.0
  • Product Component: general
  • Platform/OS : HP-UX
From the VisiBroker 8.0 installation guides[1][2] for HP-UX, the following section describes instructions on how to "Change user/group privileges from nobody to a valid non-privileged user/group combination":
If you are starting VisiBroker as root user/group, VisiBroker automatically switches root to "nobody". HP-UX does not support user/group=nobody. You must change nobody to another valid non-privileged user/group combination for your system. Note, you only need to do this if you are starting from a privileged (root) account.

To change this property directly in the agent.config file:

1.Go to [install_dir]/var/domains/base/adm/properties/agent.config.
2.Change agent.superuser.user=nobody to agent.superuser.user=xxx where xxx is the user name.
3.Change to where xxx is the group name.

[1] "BES: Installing VisiBroker on HP UX 11i v3 (64 bit)",
[2] "Installing VisiBroker on HP UX (Itanium)",

From the instructions stated above, the [install_dir]/var/domains/base/adm/properties/agent.config file and directory structure itself is inconsistent with the actual directory structure created when installing VisiBroker 8.0. The actual directory structure is: [install_dir]/var/vbroker/adm and there is no agent.config file.

The above instructions are misleading when resolving problems that arise when VisiBroker is installed and/or run using root user account.


The procedure above is outdated and not applicable to VisiBroker 8.0. It is applicable to VisiBroker 6.0, which is coupled with AppServer. The directory structure applies to AppServer. Because VisiBroker 7.0 and above are not coupled with AppServer anymore, the directory structure, as well as the agent.config file, no longer applies.

To resolve problems that arise when VisiBroker is installed and/or run using root user account, refer to the following article: "VisiBroker installation with root account"

From the article, the section on "Scenario 2: root installation & root invocation..." specifies the command to execute:

# find -perm -20 -exec chmod g-w {} \;

Running the above command will most likely resolve the issue.
Incident #2510218