search cancel

Management Center unable to connect to Reporter with "Unknown Error"

book

Article ID: 253233

calendar_today

Updated On:

Products

Management Center Management Center - VA

Issue/Introduction

Management Center unable to connect to Reporter with "Unknown Error"

Environment

Management Center and Reporter running supported version 

Cause

Reporter  is in inactive or failed state. 

reporter# reporter-status
    inactive (dead) since Mon 2022-10-31 10:32:12 UTC; 4s ago
reporter#

reporter# reporter-status
    failed (Result: exit-code) since Mon 2022-10-31 10:39:59 UTC; 32min ago
reporter#

Management Center requires Reporter service to be in active (running) state to be managed.

e.g.

reporter# reporter-status
    active (running) since Mon 2022-10-31 11:38:32 UTC; 2s ago
reporter#

Resolution

Options:

If service is simply stop, start it

start-reporter

If service is in failed state, restore to previous settings

restore-settings ? 

Note: You'll need to stop-reporter prior restore-settings, then start the service.   Run reporter-status again to see if the backup settings chosen worked. 

If nothing worked from your restore settings, you may need to rebuild your Reporter by restoring Reporter to factory defaults or spin a new reporter virtual machine.  You must build a new database using the new access logs from your ProxySGs.   Creating a database that would report previous dates is only possible if you have  backups of raw access logs located on different server (FTP, http, etc.)

 

Attachments