Last updated on FEBRUARY 23, 2012
Applies to:Solaris Cluster - Version: 3.1 to 3.3U1 05/11 - Release: 3.1 to 3.3
Oracle Solaris on x86 (32-bit)
Oracle Solaris on x86-64 (64-bit)
After installing patches, some cluster resources are failing to start when booting the Solaris Cluster server into cluster mode. The following error is reported on the console by pmfadm , which prevents pmfadm from operating normally.
pmfadm: Cannot get project ID
pmfadm -c <name> [-a <action>] [-n <retries>] [-t <period>]
[[-e <env var>]... | E] [-C <level>] <cmd...> [args...]
pmfadm -m <name> [-n <retries>] [-t <period>]
pmfadm -s <name> [-w <timeout>] [<signal>]
pmfadm -k <name> [-w <timeout>] [<signal>]
pmfadm -l <name> [-h <host>]
pmfadm -L [-h <host>]
pmfadm -q <name> [-h <host>]
<name> == Identifier for process
<retries> == Number of retries allowed (def: 0)
<period> == Mins over which to count retries (def: INF)
<env var> == One environmental variable in format "ENV = env"
<timeout> == Number seconds to wait for completion
<host> == Host (def: localhost)
<level> == Level of child processes to monitor
<action> == <scriptname> (def: none)
<cmd> == Process to start and monitor
This can also be checked by using the `id -p` command. A server operating normally will report the user, group, and project entries in parentheses, as in the following example.
# id -p
uid=0(root) gid=0(root) projid=1(user.root)
When a server is affected by this problem it will not report the project entry, as in the following example.
# id -p
uid=0(root) gid=0(root) projid=1
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms