Lindsay Haisley writes:
I've had some very strange problems related to mail and name service subsequent to an update from Ubuntu's 3.2.0-58-generic x86_64 kernel to the 3.2.0-59 and am trying figure out what's going on. I had to back out the kernel update to get everything working.Has anyone else had, or has anyone else reported problems? These may show up as courieresmtp refusing to respond on the localhost IF. I had immediate problems with the Mailman list server which stopped feeding list posts to courier for distribution to subscribers, and I've had one customer tell me that someone he knows got a NDR related to one of his email addresses which is a courier alias redirection. I haven't yet seen the NDR. Both of these involve courier responding on the localhost interface. I likewise had a problem with bind9 on the same server which stopped responding to queries from a VPN IF and also via the localhost IF on the box unless I had an explicit IPv4 interface ACL in the bind9 config. This was NOT an issue under previous Linux kernels.
Don't recall the specific kernel, but after updating to it, some time ago, I was rudely surprised when it decided that eth0 was really eth1, and eth1 was really eth0; and then kept changing its mind again, on random subsequent boots.
This was because both ports were running off different cards which had different kernel modules, and, at power on, the kernel was running separate execution thread to initialize and enable each card, and whichever thread ended up finishing first got eth0 assigned to it, and the laggard got stuck with eth1.
That's pretty much the only thing that comes to mind. This would generally create chaos if you had custom firewall rules that were getting bound to an interface port by its name. It should not generally affect applications that get bound to IP addresses; however if you had eth0 configured to come up with DHCP, and had a static mapping for eth1, having them swapped would obviously be a problem.
If that turns out to be the case here, the solution would be to bite the bullet, and set up custom udev naming rules for the ethernet ports. Don't name them ethX. Name them wan0 and lan0, and they'll come up this way, each time.
pgpmzPttXSUHV.pgp
Description: PGP signature
------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
