Clovertech

Trouble Starting Monitor Daemon

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Trouble Starting Monitor Daemon

  • Creator
    Topic
  • November 12, 2013 at 8:49 pm #53913
    Craig Weldy
    Participant

      I am running CL 5.7 on a linux VM box.  I took over support of this system over a year ago.  It has two test sites on it.  I am looking to make a second copy of the sites and I did so  The two original test sites are running.   I started the Lock manager for one of the new sites, with no problems, but when I try to start the Monitor Daemon through the site Daemons gui tab or through the command line, I don’t get any errors but the Monitor Daemon dosn’t start up.  In the network monitor all the threads are “RED and DEAD”.  When I go to the Site Daemons Tab and tell it to Kill all daemons I get this message:

      Lock manager terminated.

      [0:TEST] oilSysSemOpen: semget failed

      Sem Name = /hci/qdx5.7/integrator/bcn_emrtest15/NetConfig Key Generated : 704783539

      [0:TEST] msiGlobalInit: Can’t open guard sem: No space left on device

      msiGlobalInit: NetConfig = /hci/qdx5.7/integrator/bcn_emrtest15/NetConfig

      Lockmgr    is NOT running

      hcimonitord is NOT running

      Unable to initialize MSI, err = -1

      I checked the disk space due to the “No space left on device” line and there is plenty of space on all partitions (none more than 30% used.  I suspect I am just missing something, but at this point this is a mystery!

      Help Brothers and Sisters!!

      Craig Weldy
      Senior Interface Analyst
      Beacon Health System
      South Bend, In, 46615

    • Creator
      Topic
    Viewing 1 reply thread
    • Author
      Replies
      • November 13, 2013 at 8:27 am #79508
        Robert Kersemakers
        Participant

          Hi Craig,

          It looks like you’re not out of disk space, but out of semaphores. We are on HP-UX and have run into that problem also when trying to add another process: it just won’t start if it can’t get a semaphore. At that time it looked like a lot of semaphores were unused/’ghosts’ (not sure what the correct term is) after we deleted semaphore-files in the $HCISITEDIR/exec directory. So never do that!

          To clean up semaphores I think you will need a reboot. I am not aware there is a way to clear unused semaphores, so if someone knows this, please let us know.

          You should also have a look at kernel parameters for semaphores: you may have to increase the maximum number of semaphores.

          We check the number of semaphores with

          Code:

          ipcs -s|wc -l


          Hope this helps.

          Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

        • November 18, 2013 at 8:30 pm #79509
          Craig Weldy
          Participant

            Robert,

                Thanks for the reply and you hit the problem right on the head.  I passed the info to one of my SA’s and he had it reset in no time flat.

                Thanks for the help.

            Craig Weldy
            Senior Interface Analyst
            Beacon Health System
            South Bend, In, 46615

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