Comment 5 for bug 1848834

Hello everyone,
Thanks for the response.
As for my setup, i could reproduce it every time.
Its 2 node cluster with Ubuntu 16.04 version.
I downloaded pcs, corosync and pacemaker from xenial repo, the following revisions:

pacemaker_1.1.14-2ubuntu1.6_amd64.deb ;
pacemaker-common_1.1.14-2ubuntu1.6_all.deb;
pacemaker-cli-utils_1.1.14-2ubuntu1.6_amd64.deb;
pacemaker-resource-agents_1.1.14-2ubuntu1.6_all.deb;
corosync_2.3.5-3ubuntu2.3_amd64.deb
pcs_0.9.149-1ubuntu1.1_amd64.deb
resource-agents_1%3a3.9.7-1ubuntu1.1_amd64.deb

Ran the following steps:

pcs resource create newRes ocf:pacemaker:ClusterMon user="root" update="30" extra_options="-E /opt/nec/vcpe/scripts/db_clustermon_helper.sh op monitor on-fail="restart" interval="60"

And I see following in /var/log/message

2019-11-07T00:03:36.384243-05:00 master daemon notice lrmd 1562 notice: newRes_start_0:29654:stderr [ mesg: ttyname failed: Inappropriate ioctl for device ]
2019-11-07T00:03:36.390797-05:00 master daemon notice crmd 1565 notice: Operation newRes_start_0: ok (node=master.clusterdb.cwp, call=33, rc=0, cib-update=22, confirmed=true)
2019-11-07T00:03:36.397064-05:00 master kern warning kernel - show_signal_msg: 4 callbacks suppressed
2019-11-07T00:03:36.397241-05:00 master kern info kernel - crm_mon[29667]: segfault at 0 ip 00007f68b8eb5746 sp 00007ffea7ea4ce8 error 4 in libc-2.23.so[7f68b8e2a000+1c0000]

And for pcs status:
root@master:~/autoci# pcs status | grep newRes
 newRes (ocf::pacemaker:ClusterMon): Stopped
* newRes_monitor_60000 on slave.clusterdb.cwp 'not running' (7): call=90, status=complete, exitreason='none',
* newRes_monitor_60000 on master.clusterdb.cwp 'not running' (7): call=34, status=complete, exitreason='none',

Thanks,
Manisha.