{"action":"closed","issue":{"url":"https://api.github.com/repos/DataDog/docker-dd-agent/issues/28","labels_url":"https://api.github.com/repos/DataDog/docker-dd-agent/issues/28/labels{/name}","comments_url":"https://api.github.com/repos/DataDog/docker-dd-agent/issues/28/comments","events_url":"https://api.github.com/repos/DataDog/docker-dd-agent/issues/28/events","html_url":"https://github.com/DataDog/docker-dd-agent/issues/28","id":86300122,"number":28,"title":"Instance check skipped","user":{"login":"xueshanf","id":4178225,"avatar_url":"https://avatars.githubusercontent.com/u/4178225?v=3","gravatar_id":"","url":"https://api.github.com/users/xueshanf","html_url":"https://github.com/xueshanf","followers_url":"https://api.github.com/users/xueshanf/followers","following_url":"https://api.github.com/users/xueshanf/following{/other_user}","gists_url":"https://api.github.com/users/xueshanf/gists{/gist_id}","starred_url":"https://api.github.com/users/xueshanf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xueshanf/subscriptions","organizations_url":"https://api.github.com/users/xueshanf/orgs","repos_url":"https://api.github.com/users/xueshanf/repos","events_url":"https://api.github.com/users/xueshanf/events{/privacy}","received_events_url":"https://api.github.com/users/xueshanf/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-06-08T19:27:33Z","updated_at":"2015-06-15T14:56:02Z","closed_at":"2015-06-15T14:56:01Z","body":"What could cause this error in collector.log:\r\n\r\n```\r\n2015-06-08 19:17:57 UTC | ERROR | dd.collector | checks.http_check(network_checks.py:125) | Instance: CI  skipped because it's already running\r\n2015-06-08 19:18:24 UTC | CRITICAL | dd.collector | checks.http_check(network_checks.py:214) | Restarting Pool. One check is stuck:  CI\r\n```\r\n\r\nHere is the relevant info:\r\n\r\nImage: datadog/docker-dd-agent:latest\r\n\r\n```\r\nroot@anchorage-admiral:/# dd-agent info\r\n===================\r\nCollector (v 5.3.0)\r\n===================\r\n\r\n  Status date: 2015-06-08 19:11:52 (19s ago)\r\n  Pid: 16\r\n  Platform: Linux-4.0.1-x86_64-with-debian-7.8\r\n  Python Version: 2.7.9\r\n  Logs: <stderr>, /var/log/datadog/collector.log\r\n\r\n....\r\nhttp_check\r\n    ----------\r\n      - instance #0 [WARNING]\r\n          Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent.\r\n          Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent.\r\n          Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent.\r\n          Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent.\r\n          Warning: Using events for service checks is deprecated in favor of monitors and will be removed in future versions of the Datadog Agent.\r\n      - instance #1 [OK]\r\n      - instance #2 [OK]\r\n      - instance #3 [OK]\r\n      - instance #4 [OK]\r\n      - instance #5 [OK]\r\n      - instance #6 [OK]\r\n```\r\n\r\nThe checks that causing ERROR are https checks in conf.d/tcp_check.yaml, in fact, all https checks configured this way are skipped:\r\n\r\n```yaml\r\n-   name: CI\r\n        url: https://ci.example.com\r\n        timeout: 10\r\n        window: 5\r\n        threshold:  3\r\n        tags:\r\n            - url:https://ci.example.com\r\n            - env:anchorage\r\n        content_match: Authentication required\r\n        http_response_status_code: 403\r\n        include_content: true\r\n```\r\n\r\nI am trying to do a check based on http response code and content match here.\r\nWhat I am doing wrong? I looked the network_check source code but could not figure out why the https check was skipped. \r\n"}}