Oh one more thing - will it matter that SELinux is in permissive mode
rather than disabled?
I've never seen a circumstance where it would.
But on the server it is set to "permissive" which shows warnings in the log
files but allows the activity anyway. And I do see see this each time :
Jan 4 10:50:02 solexa2 setroubleshoot: SELinux is preventing ethtool
(ifconfig_t) "read write" to socket (initrc_t). For complete SELinux
messages. run sealert -l 97787abc-6be8-45cd-a06c-e0e572f35697
Jan 4 10:50:53 solexa2 kernel: device eth0 entered promiscuous mode
Jan 4 10:51:08 solexa2 nrpe[10937]: Error: Could not complete SSL
handshake. 1
Oh, and I just noticed that NRPE error is new since I installed NRPE from
yum instead of the sources I was using. That seems to be the crux of it I
guess. But I'm using the -n flag in my check_nrpe because I do not want to
use SSL
Once again I ask - how do I configure this to not use SSL? I don't care
about security in my situation I just want it to work. Or otherwise where
are full details on getting this working with it?
thanks,
-Alan
--
“Don't eat anything you've ever seen advertised on TV”
- Michael Pollan, author of "In Defense of Food"
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/icinga-users
