On Wed, 2020-02-19 at 18:21 +0100, Maverick wrote:
> How is it possible that pacemaker is reporting that takes 4.2 minutes
> (254930ms) to execute the start of httpd systemd unit?
Sorry I didn't get a chance to look into this sooner.
Fedora 31 introduced a change where the ftime() call that
Hi,
As i don't have much time to dig into this pacemaker vs systemd problem,
i decided to dump systemd.
For apache resource i replaced it with ocf::heartbeat:apache, openvpn i
replaced with ocf::heartbeat:anything
and for the other resources that need some more elaborated start/stop
script i
Hi,
I'm using Fedora 31 (x86_64).
For apache i can use the ocf agent sure, but i have other resources for
who don't exist an ocf agent, so for them i need to use systemd.
All ocf and lsb type resources start ok on boot, only systemd resources
have this problem.
I already enabled debug for
On February 20, 2020 10:29:54 PM GMT+02:00, Maverick wrote:
>
>> Hi Maverick,
>>
>>
>> According this thread:
>>
>https://lists.clusterlabs.org/pipermail/users/2016-December/021053.html
>>
>> You have 'startup-fencing' is set to false.
>>
>> Check it out - maybe this is your reason.
>>
>> Best
> Hi Maverick,
>
>
> According this thread:
> https://lists.clusterlabs.org/pipermail/users/2016-December/021053.html
>
> You have 'startup-fencing' is set to false.
>
> Check it out - maybe this is your reason.
>
> Best Regards,
> Strahil Nikolov
Yes, i have stonith disabled, because as soon
On February 20, 2020 9:35:07 PM GMT+02:00, Maverick wrote:
>
>Manually it starts ok, no problems:
>
>pcs resource debug-start apache --full
>(unpack_config) warning: Blind faith: not fencing unseen nodes
>Operation start for apache (systemd::httpd) returned: 'ok' (0)
>
>
>On 20/02/2020 16:46,
Manually it starts ok, no problems:
pcs resource debug-start apache --full
(unpack_config) warning: Blind faith: not fencing unseen nodes
Operation start for apache (systemd::httpd) returned: 'ok' (0)
On 20/02/2020 16:46, Strahil Nikolov wrote:
> On February 20, 2020 12:49:43 PM GMT+02:00,
On February 20, 2020 12:49:43 PM GMT+02:00, Maverick wrote:
>
>> You really need to debug the start & stop of tthe resource .
>>
>> Please try the debug procedure and provide the output:
>> https://wiki.clusterlabs.org/wiki/Debugging_Resource_Failures
>>
>> Best Regards,
>> Strahil Nikolov
>
>
> You really need to debug the start & stop of tthe resource .
>
> Please try the debug procedure and provide the output:
> https://wiki.clusterlabs.org/wiki/Debugging_Resource_Failures
>
> Best Regards,
> Strahil Nikolov
Hi,
Correct me if i'm wrong, but i think that procedure doesn't work
How is it possible that pacemaker is reporting that takes 4.2 minutes
(254930ms) to execute the start of httpd systemd unit?
Feb 19 17:04:09 boss1 pacemaker-execd [1514] (log_execute) info:
executing - rsc:apache action:start call_id:25
Feb 19 17:04:09 boss1 pacemaker-execd [1514]
Hi,
Yes, i also don't understand why is trying to stop them first.
SELinux is disabled:
# getenforce
Disabled
All systemd services controlled by the cluster are disabled from
starting at boot:
# systemctl is-enabled httpd
disabled
# systemctl is-enabled openvpn-server@01-server
disabled
On
On Mon, 2020-02-17 at 17:35 +, Maverick wrote:
>
> Hi,
>
> When i start my cluster, most of my systemd resources won't start:
>
> Failed Resource Actions:
> * apache_stop_0 on boss1 'OCF_TIMEOUT' (198): call=82,
> status='Timed Out', exitreason='', last-rc-change='1970-01-01
> 01:00:54
Hi,
When i start my cluster, most of my systemd resources won't start:
Failed Resource Actions:
* apache_stop_0 on boss1 'OCF_TIMEOUT' (198): call=82, status='Timed
Out', exitreason='', last-rc-change='1970-01-01 01:00:54 +01:00',
queued=29ms, exec=197799ms
* openvpn_stop_0 on boss1
13 matches
Mail list logo
