Good to know. I also couldn't reproduce it just by using those commands, some more setting up is probably needed. If we get reproducible steps, we might be able to identify the commit (or series of commits) that fixed it after 1.1.14. I took a quick look at the ChangeLog file but failed to spot anything obvious.
-- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1848834 Title: ClusterMon resource creation core-dumps while created with extra_option -E Status in pacemaker package in Ubuntu: Fix Released Status in pacemaker source package in Xenial: Incomplete 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.23.so[7f948cbd1000+1c0000] I am using the following command to create the resource: pcs resource create newRes ClusterMon user="root" extra_options="-E /usr/local/bin/new.sh " OR pcs resource create newRes ocf:pacemaker:ClusterMon user="root" extra_options="-E /usr/local/bin/new.sh " and immediately i see following in /var/log/messages 2019-10-19T01:53:11.783763-04:00 master daemon notice crmd 17042 notice: Operation newRes_monitor_0: not running (node=master.dhcp, call=85, rc=7, cib-update=58, confirmed=true) 2019-10-19T01:53:12.097529-04:00 master daemon info systemd - Started Session c75 of user root. 2019-10-19T01:53:12.105468-04:00 master auth info systemd-logind - New session c75 of user root. 2019-10-19T01:53:12.150340-04:00 master daemon notice lrmd 17039 notice: newRes_start_0:30376:stderr [ mesg: ttyname failed: Inappropriate ioctl for device ] 2019-10-19T01:53:12.186340-04:00 master daemon notice crmd 17042 notice: Operation newRes_start_0: ok (node=master.dhcp, call=86, rc=0, cib-update=59, confirmed=true) 2019-10-19T01:53:12.195312-04:00 master kern info kernel - crm_mon[30398]: segfault at 0 ip 00007f9cfbe41746 sp 00007ffd971060e8 error 4 in libc-2.23.so[7f9cfbdb6000+1c0000] 2019-10-19T01:53:12.216644-04:00 master auth info systemd-logind - Removed session c75. 2019-10-19T01:53:12.241439-04:00 master daemon notice lrmd 17039 notice: newRes_monitor_10000:30406:stderr [ /usr/lib/ocf/resource.d/heartbeat/ClusterMon: 155: kill: No such process ] 2019-10-19T01:53:12.241980-04:00 master daemon notice lrmd 17039 notice: newRes_monitor_10000:30406:stderr [ ] 2019-10-19T01:53:12.245273-04:00 master daemon notice crmd 17042 notice: master.dhcp-newRes_monitor_10000:87 [ /usr/lib/ocf/resource.d/heartbeat/ClusterMon: 155: kill: No such process\n\n ] 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/new.sh #!/bin/sh echo "HELLO from Crm_mon script" >> /var/log/messages exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1848834/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
