This happens (or used to happen) also in 16.04.2 (current). I paste here
a couple of evidences (17.04):
$ ps auxwww | grep ping
sgala 12545 96.5 0.0 20592 1020 pts/2 R+ 13:18 118:36 ping
192.168.25.96
(...)
$ sudo strace -p 12545
(...)
recvmsg(3, 0x7ffe0a5d0b00, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLERR}], 1, 164) = 1 ([{fd=3, revents=POLLERR}])
recvmsg(3, 0x7ffe0a5d0b00, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLERR}], 1, 164) = 1 ([{fd=3, revents=POLLERR}])
recvmsg(3, 0x7ffe0a5d0b00, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLERR}], 1, 164) = 1 ([{fd=3, revents=POLLERR}])
recvmsg(3, 0x7ffe0a5d0b00, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLERR}], 1, 164) = 1 ([{fd=3, revents=POLLERR}])
recvmsg(3, 0x7ffe0a5d0b00, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLERR}], 1, 164) = 1 ([{fd=3, revents=POLLERR}])
recvmsg(3, 0x7ffe0a5d0b00, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLERR}], 1, 164) = 1 ([{fd=3, revents=POLLERR}])
recvmsg(3, 0x7ffe0a5d0b00, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLERR}], 1, 164) = 1 ([{fd=3, revents=POLLERR}])
recvmsg(3, 0x7ffe0a5d0b00, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLERR}], 1, 164) = 1 ([{fd=3, revents=POLLERR}])
(...)
The ping is taking 100% CPU. After I killed the process, one can see
that the command line was a plain "ping 192.168.25.96"
About ping version:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=17.04
DISTRIB_CODENAME=zesty
DISTRIB_DESCRIPTION="Ubuntu 17.04"
$ dpkg -l $(dpkg-query -S $(which ping) | awk -F: '{print $1}')
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture
Description
+++-=================================-=====================-=====================-=======================================================================
ii iputils-ping 3:20161105-1ubuntu2 amd64
Tools to test the reachability of network hosts
I have also seen this going on with Ubuntu 16.04.2 LTS fully patched. I
use something like ((ping -i 60 -B [address] >& /dev/null )&)& as a poor
man's keepalive, and it jumps systematically to 100% CPU after one or
two days.
Versions for 16.04.2:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"
$ dpkg -l $(dpkg-query -S $(which ping) | awk -F: '{print $1}')
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture
Description
+++-=================================-=====================-=====================-=======================================================================
ii iputils-ping 3:20121221-5ubuntu2 amd64
Tools to test the reachability of network hosts
Note there has been some time since I last observed the bug in 16.04.2,
but I have just found my laptop spinning before I decided to look for
the bug and post here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1697646
Title:
Long-running ping command leads to 100% CPU usage
Status in iputils package in Ubuntu:
Confirmed
Bug description:
Since I've updated my laptop to Ubuntu MATE 17.04, I notice ping
sometimes gets into a runaway mode.
I'm on a shaky Wi-Fi so to monitor connectivity I usually have a long
running ping command against google's DNS server:
> ping -s16 8.8.4.4
Often, after leaving it for a while, I notice screaming vents and htop
then shows the ping process consuming 100% of one CPU. It will stay
like that until ping is killed.
I'm not sure how to troubleshoot this issue, can someone recommend a
protocol?
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: iputils-ping 3:20161105-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Tue Jun 13 11:11:26 2017
InstallationDate: Installed on 2017-04-05 (69 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
SourcePackage: iputils
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1697646/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
