Description:
Setting up the agent for multiple instances by creating additional instance directories
and requisite agent configurations.
[root@dc01mdb-01 instances]# ls -l
total 56
drwxr-xr-x 2 root root 4096 Nov 14 14:37 dev-adminlog
drwxr-xr-x 2 root root 4096 Nov 14 14:37 dev-avmdb-vip
drwxr-xr-x 2 root root 4096 Nov 14 14:33 dev-avmdb-vip2
drwxr-xr-x 2 root root 4096 Nov 14 14:36 dev-bfdmdb-vip
drwxr-xr-x 2 root root 4096 Nov 14 14:04 dev-bpmdb-vip
drwxr-xr-x 2 root root 4096 Nov 14 14:04 dev-bpmdb-vip2
drwxr-xr-x 2 root root 4096 Nov 14 14:05 dev-bpmdb-vip3
drwxr-xr-x 2 root root 4096 Nov 14 14:36 dev-dwmdb-vip
drwxr-xr-x 2 root root 4096 Nov 14 14:36 dev-dwmdb-vip2
drwxr-xr-x 2 root root 4096 Nov 14 14:35 dev-finmdb-vip
drwxr-xr-x 2 root root 4096 Nov 14 14:35 dev-qamdb-vip
drwxr-xr-x 2 root root 4096 Nov 14 14:35 dev-sessdb-vip
drwxr-xr-x 2 root root 4096 Nov 14 14:34 dev-testmdb-vip
Starting the agents yields nothing. Turns out permissions in the database were missing.
No proper logging from the agent was observed.
How to repeat:
Create an agent installation with one or multiple instances, create agent setup problems
such as missing permissions or other problems. Try to derive the cause for the problem
not using strace. Try finding out the name of the instance causing the problem.
Suggested fix:
At agent startup, report problems (or success in a single message per instance monitored
with instance name and port) in a way that allows proper debugging.
