Resolved Problem Error Postfix Centos 7.3

[bonny3]

Hi,
I have a problem in Postfix Centos 7.3,
When I launch the postfix restart..
This error comes out:

[root@occ~]# /sbin/service postfix restart
Redirecting to /bin/systemctl restart postfix.service
Job for postfix.service failed because the control process exited with error code. See "systemctl status postfix.service" and "journalctl -xe" for details.

How can I fix the problem?

Thanks

status postfix:
[root@occ ~]# systemctl status postfix.service
● postfix.service - Postfix Mail Transport Agent
Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor pres et: disabled)
Active: failed (Result: exit-code) since Wed 2017-05-31 13:45:46 CEST; 20min ago
Process: 17104 ExecStart=/usr/sbin/postfix start (code=exited, status=1/FAILUR E)
Process: 17101 ExecStartPre=/usr/libexec/postfix/chroot-update (code=exited, s tatus=0/SUCCESS)
Process: 17098 ExecStartPre=/usr/libexec/postfix/aliasesdb (code=exited, statu s=0/SUCCESS)
Main PID: 26883 (code=killed, signal=TERM)

May 31 13:45:44 occ systemd[1]: Starting Postfix Mail Transport A....
May 31 13:45:44 occ postfix/postfix-script[17168]: warning: not se...
May 31 13:45:44 occ postfix/postfix-script[17175]: starting the Po...
May 31 13:45:44 occ postfix/master[17177]: fatal: open lock file /...
May 31 13:45:45 occ postfix/master[17176]: fatal: daemon initializ...
May 31 13:45:46 occ postfix/postfix-script[17178]: fatal: mail sys...
May 31 13:45:46 occ systemd[1]: postfix.service: control process ...1
May 31 13:45:46 occ systemd[1]: Failed to start Postfix Mail Tran....
May 31 13:45:46 occ systemd[1]: Unit postfix.service entered fail....
May 31 13:45:46 occ systemd[1]: postfix.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

 

[eilko]

although you only provide a small part of the error messages, it looks like Postfix unable to start with error: open lock file /var/lib/postfix/master.lock: unable to set exclusive lock can help you

 

[bonny3]

although you only provide a small part of the error messages, it looks like Postfix unable to start with error: open lock file /var/lib/postfix/master.lock: unable to set exclusive lock can help you

Hi Eilko,
thanks for your reply,
I have this result when I launch the command "ps aux | grep postfix"
but don't work comand "kill -9 PID"

[root@occ ~]# ps aux | grep postfix
postfix 18739 0.0 0.0 398592 2696 ? Ssl May03 0:48 /usr/lib64/plesk-9.0/psa-pc-remote -p inet:[email protected] -t 7210 -P /run/psa-pc-remote.pid -u postfix -g popuser -n
postfix 19115 0.0 0.0 89140 3892 ? S 14:42 0:00 pickup -l -t fifo -u
postfix 21747 0.0 0.0 122412 7100 ? S 16:20 0:00 smtpd -n smtp -t inet -u -o stress= -s 2
postfix 21748 0.0 0.0 89116 3880 ? S 16:20 0:00 proxymap -t unix -u
postfix 21749 0.0 0.0 89132 3888 ? S 16:20 0:00 anvil -l -t unix -u
postfix 21750 0.0 0.0 89276 4396 ? S 16:20 0:00 trivial-rewrite -n rewrite -t unix -u
postfix 21752 0.0 0.0 89512 4784 ? S 16:20 0:00 cleanup -z -t unix -u
root 21780 0.0 0.0 112648 960 pts/1 S+ 16:21 0:00 grep --color=auto postfix
root 27000 0.0 0.0 89036 2148 ? Ss May23 0:58 /usr/libexec/postfix/master -w
postfix 27046 0.0 0.0 89320 3972 ? S May23 0:52 qmgr -l -t fifo -u
postfix 27215 0.0 0.0 89152 3984 ? S May23 0:00 tlsmgr -l -t unix -u
[root@occ~]# kill -9 PID
-bash: kill: PID: arguments must be process or job IDs

what am I doing wrong?

Thanks

 

[eilko]

you have to replace PID with the number of the process identifier (See Process identifier - Wikipedia).
in the example above: kill -9 18739

 

[bonny3]

you have to replace PID with the number of the process identifier (See Process identifier - Wikipedia).
in the example above: kill -9 18739

Ok,
I solved!
I managed to unlock the problem and now it works
The problem was in this line
root 27000 0.0 0.0 89036 2148 ? Ss May23 0:58 /usr/libexec/postfix/master -w
kill -9 27000

thank you very much!