Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am (or was) running sendmail 8.11.6 on a 2.4.20 kernel (Red Hat Linux 7.3). The installation has been running without problems for many months. A few days ago, upon reboot, sendmail began failing with the following entries in maillog:
Aug 21 12:12:40 mymachine sendmail: starting daemon (8.11.6): SMTP+queueing@01:00:00
Aug 21 12:12:40 mymachine sendmail: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
Aug 21 12:12:40 mymachine sendmail: daemon MTA: problem creating SMTP socket
Aug 21 12:12:45 mymachine sendmail: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Cannot assign requested address
Aug 21 12:12:45 mymachine sendmail: daemon MTA: problem creating SMTP socket
[The above repeated at 5 second intervals 10 times]
Aug 21 12:13:30 mymachine sendmail: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: server SMTP socket wedged: exiting
Has anyone seen anything like this? This is sort of "out of the blue"; all other services are working OK, and the only recent change is a NIC replacement (previous NIC damaged during blackout.) I'm willing to send more info if any sendmail experts out there would like. Thanks!
-Scott Wagner, Rochester NY US
I found the answer to this one - it seems my eth1: interface, which acqures its ip address via DHCP, conflicted with an entry:
O DaemonPortOptions=Port=smtp,Addr=a.b.c.d, Name=MTA
in my /etc/sendmail.cf .
When I manually fixed the DaemonPortOptions entry in sendmail.cf, sendmail worked fine.
I still have to figure out how to keep the DaemonPortOptions entry synchronized with the (DHCP-assigned) ip address.
Scott, do you update a DNS name after you get a new one from DHCP? I.E. do you use DynDNS or similar service? If so, you should be able to use that named address instead of a numbered one. The only problem with that approach is that it may take a few minutes until sendmail will start correctly while the address gets the update and is propogated to your upstream DNS provider(s). In fact, I hourly retart sendmail in a cron.hourly script for that reason and it seems to help. Perhaps there's a better solution?