dopetalk does not endorse any advertised product nor does it accept any liability for it's use or misuse


Our Discord Notification Server invitation link is https://discord.gg/jB2qmRrxyD

Author Topic: System and Webpage Load Slowdowns Diagnostics then a POSSIBLE FIX !  (Read 308 times)

Online Chip (OP)

  • Server Admin
  • Admin
  • Hero Member
  • ****
  • Administrator
  • *****
  • Restrictive
  • *
  • RC Discussion
  • **
  • Private
  • ***
  • Chip
  • *****
  • Join Date: Dec 2014
  • Location: Australia
  • Posts: 7388
  • Reputation Power: 0
  • Chip has hidden their reputation power
  • Gender: Male
  • Last Login:Today at 06:12:47 AM
  • Deeply Confused Learner
  • Profession: IT Engineer now retired
📎 Click on me to view all my attachments
ListAttBBC  |  v6.12  |  2026-09-10  |  Andrew.human & Claude.ai
#FileSizeDownloadsInfoDL
00sluggish-system-transfer-checklist.md5 KB11ℹ️⬇️
01Diagnosing_severe_system_slowdown_SSH_webpages_rsync.pdf  [native]89 KB17ℹ️⬇️
02live-webpage-hang-diagnosis.pdf  [native]21 KB20ℹ️⬇️
03Website under bot attack investigation and FIXED.txt144.9 KB21ℹ️⬇️
04slowdiags_20260925_211747.log2.2 KB2ℹ️⬇️
05slowdiags.bat1.8 KB1ℹ️⬇️
06pathping_128.199.200.202.log291 B1ℹ️⬇️
07pp.bat627 B2ℹ️⬇️
08Forum_Slowdown_Hotspot_Diagnosis.md37.4 KB1ℹ️⬇️
09Forum_Slowdown_Hotspot_Diagnosis.pdf  [native]152.5 KB3ℹ️⬇️
10slowdiags1.9 KB2ℹ️⬇️
11psw.sh1.2 KB2ℹ️⬇️


All the good stuff is im the PDFs.

1, Symptoms: Slow ssh connect, slow webpage loads, MAIN: Dev rsycn pulls dropping to low kbps on .json files and then temp lss of connection (speedtest is fine)

vmstat 1 5
free -m
ps aux --sort=-%cpu | head -15
iostat -x 1 5

this is a beauty, run from NUX/DOSBOX: pathping -n 128.199.200.202

This helped:

 Live  root@forum:19:03:52:~# grep -iE "^KeepAlive|^MaxKeepAliveRequests|^KeepAliveTimeout" /etc/httpd/conf/httpd.conf
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 2

 Live  root@forum:19:07:22:~# sed -i 's/^KeepAliveTimeout 2/KeepAliveTimeout 10/' /etc/httpd/conf/httpd.conf
 Live  root@forum:19:09:31:~# apachectl graceful

Claude: [23/09/2026--20:50:31:204 AEST]

Live hasn't rebooted since Monday morning, so the slowness went away by itself. The single MaxClients line doesn't match today's slowness either. It's from Tuesday 10:40 server time, a day and a half ago. Your server clock also looks about 2 hours behind Sydney, so that's roughly 12:40 AEST on Tuesday.

I doubt the Tuesday hit is the KeepAliveTimeout 10 problem I raised earlier. If holding workers for 10 seconds were starving the server, you'd see MaxClients lines in clusters, not one line in about 36 hours. More likely a short bot burst filled the workers once, mod_reqtimeout and connlimit dealt with it, and the workers were freed again.

So the most likely cause of today's slowness is your carrier link, which is already about 400ms with about 10% loss and sometimes gets worse. That fits a problem that appears and disappears with nothing changed on the server.

These two commands would confirm it:

grep -c MaxClients /var/log/httpd/error_log*        # includes rotated logs: was the Slowloris period full of these, and has it been quiet since?
grep 'Sep 23' /var/log/httpd/error_log | tail -20   # anything logged during today's slow spell

If Sep 23 shows nothing unusual during the slow spell, the server wasn't struggling and the delay was on the network.

The load average is up a bit right now: 3.19 over the last minute on 2 CPUs, against 1.55 over five minutes. That's probably just whatever you're running in the ISE directory, but it's worth knowing in case the slowness comes back soon.




📝 Inline Markdownv4.4 · 2026-09-05

INTENTIONAL DUPE:

Claude: [23/09/2026--20:50:31:204 AEST]

Live hasn't rebooted since Monday morning, so the slowness went away by itself. The single MaxClients line doesn't match today's slowness either. It's from Tuesday 10:40 server time, a day and a half ago. Your server clock also looks about 2 hours behind Sydney, so that's roughly 12:40 AEST on Tuesday.

I doubt the Tuesday hit is the KeepAliveTimeout 10 problem I raised earlier. If holding workers for 10 seconds were starving the server, you'd see MaxClients lines in clusters, not one line in about 36 hours. More likely a short bot burst filled the workers once, mod_reqtimeout and connlimit dealt with it, and the workers were freed again.

So the most likely cause of today's slowness is your carrier link, which is already about 400ms with about 10% loss and sometimes gets worse. That fits a problem that appears and disappears with nothing changed on the server.

These two commands would confirm it:

grep -c MaxClients /var/log/httpd/error_log*        # includes rotated logs: was the Slowloris period full of these, and has it been quiet since?
grep 'Sep 23' /var/log/httpd/error_log | tail -20   # anything logged during today's slow spell

If Sep 23 shows nothing unusual during the slow spell, the server wasn't struggling and the delay was on the network.

The load average is up a bit right now: 3.19 over the last minute on 2 CPUs, against 1.55 over five minutes. That's probably just whatever you're running in the ISE directory, but it's worth knowing in case the slowness comes back soon.


« Last Edit: Yesterday at 09:37:03 PM by Chip »
friendly
0
funny
0
informative
0
agree
0
disagree
0
like
0
dislike
0
No reactions
No reactions
No reactions
No reactions
No reactions
No reactions
No reactions
Our Discord Server invitation link is https://discord.gg/jB2qmRrxyD

Offline smfadmin

  • SMF (internal) Site
  • Chip
  • Sr. Member
  • *****
  • Join Date: Dec 2014
  • Location: Management
  • Posts: 636
  • Reputation Power: 0
  • smfadmin has hidden their reputation power
  • Last Login:Today at 05:24:34 AM
  • Supplied Install Member
(No subject)
« Reply #1 on: Yesterday at 07:49:52 PM »
Topic bumped
friendly
0
funny
0
informative
0
agree
0
disagree
0
like
0
dislike
0
No reactions
No reactions
No reactions
No reactions
No reactions
No reactions
No reactions
measure twice, cut once

Tags:
 


dopetalk does not endorse any advertised product nor does it accept any liability for it's use or misuse





TERMS AND CONDITIONS

In no event will d&u or any person involved in creating, producing, or distributing site information be liable for any direct, indirect, incidental, punitive, special or consequential damages arising out of the use of or inability to use d&u. You agree to indemnify and hold harmless d&u, its domain founders, sponsors, maintainers, server administrators, volunteers and contributors from and against all liability, claims, damages, costs and expenses, including legal fees, that arise directly or indirectly from the use of any part of the d&u site.


TO USE THIS WEBSITE YOU MUST AGREE TO THE TERMS AND CONDITIONS ABOVE


Founded December 2014
SimplePortal 2.3.6 © 2008-2014, SimplePortal