[Spacewalk-list] Spacewalk Monitoring not working. Problem with SELinux and gogo.pl.
Cliff Perry
cperry at redhat.com
Tue Jul 27 20:49:30 UTC 2010
Gregg Phillips wrote:
> Good Morning,
>
> I am having problems with a new installation of Spacewalk 1.0 and
> Monitoring. I am seeing the following messages from rhn-satellite status:
>
> [root at spacewalk centos-announce]# /usr/sbin/rhn-satellite status
> router (pid 775) is running...
> sm (pid 799) is running...
> c2s (pid 823) is running...
> s2s (pid 847) is running...
>
> LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 27-JUL-2010 09:12:37
>
> Copyright (c) 1991, 2005, Oracle. All rights reserved.
>
> Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE)))
> STATUS of the LISTENER
> ------------------------
> Alias LISTENER
> Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production
> Start Date 26-JUL-2010 16:36:28
> Uptime 0 days 16 hr. 36 min. 9 sec
> Trace Level off
> Security ON: Local OS Authentication
> SNMP OFF
> Default Service XE
> Listener Parameter File
> /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/network/admin/listener.ora
> Listener Log File
> /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/network/log/listener.log
> Listening Endpoints Summary...
> (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC_FOR_XE)))
>
> (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=spacewalk.cmdl.noaa.gov)(PORT=1521)))
>
> (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=9055))(Presentation=HTTP)(Session=RAW))
> Services Summary...
> Service "PLSExtProc" has 1 instance(s).
> Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this
> service...
> Service "XE" has 1 instance(s).
> Instance "XE", status READY, has 1 handler(s) for this service...
> Service "XEXDB" has 1 instance(s).
> Instance "XE", status READY, has 1 handler(s) for this service...
> Service "XE_XPT" has 1 instance(s).
> Instance "XE", status READY, has 1 handler(s) for this service...
> The command completed successfully
> osa-dispatcher (pid 937) is running...
> /etc/init.d/tomcat5 is already running (1464)
> httpd (pid 1488) is running...
> 2010-07-27 09:12:38 Monitoring: ----------- InstallSoftwareConfig STATUS
> ---------------
> 2010-07-27 09:12:38 Monitoring: ----------- GenerateNotifConfig STATUS
> ---------------
> 2010-07-27 09:12:38 GenerateNotifConfig: WARNING: STARTED BUT *NOT* RUNNING
> 2010-07-27 09:12:38 GenerateNotifConfig: ERRORS ENCOUNTERED DURING LAST
> ACTION:
> 2010-07-27 09:12:38 GenerateNotifConfig: !! ERROR FROM SHELL
> COMMAND:
> 2010-07-27 09:12:38 GenerateNotifConfig: !! STDOUT:
> 2010-07-27 09:12:38 GenerateNotifConfig: !! STDERR: Shell command
> timed out after 60 seconds
>
> 2010-07-27 09:12:38 GenerateNotifConfig: !! EXIT: -1
> 2010-07-27 09:12:38 Monitoring: ----------- NotifEscalator STATUS
> ---------------
> 2010-07-27 09:12:38 NotifEscalator: WARNING: STARTED BUT *NOT* RUNNING
> 2010-07-27 09:12:38 NotifEscalator: ERRORS ENCOUNTERED DURING LAST ACTION:
> 2010-07-27 09:12:38 NotifEscalator: !! ERROR FROM SHELL COMMAND:
> 2010-07-27 09:12:38 NotifEscalator: !! STDOUT:
> 2010-07-27 09:12:38 NotifEscalator: !! STDERR: Shell command timed
> out after 60 seconds
>
> 2010-07-27 09:12:38 NotifEscalator: !! EXIT: -1
> 2010-07-27 09:12:38 Monitoring: ----------- NotifLauncher STATUS
> ---------------
> 2010-07-27 09:12:38 NotifLauncher: WARNING: STARTED BUT *NOT* RUNNING
> 2010-07-27 09:12:38 NotifLauncher: ERRORS ENCOUNTERED DURING LAST ACTION:
> 2010-07-27 09:12:38 NotifLauncher: !! ERROR FROM SHELL COMMAND:
> 2010-07-27 09:12:38 NotifLauncher: !! STDOUT:
> 2010-07-27 09:12:38 NotifLauncher: !! STDERR: Shell command timed
> out after 60 seconds
>
> 2010-07-27 09:12:38 NotifLauncher: !! EXIT: -1
> 2010-07-27 09:12:38 Monitoring: ----------- Notifier STATUS ---------------
> 2010-07-27 09:12:38 Notifier: WARNING: STARTED BUT *NOT* RUNNING
> 2010-07-27 09:12:38 Notifier: ERRORS ENCOUNTERED DURING LAST ACTION:
> 2010-07-27 09:12:38 Notifier: !! ERROR FROM SHELL COMMAND:
> 2010-07-27 09:12:38 Notifier: !! STDOUT:
> 2010-07-27 09:12:38 Notifier: !! STDERR: Shell command timed out after
> 60 seconds
>
> 2010-07-27 09:12:38 Notifier: !! EXIT: -1
> 2010-07-27 09:12:38 Monitoring: ----------- AckProcessor STATUS
> ---------------
> 2010-07-27 09:12:38 AckProcessor: WARNING: STARTED BUT *NOT* RUNNING
> 2010-07-27 09:12:38 AckProcessor: ERRORS ENCOUNTERED DURING LAST ACTION:
> 2010-07-27 09:12:38 AckProcessor: !! ERROR FROM SHELL COMMAND:
> 2010-07-27 09:12:38 AckProcessor: !! STDOUT:
> 2010-07-27 09:12:38 AckProcessor: !! STDERR: Shell command timed
> out after 60 seconds
>
> 2010-07-27 09:12:38 AckProcessor: !! EXIT: -1
> 2010-07-27 09:12:38 Monitoring: ----------- TSDBLocalQueue STATUS
> ---------------
> 2010-07-27 09:12:38 TSDBLocalQueue: WARNING: STARTED BUT *NOT* RUNNING
> 2010-07-27 09:12:38 TSDBLocalQueue: ERRORS ENCOUNTERED DURING LAST ACTION:
> 2010-07-27 09:12:38 TSDBLocalQueue: !! ERROR FROM SHELL COMMAND:
> 2010-07-27 09:12:38 TSDBLocalQueue: !! STDOUT:
> 2010-07-27 09:12:38 TSDBLocalQueue: !! STDERR: Shell command timed
> out after 60 seconds
>
> 2010-07-27 09:12:38 TSDBLocalQueue: !! EXIT: -1
> 2010-07-27 09:12:39 MonitoringScout: ----------- InstallSoftwareConfig
> STATUS ---------------
> 2010-07-27 09:12:39 MonitoringScout: ----------- NPBootstrap STATUS
> ---------------
> 2010-07-27 09:12:39 MonitoringScout: ----------- SputLite STATUS
> ---------------
> 2010-07-27 09:12:39 SputLite: WARNING: STARTED BUT *NOT* RUNNING
> 2010-07-27 09:12:39 SputLite: ERRORS ENCOUNTERED DURING LAST ACTION:
> 2010-07-27 09:12:39 SputLite: !! ERROR FROM SHELL COMMAND:
> 2010-07-27 09:12:39 SputLite: !! STDOUT:
> 2010-07-27 09:12:39 SputLite: !! STDERR: Shell command timed out after
> 60 seconds
>
> 2010-07-27 09:12:39 SputLite: !! EXIT: -1
> 2010-07-27 09:12:39 MonitoringScout: ----------- Dequeuer STATUS
> ---------------
> 2010-07-27 09:12:39 Dequeuer: WARNING: STARTED BUT *NOT* RUNNING
> 2010-07-27 09:12:39 Dequeuer: ERRORS ENCOUNTERED DURING LAST ACTION:
> 2010-07-27 09:12:39 Dequeuer: !! ERROR FROM SHELL COMMAND:
> 2010-07-27 09:12:39 Dequeuer: !! STDOUT:
> 2010-07-27 09:12:39 Dequeuer: !! STDERR: Shell command timed out after
> 60 seconds
>
> 2010-07-27 09:12:39 Dequeuer: !! EXIT: -1
> 2010-07-27 09:12:39 MonitoringScout: ----------- Dispatcher STATUS
> ---------------
> 2010-07-27 09:12:39 Dispatcher: WARNING: STARTED BUT *NOT* RUNNING
> 2010-07-27 09:12:39 Dispatcher: ERRORS ENCOUNTERED DURING LAST ACTION:
> 2010-07-27 09:12:39 Dispatcher: !! ERROR FROM SHELL COMMAND:
> 2010-07-27 09:12:39 Dispatcher: !! STDOUT:
> 2010-07-27 09:12:39 Dispatcher: !! STDERR: Shell command timed
> out after 60 seconds
>
> 2010-07-27 09:12:39 Dispatcher: !! EXIT: -1
> rhn-search is running (2114).
> cobblerd (pid 2150) is running...
> RHN Taskomatic is running (2174).
> [root at spacewalk centos-announce]#
>
> I am also seeing these messages in /var/log/messages:
>
> Jul 26 22:00:16 spacewalk setroubleshoot: SELinux is preventing gogo.pl
> (spacewalk_monitoring_t) "name_connect" to <Unknown> (ldap_port_t). For
> complete SELinux messages. run sealert -l
> de4d4cb2-dd0a-4811-827f-b18bc31efc19
> Jul 26 22:00:16 spacewalk setroubleshoot: SELinux is preventing gogo.pl
> (spacewalk_monitoring_t) "create" to <Unknown> (spacewalk_monitoring_t).
> For complete SELinux messages. run sealert -l
> a424cf62-cb0e-4f72-bbb9-05a17ba4b009
> Jul 26 22:00:17 spacewalk setroubleshoot: SELinux is preventing gogo.pl
> (spacewalk_monitoring_t) "create" to <Unknown> (spacewalk_monitoring_t).
> For complete SELinux messages. run sealert -l
> a424cf62-cb0e-4f72-bbb9-05a17ba4b009
> Jul 26 22:00:33 spacewalk setroubleshoot: SELinux is preventing gogo.pl
> (spacewalk_monitoring_t) "name_connect" to <Unknown> (ldap_port_t). For
> complete SELinux messages. run sealert -l
> de4d4cb2-dd0a-4811-827f-b18bc31efc19
> Jul 26 22:00:33 spacewalk setroubleshoot: SELinux is preventing gogo.pl
> (spacewalk_monitoring_t) "create" to <Unknown> (spacewalk_monitoring_t).
> For complete SELinux messages. run sealert -l
> a424cf62-cb0e-4f72-bbb9-05a17ba4b009
> Jul 26 22:00:33 spacewalk setroubleshoot: SELinux is preventing gogo.pl
> (spacewalk_monitoring_t) "create" to <Unknown> (spacewalk_monitoring_t).
> For complete SELinux messages. run sealert -l
> a424cf62-cb0e-4f72-bbb9-05a17ba4b009
> Jul 26 22:01:04 spacewalk setroubleshoot: SELinux is preventing gogo.pl
> (spacewalk_monitoring_t) "name_connect" to <Unknown> (ldap_port_t). For
> complete SELinux messages. run sealert -l
> de4d4cb2-dd0a-4811-827f-b18bc31efc19
>
> I do have spacewalk-monitoring-selinux-1.0.1-1.el5 installed. Any help
> would be appreciated.
>
> TIA,
>
> Gregg.
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
when Satellite 5.3 was released, the SELinux rules for Monitoring was
released as Tech Preview, with known problems, one being gogo.pl errors.
In short, we have not worked to resolve all outstanding issues yet with
those SELinux rules for Monitoring subsystem.
https://bugzilla.redhat.com/show_bug.cgi?id=487221
http://www.redhat.com/docs/en-US/Red_Hat_Network_Satellite/5.3.0/Release_Notes/html/index.html
"SELinux modules that support Monitoring of RHN Satellite and RHN Proxy
Server on Red Hat Enterprise Linux 5 are now available. Note that
because this feature is a Technology Preview, it may not be functionally
complete and is currently not supported for production use. "
So, this doesn't help to fix your issue, other than say, it is likely we
know of the issue and have no short term plans to resolve it ourselves.
Cliff.
More information about the Spacewalk-list
mailing list