From mboxrd@z Thu Jan 1 00:00:00 1970 From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1680093186; bh=jfPSLv4oXAJFkid2zJKOa3JtM9s94uYEExu7mfqq19s=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=hoFt2ZSfBxSVo366ubJVvydp0k0qXWilIksAu7yhhQk2WGS8PAEgzqMrZGL1AcfXW afZTLan/0aDQyk6r1O45xPSJcSQIF7bwmRT44UbDoJxl5vB9cWi8caDii4p/DqRJ24 Wn65bhs9iYdjJQ8SCSz5EHvW1k/pabSnxfBQ7UQB96FGFfOaUI5Ei5S9tEz9gKx6SL qb8sqvYmO1QBScY9emEAMjrVqNFeDVLB37NAsHfvkFQYEn00a7UieKubdAbdG2c7R+ VAEil+19v9N4/nAJPs8gXdPBEck1u1ua0zDF+f1Hy4IRaEgUcs/4BQatXLWzBtH1Sc UAO8Kv0oqs9gg== To: ch In-Reply-To: <3a9e0bde-d5ea-32b1-f428-db22487a9cf6@ntrv.dk> References: <878rfhoxrs.fsf@toke.dk> <87y1nhnff4.fsf@toke.dk> <8e8da0c6-30ea-8a2e-b55b-a547d4868889@ntrv.dk> <87h6u3oolh.fsf@toke.dk> <3a9e0bde-d5ea-32b1-f428-db22487a9cf6@ntrv.dk> Date: Wed, 29 Mar 2023 14:33:06 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <878rffohz1.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID-Hash: QD6ZSNRQV3ZXSZHAFVOBAICWEBYIGKSV X-Message-ID-Hash: QD6ZSNRQV3ZXSZHAFVOBAICWEBYIGKSV X-MailFrom: toke@toke.dk X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: flent-users@flent.org X-Mailman-Version: 3.3.8 Precedence: list Subject: [Flent-users] Re: ERROR: Runner Burst 0 failed check: No command set for SilentProcessRunner List-Id: Flent discussion list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: ch writes: > On 29/03/2023 12.10, Toke H=C3=B8iland-J=C3=B8rgensen wrote: >>> to run. Resulting in the node generating traffic for the full pipe for >>> hours on end. My observation is the test does not terminate for unknown >>> reasons. >> Hmm, did you pull the latest version of traffic-gen? The version on >> github had a bug where it would just go into an infinite loop and never >> exit (and not produce any traffic either). Fixed that yesterday, so make >> sure you pull the fixed version... > > Hmm. Good question > >> # ls -la traffic-gen=20 >> -rwxr-xr-x 1 root root 22832 Mar 28 20:04 traffic-gen > > I did compile the binary yesterday afternoon. So I can only assume it=20 > contains the tree commits from yesterday. > >> # git log --oneline >> b316813 (HEAD -> master, origin/master, origin/HEAD) Use getrandom() ins= tead of rand()/srand() >> eedf705 Fix infinite loop in scheduling logic >> 5c1007e Support setting the TOS byte on transmitted packets. > > (The application is missing the option for outputting a version number=20 > or git hash using e.g. -v, -V, or --version) > >> and not produce any traffic either > > It did produce *lots* of traffic. Had to terminate flent process to=20 > terminate the child traffic-gen processes. > Attached is the graph of the network traffic levels (in MB/s) as=20 > reported by Proxmox. Ah! Seems I introduced another infinite loop while fixing the previous one; pushed another fix, please try that... -Toke