commandview problem

[Delrish]

Hi,

I want to connect to VA from HP-UX. I installed commandview.When i run armdsp , it siad : "Failed to open target Bahar@/dev/rscsi/c13t0d0:null"

Oon other server, i got :
Arrays known to the ARMServer:
No arrays were found by the ARMServer

What is the problem?

Alireza,

[Ingo Duschl]

check the array ID and if it is connected correct

[Patrick Wallek]

What happens if you do an 'armdsp -i' to display all arrays accessable to the system?

[Delrish]

armdsp -i show the array-id but when i want to connect to that array it says : Failed to open target Bahar@/dev/rscsi/c13t0d0:null

[krusty]

Hi Alireza,

Try running an "armdiscover" which actually scans the busses for VA arrays. The information gathered from an armdiscvoer is then "cached" in the file

/opt/sanmgr/commandview/server/data/DeviceDBFile

to make it faster when you do any arm commands.

Curt

[Delrish]

Hello Curt,

When I executed armdiscover, system return this error : failed to obtain remote database interface to host:localhost

Alireeza,

[krusty]

Alireza,

I've seen that before. It may be a networking issue (/etc/host file or DNS), or you can try restarting the host agent. The commands are:

/opt/sanmgr/commandview/client/sbin HA_Dial_Stop
and
/opt/sanmgr/commandview/client/sbin HA_Dial_Start

If that fails, I would try a reboot of your host.

Curt

[Delrish]

Hi Curt,

What do you mean by "It may be a networking issue (/etc/host file or DNS)"

I did not setup nameserver for my server, so /etc/resolv.conf does not exist in my system. I found another thing, when the system going to be up, HostAgent will fail and. But there is nothing in /etc/rc.log that can help to find the root of problem.
I did not find anything in syslog about it.
I tried to start it manualy it reported:


b-3.00# ./HA_Dial_Start
NOTE: hostwatchdog started
NOTE: Starting HostAgent
ERROR: HostAgent failed to start
See logfile "/opt/sanmgr/hostagent/log/HostAgentDebugOut.log"
and "/opt/sanmgr/hostagent/log/HostAgentErr.log"
ERROR: Cannot start hostagent
'HostAgent', 'dial', and/or 'hostwatchdog' processes were not started.

Regards,
Alireza

[krusty]

Hi Alireza,

I've seen networking problems where the host was not on the DNS server, or possibly the resolv.conf is not set correctly. Sorry I don't rememeber the exact fix, only that it was networking related.

With regards to the host agent not starting, do you have any other HP host agents such as Performance Advisor, Path Connectivity (XP related), or OVSAM? If so, there could be a load sequence or compatibility issue.

Curt

[Delrish]

Hi Curt,

No, I do not have these softwares on my system.attached please find the HostAgentErr. It seems there is an error related to java. have you ever seen it?

Alireza,

[krusty · Accepted solution]

Thanks for the logfile - and I think I may have your fix. There is a problem with HP-UX and java. The default value for a kernel parameter is to small. You can edit the value in the kernel. Here is a URL that explains the problem more thoroughly.

http://www.hp.com/products1/unix/java/infolibrary/prog_guide/configuration.html

And here is a snippet from that website:

Threads

The default values for HP-UX 11.0 and 11i are set too low for most Java applications. Two kernel parameters need to be set so that the limit of the maximum number of threads per process is not encountered. Usually you will see this problem as a Java Out of Memory error. You will want to set the value of the max_thread_proc higher than the expected maximum number of simultaneously active threads for your application. You can check the number of threads in your process by using the -eprof option available as of JDK 1.1.8. Analyze the Java.eprof file using HPjmeter by selecting the threads metric.

max_thread_proc
The maximum number of threads allowed in each process. The minimum value (and default) is 64, often too low for most Java applications. The maximum value is the value of nkthread.

nkthread
The total number of kernel threads available in the system. This parameter is similar to the nproc tunable except that it defines the limit for the total number of kernel threads able to run simultaneously in the system. The value must be greater than nproc. The default is approximately twice that of nproc. The maximum is 30000. The suggested value of nkthread is 2*max_thread_proc. If you have many Java processes running and each running process uses many threads, you will want to increase this value. \

Try increasing that value in your kernel, and I'll bet that is your fix.

Sincerely,

Curt

[Delrish]

Thank you, A Curt said,the problem was in kernel parameters