HP Integrity rx5670 Windows Integrity nPartition Guide - Page 147

Operational problems, All commands: ordinal not found

Get HP Integrity rx5670 PDF manuals and user guides View all HP Integrity rx5670 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 147 highlights

Troubleshooting Operational problems Operational problems The problems described below are generally associated with the use of specific commands. They are grouped in alphabetical order, by command, with any generic or non-specific problems listed at the beginning. All commands: ordinal not found This problem may be due to a conflict between the version of the OpenSSL libraries used by the nPartition commands and nPartition Provider and the versions installed by other tools. Currently, ActivCard Gold software is one source of this conflict. This problem manifests itself in other ways too. For a complete description and solution, refer to "nPartition Provider fails to start during installation" on page 139. All commands: required data unavailable or locked Because of data locking within the MP, issuing an nPartition command may display an error message stating that required data is temporarily unavailable or locked. For example, this can happen if multiple daemons, services, applications or administrators are simultaneously accessing cell information, the stable complex configuration data, or the partition configuration data on the MP. It can also happen when long or unreliable network connections exist between the MP and the remote management PC, or if the MP is busy with some other internal operation. This condition is normally transient. If it occurs, retry the command; it should succeed when tried again. If the locked data condition persists it can be remedied with the parunlock command. Use the parunlock command carefully, however. Make sure the locked data is not currently being used by another user or process before issuing the command. Fruled: LED error messages (mid-range servers only) When using the fruled command with the rx8620 or rx7620, you will see the following error message: Error: LED operation on cabinet number failed. Error: LED operation on component number failed. This is not really an error, since the HP Integrity mid-range servers do not have I/O chasses or cabinet LEDs. Frupower: cannot power off error When using the frupower command, you may see the following error message: ERROR: Cannot power off I/O chassis x/x/x (your chassis number). Chassis is attached to inactive cell x (your cell number). Please turn cell power off. Chapter 6 147

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
Troubleshooting
Operational problems
Chapter 6
147
Operational problems
The problems described below are generally associated with the use of specific
commands. They are grouped in alphabetical order, by command, with any generic or
non-specific problems listed at the beginning.
All commands: ordinal not found
This problem may be due to a conflict between the version of the OpenSSL libraries used
by the nPartition commands and nPartition Provider and the versions installed by other
tools. Currently, ActivCard Gold software is one source of this conflict.
This problem manifests itself in other ways too. For a complete description and solution,
refer to “nPartition Provider fails to start during installation” on page 139.
All commands: required data unavailable or locked
Because of data locking within the MP, issuing an nPartition command may display an
error message stating that required data is temporarily unavailable or locked. For
example, this can happen if multiple daemons, services, applications or administrators
are simultaneously accessing cell information, the stable complex configuration data, or
the partition configuration data on the MP. It can also happen when long or unreliable
network connections exist between the MP and the remote management PC, or if the MP
is busy with some other internal operation.
This condition is normally transient. If it occurs, retry the command; it should succeed
when tried again. If the locked data condition persists it can be remedied with the
parunlock
command. Use the
parunlock
command carefully, however. Make sure the
locked data is not currently being used by another user or process before issuing the
command.
Fruled
:
LED error messages (mid-range servers only)
When using the
fruled
command with the rx8620 or rx7620, you will see the following
error message:
Error: LED operation on cabinet number failed.
Error: LED operation on component number failed.
This is not really an error, since the HP Integrity mid-range servers do not have I/O
chasses or cabinet LEDs.
Frupower
:
cannot power off error
When using the
frupower
command, you may see the following error message:
ERROR: Cannot power off I/O chassis x/x/x (your chassis number).
Chassis is attached to inactive cell x (your cell number).
Please turn cell power off.