Description of problem: satellite install, selinux denials osa-dispatcher Satellite-5.3.0-RHEL5-re20090220.1-i386-embedded-oracle.iso clear audit log install latest satellite iso check audit log type=AVC msg=audit(1235187502.664:399): avc: denied { read write } for pid=9614 comm="osa-dispatcher" path="socket:[7018]" dev=sockfs ino=7018 scontext=root:system_r:osa _dispatcher_t:s0 tcontext=system_u:system_r:unconfined_t:s0-s0:c0.c1023 tclass=unix_stream_socket type=AVC msg=audit(1235187502.664:399): avc: denied { read write } for pid=9614 comm="osa-dispatcher" path="socket:[7018]" dev=sockfs ino=7018 scontext=root:system_r:osa _dispatcher_t:s0 tcontext=system_u:system_r:unconfined_t:s0-s0:c0.c1023 tclass=unix_stream_socket type=AVC msg=audit(1235187502.664:399): avc: denied { read write } for pid=9614 comm="osa-dispatcher" path="socket:[7020]" dev=sockfs ino=7020 scontext=root:system_r:osa _dispatcher_t:s0 tcontext=system_u:system_r:unconfined_t:s0-s0:c0.c1023 tclass=unix_stream_socket
*** This bug has been marked as a duplicate of bug 484653 ***
The AVC denials are completely different. Reopening.
What did you do after that installation? After the installer said * Deploying configuration files. * Update configuration in database. * Setting up Cobbler.. * Restarting services. Installation complete. Visit https://your-satellite.redhat.com to create the RHN Satellite administrator account. what other steps did you make? Could it be that you are not running the installer on a terminal but from some automation thing, and it's that thing which causes the problem?
Generally, these look like leaked descriptors from whatever automation tool you are using. Please provide info about how exactly you run those installations.
Jan and I chatted.. the differences we are seeing may be caused by running the installer in a "screen" session.
Wes confirmed that the installation was run under screen and that re-running the installation without screen does not generate the AVC denials. So currently it looks like leaked file descriptor in screen.
running w/ the correct version of screen did NOT produce this error.. I think we can close this.
closing