1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Issue Random emails deferred - Command died with signal 11: "/usr/lib64/plesk-9.0/postfix-local"

Discussion in 'Plesk 12.x for Linux' started by Soulve SysAdmin, Jul 18, 2016.

  1. Soulve SysAdmin

    Soulve SysAdmin New Pleskian

    0
    20%
    Joined:
    Jul 18, 2016
    Messages:
    4
    Likes Received:
    0
    I searched the internet for days and examined the server even more days, but I can't get a cause and therefore a resolution for this problem. It's not mentioned in any Google search results, only in just a handfull as seperate parts (signal 11 which is some kind of segmentation fault or memory problem, or Command died with signal xxx: "/usr/lib64/plesk-9.0/postfix-local" where xxxx is not 11) that do not seem to be related in any way to my problem.

    Random email get stuck on the server, internal->external, external->internal, internally forwarded, forwarded to external, etc... Both the Plesk maillog and postfix queue manager state the same error:
    Command died with signal 11: "/usr/lib64/plesk-9.0/postfix-local"
    And that's the dead end after my trace through the mail delivery processes.

    The problem seems to be there for a while, if I recall after a microupdate that got stuck and which I repaired using the reapplication tool of updates (which can restart microupdates where it got stuck or interrupted). After that problem got solved I had to resolve some sideeffects, of which the most annoying was the repair of (dirs of) pid files that where deleted from several common processes like httpd, mysqld, etc. Updates after this problematic one have been applied without any problems or error notices, so I considered the server healthy for a while, until I discoverd this problem.

    I tried some common reconfiguration tools, like mchk, reinstallation of the microupdates etc, but without positive results. I don't know what the signal 11 stands for in this context or what I can do to test/force emails straight through /usr/lib64/plesk-9.0/postfix-local to do some more debugging (I don't know the commandline options and running it without them on the command line returns "4.3.5 Local delivery is disabled due to server misconfigurations").

    Here's some details about the problem:

    - Server info (virtual server on an enterprise grade kvm platform of my provider)
    CentOS Linux 7.2.1511 (Core), Plesk version 12.5.30 Update #40, last updated at July 13, 2016 03:08 AM

    - maillog (I replaced the local configured domain with example.org)
    Jul 18 11:42:05 server-01 postfix/qmgr[4024]: 4D35CA91909: from=<do_not_reply@email.apple.com>, size=69544, nrcpt=1 (queue active)
    Jul 18 11:42:05 server-01 postfix/pipe[27722]: input attribute value: 4D35CA91909
    Jul 18 11:42:05 server-01 postfix/pipe[27722]: deliver_request_get: file active/4D35CA91909
    Jul 18 11:42:06 server-01 postfix/pipe[27722]: send attr queue_id = 4D35CA91909
    Jul 18 11:42:06 server-01 postfix/pipe[27722]: 4D35CA91909: to=<john.doe@example.org>, relay=plesk_virtual, delay=239842, delays=239842/0.04/0/0.08, dsn=4.3.0, status=deferred (Command died with signal 11: "/usr/lib64/plesk-9.0/postfix-local")
    Jul 18 11:42:06 server-01 postfix/pipe[27722]: flush_add: site example.org id 4D35CA91909
    Jul 18 11:42:06 server-01 postfix/pipe[27722]: flush_add: site example.org id 4D35CA91909 status 4

    - postqueue -p
    4D35CA91909 69544 Fri Jul 15 17:04:44 do_not_reply@email.apple.com
    (Command died with signal 11: "/usr/lib64/plesk-9.0/postfix-local")
    john.doe@example.org
     
  2. Soulve SysAdmin

    Soulve SysAdmin New Pleskian

    0
    20%
    Joined:
    Jul 18, 2016
    Messages:
    4
    Likes Received:
    0
  3. Soulve SysAdmin

    Soulve SysAdmin New Pleskian

    0
    20%
    Joined:
    Jul 18, 2016
    Messages:
    4
    Likes Received:
    0
    *bump* again!

    nice support in this forum... NOT!
     
  4. Lloyd_mcse

    Lloyd_mcse Silver Pleskian Plesk Guru

    29
    90%
    Joined:
    Dec 13, 2013
    Messages:
    646
    Likes Received:
    110
    Location:
    Sudbury, Suffolk
    Have you tried switching MTA's? Switch to Qmail and back to Postfix?

    Code:
    # /usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --install-component qmail
    and..

    Code:
    # /usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --install-component postfix
    It won't affect mailboxes.
    Hope it helps
    Kind regards

    Lloyd
     
  5. Soulve SysAdmin

    Soulve SysAdmin New Pleskian

    0
    20%
    Joined:
    Jul 18, 2016
    Messages:
    4
    Likes Received:
    0
    yes i did, no effect.
     
  6. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,572
    Likes Received:
    1,243
    Location:
    Novosibirsk, Russia
    Maybe it is caused by kernel OOM killer due to lack of VPS resources? Have you checked it?
     
  7. Romanov

    Romanov New Pleskian

    2
     
    Joined:
    Mar 24, 2017
    Messages:
    1
    Likes Received:
    0
    Location:
    Holland
    I'm experiencing the same problem, has anyone found a solution for this?

    Mar 24 14:40:56 *modded* postfix/pipe[352]: 8EEE99B34B5: to=<info@*moded*.nl>, relay=plesk_virtual, delay=7278, delays=7277/0/0/0.94, dsn=4.3.0, status=deferred (Command died with signal 11: "/usr/lib64/plesk-9.0/postfix-local")
     
  8. UFHH01

    UFHH01 Plesk addicted!

    44
    64%
    Joined:
    Jun 11, 2013
    Messages:
    6,762
    Likes Received:
    1,712
    Location:
    Hamburg / Germany
    Hi Romanov,

    could you pls. compair your error, with possible corresponding errors/issues at "/var/log/messages" or/and "/var/log/kern.log" ( around the very same timestamp from your mail.log ! )

    Could you pls. add some more informations about your system environment and the operating system, the used postfix version and your current Plesk version ( incl. #MU ) ?
     
Loading...