Strange errors in mail.warn log

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Strange errors in mail.warn log

Mario
How to avoid getting strange records in the mail.warn file?
I started to receive it after Debian upgrade from jessie to stretch and
postfix upgrade from 2.11.3 to 3.1.8.
It is generated once, just after the system reboot.

Despite the strange errors recorded in mail.warn file, it seems that postfix
works fine.

My current environment is the following:
Debian 9 stretch
Postfix 3.1.8
Dovecot 2.2.27 (c0f36b0)
10.1.23-MariaDB-9+deb9u1

errors in  mail.warn:
Mar 18 17:21:25 jessie postfix/proxymap[873]: warning: connect to mysql
server localhost: Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2 "No such file or directory")
Mar 18 17:21:25 jessie postfix/cleanup[869]: warning:
proxy:mysql:/etc/postfix/virtual_alias_maps.cf lookup error for
"[hidden email]"
Mar 18 17:21:25 jessie postfix/cleanup[869]: warning: 3A36445441:
virtual_alias_maps map lookup problem for [hidden email] -- message
not accepted, try again later
Mar 18 17:21:27 jessie postfix/cleanup[869]: warning:
proxy:mysql:/etc/postfix/virtual_alias_maps.cf lookup error for
"[hidden email]"
Mar 18 17:21:27 jessie postfix/cleanup[869]: warning: 4E5B845444:
virtual_alias_maps map lookup problem for [hidden email] -- message
not accepted, try again later
Mar 18 17:21:27 jessie postfix/cleanup[869]: warning:
proxy:mysql:/etc/postfix/virtual_alias_maps.cf lookup error for
"[hidden email]"
Mar 18 17:21:27 jessie postfix/cleanup[869]: warning: 4EF9E45444:
virtual_alias_maps map lookup problem for [hidden email] -- message
not accepted, try again later
Mar 18 17:22:24 jessie postfix/cleanup[869]: warning:
proxy:mysql:/etc/postfix/virtual_alias_maps.cf lookup error for
"[hidden email]"
Mar 18 17:22:24 jessie postfix/cleanup[869]: warning: 5D9C63FABD:
virtual_alias_maps map lookup problem for [hidden email] -- message
not accepted, try again later
Mar 18 17:22:24 jessie postfix/cleanup[869]: warning:
proxy:mysql:/etc/postfix/virtual_alias_maps.cf lookup error for
"[hidden email]"
Mar 18 17:22:24 jessie postfix/cleanup[869]: warning: 5E7733FABD:
virtual_alias_maps map lookup problem for [hidden email] -- message
not accepted, try again later




--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
Reply | Threaded
Open this post in threaded view
|

Re: Strange errors in mail.warn log

Wilfried.Essig@Essignetz.de
Look here:
> Mar 18 17:21:25 jessie postfix/proxymap[873]: warning: connect to mysql
> server localhost: Can't connect to local MySQL server through socket
> '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")


Willi
Reply | Threaded
Open this post in threaded view
|

Re: Strange errors in mail.warn log

John Fawcett
In reply to this post by Mario
On 18/03/18 19:12, Mario wrote:

> How to avoid getting strange records in the mail.warn file?
> I started to receive it after Debian upgrade from jessie to stretch and
> postfix upgrade from 2.11.3 to 3.1.8.
> It is generated once, just after the system reboot.
>
> Despite the strange errors recorded in mail.warn file, it seems that postfix
> works fine.
>
> My current environment is the following:
> Debian 9 stretch
> Postfix 3.1.8
> Dovecot 2.2.27 (c0f36b0)
> 10.1.23-MariaDB-9+deb9u1
>
> errors in  mail.warn:
> Mar 18 17:21:25 jessie postfix/proxymap[873]: warning: connect to mysql
> server localhost: Can't connect to local MySQL server through socket
> '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")
> Mar 18 17:21:25 jessie postfix/cleanup[869]: warning:
> proxy:mysql:/etc/postfix/virtual_alias_maps.cf lookup error for
> "[hidden email]"
> Mar 18 17:21:25 jessie postfix/cleanup[869]: warning: 3A36445441:
> virtual_alias_maps map lookup problem for [hidden email] -- message
> not accepted, try again later
> Mar 18 17:21:27 jessie postfix/cleanup[869]: warning:
> proxy:mysql:/etc/postfix/virtual_alias_maps.cf lookup error for
> "[hidden email]"
> Mar 18 17:21:27 jessie postfix/cleanup[869]: warning: 4E5B845444:
> virtual_alias_maps map lookup problem for [hidden email] -- message
> not accepted, try again later
> Mar 18 17:21:27 jessie postfix/cleanup[869]: warning:
> proxy:mysql:/etc/postfix/virtual_alias_maps.cf lookup error for
> "[hidden email]"
> Mar 18 17:21:27 jessie postfix/cleanup[869]: warning: 4EF9E45444:
> virtual_alias_maps map lookup problem for [hidden email] -- message
> not accepted, try again later
> Mar 18 17:22:24 jessie postfix/cleanup[869]: warning:
> proxy:mysql:/etc/postfix/virtual_alias_maps.cf lookup error for
> "[hidden email]"
> Mar 18 17:22:24 jessie postfix/cleanup[869]: warning: 5D9C63FABD:
> virtual_alias_maps map lookup problem for [hidden email] -- message
> not accepted, try again later
> Mar 18 17:22:24 jessie postfix/cleanup[869]: warning:
> proxy:mysql:/etc/postfix/virtual_alias_maps.cf lookup error for
> "[hidden email]"
> Mar 18 17:22:24 jessie postfix/cleanup[869]: warning: 5E7733FABD:
> virtual_alias_maps map lookup problem for [hidden email] -- message
> not accepted, try again later
>
>
>
>
> --
> Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html

If it happens only once and after that everything seems to be working
then you can probably just forget about it.

As this is happening only at boot, it looks like postfix starts
connecting to mariadb before before mariadb is ready to accept connections.

There could be some missing dependency in the startup scripts or it
could be a dependency which the startup scripts cannot correctly manage
(for example if maridb starts successfully but then there is a non zero
time before when it starts and when it accepts connections).

John

Reply | Threaded
Open this post in threaded view
|

Re: Strange errors in mail.warn log

Ralf Hildebrandt-2
In reply to this post by Mario
* Mario <[hidden email]>:

> Mar 18 17:21:25 jessie postfix/proxymap[873]: warning: connect to mysql
> server localhost: Can't connect to local MySQL server through socket
> '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")

a) is the mysql server running?
b) does /var/run/mysqld/mysqld.sock exist?
c) if b) = yes, is your proxymap servince running chrooted? (check master.cf, column "chroot")

--
[*] sys4 AG

https://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG, 80333 München
                                           
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein