On 5/05/20 5:04 pm, natan maciej milaszewski wrote:
Hi
I have a centos 7 and postfix3-3.4.7-1.gf.el7.x86_64
I reload postfix via:
postfix reload
May 5 06:00:52 smtp1 postfix/master[22162]: reload -- version 3.4.7,
configuration /etc/postfix
And new mail was only added to queue active
They did not want to leave and the queue was growing
May 5 06:00:52 smtp1 postfix/qmgr[6439]: 49GQwf3mj4z4D6T:
from=<powiadomie...@domain.ltd>, size=80199, nrcpt=2 (queue active)
May 5 06:00:52 smtp1 postfix/qmgr[6439]: 49GQx260b4z4D8d:
from=<user@....>, size=835317, nrcpt=1 (queue active)
May 5 06:00:52 smtp1 postfix/qmgr[6439]: 49GQwh3Cxjz4D7f:
from=<powiadomienia@.......>, size=80307, nrcpt=2 (queue active)
May 5 06:00:52 smtp1 postfix/qmgr[6439]: 49GQxP2LwLz4D9N:
from=<user1@.....>, size=27942, nrcpt=1 (queue active)
May 5 06:00:52 smtp1 postfix/qmgr[6439]: 49GQwf6SQPz4D6d:
from=<powiadomienia@.....>, size=80210, nrcpt=2 (queue active)
Problem was fixed after restart postfix
I tested reload ~4 times and the problem happened again
For second test i relod postfix via systemd (service postfix reload) -
works fine
I do find this strange because all that systemd does on reload is call
this command:
/usr/sbin/postfix reload
...which is basically the same command that you're running. Try
explicitly running /usr/sbin/postfix reload, though, just in case
there's another script getting in the way for you, or an alias or
function. It might also pay to look into your environment, certain
environment variables and settings will differ between the environment
that systemd has when it issues the reload and the one in your shell.
You can also try:
bash --noprofile --norc -c '/usr/sbin/postfix reload'
Can you check to make sure you're root when you issue postfix reload?
try temporarily turning off selinux with:
setenforce 0
...don't forget to turn it back on:
setenforce 1
...double check /var/log/maillog in the latest version of postfix, make
sure to record any log entries that show up at the exact time you run
"postfix reload". There should at least be some log entry that shows
postfix reloading:
May 6 20:23:04 CentOS7 postfix/postfix-script[1789]: refreshing the
Postfix mail system
May 6 20:23:04 CentOS7 postfix/master[1618]: reload -- version 3.5.0,
configuration /etc/postfix
Compare your output to what you get with service postfix reload and see
if there's any difference.
You may also be able to see the logs with:
service postfix status
Is the problem still in the latest version of postfix if you enable the
gf-testing repo and update?
yum --enablerepo=gf-testing update postfix3\*
Also double check that the postfix install itself has not been corrupted:
rpm -V postfix3
...if you get no output, or only output that reflects changes to config
files, then the install is fine.
Wietse already pointed you at the DEBUG_README. In addition to the
section that he pointed you to, have a look through the rest to see what
you can do. Specifically the sections titled "Manually tracing a
Postfix daemon process" and below that. Do the traces with both reload
commands and compare the output between them.
Let me know what you find so I can fix the packages from Ghettoforge in
case it has something to do with the package builds. Also if all of the
above doesn't reveal the issue I can provide you with RPMs that don't
have the usual set of CentOS patches applied for you to try, then we can
troubleshoot from there.
Good luck and let me know how you get on.
Peter
