I've seen the hang again but I still don't see much in terms of logging. Here's my cbpolicyd.log at the time:
[2011/03/17-12:01:07 - 14379] [CORE] INFO: 2011/03/17-12:01:07 CONNECT TCP Peer: "127.0.0.1:37195" Local: "127.0.0.1:10031" [2011/03/17-12:01:07 - 13703] [CORE] INFO: Starting "1" children [2011/03/17-12:01:07 - 14475] [CORE] DEBUG: Child Preforked (14475) [2011/03/17-12:01:07 - 14475] [CBPOLICYD] DEBUG: Starting up caching engine [2011/03/17-12:02:48 - 14368] [CORE] INFO: 2011/03/17-12:02:48 CONNECT TCP Peer: "127.0.0.1:41286" Local: "127.0.0.1:10031" [2011/03/17-12:02:48 - 13703] [CORE] INFO: Starting "1" children [2011/03/17-12:02:48 - 14478] [CORE] DEBUG: Child Preforked (14478) [2011/03/17-12:02:48 - 14478] [CBPOLICYD] DEBUG: Starting up caching engine And here's my postfix log: Mar 17 12:01:05 mail01 postfix/smtpd[14468]: connect from fw-1.dby1.griffin.com[83.148.189.2] Mar 17 12:02:47 mail01 postfix/smtpd[14468]: warning: problem talking to server 127.0.0.1:10031: Connection timed out Any ideas where to look? It's almost like a stale DB connection or something.. Also I've just noticed on my firewall between policyd and the Database server I'm seeing a rejected connection with the following information: not a (valid) SYN packet [PA] (CT) Thanks From: [email protected] [mailto:[email protected]] On Behalf Of Ian Mordey Sent: 17 March 2011 08:48 To: [email protected] Subject: Re: [policyd-users] Problem with cluebringer hanging. Ok. I've set it to log modules in debug. I've also disabled the modules I'm not using. I'll see if I can reproduce today. Thanks From: [email protected] [mailto:[email protected]] On Behalf Of Nigel Kukard Sent: 16 March 2011 21:20 To: [email protected] Subject: Re: [policyd-users] Problem with cluebringer hanging. I've just seen this hang again. How do I enable debugging of individual modules? Check the config file, there is a section there to enable debugging for modules. # Things to log in extreme detail # modules - Log detailed module running information # tracking - Log detailed tracking information # policies - Log policy resolution # protocols - Log general protocol info, but detailed # bizanga - Log the bizanga protocol # cache - Log cache usage on client shutdown # # There is no default for this configuration option. Options can be # separated by commas. ie. protocols,modules # #log_detail= Regards Nigel
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
