HP 1032 ClusterPack V2.4 Tutorial - Page 99

Replace a Compute Node that has failed with a new machine

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

Page 99 highlights

Problem: When I try to add a node, I get "Properties file for doesn't exist." Solution: z Make sure that the hostname is fully qualified in /etc/hosts on both the Management Server and the managed node, if it exists in /etc/hosts, and that any shortened host names are aliases instead of primary names. For example: { 10.1.2.3 cluster.abc.com cluster z should be used instead of: { 10.1.2.3 cluster z Make sure that AgentConfig is installed on the managed node, and that mxrmi and mxagent are running. z ps -ef | grep mx should produce something like this: root 23332 1 0 15:42:17 ? 1:08 /opt/mx/lbin/mxagent root 23334 1 0 15:42:17 ? 0:59 /opt/mx/lbin/mxrmi root 24269 24252 1 01:30:51 pts/0 0:00 grep mx z If AgentConfig is installed and running, uninstall it and then reinstall it: % /usr/sbin/swremove AgentConfig z To install AgentConfig, type; % /usr/sbin/swinstall -s :/var/opt/mx/depot11 AgentConfig z where is the hostname of the Management Server. Problem: scmgr prints "out of memory" errors. Solution: z On the Management Server, using SAM or kmtune, make sure that the Kernel Configurable Parameter max_thread_proc is at least 256, and that nkthread is at least 1000. Back to Top 1.9.7 Replace a Compute Node that has failed with a new machine If a Compute Node fails due to a hardware problem, and must be replaced, the new node can

  • 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
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
Problem: When I try to add a node, I get "Properties file for <xyz> doesn't exist."
Solution:
Make sure that the hostname is fully qualified in /etc/hosts on both the
Management Server and the managed node, if it exists in /etc/hosts, and
that any shortened host names are aliases instead of primary names. For
example:
10.1.2.3 cluster.abc.com cluster
should be used instead of:
10.1.2.3 cluster
Make sure that AgentConfig is installed on the managed node, and that
mxrmi and mxagent are running.
ps -ef | grep mx should produce something like this:
root 23332 1 0 15:42:17 ?
1:08 /opt/mx/lbin/mxagent
root 23334 1 0 15:42:17 ? 0:59 /opt/mx/lbin/mxrmi
root 24269 24252 1 01:30:51 pts/0 0:00 grep mx
If AgentConfig is installed and running, uninstall it and then reinstall it:
%
/usr/sbin/swremove AgentConfig
To install AgentConfig, type;
%
/usr/sbin/swinstall -s <CMS>:/var/opt/mx/depot11
AgentConfig
where <CMS> is the hostname of the Management Server.
Problem: scmgr prints "out of memory" errors.
Solution:
On the Management Server, using SAM or kmtune, make sure that the
Kernel Configurable Parameter max_thread_proc is at least 256, and that
nkthread is at least 1000.
Back to Top
1.9.7 Replace a Compute Node that has failed with a new machine
If a Compute Node fails due to a hardware problem, and must be replaced, the new node can