Also check iptables is turned off!

Jon

Sent from my iPhone

Do you get message about URL to connect to?. You should be able to install as a normal user. Check your log files as well. Jon

Sent from my iPhone

Hi,

User defined by you have to be an owner of installation files and target directory. Set umask to 022 (mandatory) and check files attributes. See to installation logs in $HOME directory for installation details.

Hi Manish,

There are two ways to install Patrol Agent -

1) Installing Patrol Agent using Root.

Create a Patrol Agent Account user over the server. $home directory should have Patrol Agent Account Directory with owning of Patrol Agent Account.

2) Installing Patrol Agent using Patrol Agent Account.

Create a Patrol Agent Account user over the server. $home directory should have Patrol Agent Account Directory with owning of Patrol Agent Account. Also you need to create installation directory e.g. you can create /opt/bmc with ownership of Patrol Agent Account. While runing the setup it will fail at the end which is a usual stage during installation with Patrol Agent account. You need to run 3 Patrol Agent post installation scripts using root over the server to complete the installation.

./Rocky

Hi,

After installation – run the script called “setperm.sh” stored in “Patrol3”.
This sets up the correct permissions on the Agent and snmpmagt executables - i.e. Permissions 6755. You must run this as ‘root’:

Execute: /export/home/patrol/setperm.sh

Invoke the script for additional Security configuration as "root". The reason for this is that you need ‘root’ permissions to create a directory in /etc namely “patrol.d”
   
/export/home/patrol/common/security/config “sec_configure.sh [PATROL3 path] [Security Level]”

Example to directory: “/export/home/patrol/common/security/config_v3.0”
                         
./sec_configure.sh /export/home/patrol/Patrol3 0

0 (zero for security)

Run the following script to ensure that Patrol is using the correct collection method (DCM)

/export/home/patrol/Patrol3.5/b1config7XXXX.sh

To validate the installation use /export/home/patrol/Patrol3.5/post_check.sh scrip

In response to your original question, not running as root does not stop

the install from running, iptables does however.

Jon

If you are runing the setup with root you don't need to run post installation scripts.

As runing with normal user you will see some 21 scripts get failed as they require root credentials.

To complete the installation we run below listed 3 post installation scripts using root or sudo root -

Suppose your Agent installation directory is /opt/bmc

1) ./agent_configure -d

Location where to run this script - /opt/bmc/Patrol3 (Run with Root)

2) ./b1config*.sh

Location where to run this script - /opt/bmc/Patrol3(Run with Root)

3) ./sec_configure.sh /opt/bmc/Patrol3 0

Location where to run this script - /opt/bmc/common/security(Run with Root)

4) You need to manually start the agent using Patrol Agent Account.

/opt/bmc/Patrol3/scripts.d

./S50PatrolAgent start

This will turn on the Patrol Agent successfully and make sure the service should run with Patrol Agent Account ownership.

./Rocky

No

Sent from my iPhone

No,

You have to run PatrolAgent process from root account in the future. If you change the password, use set_default_account.sh/set_default_account.main scripts or leave password blank in agent configuration. Starting from version 3.9 agent works properly with a blank password.

Hi,

on AIX computers, the PATROL installation account must be a member of the adm group.

Also, on later agents when you create an installable image without the root password the system creates a root script which once the agent is installed you can just run as "root" and all the permissions will be set correctly.

Should be in users home directory/BMCINSTALL/XXXXXXX

where XXXXXX is a date stamped folder

So you can easily create one image and transfer around your system

MASH

On AIX and Linux when you unzip the installers, it sometimes changes the permissions on the target directory, so double check that your user can access that directory and subfolders when you run the installer as well.