I was able to fix it by doing the following. I installed setroubleshoot "yum install setroubleshoot" Then I ran the following command "sealert -a /var/log/audit/audit.log > /path/to/mylogfile.txt" mylogfile.txt showed: found 3 alerts in /var/log/audit/audit.log -------------------------------------------------------------------------------- SELinux is preventing /usr/sbin/radiusd from create access on the semaphore . ***** Plugin catchall (100. confidence) suggests *************************** If you believe that radiusd should be allowed create access on the sem by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep radiusd /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp -------------------------------------------------------------------------------- SELinux is preventing /usr/sbin/radiusd from search access on the directory /home. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that radiusd should be allowed search access on the home directory by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep radiusd /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp -------------------------------------------------------------------------------- SELinux is preventing /usr/sbin/radiusd from name_connect access on the tcp_socket . ***** Plugin catchall (100. confidence) suggests *************************** If you believe that radiusd should be allowed name_connect access on the tcp_socket by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep radiusd /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp I ran the commands listed above: "grep radiusd /var/log/audit/audit.log | audit2allow -M mypol" "semodule -i mypol.pp" That fixed the problem, thanks again. ________________________________________ From: Bill Grant [wgrant@ebpl.org] Sent: Saturday, May 25, 2013 8:29 PM To: FreeRadius users mailing list Subject: RE: Error: rlm_sql_unixodbc: SQL down 08S01 [unixODBC][FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist You are right I temporarily disabled SE Linux with "echo 0 >/selinux/enforce" and it worked. Now I just need to figure out exactly what it is blocking. Thanks for the help! ________________________________________ From: Alan DeKok [aland@deployingradius.com] Sent: Saturday, May 25, 2013 7:44 PM To: FreeRadius users mailing list Subject: Re: Error: rlm_sql_unixodbc: SQL down 08S01 [unixODBC][FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist Bill Grant wrote:
I am having trouble starting freeradius at boot on CentOS 6.4. It starts, but it does not connect to my database; however, if run it manually from the command the it works fine. I think there is permission issue somewhere. See the log below:
when I run following command as root it works
It's probably some SELinux rule. The normal Linux APIs allow *any* process to make outbound connections. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html