For the first time today, I had policyd hang on two separate servers, at about the same time. As best I could tell, it simply was timing out on connections. Restarting postfix had no effect. A large number of other servers, sharing the same mysql database didn't have any trouble.
Unfortunately, it was crunch time, and I had to quickly restart the daemons, and couldn't spend a lot of time debugging this problem. If this happens again, what data can I gather that would help track down the trouble? And what about some sort of heartbeat function? Or has anyone done a script that can simulate the postfix transaction? Or perhaps I'll just watch the postfix logs for this happening again. I use a once-a- minute check to make sure other daemons like postfix and clamd are still running - something similar for policyd would go a long way towards making the overall system more reliable. Thanks- Tom ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
