Operating System - HP-UX
1753808 Members
7428 Online
108805 Solutions
New Discussion

ideas how to debug hpvmDaemonOpen error?

 
Vince Laurent
Respected Contributor

ideas how to debug hpvmDaemonOpen error?

I am trying to start an SAP utility and am getting an hpvm error.  Suggestions to debug (short of contacting HP which I have done):

 

---------------------------------------------------------------------------------------------
SAPOSCOL version COLL 22.10 720 - V3.1.2 2014-10-06 HP-UX IA64, 64 bit, single threaded, Non-Unicode
compiled at Oct 18 2014
systemid 274 (HP (IA-64) with HP-UX)
relno 7200
patch text COLL 22.10 720 - V3.1.2 2014-10-06 HP-UX IA64
patchno 711
intno 20020600
running on sapsnd HP-UX B.11.31 U ia64

---------------------------------------------------------------------------------------------

11:06:06 11.11.2014 LOG: Profile : no profile used
11:06:06 11.11.2014 LOG: Saposcol Version : [COLL 22.10 720 - V3.1.2 2014-10-06 HP-UX IA64]
11:06:06 11.11.2014 LOG: Working directory : /usr/sap/tmp
11:06:06 11.11.2014 LOG: Operating system : [HP-UX sapsnd B.11.31 U ia64 4283246540]
11:06:06 11.11.2014 LOG: Hardware model : [ia64 hp server Integrity Virtual Machine]
11:06:06 11.11.2014 LOG: Process Monitoring active.
11:06:06 11.11.2014 LOG: Searching for Process Monitoring Templates in /usr/sap/tmp/procmon
11:06:06 11.11.2014 LOG: INFO: /usr/sap/tmp/procmon does not exist or cannot be opened.
11:06:06 11.11.2014 LOG: INFO: Files for Process Monitoring in /usr/sap/tmp/procmon are ignored.
11:06:06 11.11.2014 ERROR: pfhpuxvirt.c 723: HPVMGuestLib_OpenHandle(): return code 1
11:06:06 11.11.2014 LOG: Shared Memory Size: 2045194.
11:06:06 11.11.2014 LOG: Shared Memory was created by process:27649
11:06:06 11.11.2014 LOG: ==== Collector submitted. This is the child process after fork()=====
11:06:06 11.11.2014 LOG: Connected stderr to log_file
11:06:06 11.11.2014 LOG: Collector daemon started
11:06:07 11.11.2014 LOG: read coll.put Tue Nov 11 11:04:22 2014
11:06:07 11.11.2014 LOG: Collector PID: 27656
hpvmDaemonOpen: Error on exec system call: No such file or directory
EOF on fgets from child
11:06:17 11.11.2014 ERROR: pfhpuxvirt.c 745: HPVMGuestLib_OpenHandle(): return code 1
11:06:31 11.11.2014 LOG: Stop Signal received.
======================= LOG: ==== Starting to deactivate collector ==========
======================= LOG: ==== Collector deactivated ====================

 

From the host:

 

(root@sapvr3)# hpvmstatus -V
[Virtual Machines]
Virtual Machine Name : sapsnd
Virtual Machine UUID : ff4d27cc-0fab-11df-a205-0017a451d10c
Virtual Machine ID : 1
Virtual Machine Label :
VM's Model Name : server Integrity Virtual Machine
VM's Serial Number : VM01005000
VM's Config Version : 4.10.0
VM's Config Label : HPVM B.04.10 clearcase opt Tue Jan 13 2009 10h03m10s PST
Operating System : HPUX
OS Version Number :
State : On (OS)
Start type : Manual
Console type : vt100-plus
Number of virtual CPUs : 1
Number of devices : 7
Number of networks : 3
Memory : 7 GB
Guest revision : 1
Running on serverid : 0
Running on pid : 25110
Application controllers : NONE
Distributed : 0
Effective serverid : 0

6 REPLIES 6
Dave Olker
HPE Pro

Re: ideas how to debug hpvmDaemonOpen error?

First, HPVM v4.1 is no longer supported so I recommend you update to a v6 version of Integrity VM.  Second, are you positive this VM guest has the required VM guest kit installed?

 

Dave

I work for HPE

[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
Dennis Handly
Acclaimed Contributor

Re: ideas how to debug hpvmDaemonOpen error?

>hpvmDaemonOpen: Error on exec system call: No such file or directory

 

This indicates a program is missing.  Using tusc can show you the name.

Stan_M
HPE Pro

Re: ideas how to debug hpvmDaemonOpen error?

The latest saposcol works with the latest patches for the supported HPVM versions. V4.10 is out of support for over 2.5 years.  

I work for HPE
Vince Laurent
Respected Contributor

Re: ideas how to debug hpvmDaemonOpen error?


@Stan_M wrote:

The latest saposcol works with the latest patches for the supported HPVM versions. V4.10 is out of support for over 2.5 years.  


Yup.  Tell me something I don't know...  I am the new admin thrown in to this mess...

Vince Laurent
Respected Contributor

Re: ideas how to debug hpvmDaemonOpen error?


@Dennis Handly wrote:

>hpvmDaemonOpen: Error on exec system call: No such file or directory

 

This indicates a program is missing.  Using tusc can show you the name.


I'll grab it and give it a go.  Thanks

Vince Laurent
Respected Contributor

Re: ideas how to debug hpvmDaemonOpen error?

I ran

 

tusc -z

 

and it is looking for software that does not exist:

 

stat("/opt/hpvm/lbin/hpvmapp", 0x87ffffffffffec00) ........................................................... ERR#2 ENOENT
Received signal 18, SIGCLD, in user mode, [SIG_DFL], no siginfo

 

Looks like upgrading HPVM is going to be my only (painful) solution.