A couple of KAs I would suggest you to review:
Tried it no luck, our remedy version is 8.1, no luck yet. I restarted plugins, it didn't help either. What could be the issue.
Have you gathered AR API+SQL logs during the use case to see what SQL is timing out?
So you are getting the error only while accessing the Server Information Page.
Did you capture the error logs upon the Page/Tab Selection?
Please get the AR, API+SQL Logs, there should be some clue from the logs.
I can't turn on any logs because the server information page is not accessible. How do I turn on the logs if the server Information page is not accessible?
1 of 1 people found this helpful
You can do that by changing the debug-mode values from the ar.cfg and restart the ARSystem server.
If you can restart, that try that.
Debug-mode has multiple value options
SQL - 1
Filter - 2
User - 4
Escalation - 8
API - 16
Thread - 32
For API+SQL its 16 + 1 = 17 i.e. Debug-mode: 17
Let me know if this helps.
Can you please post arerror.log and arjavaplugin-stderr log files? and also attach ar configuration file (ar.cfg) as well.
Can you share thread details from ar.cfg ?
I have seen rare cases where thread details are removed from ar.cfg and user cannot login at all.
In your ar.cfg/ar.confm ensure this value is set:
Plugin: ServerAdmin.dll (if windows)
Plugin: ServerAdmin.so (if linux)
Truncating ft_pending worked. ft_pending had 340+ Million rows.
Good catch, ensure to disable FTS indexing if you don't need it or else ft_pending table will pile up again