Have a two node deployment running 2.1. M&T is active on the secondary node. Primary node does not populate the dashlets on the home page and when clicking on Context Visibility the page gives an Internal Server Error. On the secondary node all is working OK and I have access to all context visibility. I've promoted the secondary to primary and rebuilt the original primary but still receive the error. Application Status shows the Indexing Engine process running. However when I stop/start the ISE processes, the Indexing Engine gave a failed to start error. But it still show up as running on a subsequent status check. Both ISE nodes have primary and reverse names loaded in DNS.
I've rebuilt, reset and rebooted. How can I troubleshoot this further?
application start ise
Starting ISE Monitoring & Troubleshooting Session Database...
Starting ISE Profiler Database...
Starting ISE pxGrid processes...
Starting ISE Application Server...
Starting ISE Indexing Engine...
ISE Indexing Engine did not start
Starting ISE Certificate Authority Service...
Starting ISE EST Service...
Starting ISE Sxp Engine Service...
Starting ISE Monitoring & Troubleshooting Log Processor...
Starting ISE Monitoring & Troubleshooting Log Collector...
Starting ISE AD Connector...
Note: ISE Processes are initializing. Use 'show application status ise'
CLI to verify all processes are in running state.
| ISE PROCESS NAME | STATE | PROCESS ID |
--------------------------------------------------------------------
| Database Listener | running | 1722 |
| Database Server | running | 65 PROCESSES |
| Application Server | running | 3360 |
| Profiler Database | running | 22123 |
| ISE Indexing Engine | running | 28967 |
| AD Connector | running | 7101 |
| M&T Session Database | running | 28548 |
| M&T Log Collector | running | 30750 |
| M&T Log Processor | running | 30663 |
| Certificate Authority Service | running | 32006 |
| EST Service | running | 2899 |
| SXP Engine Service | running | 3970 |
Thanks.
