Hello,

Trying to solve another problem, I inadvertently broke my dspam installation
on my FreeBSD server. The daemon is now crashing when postfix tries to pipe
a message to it.

Past on past experience, I suspect it is a permissions problem with the
/var/db/dspam/data dirs, but as far as I can see everything is configured
properly.

How do I determine what is going wrong?

I have recompiled dspam with debugging enabled, set debugging on in
/etc/rc.conf, and it is now outputting the log dir:

$ ls -lrt /var/log/dspam
total 624
-rw-rw----  1 root  mail   12550 Apr 26 13:28 dspam.debug
-rw-rw----  1 root  mail  561494 Apr 26 13:33 dspam.messages

But the debug log doesn't tell me why dspam is failing.

I try starting it non-daemonized this way with the hope of some feedback in
the terminal: 

# dspam --debug &

but it won't start. Starting the normal way under FreeBSD works.

I'm looking for a nice clear error message from dspam about why it is
failing, and I am sure it is producing one... but where?

Running v3.9.0.

Thanks



--
View this message in context: 
http://dspam-users.2290790.n4.nabble.com/debugging-dspam-tp4641287.html
Sent from the dspam users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Dspam-user mailing list
Dspam-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-user

Reply via email to