On August 8, 2012 9:41 , ross smith <[email protected]> wrote:
> The existing machine
> works flawlessly, but the new one produces the follow error messages,
> and errors when validating the cookie.
>
> [Wed Aug 08 09:20:57 2012] [error] mod_cosign: connect_sn: connect
> [Wed Aug 08 09:20:57 2012] [error] mod_cosign: connect_sn: connect
> [Wed Aug 08 09:20:57 2012] [error] mod_cosign: connect_sn: connect
> [Wed Aug 08 09:20:57 2012] [error] mod_cosign: connect_sn: connect
> [Wed Aug 08 09:20:57 2012] [error] mod_cosign: connect_sn: connect
> [Wed Aug 08 09:20:57 2012] [error] mod_cosign: connect_sn: connect
> [Wed Aug 08 09:20:57 2012] [error] mod_cosign: cosign_cookie_valid:
> Unable to connect to any Cosign server.

The "connect_sn: connect" errors mean that mod_cosign received an error 
from the kernel when it called connect(2).  Unfortunately, the code ( 
http://cosign.git.sourceforge.net/git/gitweb.cgi?p=cosign/cosign;a=blob;f=filters/common/connect.c;h=0139e0eb72a631e4b3d0cb2460603fe8014ded44;hb=HEAD#l757
 
) does not log which specific error was returned by the kernel.   Run 
"man 2 connect" for a list of what the potential errors are.

Do you have any Mandatory Access Control system running, such as 
SELinux, grsecurity, AppArmor, TOMOYO, or anything else?  For example, 
if you are running SELinux (which is likely the case if you're running a 
Red Hat derived Linux distribution), make sure you have the SELinux 
boolean httpd_can_network_connect set to "on" (run "getsebool -a | grep 
httpd" to see).   Also if you're running SELinux, check 
/var/log/audit/audit.log for denial messages.

--
   Mark Montague
   [email protected]


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss

Reply via email to