Best way to shut down Cloverleaf?

Clovertech Forums Cloverleaf Best way to shut down Cloverleaf?

Tagged: 

  • Creator
    Topic
  • #109341
    Michael Brande
    Participant

      What is the best way to shut down Cloverleaf? I know hciss -k h will take down the Host Server. But say you want to take down every process in a particular CL version.

    Viewing 3 reply threads
    • Author
      Replies
      • #109491
        David Barr
        Participant

          The easy way is to run $HCIROOT/bin/autostop.pl as root. This should be done automatically when the hcihostserver62 service stops.

          If you want to do it manually, you have to stop all the processes (hcienginestop -p process1,process2,etc), then stop the host server and lock manager in each site (hcisitectl -K), then stop the host server.

        • #109530
          Ronnie Altic
          Participant

            Here is a unix/linux KSH script that will shutdown everything, all processes all sites.
            Change the following two lines in the code to your system
            export QUOVADX_INSTALL_DIR=/hci/cis5.8
            HCIROOT=/hci/cis5.8/integrator

            
            #!/bin/ksh
            # History:  
            # USAGE:ksh z_ShutDown.sh
            export QUOVADX_INSTALL_DIR=/hci/cis5.8
            HCIROOT=/hci/cis5.8/integrator
            serverIni="$HCIROOT/server/server.ini"
            wSites=<code>cat $serverIni | grep &quot;environs=&quot;</code>
            wSites=<code>echo $wSites | cut -c 10-10000</code>
            sites=<code>echo $wSites | sed 's/;/ /g'</code>
            
            for sitePath in $sites
            do
              if [[ -d $sitePath ]]
              then
                 site=<code>echo $sitePath |  cut -d'/' -f5</code>
                 echo $site
                 date=<code>date</code>
                  # Set Site
                    eval <code>$HCIROOT/sbin/hcisetenv -site ksh $site</code>
                    hcisitectl -S
                    #Get process names
                    process_names=<code>cat $HCISITEDIR/NetConfig | grep process | sort -n | awk '{print $2}'</code>
                    
                    # Loop through the Processes/Threads
                    #for thread in $thread_names
                    for process in $process_names
                    do
                       
                      hcienginestop -p $process
                      if [[ $site == "eogh_t" && ( $process != "tst" || $process != "test" ) ]]
                      then
                         echo "start Process: $process"
                         #hcienginerun -p $process
                      fi
                       
                       #msg_ct_in=<code>hcimsiutil -dd  $thread | grep &quot;Msgs In&quot; | awk '{print $4}'</code>
                       #site_msg_ct_in=<code>expr $site_msg_ct_in + $msg_ct_in</code>
                       #sg_ct_out=<code>hcimsiutil -dd  $thread | grep &quot;Msgs Out&quot; | awk '{print $4}'</code>
                       #site_msg_ct_out=<code>expr $site_msg_ct_out + $msg_ct_out</code>
                       #echo "$site	$thread	$msg_ct_in	$msg_ct_out"
                       #total_msg_ct_in=<code>expr $total_msg_ct_in + $site_msg_ct_in</code> 
                       #total_msg_ct_out=<code>expr $total_msg_ct_out + $site_msg_ct_out</code> 
                    done
                    hcisitectl -K
                    echo "**** SITE $site  DONE"
              fi
              
            hciss -k h
            done
            echo "**** ALL DONE"
            exit 0
            • #109568
              David Barr
              Participant

                That would run a lot faster if you stop the processes in parallel.

                Replace the

                for process in $process_name block with something like

                hcienginestop -p$(echo $process_names | tr ' ' ,).

                • This reply was modified 5 years, 6 months ago by David Barr.
              • #109570
                Michael Brande
                Participant

                  What is a little odd to me is that the vendor did not provide a script or command to bring the entire system down. These suggestions are awesome! Thanks so much.

                  But why not a script even from Infor that will take down all processes/sites/monitoring daemons and lock manage (everything)?

                  Why no off function?

                • #109579
                  David Barr
                  Participant

                    The vendor did provide a script: $HCIROOT/bin/autostop.pl. The installation process also creates a system service to call the script.

                  • #109585
                    Michael Brande
                    Participant

                      Ahh ok cool! I saw that but got the impression there were pre req steps to run before it would work.

                    • #109751
                      David Barr
                      Participant

                        Ahh ok cool! I saw that but got the impression there were pre req steps to run before it would work.

                        You may need to enable the hcihostserver62 service. Also, there’s a config file: $HCIROOT/Autostart.cfg. You need to list all your processes there.

                    • #109586
                      Rob Lindsey
                      Participant

                        As others have stated, you can use the autostop.pl but most users of the CL system want to shutdown things in an order that they want.  autostop.pl does not allow for that.  We have several versions of  stop and start scripts.  We also run 15 different production CL servers so it all depends on what you want to do.

                        Rob

                      • #109675
                        Dustin Sayes
                        Participant

                          once you have decided how you want to stop the processes, run hcisitectl -K to stop the lock manager and monitor daemon.

                          i think this is a great example of why cloverleaf is a great engine. we have flexibility on how to bring it down and how to bring it up, to meet a sites specific needs.

                      Viewing 3 reply threads
                      • You must be logged in to reply to this topic.