{"action":"created","issue":{"url":"https://api.github.com/repos/Metaswitch/clearwater-snmp-handlers/issues/96","labels_url":"https://api.github.com/repos/Metaswitch/clearwater-snmp-handlers/issues/96/labels{/name}","comments_url":"https://api.github.com/repos/Metaswitch/clearwater-snmp-handlers/issues/96/comments","events_url":"https://api.github.com/repos/Metaswitch/clearwater-snmp-handlers/issues/96/events","html_url":"https://github.com/Metaswitch/clearwater-snmp-handlers/issues/96","id":113069769,"number":96,"title":"Some alarms are thrown way on boot because snmpd/alarm-agent isn't up yet","user":{"login":"dtheobald","id":6430927,"avatar_url":"https://avatars.githubusercontent.com/u/6430927?v=3","gravatar_id":"","url":"https://api.github.com/users/dtheobald","html_url":"https://github.com/dtheobald","followers_url":"https://api.github.com/users/dtheobald/followers","following_url":"https://api.github.com/users/dtheobald/following{/other_user}","gists_url":"https://api.github.com/users/dtheobald/gists{/gist_id}","starred_url":"https://api.github.com/users/dtheobald/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dtheobald/subscriptions","organizations_url":"https://api.github.com/users/dtheobald/orgs","repos_url":"https://api.github.com/users/dtheobald/repos","events_url":"https://api.github.com/users/dtheobald/events{/privacy}","received_events_url":"https://api.github.com/users/dtheobald/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Metaswitch/clearwater-snmp-handlers/labels/bug","name":"bug","color":"fc2929"},{"url":"https://api.github.com/repos/Metaswitch/clearwater-snmp-handlers/labels/high-priority","name":"high-priority","color":"ff0000"}],"state":"open","locked":false,"assignee":{"login":"dtheobald","id":6430927,"avatar_url":"https://avatars.githubusercontent.com/u/6430927?v=3","gravatar_id":"","url":"https://api.github.com/users/dtheobald","html_url":"https://github.com/dtheobald","followers_url":"https://api.github.com/users/dtheobald/followers","following_url":"https://api.github.com/users/dtheobald/following{/other_user}","gists_url":"https://api.github.com/users/dtheobald/gists{/gist_id}","starred_url":"https://api.github.com/users/dtheobald/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dtheobald/subscriptions","organizations_url":"https://api.github.com/users/dtheobald/orgs","repos_url":"https://api.github.com/users/dtheobald/repos","events_url":"https://api.github.com/users/dtheobald/events{/privacy}","received_events_url":"https://api.github.com/users/dtheobald/received_events","type":"User","site_admin":false},"milestone":null,"comments":4,"created_at":"2015-10-23T17:59:56Z","updated_at":"2015-12-11T20:37:04Z","closed_at":null,"body":"On boot I see messages like this in syslog:\r\n```\r\ndropped request: 'issue-alarm cluster-manager 8001.4'\r\n```\r\n\r\nI also see the alarm-agent getting a zmq_bind error (```No such file or directory```) on ```ipc:///var/run/clearwater/alarms```. My workaround code of having the alarm-agent kill itself prevents the alarm-agent from being stuck in that state, but it's worth someone else taking a look at why it (sometimes) gets that error when 0MQ is supposed to create the socket (and does at other times). I didn't have the time to get to the bottom of it, hence the workaround.\r\n\r\nDiags are available"},"comment":{"url":"https://api.github.com/repos/Metaswitch/clearwater-snmp-handlers/issues/comments/164041861","html_url":"https://github.com/Metaswitch/clearwater-snmp-handlers/issues/96#issuecomment-164041861","issue_url":"https://api.github.com/repos/Metaswitch/clearwater-snmp-handlers/issues/96","id":164041861,"user":{"login":"dtheobald","id":6430927,"avatar_url":"https://avatars.githubusercontent.com/u/6430927?v=3","gravatar_id":"","url":"https://api.github.com/users/dtheobald","html_url":"https://github.com/dtheobald","followers_url":"https://api.github.com/users/dtheobald/followers","following_url":"https://api.github.com/users/dtheobald/following{/other_user}","gists_url":"https://api.github.com/users/dtheobald/gists{/gist_id}","starred_url":"https://api.github.com/users/dtheobald/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dtheobald/subscriptions","organizations_url":"https://api.github.com/users/dtheobald/orgs","repos_url":"https://api.github.com/users/dtheobald/repos","events_url":"https://api.github.com/users/dtheobald/events{/privacy}","received_events_url":"https://api.github.com/users/dtheobald/received_events","type":"User","site_admin":false},"created_at":"2015-12-11T20:37:04Z","updated_at":"2015-12-11T20:37:04Z","body":"Reopened because the alarm agent still sees ```zmq_bind``` failures during boot which causes it to completely malfunction (i.e. process no alarms) requiring human intervention to correct.\r\n\r\nI took a closer look and have made some improvements to my fix (e.g. retrying zmq_bind before abandoning), but am not planning to spend anymore time on this due to the lack of visibility into 0MQ and I don't think it's worth anymore time because the code should handle ```zmq_bind``` errors anyway. If you're interested in my fix to ```alarm_req_listener.cpp```, let me know and I'll pass it along to you.\r\n"}}