Re: high cpu load with tcpdump

2016-08-30 Thread Manuel Bouyer
On Tue, Aug 30, 2016 at 04:12:02PM +0200, Rhialto wrote: > Meanwhile, in 7.0.1, tcpdump still seems to cause (close to) 100% cpu > load. (Tested with "tcpdump -i re1 -vvv icmp6" on an almost idle link) > > Has this been fixed in -current? Will it be in 7.0.2 (or 7.1?) soon? I'm not sure it has b

Re: high cpu load with tcpdump

2016-08-30 Thread Rhialto
On Sun 06 Mar 2016 at 18:59:57 +0100, Manuel Bouyer wrote: > On Fri, Mar 04, 2016 at 12:31:07PM +, Patrick Welche wrote: > > Was there ever a conclusion to the "pipe read returning EAGAIN" thread? > > > > https://mail-index.netbsd.org/current-users/2016/02/07/msg028841.html > > The conclusi

Re: high cpu load with tcpdump

2016-03-06 Thread Manuel Bouyer
On Fri, Mar 04, 2016 at 12:31:07PM +, Patrick Welche wrote: > Was there ever a conclusion to the "pipe read returning EAGAIN" thread? > > https://mail-index.netbsd.org/current-users/2016/02/07/msg028841.html The conclusion was that it's a programming error in the application, but there's st

Re: high cpu load with tcpdump

2016-03-04 Thread Patrick Welche
Was there ever a conclusion to the "pipe read returning EAGAIN" thread? https://mail-index.netbsd.org/current-users/2016/02/07/msg028841.html Cheers, Patrick

Re: high cpu load with tcpdump

2016-03-04 Thread Patrick Welche
On Mon, Feb 29, 2016 at 09:11:44PM +0100, 6b...@6bone.informatik.uni-leipzig.de wrote: > 2362 9 named1456773617.648034355 CALL > setsockopt(0x262,0x,0x800,0x7f7ff09f8484,4) SOL_SOCKET SO_NOSIGPIPE > 2362 6 named1456773618.151732844 CALL > setsockopt(0x260,0x,0x2

Re: high cpu load with tcpdump

2016-03-02 Thread Patrick Welche
On Mon, Feb 29, 2016 at 09:11:44PM +0100, 6b...@6bone.informatik.uni-leipzig.de wrote: > On Mon, 29 Feb 2016, Christos Zoulas wrote: > > >| Hello, > >| > >| the problem occurs only on one of my servers. I tried to find the > >| difference. It is the bind9 (bind-9.10.3pl3). If I stop the bind9, tc

Re: high cpu load with tcpdump

2016-03-01 Thread Christos Zoulas
On Mar 1, 3:08pm, 6b...@6bone.informatik.uni-leipzig.de (6b...@6bone.informatik.uni-leipzig.de) wrote: -- Subject: Re: high cpu load with tcpdump | On Mon, 29 Feb 2016, Christos Zoulas wrote: | | > | > This tcpdump ktrace is when bind is running, right? | > What happens if you sto

Re: high cpu load with tcpdump

2016-03-01 Thread 6bone
On Mon, 29 Feb 2016, Christos Zoulas wrote: This tcpdump ktrace is when bind is running, right? What happens if you stop it? How does the ktrace look then? Or once you start bind, tcpdump goes nuts and stays that way? You're right. When tcpdump is started after the bind, tcpdump caused probl

Re: high cpu load with tcpdump

2016-02-29 Thread Christos Zoulas
On Feb 29, 9:11pm, 6b...@6bone.informatik.uni-leipzig.de (6b...@6bone.informatik.uni-leipzig.de) wrote: -- Subject: Re: high cpu load with tcpdump | On Mon, 29 Feb 2016, Christos Zoulas wrote: | | > | Hello, | > | | > | the problem occurs only on one of my servers. I tried to

Re: high cpu load with tcpdump

2016-02-29 Thread 6bone
On Mon, 29 Feb 2016, Christos Zoulas wrote: | Hello, | | the problem occurs only on one of my servers. I tried to find the | difference. It is the bind9 (bind-9.10.3pl3). If I stop the bind9, tcpdump | works without problems. When I restart the bind9, the CPU load goes back | to 100%. | | Is it

Re: high cpu load with tcpdump

2016-02-29 Thread Christos Zoulas
On Feb 29, 2:48pm, 6b...@6bone.informatik.uni-leipzig.de (6b...@6bone.informatik.uni-leipzig.de) wrote: -- Subject: Re: high cpu load with tcpdump | On Sat, 27 Feb 2016, 6b...@6bone.informatik.uni-leipzig.de wrote: | | > Date: Sat, 27 Feb 2016 23:52:24 +0100 (CET) | > Fr

Re: high cpu load with tcpdump

2016-02-29 Thread 6bone
On Sat, 27 Feb 2016, 6b...@6bone.informatik.uni-leipzig.de wrote: Date: Sat, 27 Feb 2016 23:52:24 +0100 (CET) From: 6b...@6bone.informatik.uni-leipzig.de To: Joerg Sonnenberger Cc: current-users@netbsd.org Subject: Re: high cpu load with tcpdump On Sat, 27 Feb 2016, Joerg Sonnenberger wrote

Re: high cpu load with tcpdump

2016-02-27 Thread 6bone
On Sat, 27 Feb 2016, Joerg Sonnenberger wrote: fstat should tell you what the file descriptor is, I just want to identify what device seems to have the trouble. You're right. USER CMD PID FD MOUNT INUM MODE SZ|DV R/W _tcpdump tcpdump 823 root /142496

Re: high cpu load with tcpdump

2016-02-27 Thread Joerg Sonnenberger
On Sat, Feb 27, 2016 at 10:28:43PM +0100, 6b...@6bone.informatik.uni-leipzig.de wrote: > On Sat, 27 Feb 2016, Joerg Sonnenberger wrote: > > >Date: Sat, 27 Feb 2016 20:38:37 +0100 > >From: Joerg Sonnenberger > >To: current-users@netbsd.org > >Subject: Re: high cpu l

Re: high cpu load with tcpdump

2016-02-27 Thread 6bone
On Sat, 27 Feb 2016, Joerg Sonnenberger wrote: Date: Sat, 27 Feb 2016 20:38:37 +0100 From: Joerg Sonnenberger To: current-users@netbsd.org Subject: Re: high cpu load with tcpdump On Sat, Feb 27, 2016 at 08:18:41PM +0100, 6b...@6bone.informatik.uni-leipzig.de wrote: 5015 1 tcpdump

Re: high cpu load with tcpdump

2016-02-27 Thread Joerg Sonnenberger
On Sat, Feb 27, 2016 at 08:18:41PM +0100, 6b...@6bone.informatik.uni-leipzig.de wrote: > 5015 1 tcpdump 1456559035.621583576 CALL > read(3,0x7f7ff7b16000,0x8) FD 3 is a BPF instance? Joerg

Re: high cpu load with tcpdump

2016-02-27 Thread 6bone
On Fri, 26 Feb 2016, Christos Zoulas wrote: Date: Fri, 26 Feb 2016 14:52:46 + (UTC) From: Christos Zoulas To: current-users@netbsd.org Subject: Re: high cpu load with tcpdump In article , <6b...@6bone.informatik.uni-leipzig.de> wrote: Hello, On my router tcpdump uses always 10

Re: high cpu load with tcpdump

2016-02-26 Thread Christos Zoulas
In article , <6b...@6bone.informatik.uni-leipzig.de> wrote: >Hello, > >On my router tcpdump uses always 100% CPU. > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPUCPU COMMAND > 3403 _tcpdump 38019M 3016K RUN/6 0:24 98.08% 70.02% tcpdump > 0 root 00

high cpu load with tcpdump

2016-02-26 Thread 6bone
Hello, On my router tcpdump uses always 100% CPU. PID USERNAME PRI NICE SIZE RES STATE TIME WCPUCPU COMMAND 3403 _tcpdump 38019M 3016K RUN/6 0:24 98.08% 70.02% tcpdump 0 root 00 0K 1182M CPU/7 49:35 0.00% 3.76% [system] The problem also oc