HP 1032 ClusterPack V2.4 Tutorial - Page 158

How can I tell if Clusterware Pro V5.1 is running?, 7.5 How do I start and stop the Clusterware

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 158 highlights

The /etc/exports file on the Management Server, and the /etc/fstab file on each Compute Node is updated automatically by ClusterPack. Back to Top 3.7.4 How can I tell if Clusterware Pro V5.1 is running? On the Management Server, several Clusterware Pro V5.1 services must be running in order to provide fu functionality for the tool. All of these services are located in /share/platform/clusterware. In order to check on the status of the services, the following command can be issued: % ps -ef | grep clusterware On the Management Server, typical output will look like this: root 20156 20121 0 Aug 2 pts/0 0:00 /share/platform/clusterware/etc/gabd -2 root 20152 20110 0 Aug 2 ? 0:00 /share/platform/clusterware/1.0/hppa11- 64/etc/pim root 20116 1 0 Aug 2 ? 0:00 /share/platform/clusterware/1.0/hppa11- 64/etc/sbatchd root 20163 20116 0 Aug 2 ? 0:05 /share/platform/clusterware/1.0/hppa11- 64/etc/mbatchd -d /share/pla root 20110 1 0 Aug 2 ? 0:11 /share/platform/clusterware/1.0/hppa11- 64/etc/lim root 20113 1 0 Aug 2 ? 0:00 /share/platform/clusterware/1.0/hppa11- 64/etc/res On a Compute Node, Clusterware Pro V5.1 uses different services than on the Management node. The method of checking the currently running processes is the same: % ps -ef | grep clusterware On a Compute Node, typical output will look like this: root 17426 1 0 Aug 2 ? 8:35 /share/platform/clusterware/1.0/hppa11-64/etc/lim root 17427 1 0 Aug 2 ? 0:00 /share/platform/clusterware/1.0/hppa1164/etc/sbatchd root 17428 1 0 Aug 2 ? 0:00 /share/platform/clusterware/1.0/hppa11-64/etc/res Back to Top 3.7.5 How do I start and stop the Clusterware Pro V5.1 daemons? A set of wrapper scripts are provided by the ClusterPack solution to streamline the starting and stopping o services.

  • 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
The /etc/exports file on the Management Server, and the /etc/fstab file on each Compute Node is updated
automatically by ClusterPack.
Back to Top
3.7.4 How can I tell if Clusterware Pro V5.1 is running?
On the Management Server, several Clusterware Pro V5.1 services must be running in order to provide fu
functionality for the tool. All of these services are located in /share/platform/clusterware.
In order to check on the status of the services, the following command can be issued:
%
ps -ef | grep clusterware
On the Management Server, typical output will look like this:
root 20156 20121 0 Aug 2 pts/0 0:00 /share/platform/clusterware/etc/gabd -2
root 20152 20110 0 Aug 2 ?
0:00 /share/platform/clusterware/1.0/hppa11-
64/etc/pim
root 20116
1 0 Aug 2 ?
0:00 /share/platform/clusterware/1.0/hppa11-
64/etc/sbatchd
root 20163 20116 0 Aug 2 ?
0:05 /share/platform/clusterware/1.0/hppa11-
64/etc/mbatchd -d /share/pla
root 20110
1 0 Aug 2 ?
0:11 /share/platform/clusterware/1.0/hppa11-
64/etc/lim
root 20113
1 0 Aug 2 ?
0:00 /share/platform/clusterware/1.0/hppa11-
64/etc/res
On a Compute Node, Clusterware Pro V5.1 uses different services than on the Management node. The
method of checking the currently running processes is the same:
%
ps -ef | grep clusterware
On a Compute Node, typical output will look like this:
root 17426 1 0 Aug 2 ? 8:35 /share/platform/clusterware/1.0/hppa11-64/etc/lim
root 17427 1 0 Aug 2 ? 0:00 /share/platform/clusterware/1.0/hppa11-
64/etc/sbatchd
root 17428 1 0 Aug 2 ? 0:00 /share/platform/clusterware/1.0/hppa11-64/etc/res
Back to Top
3.7.5 How do I start and stop the Clusterware Pro V5.1 daemons?
A set of wrapper scripts are provided by the ClusterPack solution to streamline the starting and stopping o
services.