From: Herve Kergourlay <herve.kergourlay@asg.com>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Network issue
Date: Fri, 4 Aug 2017 07:25:44 +0000 [thread overview]
Message-ID: <3ad9dda84c2a4f859c602e437a36421f@asg.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2012 bytes --]
Hi
We have a customer suffering from network issues on a server in a context of RAC cluster / https://en.wikipedia.org/wiki/Oracle_RAC
The symptom is the following ;
A call to getaddrinfo on a server name fails after some times in production, with errno=11 "Resource temporarily unavailable"
The customer have a second cluster node in the same conditions without the issue.
When the issue occurs we can see in system logs the following sequence
Jan 24 14:22:06 raca-srv2 kernel: device eth0 entered promiscuous mode
Jan 24 14:22:06 raca-srv2 kernel: device eth2 entered promiscuous mode
Jan 24 14:22:06 raca-srv2 kernel: device eth9 entered promiscuous mode
Jan 24 14:22:06 raca-srv2 kernel: device eth8 entered promiscuous mode
Jan 24 14:22:06 raca-srv2 kernel: device eth1 entered promiscuous mode
Jan 24 14:22:06 raca-srv2 kernel: device eth1 left promiscuous mode
Jan 24 14:22:08 raca-srv2 kernel: device eth2 left promiscuous mode
Jan 24 14:22:29 raca-srv2 kernel: device eth8 left promiscuous mode
Jan 24 14:22:35 raca-srv2 kernel: device eth9 left promiscuous mode
Jan 24 14:22:39 raca-srv2 kernel: nr_pdflush_threads exported in /proc is scheduled for removal
Jan 24 14:22:39 raca-srv2 kernel: sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case. If you have one, please send an email to linux-mm@kvack.org.
Jan 24 14:22:45 raca-srv2 kernel: device eth0 left promiscuous mode
Jan 24 14:26:46 raca-srv2 kernel: bnx2x 0000:88:00.0 eth8: NIC Link is Down
Jan 24 14:26:46 raca-srv2 kernel: bonding: bond0: link status definitely down for interface eth8, disabling it
Jan 24 14:26:46 raca-srv2 kernel: bonding: bond0: making interface eth0 the new active one.
As your email address is explicitly notified, I send you this email. I hope you will be able to us to understand what is happening
If you have questions on the context, I will be pleased to give you any usefull answers needed.
Regards
Hervé
[-- Attachment #2: Type: text/html, Size: 6641 bytes --]
reply other threads:[~2017-08-04 7:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ad9dda84c2a4f859c602e437a36421f@asg.com \
--to=herve.kergourlay@asg.com \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox