hi,

thanks for your advice

it seems that while editing the dspam.conf file the location of mysql.sock was 
changed by mistake and hence the error.

it seems that anytime the mysql initialization fails then then problem is 99 
percent related to dspam database connectivity

things are working perfect now

rajesh mahadevan


---------- Original Message ----------------------------------
From: Michael Alger <[EMAIL PROTECTED]>
Reply-To: [email protected]
Date:  Thu, 15 Mar 2007 19:18:06 -0400

>On Thu, Mar 15, 2007 at 10:16:34PM +0000, 24x7server wrote:
>> we configured and installed dspam with these options
>> 
>> ./configure ...
>>    --with-storage-driver=mysql_drv
>>    --with-mysql-includes=/usr/include/mysql
>>    --with-mysql-libraries=/usr/lib/mysql
>>    --enable-preferences-extension
>>    --enable-signature-headers
>>    --enable-mysql4-initialization
>> 
>> we are getting this error in dspam.debug
>> 
>> _ds_init_storage() failed
>>  _ds_init_storage: mysql_init: unable to initialize handle to database
>
>Double-check that your MySQL configuration in your dspam.conf is
>correct, i.e. MySQLServer, MySQLUser, MySQLPass, and MySQLdb.
>
>> and further on we noted that the file libmysql_drv.so does not exist
>> at all
>> 
>> /etc/dspam/lib/libmysql_drv.so
>
>It won't do; if you only specify one storage driver, it is statically
>linked into dspam. If you really want it as an external library, you can
>specify the same storage driver twice:
>
>  --with-storage-driver=mysql_drv,mysql_drv
>
>

Reply via email to