I've been running 1.82 for a long time, finally wanting to make the  
move to Cluebringer, but ran into some issues last night, and after a  
few hours of beating my head against the wall had to restore my system  
to get back in business.  I'm going from memory here because the logs  
are no longer available.

I followed the install doc, I had all of the required components  
installed that were listed, except for Mail::SPF, as I don't use SPF.

The Install doc indicated that I should import the policyd.mysql file  
into a database called policyd, but the cluebringer.conf file listed  
the default database as 'cluebringer', so I did the import into that  
database instead, as my old policyd was still in place.  That didn't  
seem like an issue, but might be something to change in the docs?

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.  I know that PHP can  
talk to MySQL just fine (I run phpMyAdmin), and even reinstalled the  
other required drivers again just to be sure, but nothing got around  
that error.


My second issue is that I don't run amavisd here currently, from the  
Install doc, it wasn't clear if this is a requirement or not?  Is this  
what will now call cluebringer, rather than it running as a daemon?


Thanks.
_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users

Reply via email to