Clovertech

Disabling A Site

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Disabling A Site

  • Creator
    Topic
  • September 18, 2007 at 8:26 pm #49527
    Robert Milfajt
    Participant

      We have a site on our test box which is a copy of production, mostly used to migrate changes forward to production.  However, from time to time, the monitor daemon is started and this causes a battery of alerts to fire off which tends to be a nuiscance.

      Does anyone know of a way to disable the starting of the monitord and/or lockd for a particular site on a box?

      Right now we are 3.8.1P (AIX 5.2), but are going to 5.5 rev1 (AIX 5.3) so advice on either platform would be welcome.

      Thanks,

      Bob

      Robert Milfajt
      Northwestern Medicine
      Chicago, IL

    • Creator
      Topic
    Viewing 4 reply threads
    • Author
      Replies
      • September 19, 2007 at 1:03 pm #62328
        Rob Abbott
        Keymaster

          You could rename/delete the default.alrt file in this site – that will prevent any alerts from firing if monitord was ever started.

          Rob Abbott
          Cloverleaf Emeritus

        • September 20, 2007 at 5:14 am #62329
          Richard Hart
          Participant

            Bob.

            We have many sites and our ‘standard’ is for the config file to be

            NetConfig – the site is in use

            NetConfig.disabled – the site is disabled.

            We have a script that returns all ‘active’ sites for autostart and housekeeping tasks and our ‘startSite.sh’ script will not start a disabled site.

            If we have a site which should not be used, we ‘disable’ the siteInfo file

            ie

            mv siteInfo siteInfo.disabled

            This make the setsite command fail.

          • September 20, 2007 at 12:39 pm #62330
            Robert Milfajt
            Participant

              Rob, I did that for now, but since this NetConfig contains production definitions, I really want to avoid the daemons and processes from starting up.

              Richard, I like your idea and will give it a try.

              Thanks,

              Bob

              Robert Milfajt
              Northwestern Medicine
              Chicago, IL

            • September 20, 2007 at 5:53 pm #62331
              Ed Mastascusa
              Participant

                Robert,

                I’m not sure if this does 100% of what you want, but you can disable the engine and monitor daemon at startup by configuring a “very big” minfreediskspace in the site’s siteInfo file.

                When you set minfreediskspace sufficiently large the engine / monitor daemon for the site will terminate on start up as shown below. However, the lock manager will run.

                here’s what I got on a site where I set minfreediskspace=10000000000

                hcisitectl -S

                Starting hcimonitord

                hcimonitord failed to execute properly

                in the hcimonitord.log file

                /hci/qdx5.5/integrator/vanilla’s File System is too full; there must be more than 4194303MB free

              • September 21, 2007 at 6:27 pm #62332
                Robert Milfajt
                Participant

                  The same effect happens with Richard’s suggestion.  From Unix nothing starts up and it errors out.  From the GUI, you cannot even pick the site.  Thanks for the suggestion though…

                  Bob

                  TGIF  8)

                  Robert Milfajt
                  Northwestern Medicine
                  Chicago, IL

              • Author
                Replies
              Viewing 4 reply threads
              • The forum ‘Cloverleaf’ is closed to new topics and replies.