Stevan, It is OK, if i disable logging. I just wanted to point the problem about logging ;)
On Thu, Dec 17, 2009 at 5:25 PM, Stevan Bajić <[email protected]> wrote: > On Thu, 17 Dec 2009 17:23:20 +0200 > Ibrahim Harrani <[email protected]> wrote: > > > Hi Stevan, > > > > Unfortunately no, the error message is still exist. > > # tail -f /var/log/dspam/dspam.log > > 80322: [12/17/2009 15:27:32] Daemon process starting > > > > 80322: [12/17/2009 15:27:57] query error: %s: see sql.errors for more > > details > > 80322: [12/17/2009 15:27:57] query error: %s: see sql.errors for more > > details > > 80322: [12/17/2009 15:27:57] query error: %s: see sql.errors for more > > details > > 80322: [12/17/2009 15:27:57] query error: %s: see sql.errors for more > > details > > > Can you please try once without the various --debug options? They should > remove the additional logging of those SQL commands. > > > > It seems that logging mechanism is working well. > > 36569: [12/17/2009 17:19:08] Daemon terminating on signal %d > > > > It seems that macros in header files does not handled %s,%d values. > > > > language.h:#define ERR_DAEMON_TERMINATE "Daemon terminating on signal > %d" > > pgsql_drv.c: LOG (LOG_WARNING, "query error: %s: see sql.errors for more > > details", error); > > > > It may be better to rewrite logging mechanism? > > > > Thanks. > > > > > > > > > > On Thu, Dec 17, 2009 at 1:17 PM, Stevan Bajić <[email protected]> wrote: > > > > > On Thu, 17 Dec 2009 12:13:57 +0200 > > > Ibrahim Harrani <[email protected]> wrote: > > > > > > > Hi Stevan, > > > > > > > Hallo Ibrahim, > > > > > > > > > > I have an error in dspam.log file > > > > #tail /var/log/dspam/dspam.log > > > > 60222: [12/17/2009 11:48:36] query error: %s: see sql.errors for more > > > > details > > > > 60222: [12/17/2009 11:48:36] query error: %s: see sql.errors for more > > > > details > > > > 60222: [12/17/2009 11:48:36] query error: %s: see sql.errors for more > > > > details > > > > 60222: [12/17/2009 11:48:36] query error: %s: see sql.errors for more > > > > details > > > > > > > > But I don't see any error in sql.errors. I double checked the log > file. > > > > There is only verbose debug messages not errors like following > > > > > > > is the attached patch fixing that issue? > > > > > > -- > > > Kind Regards from Switzerland, > > > > > > Stevan Bajić > > > > > > > > > > ------------------------------------------------------------------------------ > > > This SF.Net email is sponsored by the Verizon Developer Community > > > Take advantage of Verizon's best-in-class app development support > > > A streamlined, 14 day to market process makes app distribution fast and > > > easy > > > Join now and get one step closer to millions of Verizon customers > > > http://p.sf.net/sfu/verizon-dev2dev > > > _______________________________________________ > > > Dspam-user mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/dspam-user > > > > > > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Dspam-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspam-user >
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Dspam-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspam-user
