Hi,
Apologies for the weird *'s in the previous post, some stray formatting.....
Making slow progress - have now got rid of the "invalid argument" error,
and opendkim "appears" to be happy with the command strings, but it won't
start up, fails very rapidly (inside 1 second) of starting.
The string that appears to be acceptable is:
dsn:pgsql://<username>:<password>_at_5432+hostname/dbname/key=val?......
There is nothing in any logs from PGSQL or maillog, and the journal gives
the following line:
opendkim.service: control process exited, code exited status = 78
The service starts up and run fine if I use files, rather than database
sets, so there is no fundamental problem with the install - but the
database interface is not playing.
The Fedora package opendbx-postgresql has been installed, cannot find any
other dependencies that might be missing.
Any ideas??
On 20 July 2015 at 16:20, Garth Rees <garthrees1960_at_gmail.com> wrote:
> Hi,
>
> Having just ventured into the world of DKIM, I am a total newb on this
> area......
>
> I am attempting to use Unix socket to connect to my PGASQL database for
> lookup of the DKIM datasets.
>
> Am not able to get OpenDKIM to start, as it constantly returns the
> following error in the journal.
>
> - dsn:pgsql//username:password_at_............ datacol=xxxxx*
> dkmif_db-open(): invalid argument*
>
> It would appear that it is related to the connection to PGSQL socket,
> which "SHOULD" be* /var/run/postgresql/.s.PGSQL.5432*
>
> Having read the documentation on the use of ODBX backends for the
> datasets, I know I cannot use the "/" in the string as it is reserved. I
> have tried quotation marks to "contain" the whole address, but nothing has
> worked thus far, and nothing has come up in my searching.
>
>
> Can anyone tell me HOW the port & host should be written to get a
> connection to unix-socket at /var/run/postgresql/.s.PGSQL.5432 ?
>
>
> Cheers,
>
> GM
>
Received on Mon Jul 20 2015 - 21:27:22 PST