On 12/07/18 18:54 +0200, Jan Pokorný wrote:
>>> On 12 Jul 2018, at 15:47, Jan Pokorný wrote:
>>> On 11/07/18 18:43 +0200, Salvatore D'angelo wrote:
>>> On Wed, 2018-07-11 at 18:43 +0200, Salvatore D'angelo wrote:
[...] question is pacemaker install
/etc/init.d/pacemaker
On 12/07/18 16:51 +0200, Salvatore D'angelo wrote:
> My “talent” as you said comes from a bad knowledge of system vs upstart vs
> sysV mechanism.
Rule of thumb: aim at what's a first class citizen in your
distribution/system of choice -- for your particular situation,
others already indicated
Hi Jan,
My “talent” as you said comes from a bad knowledge of system vs upstart vs sysV
mechanism.
Let me only underline that I compile directly on target system and not a
different machine.
Moreover, all ./configure requirements are met because when this didn’t happen
the ./configure stopped
Hello Salvatore,
we can cope with that without much trouble, but you seem to have
a talent to present multiple related issues at once, or perhaps
to start solving the problems from the too distant point :-)
As mentioned, that's also fine, but let's separate them...
On 11/07/18 18:43 +0200,
Hi,
I have a cluster on three bare metal and I use two busters nodes to keep
walking files and backup store on an object store.
I use Docker for test purpose.
Here the possible upgrade scenario you can apply:
On Wed, Jul 11, 2018 at 04:31:31PM -0600, Casey & Gina wrote:
> Forgive me for interjecting, but how did you upgrade on Ubuntu? I'm
> frustrated with limitations in 1.1.14 (particularly in PCS so not sure
> if it's relevant), and Ubuntu is ignoring my bug reports, so it would
> be great to
> After I successfully upgraded Pacemaker from 1.1.14 to 1.1.18 and corosync
> from 2.3.35 to 2.4.4 on Ubuntu 14.04 I am trying to repeat the same scenario
> on Ubuntu 16.04.
Forgive me for interjecting, but how did you upgrade on Ubuntu? I'm frustrated
with limitations in 1.1.14
Sorry replied too soon.
Since disabling the update-rc.d command I assume the build process creates the
services.
The only problem is that enabling them with systemctl does not work because it
leverage on update-rc.d command that works only if LSB header container at
least one run level.
For
Hi,
I solved the issue (I am not sure to be honest) simply removing the update-rc.d
command.
I noticed I can start the corosync and pacemaker services with:
service corosync start
service pacemaker start
I am not sure if they have been enabled at book (on Docker is not easy to test).
I do not
On Wed, 2018-07-11 at 22:07 +0300, Andrei Borzenkov wrote:
> 11.07.2018 21:01, Salvatore D'angelo пишет:
> > 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:
>
> Then you built corosync without
On Wed, Jul 11, 2018 at 08:01:46PM +0200, Salvatore D'angelo wrote:
> 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:
>
> root@pg1:~# systemctl enable corosync
> corosync.service is not a native
11.07.2018 21:01, Salvatore D'angelo пишет:
> 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:
Then you built corosync without systemd integration. systemd will prefer
native units.
>
> root@pg1:~#
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:
root@pg1:~# systemctl enable corosync
corosync.service is not a native service, redirecting to systemd-sysv-install
Executing
On Wed, 2018-07-11 at 18:43 +0200, Salvatore D'angelo wrote:
> Hi,
>
> Yes that was clear to me, but question is pacemaker install
> /etc/init.d/pacemaker script but its header is not compatible with
> newer system that uses LSB.
> So if pacemaker creates scripts in /etc/init.d it should create
Hi,
Yes that was clear to me, but question is pacemaker install
/etc/init.d/pacemaker script but its header is not compatible with newer system
that uses LSB.
So if pacemaker creates scripts in /etc/init.d it should create them so that
they are compatible with OS supported (not sure if Ubuntu
11.07.2018 18:08, Salvatore D'angelo пишет:
> Hi All,
>
> After I successfully upgraded Pacemaker from 1.1.14 to 1.1.18 and corosync
> from 2.3.35 to 2.4.4 on Ubuntu 14.04 I am trying to repeat the same scenario
> on Ubuntu 16.04.
16.04 is using systemd, you need to create systemd unit. I do
16 matches
Mail list logo
