As it turned out, the problem was with 1-2-3 Systems' VPS service.
Through this mailing list I found another person who was having the
exact same problem with me with qmgr being killed constantly, who also
happened to be hosted on the same physical box as me at 1-2-3 Systems.
Since we were t
Le 20/12/2010 20:22, Jeff Morris a écrit :
[snip]
Interestingly, I also received one other off-list response to my email
from someone else who is experiencing the exact smae problem. Despite
*hours* of Googling, he is the only other person I've managed to come
across with this same issue, and he
On 12/18/2010 11:03 PM, Victor Duchovni wrote:
postfix/master[20377]: warning: process /usr/libexec/postfix/qmgr pid 20380
killed by signal 15
This is SIGTERM. Are you running "postfix stop" frequently?
No. In fact I'm not running it at all. In fact in the interest of
troubleshooting this,
Jeff Morris:
>
> I have a CentOS 5.5 x86 server running on an OpenVZ VPS at 123systems.net.
>
> I have postfix installed on this server and configured as a secondary MX.
>
> I am frequently getting the following warning logged to maillog:
>
> postfix/master[20377]: warning: process /usr/libexec
On Sat, Dec 18, 2010 at 06:17:08PM -0600, Jeff Morris wrote:
> postfix/master[20377]: warning: process /usr/libexec/postfix/qmgr pid 20380
> killed by signal 15
This is SIGTERM. Are you running "postfix stop" frequently?
> I've done some troubleshooting and can't figure out why qmgr is being
>
I have a CentOS 5.5 x86 server running on an OpenVZ VPS at 123systems.net.
I have postfix installed on this server and configured as a secondary MX.
I am frequently getting the following warning logged to maillog:
postfix/master[20377]: warning: process /usr/libexec/postfix/qmgr pid
20380 kil
