Idézem/Quoting Lindsay Haisley <fmouse-cour...@fmp.com>: > On Wed, 2016-12-28 at 15:44 -0800, Gordon Messmer wrote: >> On 12/28/2016 02:07 PM, Lindsay Haisley wrote: >> > This generally removes any dependency on DNS for resolving >> "localhost". >> >> Courier uses DNS for everything that comes to mind. Modifying >> /etc/hosts won't resolve the problem in question. > > True. > > Another problem which I've had on occasion, although it doesn't sound > as if this is Viktor's problem, is with firewall configuration. If the > default INPUT policy is DROP, and localhost and there's no firewall > rule allowing it, then localhost traffic will be blocked. > > This more or less applies to Linux, although any OS with configurable > kernel-based firewall rules will probably have similar properties. > > Viktor, when this happens, does "ifconfig" show an existing localhost > interface, "lo" or "lo0"?
Thank you for your help. I was running only netstat and tcpdump during Monit alerts. I am going to add ifconfig the next time I debug this. Usually it is a provider problem. It occurs when there is a network congestion or I don't know what. From the virtual instances "I" do not see the physical network. And the incident (no response from lo) usually takes 2 or 4 minutes then Monit restarts Courier and everything is back up again. SZÉPE Viktor https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md -- +36-20-4242498 s...@szepe.net skype: szepe.viktor Budapest, III. kerület ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
