Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
I tried pmdabash, following the instructions in manual page.
[root@pes-guest-79 bash]# ./Install
You will need to choose an appropriate configuration for installation of
the "bash" Performance Metrics Domain Agent (PMDA).
collector collect performance statistics on this system
monitor allow this system to monitor local and/or remote systems
both collector and monitor configuration for this system
Please enter c(ollector) or m(onitor) or b(oth) [b]
Install bash as a daemon or dso agent? [daemon]
PMCD should communicate with the bash daemon via a pipe or a socket? [pipe]
Updating the Performance Metrics Name Space (PMNS) ...
Terminate PMDA if already installed ...
Updating the PMCD control file, and notifying PMCD ...
Check bash metrics have appeared ... 10 metrics and 0 values
[root@pes-guest-79 bash]# pminfo -f bash
bash.xtrace.numclients
No value(s) available!
bash.xtrace.maxmem
No value(s) available!
bash.xtrace.queuemem
No value(s) available!
bash.xtrace.count
No value(s) available!
bash.xtrace.records
No value(s) available!
bash.xtrace.parameters.pid
No value(s) available!
bash.xtrace.parameters.parent
No value(s) available!
bash.xtrace.parameters.lineno
No value(s) available!
bash.xtrace.parameters.function
No value(s) available!
bash.xtrace.parameters.command
No value(s) available!
[root@pes-guest-79 bash]#
[root@pes-guest-79 bash]#
[root@pes-guest-79 bash]#
[root@pes-guest-79 bash]# cat t.sh
#!/bin/bash
source $PCP_DIR/etc/pcp.sh
pcp_trace on $@ # enable tracing
echo $?
[root@pes-guest-79 bash]#
[root@pes-guest-79 bash]#
[root@pes-guest-79 bash]#
[root@pes-guest-79 bash]# ./t.sh
<after staring at frozen script for a while, Ctrl+C is applied...>
^C/usr/share/pcp/lib/bashproc.sh: line 57: /var/lib/pcp/tmp/pmdabash/24373: Interrupted system call
56 # setup link between xtrace & fifo
57 exec 99>"${PCP_TRACE_DATA}"
According to strace it really tries to connect to its pipe:
23856 0.000093 open("/var/lib/pcp/tmp/pmdabash/23856", O_WRONLY|O_CREAT|O_TRUNC, 0666) = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
23856 5.569255 --- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL, si_value={int=0, ptr=0x7f5200000000}} ---
Version-Release number of selected component (if applicable):
pcp-3.9.10-8.el7
bash-4.2.46-12.el7
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2017:1968
Description of problem: I tried pmdabash, following the instructions in manual page. [root@pes-guest-79 bash]# ./Install You will need to choose an appropriate configuration for installation of the "bash" Performance Metrics Domain Agent (PMDA). collector collect performance statistics on this system monitor allow this system to monitor local and/or remote systems both collector and monitor configuration for this system Please enter c(ollector) or m(onitor) or b(oth) [b] Install bash as a daemon or dso agent? [daemon] PMCD should communicate with the bash daemon via a pipe or a socket? [pipe] Updating the Performance Metrics Name Space (PMNS) ... Terminate PMDA if already installed ... Updating the PMCD control file, and notifying PMCD ... Check bash metrics have appeared ... 10 metrics and 0 values [root@pes-guest-79 bash]# pminfo -f bash bash.xtrace.numclients No value(s) available! bash.xtrace.maxmem No value(s) available! bash.xtrace.queuemem No value(s) available! bash.xtrace.count No value(s) available! bash.xtrace.records No value(s) available! bash.xtrace.parameters.pid No value(s) available! bash.xtrace.parameters.parent No value(s) available! bash.xtrace.parameters.lineno No value(s) available! bash.xtrace.parameters.function No value(s) available! bash.xtrace.parameters.command No value(s) available! [root@pes-guest-79 bash]# [root@pes-guest-79 bash]# [root@pes-guest-79 bash]# [root@pes-guest-79 bash]# cat t.sh #!/bin/bash source $PCP_DIR/etc/pcp.sh pcp_trace on $@ # enable tracing echo $? [root@pes-guest-79 bash]# [root@pes-guest-79 bash]# [root@pes-guest-79 bash]# [root@pes-guest-79 bash]# ./t.sh <after staring at frozen script for a while, Ctrl+C is applied...> ^C/usr/share/pcp/lib/bashproc.sh: line 57: /var/lib/pcp/tmp/pmdabash/24373: Interrupted system call 56 # setup link between xtrace & fifo 57 exec 99>"${PCP_TRACE_DATA}" According to strace it really tries to connect to its pipe: 23856 0.000093 open("/var/lib/pcp/tmp/pmdabash/23856", O_WRONLY|O_CREAT|O_TRUNC, 0666) = ? ERESTARTSYS (To be restarted if SA_RESTART is set) 23856 5.569255 --- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL, si_value={int=0, ptr=0x7f5200000000}} --- Version-Release number of selected component (if applicable): pcp-3.9.10-8.el7 bash-4.2.46-12.el7 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: