Forum Discussion
Terrence
Nimbostratus
NimbostratusManagement Interface has become slow and unresponsive.
As we deploy more and more applications behind our F5 load balancers, the web gui has become slow and unresponsive, sometimes to the point where the gui loses connection to the LTM's. The deployment currently consists of a pair of 3600's in HA running 11.3.0(Build 3131.0), with the following elements deployed:
- 201 virtual servers
- 125 nodes
- 242 pools
- 210 monitors(some might not be active)
- 148 http class profiles
As it stands traffic is not currently being impacted by the issue, however as more objects get moved to the device management becomes more impacted. We are currently peaking at around 10000 active connections, however load does not appear to be the cause as we currently only have ~3000 active connections and the responsiveness is the same.
I know there could be numerous reasons why the management interface is slow, but in the communities experience what is likely to be the cause.
TerrenceAdditionally the slowness isnt isolated to the http gui, tmsh also seems sluggish
Cory_50405Noctilucent
What's the system uptime of your appliances? We've experienced memory leaks in the past with the 11.3 train, but I don't have any of the solution articles off the top of my head to back that up.
Does the slowness also occur on your standby unit, or just the active unit?
nitassEmployee
Additionally the slowness isnt isolated to the http gui, tmsh also seems sluggish
does it happen when accessing gui and tmsh through tmm interface (selfip)?
if not, have you tried to ping mgmt ip? was there any timeout?
just my 2 cents.
TortiAltostratus
how much modules are you running on the systems - only ltm? is the system swapping?
- nitass
for gui, is it slow in every page or only specific page such as pool, node? have you set up dns server ip? is it workable?
for tmsh, when is it slow? is it always slow or just when logging in?
- nitass
as Torti said, can you check what process eats up memory?
- Stefan_Klotz
Cumulonimbus
Hi there, we have the same issue with exactly the same TMOS version 11.3.0. The idea with the memory leakage sound good as our slow response gets slower and slower over time. At the moment it's totally unresponsive on the WebGUI and even the CLI is very very slow. Also for us, both machines are affected. This is what I get from the "top"-command: top - 12:26:55 up 215 days, 10:44, 1 user, load average: 0.04, 0.06, 0.15 Tasks: 231 total, 2 running, 229 sleeping, 0 stopped, 0 zombie Cpu(s): 8.5%us, 3.8%sy, 1.0%ni, 86.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 4060880k total, 4033436k used, 27444k free, 1736k buffers Swap: 1048568k total, 491684k used, 556884k free, 170496k cached
Is there maybe something known in the meanwhile related to this TMOS version? Thank you!
Ciao Stefan :)
- Cory_50405
Try running this from CLI to see if it helps:
bigstart restart httpd tomcat
This should restart the configuration utility
- Stefan_Klotz
Hi Cory, I already tried a "bigstart restart httpd", but without success. Now with your command (restarting the tomcat daemon as well) it also first looks like not solving the issue, but the tomcat will not be displayed on the CLI and takes a few minutes. Hm, the Standby behaves now as usual, but the Active is still unresponsive. Any more ideas? Thank you!
Ciao Stefan :)
- Cory_50405
Did you also restart these daemons on your active unit? If so and it didn't help, a reboot may be the only thing to free up the leaked memory.
