Hi.
On Thu, Jul 02, 2020 at 07:13:11AM +0200, Nico Becker wrote:
> hello,
> i am again. i tcpdump the port.
> > tcpdump -pni any -c1024 -s0 -w /tmp/journal.pcap tcp port 19531
> i check the capture size after the cpu load is at 100%.
> but the size doesnt increase after the systemd-journal
hello,
i am again. i tcpdump the port.
tcpdump -pni any -c1024 -s0 -w /tmp/journal.pcap tcp port 19531
i check the capture size after the cpu load is at 100%.
but the size doesnt increase after the systemd-journal use 100 %cpu.
=> i think it isnt the connection to the "client".
i disconnect the
Hello,
wow thanks for the answer, reco.
i ve some more information.
lsof -Pnp (pid from systemd-journal)
lsof -Pnp 1424
systemd-j 1424 systemd-journal-gateway0r CHR1,3 0t0
1028 /dev/null
systemd-j 1424 systemd-journal-gateway1u unix 0x625ea7cf 0t0
8805 type=STRE
Hi.
On Wed, Jul 01, 2020 at 09:48:00AM +0200, Nico Becker wrote:
> Can somebody give me some hints?
Sure. First, the poll(2) by itself is interesting, but useless if you
don't know what file descriptors 3 and 5 are referring to. So,
lsof -Pnp (pid from systemd-journal)
Or at least:
ls
hello,
i use debian 9 stretch (arm) for an small embedded project.
i install the systemd-journal-remote to read the log messages from the
browser.
all the time i get an very high cpu load from the systemd-journal.
i think it is only if browse the syslog messages on
http://ip_address_empedded_de
5 matches
Mail list logo
