{"action":"created","issue":{"url":"https://api.github.com/repos/corosync/corosync/issues/336","repository_url":"https://api.github.com/repos/corosync/corosync","labels_url":"https://api.github.com/repos/corosync/corosync/issues/336/labels{/name}","comments_url":"https://api.github.com/repos/corosync/corosync/issues/336/comments","events_url":"https://api.github.com/repos/corosync/corosync/issues/336/events","html_url":"https://github.com/corosync/corosync/issues/336","id":312036622,"number":336,"title":"Watchdog should be started AFTER configuration validation, not BEFORE, else it can cause reboot loop.","user":{"login":"XANi","id":147394,"avatar_url":"https://avatars1.githubusercontent.com/u/147394?v=4","gravatar_id":"","url":"https://api.github.com/users/XANi","html_url":"https://github.com/XANi","followers_url":"https://api.github.com/users/XANi/followers","following_url":"https://api.github.com/users/XANi/following{/other_user}","gists_url":"https://api.github.com/users/XANi/gists{/gist_id}","starred_url":"https://api.github.com/users/XANi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/XANi/subscriptions","organizations_url":"https://api.github.com/users/XANi/orgs","repos_url":"https://api.github.com/users/XANi/repos","events_url":"https://api.github.com/users/XANi/events{/privacy}","received_events_url":"https://api.github.com/users/XANi/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-04-06T16:20:11Z","updated_at":"2018-04-09T11:02:12Z","closed_at":null,"author_association":"NONE","body":"2.4.2 from Debian\r\n\r\n Currently, loading bad config will cause server to hard reboot in some cases. For example. corosync died with\r\n\r\n    corosync[6423]: Apr 06 17:56:17 crit    [QUORUM] Quorum provider: corosync_votequorum failed to initialize.\r\n    corosync[6423]: Apr 06 17:56:17 error   [SERV  ] Service engine 'corosync_quorum' failed to load for reason 'configuration error: nodelist or quorum.expected_votes must be configured!'\r\n    corosync[6423]: Apr 06 17:56:17 error   [MAIN  ] Corosync Cluster Engine exiting with status 20 at service.c:356\r\n\r\nYet coresync managed to set up watchdog before getting to that point so server hard-resetted before it was even possible to check what is wrong (it was deployed via CM so I wasn't even logged on server). And then it caused a reboot loop.\r\n\r\nAside from that the error message is incorrect,  problem in question was some bad /etc/hosts entries after install (debian added ```127.0.1.1\thostname.example.com hostname``` there and node address was specified as host). So it probably should be changed to something along the lines of \"I can't find myself in nodelist\""},"comment":{"url":"https://api.github.com/repos/corosync/corosync/issues/comments/379714676","html_url":"https://github.com/corosync/corosync/issues/336#issuecomment-379714676","issue_url":"https://api.github.com/repos/corosync/corosync/issues/336","id":379714676,"user":{"login":"jfriesse","id":733814,"avatar_url":"https://avatars2.githubusercontent.com/u/733814?v=4","gravatar_id":"","url":"https://api.github.com/users/jfriesse","html_url":"https://github.com/jfriesse","followers_url":"https://api.github.com/users/jfriesse/followers","following_url":"https://api.github.com/users/jfriesse/following{/other_user}","gists_url":"https://api.github.com/users/jfriesse/gists{/gist_id}","starred_url":"https://api.github.com/users/jfriesse/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jfriesse/subscriptions","organizations_url":"https://api.github.com/users/jfriesse/orgs","repos_url":"https://api.github.com/users/jfriesse/repos","events_url":"https://api.github.com/users/jfriesse/events{/privacy}","received_events_url":"https://api.github.com/users/jfriesse/received_events","type":"User","site_admin":false},"created_at":"2018-04-09T11:02:12Z","updated_at":"2018-04-09T11:02:12Z","author_association":"OWNER","body":"@XANi Could you please paste complete config and not just snip? Because I'm unable to reproduce the issue, because corosync will ether:\r\n- Fail with error when it cannot find matching interface (`error   [MAIN  ] parse error in config: No interfaces defined`) when using `127.0.1.1`\r\n- Or starts and runs happily even with `127.0.0.1`\r\n\r\n> Also, docs basically say \"use IP\" yet the hostname is still accepted.\r\n\r\nBut this is not a problem. Using name is perfectly ok.\r\n"}}
{"actor":{"display_login":"jfriesse"}}