Mailing List Archive

DBMail services dbmail-pop3d and dbmail-lmtpd remain inactive after start and enable, erratic start on one or the other
Hi!

I set up an error report on this already (0001076
<http://www.dbmail.org/mantis/view.php?id=1076>), but I thought I'd ask the
mailing list too. If you've already seen the error report and aren't really
sure how to fix this issue, thanks for trying, and I apologize for filling
your inbox.

We're testing DBMail 3.2.3 on a RHEL 7 server, as part of upgrading our
existing DBMail routing servers. Unfortunately, every time we start
dbmail-pop3d or dbmail-lmtpd, both services get stuck on "enabled but
inactive" and refuse to go anywhere.

The Repo we're using defaults to effective_user nobody, effective_group
nobody. In the bug report, someone suggested that we change that to dbmail
/ dbmail, as the repo creates a dbmail user, and the nobody / nobody thing
should be a bug. However, after changing this, we're still running into the
same issue at the same point in the process.

The exact messages are this:

---When LMTPD fails to start:---
dbmail-lmtpd.service - DBMail LMTP Server
Loaded: loaded (/usr/lib/systemd/system/dbmail-lmtpd.service; enabled)
Active: inactive (dead) since Wed 2015-11-11 16:18:43 CST; 2s ago
Process: 47864 ExecStart=/usr/sbin/dbmail-lmtpd (code=exited,
status=0/SUCCESS)
Main PID: 47865 (code=exited, status=0/SUCCESS)

---When POP3D successfully starts:---
dbmail-pop3d.service - DBMail pop3 Server
Loaded: loaded (/usr/lib/systemd/system/dbmail-pop3d.service; enabled)
Active: active (running) since Wed 2015-11-11 16:18:13 CST; 14s ago
Process: 47832 ExecStart=/usr/sbin/dbmail-pop3d (code=exited,
status=0/SUCCESS)
Main PID: 47834 (dbmail-pop3d)
CGroup: /system.slice/dbmail-pop3d.service
ââ47834 /usr/sbin/dbmail-pop3d

And here's our most recent dbmail.err entry for these:

Dec 08 09:26:53 oexdev1 dbmail-pop3d[56241]: [0x7fcf2fd6b000] Info:[debug]
configure_debug(+79): [POP] syslog [31 -> 31] stderr [31 -> 511]
Dec 08 09:26:53 oexdev1 dbmail-pop3d[56241]: [0x7fcf2fd6b000]
Debug:[server] server_config_load(+1015): max_db_connections [10]
Dec 08 09:26:53 oexdev1 dbmail-pop3d[56241]: [0x7fcf2fd6b000]
Debug:[config] config_get_timeout(+445): timeout [300] seconds
Dec 08 09:26:53 oexdev1 dbmail-pop3d[56241]: [0x7fcf2fd6b000]
Debug:[config] config_get_timeout(+456): login_timeout [60] seconds
Dec 08 09:26:53 oexdev1 dbmail-pop3d[56241]: [0x7fcf2fd6b000]
Debug:[server] server_config_load(+1024): no value for SOCKET in config file
Dec 08 09:26:53 oexdev1 dbmail-pop3d[56241]: [0x7fcf2fd6b000]
Debug:[server] server_config_load(+1026): socket []
Dec 08 09:26:53 oexdev1 dbmail-pop3d[56241]: [0x7fcf2fd6b000]
Debug:[server] server_config_load(+1047): binding to PORT [110]
Dec 08 09:26:53 oexdev1 dbmail-pop3d[56241]: [0x7fcf2fd6b000]
Debug:[server] server_config_load(+1076): binding to IP [0.0.0.0]
Dec 08 09:26:53 oexdev1 dbmail-pop3d[56241]: [0x7fcf2fd6b000]
Debug:[server] server_config_load(+1082): no value for BACKLOG in config
file. Using default value [128]
Dec 08 09:26:53 oexdev1 dbmail-pop3d[56241]: [0x7fcf2fd6b000]
Debug:[server] server_config_load(+1086): POP backlog [128]
Dec 08 09:26:53 oexdev1 dbmail-pop3d[56241]: [0x7fcf2fd6b000]
Debug:[server] server_config_load(+1093): not resolving client IP
Dec 08 09:26:53 oexdev1 dbmail-pop3d[56241]: [0x7fcf2fd6b000]
Debug:[server] server_config_load(+1102): Disabling POP-before-SMTP
Dec 08 09:26:53 oexdev1 dbmail-pop3d[56241]: [0x7fcf2fd6b000]
Debug:[server] server_config_load(+1109): Disabling POP Authentication
logging
Dec 08 09:26:53 oexdev1 dbmail-pop3d[56241]: [0x7fcf2fd6b000]
Debug:[server] server_config_load(+1119): effective user shall be [dbmail]
Dec 08 09:26:53 oexdev1 dbmail-pop3d[56241]: [0x7fcf2fd6b000]
Debug:[server] server_config_load(+1128): effective group shall be [dbmail]
Dec 08 09:26:57 oexdev1 dbmail-lmtpd[56258]: [0x7fe25269f000] Info:[debug]
configure_debug(+79): [LMTP] syslog [31 -> 31] stderr [31 -> 511]
Dec 08 09:26:57 oexdev1 dbmail-lmtpd[56258]: [0x7fe25269f000]
Debug:[server] server_config_load(+1015): max_db_connections [10]
Dec 08 09:26:57 oexdev1 dbmail-lmtpd[56258]: [0x7fe25269f000]
Debug:[config] config_get_timeout(+445): timeout [300] seconds
Dec 08 09:26:57 oexdev1 dbmail-lmtpd[56258]: [0x7fe25269f000]
Debug:[config] config_get_timeout(+456): login_timeout [60] seconds
Dec 08 09:26:57 oexdev1 dbmail-lmtpd[56258]: [0x7fe25269f000]
Debug:[server] server_config_load(+1024): no value for SOCKET in config file
Dec 08 09:26:57 oexdev1 dbmail-lmtpd[56258]: [0x7fe25269f000]
Debug:[server] server_config_load(+1026): socket []
Dec 08 09:26:57 oexdev1 dbmail-lmtpd[56258]: [0x7fe25269f000]
Debug:[server] server_config_load(+1047): binding to PORT [24]
Dec 08 09:26:57 oexdev1 dbmail-lmtpd[56258]: [0x7fe25269f000]
Debug:[server] server_config_load(+1076): binding to IP [0.0.0.0]
Dec 08 09:26:57 oexdev1 dbmail-lmtpd[56258]: [0x7fe25269f000]
Debug:[server] server_config_load(+1082): no value for BACKLOG in config
file. Using default value [128]
Dec 08 09:26:57 oexdev1 dbmail-lmtpd[56258]: [0x7fe25269f000]
Debug:[server] server_config_load(+1086): LMTP backlog [128]
Dec 08 09:26:57 oexdev1 dbmail-lmtpd[56258]: [0x7fe25269f000]
Debug:[server] server_config_load(+1093): not resolving client IP
Dec 08 09:26:57 oexdev1 dbmail-lmtpd[56258]: [0x7fe25269f000]
Debug:[server] server_config_load(+1100): no value for LMTP_BEFORE_SMTP in
config file
Dec 08 09:26:57 oexdev1 dbmail-lmtpd[56258]: [0x7fe25269f000]
Debug:[server] server_config_load(+1102): Disabling LMTP-before-SMTP
Dec 08 09:26:57 oexdev1 dbmail-lmtpd[56258]: [0x7fe25269f000]
Debug:[server] server_config_load(+1109): Disabling LMTP Authentication
logging
Dec 08 09:26:57 oexdev1 dbmail-lmtpd[56258]: [0x7fe25269f000]
Debug:[server] server_config_load(+1119): effective user shall be [dbmail]
Dec 08 09:26:57 oexdev1 dbmail-lmtpd[56258]: [0x7fe25269f000]
Debug:[server] server_config_load(+1128): effective group shall be [dbmail]

I'd appreciate any suggestions you might have. I'll admit, I'm fairly new
to managing DBMail servers, so there's a good chance the issue originated
from a ID10T error on my end.