Linux - Server This forum is for the discussion of Linux Software used in a server related context. |
Notices |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
05-29-2008, 06:54 AM
|
#1
|
LQ Newbie
Registered: Sep 2006
Posts: 19
Rep:
|
Postfix issue - no local interface found for (invalid) ip
Greetings,
Apparently my Postfix which has been running fine for the last three months suddenly and mysteriously broke.
In my mail log I am receiving the following error messages:
<snip>
May 29 03:03:48 bocacentral postfix/master[22144]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
May 29 03:03:51 bocacentral postfix[28179]: fatal: parameter inet_interfaces: no local interface found for 69.50.160.213
May 29 03:04:22 bocacentral postfix[3657]: fatal: parameter inet_interfaces: no local interface found for 69.50.160.213
May 29 03:26:27 bocacentral postfix[32672]: fatal: parameter inet_interfaces: no local interface found for 69.50.160.213
May 29 03:31:01 bocacentral postfix[6140]: fatal: parameter inet_interfaces: no local interface found for 69.50.160.213
</snip>
I looked everywhere, particularly main.cf and master.cf, hosts, etc. and the config files appear to have my correct and valid IP addressing.
It seems Postfix will not even start because if I go to /etc/init.d and try to manually restart Postfix it throws a similar error.
I am also running Apache on this box and that seems to be fine...I can access any web pages via URL without having to specify IP.
Where is Posftix getting this bogus IP address??? How can I fix it? And the big question, would someone please enlighten me as to how this could have happened to begin with.
The only recent "changes" I am aware of are an increase in disk space and memory to my VPS, but to the best of my knowledge that is all.
Thanks!
|
|
|
05-29-2008, 08:11 AM
|
#2
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417
|
can you show us your config and the ifconfig output on your system? seems you have a line that reads "inet_interfaces = 69.x.y.z" when that IP is not on your actual server.
|
|
|
05-29-2008, 09:06 AM
|
#3
|
LQ Newbie
Registered: Sep 2006
Posts: 19
Original Poster
Rep:
|
postfix problem - interface not found
Hi Chris,
Thanks for your reply.
Here are the results of my ifconfig:
<snip>
bocacentral:~# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3380 errors:0 dropped:0 overruns:0 frame:0
TX packets:3380 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1013889 (990.1 KiB) TX bytes:1013889 (990.1 KiB)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:791 errors:0 dropped:0 overruns:0 frame:0
TX packets:695 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:68899 (67.2 KiB) TX bytes:71504 (69.8 KiB)
venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:206.123.89.201 P-t-P:206.123.89.201 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:
</snip>
Here are the contents of my main.cf:
<snip>
# See /usr/share/postfix/main.cf.dist for a commented, more complete version
# Debian specific: Specifying a file name will cause the first
# line of that file to be used as the name. The Debian default
# is /etc/mailname.
#myorigin = /etc/mailname
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
# appending .domain is the MUA's job.
append_dot_mydomain = no
# Uncomment the next line to generate "delayed mail" warnings
delay_warning_time = 4h
# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${queue_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${queue_directory}/smtp_scache
# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.
myhostname = mail.bocacentral.com
mydomain = bocacentral.com
alias_maps = hash:/etc/aliases, hash:/etc/mail/aliases, hash:/var/lib/mailman/data/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination =$myhostname, $mydomain
relayhost =
relay_domains = $mydestination, bocacentral.com
mynetworks = 127.0.0.1, 206.123.89.201
mailbox_command = procmail -a "$EXTENSION"
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = ALL
alltransport_maps = hash:/etc/postfix/transport
mailman_destination_recipient_limit = 1
</snip>
Thanks,
B
|
|
|
12-04-2010, 04:26 AM
|
#4
|
Member
Registered: Feb 2004
Location: Australia
Distribution: Ubuntu, Fedora 10
Posts: 632
Rep:
|
I just had this problem. I have about three different websites running on my server and just removed one but forgot to update the postfix main.cf file. Somehow postfix detected that the domain I removed was no longer attached to my nameservers and caused the problem. After removing the domain it worked.
|
|
|
12-04-2010, 05:03 AM
|
#5
|
Senior Member
Registered: Jul 2007
Distribution: Gentoo
Posts: 2,125
|
I saw an interesting piece of information here. Perhaps there is some old configuration information that it is still getting.
Quote:
postfix runs in a *kind of* chrooted environment
Take a look at /var/spool/postfix there are some insteresting things there like: /var/spool/postfix/etc/resolv.conf
this why postfix was using an old IP address. postfix had not been updated and therefore was using your old network settings.
|
|
|
|
12-04-2010, 05:07 AM
|
#6
|
Senior Member
Registered: Jul 2007
Distribution: Gentoo
Posts: 2,125
|
Also take a look here. BTW, I googled for "fatal: parameter inet_interfaces: no local interface found for" with quotes and found that this seems to be fairly common symptom, but many causes. It seems that there may be some IPV6 issues. I noticed that your interfaces looks unusual, with the loopback interface and a virtual loopback interface, but no physical ones. I suspect this is because of your VPS.
|
|
|
All times are GMT -5. The time now is 04:03 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|