topic Re: ICOD boot error - not! in Operating System - HP-UX

ICOD boot error - not!

Norman Dignard — Thu, 22 May 2008 11:09:51 GMT

We have 2 j5600's similar hw and setup basically the same. Somesome reason on one system the icod daemon tries to start and we get the following error:

Output from "/sbin/rc2.d/S602icod start":
----------------------------
ERROR: The following low-level error occurred:

CIM_ERR_NOT_SUPPORTED
ERROR: /etc/inittab is missing the required entry for the Instant Capacity daemon (icapd).
Refer to the icapd (1m) man page for more
information.
ERROR: The following low-level error occurred:

CIM_ERR_NOT_SUPPORTED
ERROR: The Instant Capacity (iCAP) Agent
was unable to reconcile the number of active
processors with the intended number of active
processors. For further information about
the Instant Capacity status, run icapstatus (1m).
"/sbin/rc2.d/S602icod start" FAILED

The other host just skips the startup. I've checked /etc/inittab - no entry exists. I've uninstalled/reinstalled icod but still get the error msg.
We don't have/use icod on these systems.
Why is this system behaving this way and how can I "deactivate" icod's startup?

Re: ICOD boot error - not!

Duncan Edmonstone — Thu, 22 May 2008 13:14:09 GMT

Norman,

The first thing the start script does is check whether this is an iCOD capable system by running "icapstatus -z". This returns 4 on systems that don't support iCOD and the script then exits. Your system doesn't support iCOD so the icapstatus should just retrun 4, but the icapstatus command is also dependent on WBEM, and in your case it looks like there is something wrong with WBEM on your system, hence the CIM error.

There are 2 choices you have here to resolve this:

1) Figure out what is wrong with WEBM (start by seeing if cimserver is running).

2) Just delete the symbolic link /sbin/rc2.d/S602icod - its never going to do anything usefull on a J6500 anyway.

HTH

Duncan

Re: ICOD boot error - not!

Norman Dignard — Thu, 22 May 2008 14:21:00 GMT

I though that it is WBEM and the cim_server is running. I just can't seem to find what config in WBEM is trying to start icod.
Any ideas?

Re: ICOD boot error - not!

Duncan Edmonstone — Thu, 22 May 2008 14:59:31 GMT

Nothing in CIM is trying to start icod.

The icapstatus command called from S602icod attempts to interrogate the system using CIM.

As you don't really care about icod on a J class server, I figured the easiest thing to do would be to just remove the symbolic link to the startup script.

But if you want to follow this through and figure out what is wrong with WBEM, start using this checklist:

http://docs.hp.com/en/B8465-90017/ch07s01.html

HTH

Duncan

Re: ICOD boot error - not!

john D_3 — Thu, 22 May 2008 15:02:39 GMT

If you do not want to start icod services in startup, please remove:

/sbin/rc2.d/S602icod
/sbin/rc1.d/K398icod

and rename or remove /sbin/init.d/icod from the system.

Re: ICOD boot error - not!

Dennis Handly — Fri, 23 May 2008 10:57:37 GMT

>Mehmood: please remove: /sbin/rc2.d/S602icod
/sbin/rc1.d/K398icod

Instead of removing these two, there should be a configuration file in /etc/rc.config.d/ that you can edit or uninstall ICOD.

Re: ICOD boot error - not!

Torsten. — Fri, 23 May 2008 11:09:15 GMT

Hmm, I think there is nothing related in /etc/rc.config.d/

this is what the startup script does:

/usr/sbin/icapstatus -z

if [[ $? = 4 ]]; then
### This is not a supported system
exit 2; ### N/A

Something went wrong with your system - it does not exit the script at this point.

What result do you get from the icapstatus command?

Re: ICOD boot error - not!

Norman Dignard — Fri, 23 May 2008 11:17:08 GMT

There is noting in /etc/rc.config.d for icod.
As for the icapstatus cmd it returns:
icapstatus -z
ERROR: The following low-level error occurred:

CIM_ERR_INVALID_NAMESPACE: root/cimv2/npar

Re: ICOD boot error - not!

Dennis Handly — Fri, 23 May 2008 11:33:11 GMT

>Torsten: I think there is nothing related in /etc/rc.config.d/

Then it seems that you should swremove ICOD.

>### This is not a supported system
exit 2; ### N/A
>it does not exit the script at this point.

Why do you say that? exit 2 is probably a signal to rc(1m) that there was an error.

Re: ICOD boot error - not!

Torsten. — Fri, 23 May 2008 11:41:02 GMT

Here is the problem:

icapstatus -z
ERROR: The following low-level error occurred:

CIM_ERR_INVALID_NAMESPACE: root/cimv2/npar

Normally it should look like this:

# /usr/sbin/icapstatus -z
#
# echo $?
4

Re: ICOD boot error - not!

Torsten. — Fri, 23 May 2008 11:43:23 GMT

Dennis, have a look into the script - the procedure is even called "exit_non_supported".

;-)

Re: ICOD boot error - not!

Dennis Handly — Sat, 24 May 2008 01:15:18 GMT

>Torsten: have a look into the script - the procedure is even called "exit_non_supported".

Yes. My system exits and rc.log says SKIPPED.

Re: ICOD boot error - not!

Torsten. — Thu, 29 May 2008 09:07:48 GMT

Maybe worth to check:

# cimprovider -l -s
MODULE STATUS
OperatingSystemModule OK
ComputerSystemModule OK
ProcessModule OK
IPProviderModule OK
SDProviderModule OK
HP_NParProviderModule OK
HP_VParProviderModule OK
HP_iCODProviderModule OK
HP_iCAPProviderModule OK
HP_GiCAPProviderModule OK

# cimserver -v
A.02.05.04

# cimconfig -l -c
sslClientVerificationMode=disabled
enableSubscriptionsForNonprivilegedUsers=false
shutdownTimeout=30
authorizedUserGroups=
enableRemotePrivilegedUserAccess=true
enableHttpsConnection=true
enableNamespaceAuthorization=false
enableHttpConnection=false

Re: ICOD boot error - not!

Norman Dignard — Thu, 29 May 2008 10:40:01 GMT

I'm afraid that this is not much help either.

# cimprovider -l -s
MODULE STATUS
OperatingSystemModule OK
ComputerSystemModule OK
ProcessModule OK
IPProviderModule OK
SDProviderModule OK

# cimserver -v
A.02.07

#root@nesaweb/homeroot #cimconfig -l -c
enableAuditLog=false
sslClientVerificationMode=disabled
enableSubscriptionsForNonprivilegedUsers=false
shutdownTimeout=30
authorizedUserGroups=
enableRemotePrivilegedUserAccess=true
enableHttpsConnection=true
enableNamespaceAuthorization=false
enableHttpConnection=false

Re: ICOD boot error - not!

Torsten. — Thu, 29 May 2008 10:46:14 GMT

these modules are missing

HP_iCODProviderModule OK
HP_iCAPProviderModule OK

can you check that on the other "working" system?

Re: ICOD boot error - not!

Norman Dignard — Thu, 29 May 2008 11:15:01 GMT

Perhaps your correct. One my otehr system I get:
root@nesadev/homeroot #cimprovider -l -s
MODULE STATUS
OperatingSystemModule OK
ComputerSystemModule OK
ProcessModule OK
IPProviderModule OK
EMSHAProviderModule OK
IOTreeModule OK
HPUXLVMProviderModule OK
HP_NParProviderModule OK
HPUXSCSIProviderModule OK
HPUXFCProviderModule OK
HPUXLANProviderModule OK
HP_iCODProviderModule OK
HP_iCAPProviderModule OK
HP_GiCAPProviderModule OK
SFMProviderModule OK
HP_VParProviderModule OK
HP_UtilizationProviderModule OK
SDProviderModule OK

cimserver is A.2.05. We had the same versions on the problem box but I could not resolve this icod problem so I uninstalled icod and installed 2.07.

Are these modules included in 207? Is there some other step I'm missing?

Re: ICOD boot error - not!

Torsten. — Thu, 29 May 2008 11:29:43 GMT

This is what I get from swlist:

# swlist -l file|grep -i provider|grep -i icod
iCOD.ICOD-COMMON: /opt/icod/mof/HP_GiCAPProviderClasses.mof
iCOD.ICOD-COMMON: /opt/icod/mof/HP_GiCAPProviderReg.mof
iCOD.ICOD-COMMON: /opt/icod/mof/HP_GiCAPProviderReg25.mof
iCOD.ICOD-COMMON: /opt/icod/mof/HP_iCAPProviderClasses.mof
iCOD.ICOD-COMMON: /opt/icod/mof/HP_iCAPProviderReg.mof
iCOD.ICOD-COMMON: /opt/icod/mof/HP_iCAPProviderReg25.mof
iCOD.ICOD-COMMON: /opt/icod/mof/HP_iCODProviderReg.mof
iCOD.ICOD-COMMON: /opt/icod/mof/HP_iCODProviderReg25.mof
iCOD.ICOD-RUN: /opt/icod/lib/libiCODProviderModule.1

So maybe there is something wrong with your icod bundle.

Run swverify and if needed swconfig \*

Re: ICOD boot error - not!

Norman Dignard — Thu, 29 May 2008 13:15:34 GMT

I checked the out and the same filesets are listed.
I reinstalled icod and get:
* Beginning the Configure Execution Phase.
* Filesets: 1
ERROR: Unable to update /opt/icod/mof/HP_iCODComplexClass.mof:
PGS04812: Parsing error: parse error: PGS04830: Could not find
declaration for qualifier named Description
ERROR: Unable to update /opt/icod/mof/HP_iCAPProviderClasses.mof:
PGS04812: Parsing error: parse error: PGS04830: Could not find
declaration for qualifier named Description
ERROR: Unable to update /opt/icod/mof/HP_GiCAPProviderClasses.mof:
PGS04812: Parsing error: parse error: PGS04830: Could not find
declaration for qualifier named Key
Configuring GiCAP XML files.
Checking for partitionable system.
ERROR: Software configuration has failed. After addressing the issues
in the following output, configure this software with
'swconfig iCOD'.
ERROR: The following low-level error occurred:

CIM_ERR_INVALID_CLASS: HP_NParLocalPartition
ERROR: The "configure" script for "iCOD.ICOD-RUN" failed (exit code
"1"). The script location was
"/var/adm/sw/products/iCOD.2/ICOD-RUN/configure".
* This script had errors and the execution of this fileset
cannot proceed until the problem is fixed. Check the above
output from the script for further details.
* Running config clean command /usr/lbin/sw/config_clean.

* Summary of Execution Phase:
ERROR: Installed iCOD.ICOD-RUN,l=/,r=B.11.11.08.03.01.03
ERROR: 1 of 42 filesets had Errors.
* 41 of 42 filesets were Skipped.
ERROR: The Execution Phase had errors. See the above output for
details.

Ran swverify B9073BA and it fails for ICOD-COMMON and ICOD_RUN.
Running swconfig B9073BA I get 41 filesets already configured 1 failed. teh job shows the same errors as above.

Re: ICOD boot error - not!

Torsten. — Thu, 29 May 2008 14:20:21 GMT

interesting ...

Any errors for swverify over all products?

Re: ICOD boot error - not!

Norman Dignard — Thu, 29 May 2008 17:06:04 GMT

I ran swverify on the entire system and
it reported a few errors most of which I don't think have any relevance to icod.
In summary other than some file permissions/size/mtime issues (non icod/wbem) the job reported -

* The software "iCOD.ICOD-RUN,l=/,r=B.11.11.08.03.01.03" is not
in the correct state (AVAILABLE, INSTALLED, or CONFIGURED).
You will need to recopy, reinstall or configure this software before operating on software that depends on it.
The corequisite "iCOD.ICOD.RUN,l=/,r=B.11.11.08.03.01.03" for fileset "iCOD.ICOD-COMMON,l=/,r=B.11.11.08.03.01.03" cannot be
successfully resolved.
ERROR: The dependencies for fileset
"iCOD.ICOD-OMMON,l=/,r=B.11.11.08.03.01.03" cannot be resolved (see previous lines).
NOTE: Volatile file "/.profile" missing.
(we move root's account)
Fileset "HPPowerManagerServer.exec,l=/,r=4.1Build8" had fileerrors.
(not using this)
ERROR: File "/opt/java1.4 ...." missing.
ERROR: Verify failed Jdk14.JDK14-COM,l=/opt/java1.4,r=1.4.2.11.00I ran swverfy on the entire system
(We installed java1.5)

ERROR: Verify failed hpuxwsTOMCAT.TOMCAT,l=/opt/hpws/tomcat,r=A.5.5.9
(not configured/used)

ERROR: Verify failed iCOD.ICOD-COMMON,l=/,r=B.11.11.08.03.01.03

ERROR: Verify failed iCOD.ICOD-RUN,l=/,r=B.11.11.08.03.01.03

Not much help here.