Re: [Dbmail-dev] Can't run dbmail revision 1940

2005-12-16 Thread Paul J Stevens
Add:

TRACE_SYSLOG=1
TRACE_STDERR=0

to your dbmail.conf as documented in the example config.

This one had me stumped as well last week :-(




Oleg Lapshin wrote:
 Hello.
 I compiled dbmail rev 1940.
 Run dbmail-imapd and  no messages at all.(TRACE_LEVEL=5)
 no forking, no work.
 
 I attach output from strace dbmail-imapd -n -v command
 (only dbmail-imapd -V and dbmail-imapd -h give me output)
 
 

-- 
  
  Paul Stevens  paul at nfg.nl
  NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
  The Netherlandshttp://www.nfg.nl


Re: [Dbmail-dev] Can't run dbmail revision 1940

2005-12-16 Thread Aaron Stone
On Fri, 2005-12-16 at 14:05 +0300, Oleg Lapshin wrote:
 В сообщении от 16 декабря 2005 13:44 Paul J Stevens написал(a):
  Add:
 
  TRACE_SYSLOG=1
  TRACE_STDERR=0
 
  to your dbmail.conf as documented in the example config.
 
  This one had me stumped as well last week :-(
 
 Sorry ;)
 
 Output:
 Dec 16 13:48:23 bagira dbmail/imap4d[3862]: dbmysql.c,db_connect: 
 mysql_real_connect failed: Unknown MySQL server
 host 'localhost   # host for database, set to localhost if 
 database is om ' (3)
 
 I had in config:
 host=localhost   # host for database, set to localhost if database is om
  # the same host as dbmail and you want to use a local socket
  # for connecting.
 
 and when I change to:
 host=localhost
  # host for database, set to localhost if database is om
  # the same host as dbmail and you want to use a local socket
  # for connecting.
 
 (add newline after localhost)
 dbmail-imapd is runing
 
 So, are there errors in parsing config file?
 or comments _must_ begin with newline?

The problem was that you didn't have the two config items TRACE_SYSLOG
and TRACE_STDERR. I thoughlessly made those mandatory with a stupid
fatal error message.

Aaron



Re: [Dbmail-dev] Can't run dbmail revision 1940

2005-12-16 Thread Oleg Lapshin
 The problem was that you didn't have the two config items TRACE_SYSLOG
 and TRACE_STDERR. I thoughlessly made those mandatory with a stupid
 fatal error message.

NO!

When I try to run dbmail-imapd with this in config:

TRACE_LEVEL=5
TRACE_SYSLOG=1
TRACE_STDERR=0
host=localhost  # host for database, set to localhost if database is om

dbmail-imapd don't run!
but when I change to

host=localhost
  # host for database, set to localhost if database is om

(newline after localhost) dbmail-imapd run.

-- 
Oleg Lapshin



Re: [Dbmail-dev] Can't run dbmail revision 1940

2005-12-16 Thread Paul J Stevens
There're not fatal. But when they are missing there's no logging at all!
Which effectively hides the cause of any fatal errors :-)

Aaron Stone wrote:
 That's dumb, why are those TRACE_FATAL when not found? I just copied it
 twice more to the new options; I don't think any failure to find the
 TRACE_* config options should be FATAL, just result in sane defaults.
 
 I'll make it part of my trace-fixing project to fix that!
 
 Aaron
 
 On Fri, 2005-12-16 at 11:44 +0100, Paul J Stevens wrote:
 
Add:

TRACE_SYSLOG=1
TRACE_STDERR=0

to your dbmail.conf as documented in the example config.

This one had me stumped as well last week :-(




Oleg Lapshin wrote:

Hello.
I compiled dbmail rev 1940.
Run dbmail-imapd and  no messages at all.(TRACE_LEVEL=5)
no forking, no work.

I attach output from strace dbmail-imapd -n -v command
(only dbmail-imapd -V and dbmail-imapd -h give me output)



 
 ___
 Dbmail-dev mailing list
 Dbmail-dev@dbmail.org
 http://twister.fastxs.net/mailman/listinfo/dbmail-dev
 

-- 
  
  Paul Stevens  paul at nfg.nl
  NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
  The Netherlandshttp://www.nfg.nl