Haha, wow, that was silly -- that logging level cleared it right up. It was
complaning the URI had no password set.

THe password was indeed set... but it has the character '@' in it... and I
wasn't URL encoding it (equivalent is %40).

Soon as I URL encoded the password it connected and complained about the
2.2 DB structure (I had reverted it for 2.2).

Thanks much for the help.


On Fri, Sep 13, 2013 at 5:16 AM, Paul J Stevens <[email protected]> wrote:

> On 09/13/2013 01:55 PM, Vitaliy Mikitchenko wrote:
>
> > Program received signal SIGSEGV, Segmentation fault.
> > Connection_close (C=C@entry=0x0) at src/db/Connection.c:257
> > 257             ConnectionPool_returnConnection(C->parent, C);
> > (gdb) backtrace
> > #0  Connection_close (C=C@entry=0x0) at src/db/Connection.c:257
> > #1  0x00007ffff5cde3c6 in db_con_close (c=c@entry=0x0) at dm_db.c:283
> > #2  0x00007ffff5ce12f0 in db_connect () at dm_db.c:227
>
> dbmail can't obtain a database connection at startup.
>
> It shouldn't try to close such a NULL connection, but rather bail out
> with a warning.
>
> Try to run it with logging_level=511
>
> Are you using 'localhost'? If so, please be advised that mysql treats
> localhost connections as 'use the unix socket', rather than: use
> '127.0.0.1' network connections. Most likely the 'exim' user doesn't
> have access to that socket.
>
> If you are using localhost, try 127.0.0.1 instead.
>
>
> --
> ________________________________________________________________
> Paul J Stevens        pjstevns @ gmail, twitter, skype, linkedin
>
>   * Premium Hosting Services and Web Application Consultancy *
>
>            www.nfg.nl/[email protected]/+31.85.877.99.97
> ________________________________________________________________
> _______________________________________________
> DBmail mailing list
> [email protected]
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
>
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Reply via email to