On Nov 23, 2009, at 10:41 AM, Nigel Kukard wrote:
>> My real issue was when I brought up the webui, the main page >> loaded, but anything beyond that brought up the dreaded "Error >> connecting to Policyd v2 DB: could not find driver" message. >> > > That is more a PHP vs. MySQL issue ... what I can say is you > probably need PHP 5 with PDO support. Ah, I'm seeing it now. I had checked for PDO originally and saw that support was there, but didn't notice that only certain DB formats were supported, and of course mysql was missing from that list... I'll get that fixed this evening and give it another go. On Nov 23, 2009, at 11:00 AM, Tobias J Kreidl wrote: > The clincher as to running policyd (either version) is the main.cf > file in postfix. You need something like this at the top, because > you want your rate limiting to kick in prior to everything else: > > smtpd_recipient_restrictions = > check_policy_service inet:127.0.0.1:10031 Yup, I had that from the 1.x version still, so that's fine. My original assumption, though, was that Cluebringer may have been started up via the Web interface, but now I'm thinking that may not be correct? There was nothing in the docs on actually starting the process, I'm assuming that /usr/local/sbin/cbpolicyd will kick this off? How should a config file be specified? This all got started with an ill advised upgrade to MySQL (5.0.x to 5.1.x, simple upgrade, what could go wrong?!?), I had forgotten just how many things would need to be recompiled for the new libraries, and my whole system went to hell in short order... My normal upgrade process is to clone my drive, boot that on another system, run through upgrades, test, make sure I have a good backup before doing upgrades on the live system, etc... This time, none of that happened, lesson learned. ;) _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
