I got a question from one of our customers how to stop Cloverleaf completely.
On Windows I would close the gui, stop all processes, stop the monitor daemon, host server and the Windows Service.
What is the equivalent of the Window Service on Linux if any. (Cloverleaf version 19.1.2.2)
I think the Lock Manager is the Unix equivalent of the Windows Service. However: there will always be only one Windows service on a Windows Cloverleaf, but on Unix every site has its own Lock Manager.
You use ‘hcisitectl’ to stop and start the Lock Manager. You also use this command to stop the Monitor Daemon.
Stop Lock Manager: hcisitectl -k l
Start Lock Manager; hcisitectl -s l
Use ‘hcistiectl –‘ for more options. In a shutdown scenario you will first stop all processes in a site, then stop Monitor Daemon and Lock Manager in one go.
Nowadays in an (RHEL) Unix High Availability Setup, you can also stop Cloverleaf completely by stopping the cluster resource. For example if your Cloverleaf cluster resource is named ‘cloverleaf’ you can stop it (under root) with ‘pcs resource disable cloverleaf’. The system will then stop all sites one by one, including Lock Manager and Daemon.
Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands
Hello – question on the opposite of shutting down Cloverleaf. But to make sure I’m understanding properly. To fully shutdown Cloverleaf you first shutdown all the processes in the site, then shutdown the monitor daemon and lock manager in the site; then move on to other sites until all processes, monitor daemon and lock manager are shutdown in all the sites. Is that correct?
To fully/properly start up Cloverleaf , go into each site, start all the processes, then start the lock manager, then the monitor daemon in the site; then do the same on the rest of the Cloverleaf sites (?). We are running Cloverleaf on a linux environment.
We’re looking to do the shutdown and start up of Cloverleaf manually though scripts.
To start Cloverleaf, start the lock manager and monitor first, then start the processes. I think it is desirable to have the lock manager running before messages are processed through threads.
it is interesting that our HACMP environment, configured by Infor, has a shell script that determines all the processes in a site and does a kill -9 on the PIDs, then a kill -9 on the lock manager and the monitor. And does that for all sites. Then kills the host server. So nine sites with a total of 400 threads will end in about eight seconds. Never lost a message, never had a problem. We use Recovery Databases for everything.
So we have built a singular script to shutdown and to startup Cloverleaf and everything else that we do on our engine systems. It is a manual process because you just never know when the system has to do work before anything starts up. We have 1 system that has 25 sites with 294 processes and 4,000+ threads. Our shutdown script takes about 15 minutes to shutdown everything. Each process in each site has the command hcienginestop run against it so it does the “normal” stop and handles the killing if necessary.
.
.