Uploaded image for project: 'CFEngine Community'
  1. CFEngine Community
  2. CFE-462

cf-monitord can hard-lock

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: Low
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: cf-monitord
    • Labels:
      None

      Description

      I don't really know how to reproduce this, but I had a stale cf-monitord process not killable with SIGTERM. The following lines were logged every time I tried to send the signal:

      <pre>
      Mar 12 14:31:20 localhost cf-monitord[6955]: Logical start time Tue Feb 26 15:36:06 2013
      Mar 12 14:31:20 localhost cf-monitord[6955]: This sub-task started really at Tue Feb 26 15:36:06 2013
      Mar 12 14:31:21 localhost cf-monitord[6955]: Received signal 15 (SIGTERM) while doing [lock.cfe_internal_bundle_hardcoded.monitor_cfengine.handle.-localhost.the_monitor_daemon_7847_MD5=39fdac8877c3432a44a4af76e89dcc38]
      </pre>

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              a10038 jimis (Dimitrios Apostolou)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Summary Panel