On 11/03/19 14:08 -0500, Ken Gaillot wrote:
> Both issues turned out to be SELinux-related. I believe everything is
> working properly again.
Thanks for looking into that (beside the long term maintenance,
important nonetheless), will keep an eye on recidivating of those.
--
Jan (Poki)
On 11/03/2019 21:18, Full Name wrote:
I am a complete newbie here, so please bear with me, if I ask something
stupid and/or obvious.
I have been able to deploy and configure the software across three nodes,
each running on a separate Virtual Box VM. Following the steps mentioned in
On 03/11/2019 08:12 PM, Ken Gaillot wrote:
> On Mon, 2019-03-11 at 18:18 +, lejeczek wrote:
>> hi guys
>> I have a pacemaker which reports:
>>
>> $ systemctl status -l pacemaker
>> ● pacemaker.service - Pacemaker High Availability Cluster
>> Manager
>> Loaded: loaded
On Mon, 2019-03-11 at 18:18 +, lejeczek wrote:
> hi guys
> I have a pacemaker which reports:
>
> $ systemctl status -l pacemaker
> ● pacemaker.service - Pacemaker High Availability Cluster
> Manager
> Loaded: loaded (/etc/systemd/system/pacemaker.service;
> enabled; vendor preset:
Both issues turned out to be SELinux-related. I believe everything is
working properly again.
On Mon, 2019-03-11 at 14:36 +0100, Jan Pokorný wrote:
> On 08/03/19 15:24 -0600, Ken Gaillot wrote:
> > I plan to move the bugzilla and wiki sites over the weekend, and
> > everything else sometime in
hi guys
I have a pacemaker which reports:
$ systemctl status -l pacemaker
● pacemaker.service - Pacemaker High Availability Cluster
Manager
Loaded: loaded (/etc/systemd/system/pacemaker.service;
enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/pacemaker.service.d
On 08/03/19 15:24 -0600, Ken Gaillot wrote:
> I plan to move the bugzilla and wiki sites over the weekend, and
> everything else sometime in the week after that.
To provide feedback:
* wiki: seems really slow now
* bugzilla: at standard responsive speed, but when adding a comment:
> An
