1 Topic by cvcvelo (edited by cvcvelo 2020-07-03 04:29:07)

  • cvcvelo
  • Member
  • Offline
  • Registered: 2014-06-16
  • Posts: 151

Topic: iredapd failures after upgrade

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.3
- Deployed with iRedMail Easy or the downloadable installer? downloadable
- Linux/BSD distribution name and version: Debian 10.4
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MariaDB
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

After upgrading to iRedMail 1.3 and iRedAPD 4.1, there are log errors like this one, causing deferred message delivery:

Jul  2 13:16:59 mail9 postfix/smtpd[23542]: warning: problem talking to server 127.0.0.1:7777: Success
Jul  2 13:16:59 mail9 postfix/smtpd[23542]: 49yTs64ffMzxQ1m: reject: END-OF-MESSAGE from 66-220-155-152.mail-mail.facebook.com[66.220.155.152]: 451 4.3.5 <END-OF-MESSAGE>: End-of-data rejected: Server configuration problem; from=<notification@facebookmail.com> to=<recipient@example.org> proto=ESMTP helo=<66-220-155-152.mail-mail.facebook.com>

'systemctl status iredapd' shows iRedAPD is running* and 'netstat -an | grep 7777' shows the server is listening on that port. The status command also shows errors like this:

Jul 02 13:16:58 mail9 python3[20222]: error: uncaptured python exception, closing channel <libs.channel.Policy connected 127.0.0.1:41812 at 0x7fe44fe03940> (<class 'KeyError'>:'59f8.5efe3dfd.13e86.0' [/usr/lib/python3.7/asyncore.py|readwrite|108] [/usr/l
Jul 02 13:16:58 mail9 python3[20222]: error: uncaptured python exception, closing channel <libs.channel.Policy connected 127.0.0.1:41832 at 0x7fe45035e668> (<class 'KeyError'>:'59f8.5efe3dfd.13e86.0' [/usr/lib/python3.7/asyncore.py|readwrite|108] [/usr/l

Restarting the iRedAPD service helps, I think, but after a little while these kind of errors reappear.

Thanks in advance for a fix and/or troubleshooting clues.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by slm858uk

  • slm858uk
  • Member
  • Offline
  • Registered: 2016-01-29
  • Posts: 8

Re: iredapd failures after upgrade

I'm by no means an expert and you might want to wait for someone who is but i recently upgraded my iRedMail and this sounded familiar as i made a change for this. As you are on already on v1.3 it should already be incorporated but take a look at the change in the link below and see if your installation has this fix.

https://docs.iredmail.org/upgrade.iredm … ok-servers

3 Reply by diespezialisten

  • diespezialisten
  • Member
  • Offline
  • Registered: 2019-04-30
  • Posts: 7

Re: iredapd failures after upgrade

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.3
- Deployed with iRedMail Easy or the downloadable installer? downloadable
- Linux/BSD distribution name and version: CentOS 7.8.2003
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MariaDB
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Same issue here:

Jul  3 11:12:57 mx01 postfix/smtpd[30190]: warning: problem talking to server 127.0.0.1:7777: Success
Jul  3 11:12:57 mx01 postfix/smtpd[30190]: AB6DDE09A3: reject: END-OF-MESSAGE from vlpdubai.ingredients.de[95.216.212.219]: 451 4.3.5 Server configuration problem; from=<vlpdubai@ingredients.de> to=<technik@diespezialisten.de> proto=ESMTP helo=<vlpdubai.ingredients.de>

I have no idea under what conditions this happens and why. Sometimes everything works smooth and sometimes the mail is rejected. Even if the sending mailserver and the from address is same.

I double checked the Installation from the upgrade. Beut eveything seems to be fine.

Any hints?

4 Reply by cvcvelo

  • cvcvelo
  • Member
  • Offline
  • Registered: 2014-06-16
  • Posts: 151

Re: iredapd failures after upgrade

slm858uk wrote:

I'm by no means an expert and you might want to wait for someone who is but i recently upgraded my iRedMail and this sounded familiar as i made a change for this. As you are on already on v1.3 it should already be incorporated but take a look at the change in the link below and see if your installation has this fix.

https://docs.iredmail.org/upgrade.iredm … ok-servers

Thanks slm858uk. Pretty sure this isn't my issue, as the /etc/postfix/helo_access.pcre file already contains the prepend suggested fix for Facebook at that URL, and also I'm getting the same failures from other domains.

"Server configuration problem" is pretty vague. And iredapd is still running after the error occurs. Not sure what to do next to identify and fix the problem.

5 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,088

Re: iredapd failures after upgrade

It looks like an iRedAPD issue, but we didn’t address it yet. Sorry about this trouble.

As a temporary fix, you can re-link /opt/iRedAPD-3.6 to /opt/iredapd and restart iredapd service. This downgrades it to 3.6.

6 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,088

Re: iredapd failures after upgrade

cvcvelo wrote:

Jul 02 13:16:58 mail9 python3[20222]: error: uncaptured python exception, closing channel <libs.channel.Policy connected 127.0.0.1:41812 at 0x7fe44fe03940> (<class 'KeyError'>:'59f8.5efe3dfd.13e86.0' [/usr/lib/python3.7/asyncore.py|readwrite|108] [/usr/l

hi cvcvelo,

Could you send me log lines above and below this line for troubleshooting? mail me: zhb _at_ iredmail.org.

7 Reply by cvcvelo

  • cvcvelo
  • Member
  • Offline
  • Registered: 2014-06-16
  • Posts: 151

Re: iredapd failures after upgrade

ZhangHuangbin wrote:

It looks like an iRedAPD issue, but we didn’t address it yet. Sorry about this trouble.

As a temporary fix, you can re-link /opt/iRedAPD-3.6 to /opt/iredapd and restart iredapd service. This downgrades it to 3.6.

Thanks, zhb. I regret to report that 3.6 fails to start after symlink'ing it to iredapd. Here's the error:

# systemctl status iredapd.service
● iredapd.service - iRedAPD (A simple posfix policy server)
   Loaded: loaded (/lib/systemd/system/iredapd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-07-03 19:13:45 PDT; 45s ago
  Process: 26690 ExecStart=/usr/bin/python3 /opt/iredapd/iredapd.py (code=exited, status=1/FAILURE)

Jul 03 19:13:45 mail9 python3[26690]:   File "/opt/iredapd/iredapd.py", line 47, in main
Jul 03 19:13:45 mail9 python3[26690]:     plugins=settings.plugins)
Jul 03 19:13:45 mail9 python3[26690]:   File "/opt/iRedAPD-3.6/libs/channel.py", line 44, in __init__
Jul 03 19:13:45 mail9 python3[26690]:     qr = utils.load_enabled_plugins(plugins=plugins)
Jul 03 19:13:45 mail9 python3[26690]:   File "/opt/iRedAPD-3.6/libs/utils.py", line 523, in load_enabled_plugins
Jul 03 19:13:45 mail9 python3[26690]:     for item in sorted(pnl, reverse=True):
Jul 03 19:13:45 mail9 python3[26690]: TypeError: '<' not supported between instances of 'dict' and 'dict'
Jul 03 19:13:45 mail9 systemd[1]: iredapd.service: Control process exited, code=exited, status=1/FAILURE
Jul 03 19:13:45 mail9 systemd[1]: iredapd.service: Failed with result 'exit-code'.
Jul 03 19:13:45 mail9 systemd[1]: Failed to start iRedAPD (A simple posfix policy server).

For now, I've gone back to iredapd 4.1, but it's only a matter of time before it will fail again. It has failed three times so far today, each requiring a manual restart.

I will send you the log lines you requested in just a moment.

8 Reply by cvcvelo

  • cvcvelo
  • Member
  • Offline
  • Registered: 2014-06-16
  • Posts: 151

Re: iredapd failures after upgrade

ZhangHuangbin wrote:

Could you send me log lines above and below this line for troubleshooting?

Done. Please let me know if you need anything else.