- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- would the package be restarted when the cluster is...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2005 05:24 AM
05-25-2005 05:24 AM
Now, my question is, how come the package was not restarted? I thought whenever the cluster is reformed, the package based on the cluster will be also restarted. Isn't ?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2005 05:29 AM
05-25-2005 05:29 AM
Re: would the package be restarted when the cluster is being reformed?
If the cluster doesn't completely go down, then the package will continue to run where it was unless that node leaves the cluster.
If the package was already down, it will not restart simply because of a cluster reformation.
If you are looking at syslog.log information, you can post it here and I can take a look at the messages that we're seeing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2005 05:35 AM
05-25-2005 05:35 AM
Re: would the package be restarted when the cluster is being reformed?
Only those packages which were running on nodes which experienced problem and caused reformation will be restarted on adoptive nodes. Even on those nodes also in case of local lan switch over it will continue running without restart.
HTH,
Devender
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2005 05:54 AM
05-25-2005 05:54 AM
Re: would the package be restarted when the cluster is being reformed?
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2005 06:50 AM
05-25-2005 06:50 AM
Solutionis the package going down when this cluster reformation happens ? If yes, your cluster configuration (networking wise) is not a good one and has to be reworked one way or another as this is not an acceptable behavior, especially you are running clustered environment for high availability not just for kicks.
Secondly, it sounds like you are experiencing this situation frequently. If so, your auto_run may be set to true but when the package fails over to the second node due to a cluster malfunction of any kind, any reason, it is set to false to prevent unnecessary jumping back and forth. So, when the package fails over, and you are sure the other node is fine, you need to enable the package for running on the now alternate node.
Example
CLUSTER STATUS
MyCluster up
NODE STATUS STATE
node1 up running
node2 up running
PACKAGE STATUS STATE AUTO_RUN NODE
pkg1 up running disabled node2
pkg2 up running disabled node2
now as you see both pkg1 and pkg2 are disable to fail over to the node1 if there is a failure. If you are sure node1 is in good shape to run them, you need to enable them using the following commands:
# cmmodpkg -e -n node1 pkg1
# cmmodpkg -e -n node1 pkg2
at this time the disabled should turn to enabled when you run a cmviewcl command.
UNIX because I majored in cryptology...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2005 06:56 PM
05-25-2005 06:56 PM