Bug 894739

Summary: [abrt] policycoreutils-devel-2.1.13-52.fc19: yacc.py:2141:yacc:YaccError: Unable to construct parser.
Product: [Fedora] Fedora Reporter: Tom London <selinux>
Component: policycoreutilsAssignee: Daniel Walsh <dwalsh>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dwalsh, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:02e7a5935e6f57f64a0bf5ce5a568b59328d6a78
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-15 14:39:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: environ
none
File: smolt_data none

Description Tom London 2013-01-13 15:24:43 UTC 
Description of problem:
Booted up in permissive mode.

Version-Release number of selected component:
policycoreutils-devel-2.1.13-52.fc19

Additional info:
cmdline:        /usr/bin/python -Es /usr/bin/sepolgen-ifgen
dso_list:       policycoreutils-python-2.1.13-52.fc19.x86_64
executable:     /usr/bin/sepolgen-ifgen
kernel:         3.8.0-0.rc2.git2.2.fc19.x86_64
uid:            0
Comment 1 Tom London 2013-01-13 15:24:45 UTC 
Created attachment 677746 [details]
File: backtrace
Comment 2 Tom London 2013-01-13 15:24:47 UTC 
Created attachment 677747 [details]
File: core_backtrace
Comment 3 Tom London 2013-01-13 15:24:48 UTC 
Created attachment 677748 [details]
File: environ
Comment 4 Tom London 2013-01-13 15:24:50 UTC 
Created attachment 677749 [details]
File: smolt_data
Comment 5 Miroslav Grepl 2013-01-14 09:54:58 UTC 
Are you still getting it with -54.fc19 release?
Comment 6 Tom London 2013-01-14 14:29:43 UTC 
Hmmm... Interesting.  I've been running -54 since 10 January (this occurred on 13 January):

Jan 06 07:54:14 Updated: policycoreutils-2.1.13-52.fc19.x86_64
Jan 06 07:54:16 Updated: policycoreutils-python-2.1.13-52.fc19.x86_64
Jan 06 07:54:58 Updated: policycoreutils-devel-2.1.13-52.fc19.x86_64
Jan 06 07:54:59 Updated: policycoreutils-gui-2.1.13-52.fc19.x86_64
Jan 06 07:55:00 Updated: policycoreutils-sandbox-2.1.13-52.fc19.x86_64
Jan 09 06:20:11 Updated: policycoreutils-2.1.13-53.fc19.x86_64
Jan 09 06:20:13 Updated: policycoreutils-python-2.1.13-53.fc19.x86_64
Jan 09 06:20:19 Updated: policycoreutils-devel-2.1.13-53.fc19.x86_64
Jan 09 06:20:53 Updated: policycoreutils-gui-2.1.13-53.fc19.x86_64
Jan 09 06:20:55 Updated: policycoreutils-sandbox-2.1.13-53.fc19.x86_64
Jan 10 07:37:44 Updated: policycoreutils-2.1.13-54.fc19.x86_64
Jan 10 07:37:47 Updated: policycoreutils-python-2.1.13-54.fc19.x86_64
Jan 10 07:39:00 Updated: policycoreutils-devel-2.1.13-54.fc19.x86_64
Jan 10 07:39:41 Updated: policycoreutils-gui-2.1.13-54.fc19.x86_64
Jan 10 07:39:42 Updated: policycoreutils-sandbox-2.1.13-54.fc19.x86_64

[root@tlondon ~]# rpm -qa policycoreutils\*
policycoreutils-python-2.1.13-54.fc19.x86_64
policycoreutils-devel-2.1.13-54.fc19.x86_64
policycoreutils-sandbox-2.1.13-54.fc19.x86_64
policycoreutils-2.1.13-54.fc19.x86_64
policycoreutils-gui-2.1.13-54.fc19.x86_64
[root@tlondon ~]# 

I wonder if booting permissively "allowed it to find something old"...

A quick scan of /var/log/messages: I see only this:

Jan 13 07:21:56 tlondon abrt-server[1428]: Problem directory '/var/spool/abrt/pyhook-2013-01-09-06:20:17-2063' can't be accessed by user with uid 1000

[root@tlondon abrt]# ls -l
total 44
-rw-r--r--. 1 root root 18432 Mar 30  2011 abrt-db
-rw-r--r--. 1 root root    24 Oct  7  2011 last-ccpp
-rw-------. 1 root root    23 Jan  9 06:20 last-via-server
drwxr-x---. 2 abrt root  4096 Jan  9 06:20 pyhook-2012-07-11-06:44:47-4254
drwxr-x---. 2 abrt root  4096 Jan  9 06:20 pyhook-2012-11-17-07:27:06-2169
drwxr-x---. 2 abrt tbl   4096 Jan 13 07:21 pyhook-2013-01-09-06:20:17-2063
[root@tlondon abrt]# 

and

[root@tlondon pyhook-2013-01-09-06:20:17-2063]# cat cmdline
/usr/bin/python -Es /usr/bin/sepolgen-ifgen[root@tlondon pyhook-2013-01-09-06:20:17-2063]# 

Possible that enforcing mode (or something else) "delayed" scanning this?
Comment 7 Daniel Walsh 2013-01-15 02:01:00 UTC 
So it seems to be working now?  Could this have been caused by the role_attributes change?
Comment 8 Tom London 2013-01-15 14:28:57 UTC 
Working? Well, I no longer see anything on either enforcing or permissive reboots, and I don't see the 'abrt-server' message in /var/log/messages.

So I guess yes.