Description of problem: localhost:~> rpm -q pcp pcp-3.8.0-1.el6.x86_64 localhost:~> sudo rpm -V pcp missing /var/lib/pcp/pmns/.NeedRebuild localhost:~> pmatop Traceback (most recent call last): File "/usr/bin/pmatop", line 765, in <module> status = curses.wrapper(main) # pylint: disable-msg=C0103 File "/usr/lib64/python2.6/curses/wrapper.py", line 43, in wrapper return func(stdscr, *args, **kwds) File "/usr/bin/pmatop", line 643, in main proc.setup_metrics (pmc) File "/usr/lib64/python2.6/site-packages/pcp/pmsubsys.py", line 65, in setup_metrics raise pmErr, (c_api.PM_ERR_NAME, "", name_pattern) pcp.pmapi.pmErr: PM_ERR_NAME Unknown metric name: proc.* localhost:~> service pmcd status Checking for pmcd: running localhost:~>
pmatop appears to require the proc PMDA to be activated, as in # cd /var/lib/pcp/pmdas/proc; ./Install pmatop should offer this advice if it detects the problem, rather than letting a low level exception propagate out. (How much can pmatop do without proc.*?)
pcp-3.8.1-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/pcp-3.8.1-1.el6
pcp-3.8.1-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
With 3.8.1 I'm getting this both before and after the activation: localhost:~> rpm -q pcp pcp-3.8.1-1.el6.x86_64 localhost:~> sudo rpm -V pcp missing /var/lib/pcp/pmns/.NeedRebuild localhost:~> pmatop Traceback (most recent call last): File "/usr/bin/pmatop", line 732, in <module> status = curses.wrapper(main) # pylint: disable-msg=C0103 File "/usr/lib64/python2.6/curses/wrapper.py", line 43, in wrapper return func(stdscr, *args, **kwds) File "/usr/bin/pmatop", line 670, in main stdscr.move (proc.command_line, 0) AttributeError: '_ProcPrint' object has no attribute 'command_line' localhost:~> service pmcd status Checking for pmcd: running localhost:~>
pcp-3.8.2-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/pcp-3.8.2-1.fc19
pcp-3.8.2-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/pcp-3.8.2-1.fc18
pcp-3.8.2-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/pcp-3.8.2-1.fc17
pcp-3.8.2-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/pcp-3.8.2-1.el6
pcp-3.8.2-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/pcp-3.8.2-1.el5
Package pcp-3.8.2-1.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing pcp-3.8.2-1.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11023/pcp-3.8.2-1.el6 then log in and leave karma (feedback).
pcp-3.8.2-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
Note that the pcp 3.8.1 -> 3.8.2 upgrade preserves a modified pmcd.conf, so the newly-default proc pmda will not be activated by default. Worse, the proc pmda's /var/lib/pcp/pmdas directory lacks Install/Remove scripts, so one can't activate them by hand either. In my case, I opted to have rpm overwrite the pmcd.conf during a yum reinstall to get this working.
(In reply to Frank Ch. Eigler from comment #12) > Note that the pcp 3.8.1 -> 3.8.2 upgrade preserves a modified pmcd.conf, > so the newly-default proc pmda will not be activated by default. Worse, > the proc pmda's /var/lib/pcp/pmdas directory lacks Install/Remove scripts, > so one can't activate them by hand either. In my case, I opted to have > rpm overwrite the pmcd.conf during a yum reinstall to get this working. Right, so how one should start using pmatop after installing 3.8.2 for the first time on a system?
That should Just Work (tm); % sudo service pmcd start; pmatop
(In reply to Frank Ch. Eigler from comment #14) > That should Just Work (tm); % sudo service pmcd start; pmatop Nope, it's still the same as before: localhost:~> rpm -q pcp pcp-3.8.2-1.el6.x86_64 localhost:~> sudo rpm -V pcp missing /var/lib/pcp/pmns/.NeedRebuild localhost:~> pmatop Traceback (most recent call last): File "/usr/bin/pmatop", line 741, in <module> status = curses.wrapper(main) # pylint: disable-msg=C0103 File "/usr/lib64/python2.6/curses/wrapper.py", line 43, in wrapper return func(stdscr, *args, **kwds) File "/usr/bin/pmatop", line 679, in main stdscr.move (proc.command_line, 0) AttributeError: '_ProcPrint' object has no attribute 'command_line' localhost:~> service pmcd status Checking for pmcd: running localhost:~>
Interestingly, the error is printed when using a standard 80x24 terminal but pmatop starts up nicely when the terminal used is at least 80x28.
sourceware.org/git/pcpfans.git branch scox/dev commit bd98b690b7605f7af779ea843f4682214f02f24c Author: Stan Cox <scox> Date: Mon Aug 5 16:44:21 2013 -0400 Fix pmatop interactive help. * pmatop (main): Display interactive help on its own screen.
pcp-3.8.2-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
sourceware.org/git/pcpfans.git branch scox/dev commit feb87493a9239be489c9d2ab66433c430b637207 Author: Stan Cox <scox> Date: Thu Aug 8 18:28:01 2013 -0400 Decrease screen real estate used for display. * pmatop.py (_AtopPrint): Add end_of_screen. Use throughout. (_ProcessorPrint): Don't display cpus with no activity in interval. (_DiskPrint): Likewise for lvm. (_NetPrint): Lisewise for net.
Hi Stan, I'm happy to confirm that pmatop of pcpfans scox/dev feb87493 now finally starts up correctly also on a standard 80x24 terminal. Thanks!
pcp-3.8.2-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
Patch upstream, will be part of 3.8.3 (not 3.8.2).
pcp-3.8.2-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.