Postfix Problems

  • Lately I am finding that Postfix dies and can not flush its mail queue. I have to restart the service to get mail delivered out of the system. This happens several times a day.


    The system mail log is flooded with all sorts of warnings and fatals that I have never seen before, a small sample of which I include below:


    Anyone else having problems or able to offer any insight?


    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    • Official Post

    Are you running the flashmemory plugin? Wonder if file(s) are missing or have the wrong permissions in /var/spool/postfix.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Geeze that is pretty weird, I would be interested in seeing why. I have postfix/dovecot running 2 systems over a year now have not had that particular issue.

    I have had postfix running on OMV for over eight years and not had this problem.......until now.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

  • Are you running the flashmemory plugin? Wonder if file(s) are missing or have the wrong permissions in /var/spool/postfix.

    I am running the flashmemory plugin. I have had a consistent set of warnings for many years about these things but just ignored them as they didn't break things:


    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    • Official Post

    I cheated and asked chatgpt for permissions fixes. I didn't test but this seems helpful:


    cp -a /etc/{hosts,localtime,nsswitch.conf,resolv.conf,services} /var/spool/postfix/etc/

    cp -a /lib/x86_64-linux-gnu/{libgcc_s.so.1,libnss_mdns.so.2,libnss_mdns4.so.2,...} /var/spool/postfix/lib/x86_64-linux-gnu/

    chmod go-w /etc/postfix/main-local-delivery.cf /etc/postfix/sasl_passwd.copy

    cp -a /etc/ssl/certs/{GlobalSign_ECC_Root_CA_-_R4.pem,ssl-cert-snakeoil.pem} /var/spool/postfix/etc/ssl/certs/

    chown root:root /var/spool/postfix/etc/*

    chown root:root /var/spool/postfix/lib/x86_64-linux-gnu/*

    chmod 644 /var/spool/postfix/etc/*

    chmod 644 /var/spool/postfix/lib/x86_64-linux-gnu/*

    systemctl restart postfix


    I would also do a sudo folder2ram -syncall if this fixes it.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • This line has an incomplete file list (...) so I used just what was complete. I'll let you know how it turns out.


    Code
    cp -a /lib/x86_64-linux-gnu/{libgcc_s.so.1,libnss_mdns.so.2,libnss_mdns4.so.2,...} /var/spool/postfix/lib/x86_64-linux-gnu/

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    • Official Post

    I missed that. Kind of weird. I would guess you might see logs complaining about other files that might need to be copied if those three aren't enough.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I managed to figure out which files were missing from that command ... and included them. This seems to have solved the problems in post #5. We'll see if it stays up.


    Thanks

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

  • Well, the reports in the log about file differences have disappeared. But problems of breaking Postfix continued.


    I looked really hard at this and discovered that uninstalling the Flash Memory plugin solves it and reinstalling the plugin reliably and immediately breaks it again. Also affected is the rsyslog service which seems to also break.


    I am pretty sure that the Flash Memory plugin has undergone some changes recently and perhaps it's just coincidental that the observed breakage here started in the same timeframe, or perhaps not.


    In the meantime since my OMV system disk is now an SSD I can do without the plugin for now.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    • Official Post

    looked really hard at this and discovered that uninstalling the Flash Memory plugin solves it and reinstalling the plugin reliably and immediately breaks it again. Also affected is the rsyslog service which seems to also break.


    I am pretty sure that the Flash Memory plugin has undergone some changes recently and perhaps it's just coincidental that the observed breakage here started in the same timeframe, or perhaps not.

    I have the flashmemory installed on three production systems that are sending emails and haven't had any issues. The change just forces a logrotate and journalctl rotate. Not sure how that would break anything.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I dunno. I've had the plugin running for years without problems until recently.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    • Official Post

    What is the output of the following?

    logrotate --force /etc/logrotate.conf

    echo $?

    journalctl --rotate

    echo $?

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • There are some custom logs that are generating errors below but I have never had any problems with them. At this time the Flash Memory plugin is not installed.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    • Official Post

    There are some custom logs that are generating errors below but I have never had any problems with them. At this time the Flash Memory plugin is not installed.

    Those errors have likely always been there but nothing ever looked at them. I think if they were fixed, the folder2ram calls would be fine. Neither of these two calls are specific to the flashmemory plugin or even folder2ram.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Thanks, I'll see what I can do with them.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

  • Did you manage to fix it? i have the same issue.

    Yes, but I had to uninstall the Flashmemory plugin to solve it. That also badly interacts with the rsyslog service when the logs are rotated.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    Edited once, last by gderf ().

    • Official Post

    That also badly interacts with the rsyslog service when the logs are rotated.

    That is because you have some bad logrotate configs. One that still references and init script.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • That is because you have some bad logrotate configs. One that still references and init script.

    I got rid of those logrotates that I setup, but something still gives trouble when I manually force logrotation:


    Code
    /sbin/invoke-rc.d: 538: /etc/init.d/rsyslog: not found
    invoke-rc.d: initscript rsyslog, action "rotate" failed.
    error: error running non-shared postrotate script for /var/log/syslog of '/var/log/syslog '

    But the logs do seem to be rotating all the same and also when scheduled normally.


    However, with the Flash Memory plugin installed the rsyslog service does not restart which breaks my swatchdog setup.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!