Autor: Yves Goergen Datum: To: Dan Egli, exim-users Betreff: Re: [exim] Temporary internal error
Yes, /var/run does exist. That wasn't my issue. It was that Exim needs
the full file name of the socket (/var/run/postgresql/.s.PGSQL.5432),
not just the directory (/var/run/postgresql) as other programs.
But I noticed that /var/run is a link to /run. I might change my
configurations to use /run directly. Not sure if that's better.
-Yves
-------- Ursprüngliche Nachricht --------
Von: Dan Egli via Exim-users <exim-users@???>
Gesendet: Freitag, 18. September 2020, 04:16 MESZ
Betreff: [exim] Temporary internal error
On 9/17/2020 1:56 PM, Yves Goergen via Exim-users wrote:
Hm, this prints more details, among others:
PGSQL new connection: socket=/var/run/postgresql database=) user=dfctl
lookup deferred: PGSQL invalid filename for socket: /var/run/postgresql
I'm not sure what's exactly invalid here. But it's not what I
configured either. This is the relevant config:
I can tell you at least one problem right off. Ubuntu 20.04 doesn't use
/var/run but /run. In fact, there IS NO /var/run directory! I had to
deal with the same thing for another program. I wound up just making a
symlink of /run in /var/run (i.e. ln -s /run /var/run) and that solved
the issue. But you don't have to do that. Since your config shows
/var/run/postgresql then change it to /run/postgresql and see if that
doesn't help.