Apparmor blocks Dovecot logging on Plesk server: Failed name lookup - disconnected path

Follow

Comments

7 comments

  • Avatar
    Sascha Henken

    This solution does not work. It keeps reporting these errors however customers can send and receive emails normally.

    1
    Comment actions Permalink
  • Avatar
    b_p

    I just upgraded from 17.5 to 17.8.11 and see this error appearing!

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Sascha,

    The bug described in this article was already fixed. The article will be updated with this info.

    I have created a ticket to investigate the issue you have.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    @b_p, as specified in the comment, it might be required to reboot the server.

    Have you tried it?

    0
    Comment actions Permalink
  • Avatar
    b_p (Edited )

    @Ivan: yes, the problem persists

    There is even more challenges regarding AppArmor:

    Apr 5 21:08:19 myserver kernel: [99113.418914] audit: type=1400 audit(1554491299.027:49118): apparmor="ALLOWED" operation="open" profile="/usr/lib/dovecot/auth" name="/var/spool/postfix/plesk/passwd.db" pid=8924 comm="auth" requested_mask="wc" denied_mask="wc" fsuid=0 ouid=112

    Apr 5 21:08:19 myserver kernel: [99113.421926] audit: type=1400 audit(1554491299.027:49119): apparmor="ALLOWED" operation="connect" profile="/usr/lib/dovecot/imap" name="/run/dovecot/stats-writer" pid=9685 comm="imap" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
    Apr 5 21:08:38 myserver kernel: [99133.005024] audit_printk_skb: 30 callbacks suppressed
    Apr 5 21:08:38 myserver kernel: [99133.005029] audit: type=1400 audit(1554491318.611:49130): apparmor="ALLOWED" operation="file_perm" profile="/usr/lib/dovecot/stats" name="/run/dovecot/stats-writer" pid=7098 comm="stats" requested_mask="w" denied_mask="w" fsuid=997 ouid=0

     

    Apr 5 23:33:08 myserver kernel: [ 7284.670764] audit: type=1400 audit(1554499988.692:3588): apparmor="ALLOWED" operation="file_perm" profile="/usr/lib/dovecot/stats" name="/run/dovecot/stats-writer" pid=2843 comm="stats" requested_mask="w" denied_mask="w" fsuid=997 ouid=0
    Apr 5 23:33:08 myserver kernel: [ 7284.670774] audit: type=1400 audit(1554499988.692:3589): apparmor="ALLOWED" operation="file_perm" profile="/usr/lib/dovecot/stats" name="/run/dovecot/stats-writer" pid=2843 comm="stats" requested_mask="w" denied_mask="w" fsuid=997 ouid=0
    Apr 5 23:33:08 myserver kernel: [ 7284.670919] audit: type=1400 audit(1554499988.696:3590): apparmor="ALLOWED" operation="file_perm" profile="/usr/lib/dovecot/stats" name="/run/dovecot/stats-writer" pid=2843 comm="stats" requested_mask="r" denied_mask="r" fsuid=997 ouid=0
    Apr 5 23:33:08 myserver kernel: [ 7284.670930] audit: type=1400 audit(1554499988.696:3591): apparmor="ALLOWED" operation="file_perm" profile="/usr/lib/dovecot/stats" name="/run/dovecot/stats-writer" pid=2843 comm="stats" requested_mask="r" denied_mask="r" fsuid=997 ouid=0
    Apr 5 23:33:08 myserver kernel: [ 7284.962796] audit: type=1400 audit(1554499988.988:3592): apparmor="ALLOWED" operation="open" profile="/usr/lib/dovecot/auth" name="/var/spool/postfix/plesk/passwd.db" pid=18684 comm="auth" requested_mask="wc" denied_mask="wc" fsuid=0 ouid=112
    Apr 5 23:33:08 myserver kernel: [ 7284.965611] audit: type=1400 audit(1554499988.988:3593): apparmor="ALLOWED" operation="connect" profile="/usr/lib/dovecot/imap" name="/run/dovecot/stats-writer" pid=20204 comm="imap" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0

    0
    Comment actions Permalink
  • Avatar
    Vladimir Chernikov

    Hello @b_p,

    As I can see, the provided log entries do not contain "info="Failed name lookup - disconnected path"" and should be normally processed because they are all in "ALLOWED" state.

    If you still see the log entries with "Failed name lookup - disconnected path" message please submit the ticket to Plesk Technical Support and we investigate it further:
    https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support-

    0
    Comment actions Permalink
  • Avatar
    Sascha Henken

    I had to reboot the machine before the changes took effect as the Apparmor Reload didn´t work. So the solution is good to go. However I wonder that the bug has already been fixed as you say since the server where it happend was running the latest Onyx 17.5. Build. Anyway. It seems to be fixed in 17.8. so i´m planning to upgrade Onyx in the upcoming days.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request