After upgrading postfix in dapper, it no longer starts

[Steve Peters]

After the most recent update to postfix in Dapper, postfix will not start. In /var/log/mail.err, I see the following error message. I've not made any changes to /etc/postfix/master.cf, or other network configuration, so I'm suspecting the upgrade.

Jan 25 09:26:18 localhost postfix/master[8176]: fatal: /etc/postfix/master.cf: line 18: no valid IP address found: smtp

[LaMont Jones (lamont)]

I cannot reproduce this issue on any of my machines. What architecture is the machine, and what verison of postfix do you have?

[Steve Peters (steve-fisharerojo)]

On Thu, Jan 26, 2006 at 04:31:07PM -0000, LaMont Jones wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/29661
>
> Task: ubuntu postfix
> Status: Unconfirmed => Needs Info
>
> Comment:
> I cannot reproduce this issue on any of my machines. What architecture
> is the machine, and what verison of postfix do you have?

steve@kirk:~$ uname -a
Linux kirk 2.6.15-13-386 #1 PREEMPT Thu Jan 19 16:24:40 UTC 2006 i686 GNU/Linux
steve@kirk:~$ dpkg -l postfix
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii postfix 2.2.8-6 A high-performance mail transport agent

[claes (claes-backstrom)]

I have the exact same problem. I use network-manager to handle my ip configuration. It might be that? I tried to start postfix after network-manager have configured my interface but still the same problem.

[claes (claes-backstrom)]

I have solved my problem.
By some reason my loopback device didn't come up. I had 2 lines in my /etc/network/interfaces reading: "auto eth1" and that stopped the loopback device from working. I removed one of the lines started lo with: sudo ifup lo and it come up. Restarted postfix and everything worked. Not sure why I had 2 lines with auto eth1. But now it seems to work as it should.

[Steve Peters (steve-fisharerojo)]

OK, that must have been what fixed it for me too then. In my /etc/networking/interfaces I saw:

auto eth0 lo
...
auto eth0

I commented out the second one, but it did not seem to have a direct effect. I upgraded ifupdown, rebooted, and everything was working again. I'll go with your explanation that the "auto eth0" in /etc/networking/interfaces is the problem

[Steve Peters (steve-fisharerojo)]

The fixes to /etc/networking/interfaces fixed my problems.