<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Yes, but doing what you suggested the system find that sysV is installed and try to leverage on update-rc.d scripts and the failure occurs:<div class=""><br class=""></div><div class=""><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">root@pg1:~# systemctl enable corosync</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">corosync.service is not a native service, redirecting to systemd-sysv-install</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Executing /lib/systemd/systemd-sysv-install enable corosync</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">update-rc.d: error: corosync Default-Start contains no runlevels, aborting.</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">the only fix I found was to manipulate manually the header of /etc/init.d/corosync adding the rows mentioned below.</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">But this is not a clean approach to solve the issue.</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">What pacemaker suggest for newer distributions?</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">If you look at corosync code the init/corosync file does not container run levels in header.</span></div><div style="margin: 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">So I suspect it is a code problem. Am I wrong?</span></div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 11 Jul 2018, at 19:29, Ken Gaillot <<a href="mailto:kgaillot@redhat.com" class="">kgaillot@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Wed, 2018-07-11 at 18:43 +0200, Salvatore D'angelo wrote:<br class=""><blockquote type="cite" class="">Hi,<br class=""><br class="">Yes that was clear to me, but question is pacemaker install<br class="">/etc/init.d/pacemaker script but its header is not compatible with<br class="">newer system that uses LSB.<br class="">So if pacemaker creates scripts in /etc/init.d it should create them<br class="">so that they are compatible with OS supported (not sure if Ubuntu is<br class="">one).<br class="">when I run “make install” anything is created for systemd env.<br class=""></blockquote><br class="">With Ubuntu 16, you should use "systemctl enable pacemaker" instead of<br class="">update-rc.d.<br class=""><br class="">The pacemaker configure script should have detected that the OS uses<br class="">systemd and installed the appropriate unit file.<br class=""><br class=""><blockquote type="cite" class="">I am not a SysV vs System expert, hoping I haven’t said anything<br class="">wrong.<br class=""><br class=""><blockquote type="cite" class="">On 11 Jul 2018, at 18:40, Andrei Borzenkov <<a href="mailto:arvidjaar@gmail.com" class="">arvidjaar@gmail.com</a>><br class="">wrote:<br class=""><br class="">11.07.2018 18:08, Salvatore D'angelo пишет:<br class=""><blockquote type="cite" class="">Hi All,<br class=""><br class="">After I successfully upgraded Pacemaker from 1.1.14 to 1.1.18 and<br class="">corosync from 2.3.35 to 2.4.4 on Ubuntu 14.04 I am trying to<br class="">repeat the same scenario on Ubuntu 16.04.<br class=""></blockquote><br class="">16.04 is using systemd, you need to create systemd unit. I do not<br class="">know<br class="">if there is any compatibility layer to interpret upstart<br class="">configuration<br class="">like the one for sysvinit.<br class=""><br class=""><blockquote type="cite" class="">As my previous scenario I am using Docker for test purpose before<br class="">move to Bare metal.<br class="">The scenario worked properly after I downloaded the correct<br class="">dependencies versions.<br class=""><br class="">The only problem I experienced is that in my procedure install I<br class="">set corosync and pacemaker to run at startup updating the init.d<br class="">scripts with this commands:<br class=""><br class="">update-rc.d corosync defaults<br class="">update-rc.d pacemaker defaults 80 80<br class=""><br class="">I noticed that links in /etc/rc<run level> are not created.<br class=""><br class="">I have also the following errors on second update-rc.d command:<br class="">insserv: Service corosync has to be enabled to start service<br class="">pacemaker<br class="">insserv: exiting now!<br class=""><br class="">I was able to solve the issue manually replacing these lines in<br class="">/etc/init.d/corosync and /etc/init.d/pacemaker:<br class=""># Default-Start:<br class=""># Default-Stop:<br class=""><br class="">with this:<br class=""># Default-Start: 2 3 4 5<br class=""># Default-Stop: 0 1 6<br class=""><br class="">I didn’t understand if this is a bug of corosync or pacemaker or<br class="">simply there is a dependency missing on Ubuntu 16.04 that was<br class="">installed by default on 14.04. I found other discussion on this<br class="">forum about this problem but it’s not clear the solution.<br class="">Thanks in advance for support.<br class=""><br class=""><br class=""><br class=""><br class="">_______________________________________________<br class="">Users mailing list: <a href="mailto:Users@clusterlabs.org" class="">Users@clusterlabs.org</a><br class=""><a href="https://lists.clusterlabs.org/mailman/listinfo/users" class="">https://lists.clusterlabs.org/mailman/listinfo/users</a><br class=""><br class="">Project Home: http://www.clusterlabs.org<br class="">Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scra<br class="">tch.pdf<br class="">Bugs: http://bugs.clusterlabs.org<br class=""><br class=""></blockquote><br class="">_______________________________________________<br class="">Users mailing list: <a href="mailto:Users@clusterlabs.org" class="">Users@clusterlabs.org</a><br class=""><a href="https://lists.clusterlabs.org/mailman/listinfo/users" class="">https://lists.clusterlabs.org/mailman/listinfo/users</a><br class=""><br class="">Project Home: http://www.clusterlabs.org<br class="">Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratc<br class="">h.pdf<br class="">Bugs: http://bugs.clusterlabs.org<br class=""></blockquote><br class="">_______________________________________________<br class="">Users mailing list: <a href="mailto:Users@clusterlabs.org" class="">Users@clusterlabs.org</a><br class=""><a href="https://lists.clusterlabs.org/mailman/listinfo/users" class="">https://lists.clusterlabs.org/mailman/listinfo/users</a><br class=""><br class="">Project Home: http://www.clusterlabs.org<br class="">Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.<br class="">pdf<br class="">Bugs: http://bugs.clusterlabs.org<br class=""></blockquote>-- <br class="">Ken Gaillot <<a href="mailto:kgaillot@redhat.com" class="">kgaillot@redhat.com</a>><br class="">_______________________________________________<br class="">Users mailing list: <a href="mailto:Users@clusterlabs.org" class="">Users@clusterlabs.org</a><br class=""><a href="https://lists.clusterlabs.org/mailman/listinfo/users" class="">https://lists.clusterlabs.org/mailman/listinfo/users</a><br class=""><br class="">Project Home: http://www.clusterlabs.org<br class="">Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<br class="">Bugs: http://bugs.clusterlabs.org<br class=""></div></div></blockquote></div><br class=""></div></div></body></html>