Bug 91420
| Summary: | xinetd 2.3.11-1.7x breaks smtp service for qmail | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Brian Hayward <hayward> |
| Component: | xinetd | Assignee: | Jay Fenlason <fenlason> |
| Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | esammons, jfeeney |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | athlon | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-05-22 14:13:21 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
When I say "qmail-smtpd doesn't start, above" Clearly what I mean is: "xinetd does not listen on port 25 for requests" Delete the meaningless RECORD option from the log_on_failure line in your config. Older versions of xinetd ignored this unimplementd option. Xinetd 2.3.11 flags this (never implemented) option as an error. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020913 Description of problem: It ignores my SMTP service with this version of xinetd. If I revert back to xinetd-2.3.7-4.7x, the smtp service runs fine. Here are the contents of my smtp service description for xinetd: service smtp { socket_type = stream wait = no user = qmaild disable = no server = /var/qmail/bin/tcp-env server_args = /var/qmail/bin/qmail-smtpd log_on_success = HOST PID USERID DURATION USERID log_on_failure = HOST RECORD ATTEMPT USERID } Version-Release number of selected component (if applicable): xinetd-2.3.11-1.7x.i386 How reproducible: Always Steps to Reproduce: 1.Install new package 2.qmail-smtpd doesn't start 3. Actual Results: May 22 06:44:38 lotus xinetd[1167]: xinetd Version 2.3.11 started with libwrap loadavg options compiled in. May 22 06:44:38 lotus xinetd[1167]: Started working: 7 available services May 22 06:44:41 lotus xinetd: xinetd startup succeeded Expected Results: May 22 06:46:11 lotus xinetd: xinetd shutdown succeeded May 22 06:46:11 lotus xinetd[1213]: xinetd Version 2.3.7 started with libwrap options compiled in. May 22 06:46:11 lotus xinetd[1213]: Started working: 8 available services May 22 06:46:14 lotus xinetd: xinetd startup succeeded Additional info: The only thing I changed to get expected results was to revert to the previous version of xinetd. I guess I shouldn't trust running up2date from cron.