Version-Release number of selected component:
cmdline: /var/lib/pcp/pmdas/rpm/pmdarpm -d 123
runlevel: N 3
Thread no. 1 (9 frames)
#0 luaH_getstr at ltable.c:458
#1 luaH_set at ltable.c:495
#2 luaV_settable at lvm.c:141
#3 lua_settable at lapi.c:651
#4 luaL_findtable at lauxlib.c:371
#5 luaL_openlib at lauxlib.c:247
#6 rpmReadConfigFiles at /lib64/librpm.so.3
#7 rpm_update_cache at rpm.c:407
#8 rpm_inotify at rpm.c:490
Created attachment 838095 [details]
Created attachment 838096 [details]
Created attachment 838097 [details]
Created attachment 838098 [details]
Created attachment 838099 [details]
Created attachment 838100 [details]
Created attachment 838101 [details]
Created attachment 838102 [details]
Created attachment 838103 [details]
Created attachment 838104 [details]
This commit to reduce the number of events noticed by inotify seems to resolve the problem:
Throttle inotify to only watch Packages.
Updating state, setting assignment to reflect the good work Stan has done in fixing & testing here. Fix was released upstream in pcp-3.8.12, but I overlooked adding this BZ into the changelog - sorry about that!
This problem still recurs intermittently.
[269814.151162] pmdarpm: segfault at d ip 00002b76f900ffe0 sp 00002b76fb19ca40 error 4 in liblua-5.1.so[2b76f8ffc000+2b000]
[269814.151173] potentially unexpected fatal signal 11.
[269814.151175] CPU: 2 PID: 1864 Comm: pmdarpm Tainted: PF O 3.13.5-101.fc19.x86_64 #1
[269814.151176] Hardware name: ASUS All Series/H87M-PLUS, BIOS 0306 04/07/2013
[269814.151177] task: ffff880406929140 ti: ffff8800d711a000 task.ti: ffff8800d711a000
[269814.151178] RIP: 0033:[<00002b76f900ffe0>] [<00002b76f900ffe0>] 0x2b76f900ffe0
[269814.151189] RSP: 002b:00002b76fb19ca40 EFLAGS: 00010246
[269814.151189] RAX: 0000000000000001 RBX: 00002b76fb19ca50 RCX: 000000000000000d
[269814.151190] RDX: 0000000000000001 RSI: 00002b76fb19ca50 RDI: 0000000000000001
[269814.151190] RBP: 0000000000000000 R08: 0000000000000000 R09: 00002b76fb19cabc
[269814.151191] R10: 0000000000000005 R11: 00002b76f67f6020 R12: 00002b76fc03bf60
[269814.151192] R13: 00002b76fc03d5d0 R14: 00002b76fc03d520 R15: 00002b76fc03d540
[269814.151193] FS: 00002b76fb1a5700(0000) GS:ffff88041ec80000(0000) knlGS:0000000000000000
[269814.151193] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[269814.151194] CR2: 000000000000000d CR3: 000000032efd5000 CR4: 00000000001407e0
I don't have a core dump at this time.
Please see commit 2b819ff78995c on pcpfans.git.
It appears to correct this problem.
pcp-3.9.2-1.el6 has been submitted as an update for Fedora EPEL 6.
pcp-3.9.2-1.el5 has been submitted as an update for Fedora EPEL 5.
pcp-3.9.2-1.fc20 has been submitted as an update for Fedora 20.
pcp-3.9.2-1.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora EPEL 5 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing pcp-3.9.2-1.el5'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
pcp-3.9.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.
pcp-3.9.2-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
pcp-3.9.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.
pcp-3.9.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.