https://bz.apache.org/bugzilla/show_bug.cgi?id=70320
Bug ID: 70320
Summary: ubuntu 26.10 (ARM) CIFS + apache2 high communication
rate
Product: Apache httpd-2
Version: 2.4.68
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: All
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
hi. i am using ubuntu ARM 26.10 for my raspberry pi 4 and i have some problems.
the communication between my NAS and my PI is extremly high after i installed
apache2.
i use as example:
tcpdump -i any -nn -tttt -l -s 0 'ip and host 192.168.8.141' \>\>
/root/network-traffic_141.log
to capture the communication
real example A without apache2 which is ok and legitime looks like that:
2026-11-17 13:45:56.089446 eth0 Out IP 192.168.8.141.45564 \> 192.168.8.1.123:
NTPv4, Client, length 48
2026-11-17 13:45:56.090387 eth0 In IP 192.168.8.1.123 \> 192.168.8.141.45564:
NTPv4, Server, length 48
2026-11-17 13:46:07.165973 eth0 Out IP 192.168.8.141.47108 \>
192.168.8.129.445: Flags \[P.\], seq 360:432, ack 361, win 126, options
\[nop,nop,TS val 1798872647 ecr 180546038\], length 72
2026-11-17 13:46:07.166602 eth0 In IP 192.168.8.129.445 \>
192.168.8.141.47108: Flags \[P.\], seq 361:433, ack 432, win 1357, options
\[nop,nop,TS val 180552182 ecr 1798872647\], length 72
2026-11-17 13:46:07.166672 eth0 Out IP 192.168.8.141.47108 \>
192.168.8.129.445: Flags \[.\], ack 433, win 126, options \[nop,nop,TS val
1798872647 ecr 180552182\], length 0
2026-11-17 13:47:00.289442 eth0 Out IP 192.168.8.141.51915 \> 192.168.8.1.123:
NTPv4, Client, length 48
2026-11-17 13:47:00.290302 eth0 In IP 192.168.8.1.123 \> 192.168.8.141.51915:
NTPv4, Server, length 48
2026-11-17 13:47:08.605973 eth0 Out IP 192.168.8.141.47108 \>
192.168.8.129.445: Flags \[P.\], seq 432:504, ack 433, win 126, options
\[nop,nop,TS val 1798934087 ecr 180552182\], length 72
2026-11-17 13:47:08.606619 eth0 In IP 192.168.8.129.445 \>
192.168.8.141.47108: Flags \[P.\], seq 433:505, ack 504, win 1357, options
\[nop,nop,TS val 180558326 ecr 1798934087\], length 72
2026-11-17 13:47:08.606694 eth0 Out IP 192.168.8.141.47108 \>
192.168.8.129.445: Flags \[.\], ack 505, win 126, options \[nop,nop,TS val
1798934087 ecr 180558326\], length 0
so wide ok. all minute the communication appears between my NAS and my PI.
nothing special...the file is 19kb big after 25min. no problem all is fine
but if the apache2 is installed and running i get that output in ms:
2026-11-17 15:24:33.643119 eth0 In IP 192.168.8.129.445 \>
192.168.8.141.47108: Flags \[.\], seq 5343451:5366619, ack 10401, win 63955,
options \[nop,nop,TS val 181142831 ecr 1804779123\], length 23168
2026-11-17 15:24:33.643223 eth0 In IP 192.168.8.129.445 \>
192.168.8.141.47108: Flags \[.\], seq 5366619:5368027, ack 10401, win 63955,
options \[nop,nop,TS val 181142831 ecr 1804779124\], length 1408
2026-11-17 15:24:33.643257 eth0 Out IP 192.168.8.141.47108 \>
192.168.8.129.445: Flags \[.\], ack 5368027, win 1789, options \[nop,nop,TS val
1804779124 ecr 181142831\], length 0
2026-11-17 15:24:33.643353 eth0 In IP 192.168.8.129.445 \>
192.168.8.141.47108: Flags \[.\], seq 5368027:5379611, ack 10401, win 63955,
options \[nop,nop,TS val 181142831 ecr 1804779124\], length 11584
2026-11-17 15:24:33.643407 eth0 Out IP 192.168.8.141.47108 \>
192.168.8.129.445: Flags \[.\], ack 5379611, win 1789, options \[nop,nop,TS val
1804779124 ecr 181142831\], length 0
2026-11-17 15:24:33.643423 eth0 In IP 192.168.8.129.445 \>
192.168.8.141.47108: Flags \[P.\], seq 5379611:5384411, ack 10401, win 63955,
options \[nop,nop,TS val 181142831 ecr 1804779124\], length 4800
2026-11-17 15:24:33.643452 eth0 Out IP 192.168.8.141.47108 \>
192.168.8.129.445: Flags \[.\], ack 5384411, win 1789, options \[nop,nop,TS val
1804779124 ecr 181142831\], length 0
2026-11-17 15:24:33.643812 eth0 In IP 192.168.8.129.445 \>
192.168.8.141.47108: Flags \[.\], seq 5384411:5395995, ack 10401, win 63955,
options \[nop,nop,TS val 181142831 ecr 1804779124\], length 11584
2026-11-17 15:24:33.643904 eth0 Out IP 192.168.8.141.47108 \>
192.168.8.129.445: Flags \[.\], ack 5395995, win 1789, options \[nop,nop,TS val
1804779125 ecr 181142831\], length 0
2026-11-17 15:24:33.643943 eth0 In IP 192.168.8.129.445 \>
192.168.8.141.47108: Flags \[.\], seq 5395995:5407579, ack 10401, win 63955,
options \[nop,nop,TS val 181142831 ecr 1804779124\], length 11584
2026-11-17 15:24:33.644008 eth0 Out IP 192.168.8.141.47108 \>
192.168.8.129.445: Flags \[.\], ack 5407579, win 1789, options \[nop,nop,TS val
1804779125 ecr 181142831\], length 0
2026-11-17 15:24:33.644017 eth0 In IP 192.168.8.129.445 \>
192.168.8.141.47108: Flags \[.\], seq 5407579:5413371, ack 10401, win 63955,
options \[nop,nop,TS val 181142831 ecr 1804779124\], length 5792
2026-11-17 15:24:33.644056 eth0 Out IP 192.168.8.141.47108 \>
192.168.8.129.445: Flags \[.\], ack 5413371, win 1789, options \[nop,nop,TS val
1804779125 ecr 181142831\], length 0
2026-11-17 15:24:33.644126 eth0 In IP 192.168.8.129.445 \>
192.168.8.141.47108: Flags \[.\], seq 5413371:5419163, ack 10401, win 63955,
options \[nop,nop,TS val 181142831 ecr 1804779124\], length 5792
2026-11-17 15:24:33.644171 eth0 Out IP 192.168.8.141.47108 \>
192.168.8.129.445: Flags \[.\], ack 5419163, win 1789, options \[nop,nop,TS val
1804779125 ecr 181142831\], length 0
2026-11-17 15:24:33.644183 eth0 In IP 192.168.8.129.445 \>
192.168.8.141.47108: Flags \[.\], seq 5419163:5421275, ack 10401, win 63955,
options \[nop,nop,TS val 181142831 ecr 1804779125\], length 2112
2026-11-17 15:24:33.644209 eth0 Out IP 192.168.8.141.47108 \>
192.168.8.129.445: Flags \[.\], ack 5421275, win 1789, options \[nop,nop,TS val
1804779125 ecr 181142831\], length 0
2026-11-17 15:24:33.644574 eth0 In IP 192.168.8.129.445 \>
192.168.8.141.47108: Flags \[.\], seq 5421275:5432859, ack 10401, win 63955,
options \[nop,nop,TS val 181142831 ecr 1804779125\], length 11584
2026-11-17 15:24:33.644639 eth0 Out IP 192.168.8.141.47108 \>
192.168.8.129.445: Flags \[.\], ack 5432859, win 1789, options \[nop,nop,TS val
1804779125 ecr 181142831\], length 0
2026-11-17 15:24:33.644778 eth0 In IP 192.168.8.129.445 \>
192.168.8.141.47108: Flags \[.\], seq 5432859:5448787, ack 10401, win 63955,
options \[nop,nop,TS val 181142831 ecr 1804779125\], length 15928
2026-11-17 15:24:33.644820 eth0 In IP 192.168.8.129.445 \>
192.168.8.141.47108: Flags \[P.\], seq 5448787:5449947, ack 10401, win 63955,
options \[nop,nop,TS val 181142831 ecr 1804779125\], length 1160
2026-11-17 15:24:33.644890 eth0 Out IP 192.168.8.141.47108 \>
192.168.8.129.445: Flags \[.\], ack 5449947, win 1789, options \[nop,nop,TS val
1804779126 ecr 181142831\], length 0
2026-11-17 15:24:33.645045 eth0 In IP 192.168.8.129.445 \>
192.168.8.141.47108: Flags \[.\], seq 5449947:5461531, ack 10401, win 63955,
options \[nop,nop,TS val 181142831 ecr 1804779125\], length 11584
2026-11-17 15:24:33.645102 eth0 Out IP 192.168.8.141.47108 \>
192.168.8.129.445: Flags \[.\], ack 5461531, win 1789, options \[nop,nop,TS val
1804779126 ecr 181142831\], length 0
and so on. the log file without web traffic or really minimalistic one goes in
around 20 min up to 38Mb. as you see the communication is in ms. that produce
high network traffic and the server is really slow. its the 3rd new
installation because i tested something and on an ubuntu 26.10 on an x86
hardware that doesnt appear. all works with the apache server regular and if no
body needs data from the NAS the communication is as it is in real example A.
Do you have some ideas what to do or is that an internal kernel bug for ARM?
any hints what i can do? thx br
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]