ClusterMon resource creation core-dumps while created with extra_option -E
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pacemaker (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Triaged
|
Low
|
Unassigned |
Bug Description
Hi
I have a 2 nodes cluster with a number of resources working fine.
I am using Ubuntu 16.04 with Pacemaker: 1.1.14
The moment i create a ClusterMon resource with an extra_option "-E" to run a script, it crashes and i can see the following in dmesg
[73880.444953] crm_mon[20739]: segfault at 0 ip 00007f948cc5c746 sp 00007ffed0cb0fb8 error 4 in libc-2.
I am using the following command to create the resource:
pcs resource create newRes ClusterMon user="root" extra_options="-E /usr/local/
OR
pcs resource create newRes ocf:pacemaker:
and immediately i see following in /var/log/messages
2019-10-
2019-10-
2019-10-
2019-10-
2019-10-
2019-10-
2019-10-
2019-10-
2019-10-
2019-10-
Note:
- All other types of resources i.e. IPAddr, Drbd, systemd are working fine.
- Also, if the newRes is created wihtout -E, it works fine.
- Script has no complicated code. Event without the "echo" command i am seeing same issue.
cat /usr/local/
#!/bin/sh
echo "HELLO from Crm_mon script" >> /var/log/messages
exit
summary: |
- ClusterMon resource core-dumps while created with extr_option -E + ClusterMon resource creation core-dumps while created with extra_option + -E |
affects: | corosync (Ubuntu) → pacemaker (Ubuntu) |
Changed in pacemaker (Ubuntu Xenial): | |
status: | Incomplete → Triaged |
assignee: | nobody → Rafael David Tinoco (rafaeldtinoco) |
Changed in pacemaker (Ubuntu Xenial): | |
assignee: | Rafael David Tinoco (rafaeldtinoco) → nobody |
Thank you for taking the time to report this issue. Unfortunately I couldn't reproduce the coredump following the steps you provided. What I did is the following:
1. Started an amd64 Xenial virtual machine using multipass bin/new. sh identical to yours, and
extra_ options= "-E /usr/local/ bin/new. sh " ClusterMon \ bin/new. sh"
2. Installed pacemaker and pcs
3. Created /usr/local/
marked it as executable
4. Ran: pcs resource create newRes ClusterMon user="root" \
5. Ran: pcs resource create newRes ocf:pacemaker:
user="root" extra_options="-E /usr/local/
6. Checked the kernel messages.
In both cases no coredumps happened. Without a reproducer where isn't enough information for a developer to confirm this issue is a bug, or to begin working on it. Is it possible for you to provide up complete steps to reproduce from scratch from a clean system? You could use multipass to conveniently start a VM, or LXD to start a container (the *host* kernel is used in this case.)
I'm marking this report as Incomplete for the moment; please change its status back to New after providing more information. Thanks!