Description of problem: Intent is to allow users to delete existing logging files and re-run our tools without getting into a permission error spacewalk-splice-tool was running as root and if it started prior to splice mod_wsgi some logging files under /var/log/splice would be owned by root. This would cause splice mod_wsgi app to be unable to log any info. To replicate this issue. 1) Delete logs under /var/log/splice/*.log 2) Run spacewalk-splice-tool 3) Verify that new log files are group owned by 'splice' and group readable/writeable
This bug is intended for SAM 1.3.0 GA. Not for Beta
mod_wsgi runs in the splice group now, this bz should be fixed. Marking as ON_QA.
Verified with spacewalk-splice-tool-0.40-1.el6sam: # ls -la /var/log/splice/ total 9788 drwxrwxr-x. 3 apache splice 4096 Aug 26 08:28 . drwxr-xr-x. 20 root root 4096 Aug 25 03:09 .. drwxrwxr-x. 2 splice splice 4096 Aug 14 14:29 celery -rw-r--r--. 1 splice splice 0 Aug 26 08:28 general.log -rw-r--r--. 1 splice splice 0 Aug 26 08:28 report_server.log -rw-r--r--. 1 splice splice 3327 Aug 26 08:28 spacewalk_splice_tool.log -rw-r--r--. 1 splice splice 756 Aug 26 08:28 splice.log
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. http://rhn.redhat.com/errata/RHEA-2013-1390.html