Clovertech

monitord error

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › monitord error

  • Creator
    Topic
  • May 2, 2012 at 3:49 pm #53075
    Xiaochun Tong
    Participant

      One of our sites is getting these errors in the monitord log ($HCISITEDIR/exec/hcimonitord.log). These are filling up the log very quickly.

      Any idea what’s causing this?

      [msi :msi :WARN/0:_hcimonitord_:05/02/2012 10:41:08] read of fifo failed: Error 0

      [msi :msi :WARN/0:_hcimonitord_:05/02/2012 10:41:08] read 0 bytes, expected 4

      [msi :msi :WARN/0:_hcimonitord_:05/02/2012 10:41:08] read of fifo failed: Error 0

      [msi :msi :WARN/0:_hcimonitord_:05/02/2012 10:41:08] read 0 bytes, expected 4

      [msi :msi :WARN/0:_hcimonitord_:05/02/2012 10:41:08] read of fifo failed: Error 0

      [msi :msi :WARN/0:_hcimonitord_:05/02/2012 10:41:08] read 0 bytes, expected 4

      [msi :msi :WARN/0:_hcimonitord_:05/02/2012 10:41:08] read of fifo failed: Error 0

      [msi :msi :WARN/0:_hcimonitord_:05/02/2012 10:41:08] read 0 bytes, expected 4

      [msi :msi :WARN/0:_hcimonitord_:05/02/2012 10:41:08] read of fifo failed: Error 0

      [msi :msi :WARN/0:_hcimonitord_:05/02/2012 10:41:08] read 0 bytes, expected 4

      [msi :msi :WARN/0:_hcimonitord_:05/02/2012 10:41:08] read of fifo failed: Error 0

      [msi :msi :WARN/0:_hcimonitord_:05/02/2012 10:41:08] read 0 bytes, expected 4

    • Creator
      Topic
    Viewing 0 reply threads
    • Author
      Replies
      • May 3, 2012 at 3:34 pm #76474
        Xiaochun Tong
        Participant

          This is what I had to do to clear the errors:

          monitor daemon cleanup. This is for cleaning up the moniotr daemon when pid file has been deleted or when the monitor daemon is locked up and not communicating.

          These steps can be done while engines are running so just ignore the engines.

          Run ps -ef | grep monitord or ps -ef | grep site name or ps -ef | grep monitord | grep sitename

          This will allow you to see what process id the monitor daemon is running under.

          You will need to do a kill -9 on the relevant process id number.

          Remove the pid and cmd_port files if they exist in the exec/hcimonitord directory.

          Run hcisitectl -sm to restart the monitor daemon or hcisitectl -s if both daemons are down and need starting.

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