NimbostratusHello all,
We've been encountering numerous instances where GUI page would be very slow to load and sometimes lead to crash. Workaround is always restarting the tomcat httpd services but frequency has been increasing recently. I have a SOL article pointing it memory leaks to be the case but it was also stated in there that it was already fixed in 11.4.0. We are currently in 11.6.0. Anyone experiencing same issue>
Also run
tmsh show sys memory/Patrik
NimbostratusYeah, this is not pre-installed in F5.
That might bite you in the a** if you call F5 support. Just some heads up. :)
/Patrik
NimbostratusI see..
Now, to make this thread even more full of juicy information, could you please provide the output from
tmsh show sys memory/Patrik
NimbostratusMaybe I'll just this privately to you this time. :)
That's an insane system you got there, and it does not looks like it's taxed in terms of memory in the TMM either. If I were you I'd uninstall the splunkd daemon and contact F5 (or if you're courageous, don't and call them anyway).
Please feel free to post the solution here later? Sorry that I can't do more.
/Patrik
NimbostratusYeah, I will update this one in case I get to find the solution. You've helped so much already. Thanks!
NimbostratusHello,
I've Been reading this case & I'm exactly in the same situation. WebGUI becomes unusable, it works when restarting httpd service "bigstart restart httpd"
SSH is fine bug HTTPS is slow & Goes down after seconds.
MVPYazid,
This would happen when some resource is eating the memory. Can you open a F5 case and upload the qkview for them to review.
NimbostratusHello Yazid/everyone,
Apologies for not updating this thread before, but what we managed to do to stop the crash of webui was adding additional parameters in /etc/tomcat/server.xml:
redirectPort="8443"
enableLookups="true"
address="127.0.0.1"
maxParameterCount="32500"
maxConnections="10" <==== Add this parameter to match the Apache MaxClients value
keepAliveTimeout="5000" <=====Add this parameter to define a timeout of 5000 milliseconds (or whatever value you want to use)
tomcatAuthentication="false" />
And then restart httpd and tomcat service.
Hope this helps!
CumulonimbusHi dude,
I alredy had this kind of behaviour, I advise you to modify "management ressource provisioning"
-Go to : System ›› Resource Provisioning : Module Allocation - For Management (MGMT) module switch from small to large. it will help you improve the fluidity of the GUI.
For information I had encounter this behaviour because of Large configuration embeded on the same device (ASM, APM, LTM...).
Let me know if this tips help you.
Regards