Roundup Tracker - Issues

Message3362

Author chrismacgregor
Recipients
Date 2005-02-01.10:36:25
Message-id
In-reply-to
On Fedora Core 3, with patches current as of 31 Jan
2005, I'm trying Roundup 0.7.11.  I have selinux
enabled in targeted mode.

When I tried to access the web interface on my first
freshly set-up tracker, I got a Python traceback. 
Knowing it might be selinux, I checked and found these
in /var/log/messages:

Feb  1 01:58:18 secure1 kernel:
audit(1107251898.241:0): avc:  denied  { getattr } for
 pid=5772 exe=/usr/bin/python path=/var dev=hda3
ino=8191585 scontext=user_u:system_r:httpd_sys_script_t
tcontext=system_u:object_r:var_t tclass=dir
Feb  1 01:58:44 secure1 kernel:
audit(1107251924.762:0): avc:  denied  { getattr } for
 pid=5773 exe=/usr/bin/python path=/var dev=hda3
ino=8191585 scontext=user_u:system_r:httpd_sys_script_t
tcontext=system_u:object_r:var_t tclass=dir
Feb  1 01:58:45 secure1 kernel:
audit(1107251925.180:0): avc:  denied  { write } for 
pid=5773 exe=/usr/bin/python name=lock dev=hda3
ino=11116127
scontext=user_u:system_r:httpd_sys_script_t
tcontext=root:object_r:usr_t tclass=file

Now, obviously this is not really a bug in Roundup, but
it'd be super helpful if you guys could include a patch
or clue or something about how to tweak the policy file
to get things to work.  If I figure it out I'll post an
update, but don't hold your breath - I have too much
going on to spend much time on this.
History
Date User Action Args
2009-02-03 14:23:56adminlinkissue1113861 messages
2009-02-03 14:23:56admincreate