Problem connecting to Unisphere on Control Station

We're having a problem with our Control Station. The Unisphere software has lost almost all of its functionality. I can log in to Unisphere as nasadmin or root but I am unable to manage our NS480. Whenever I reboot the control station I receive an error email:

Event Time: Feb 9 14:08:38 2017

Brief Description: System Management Daemon respawning too fast; disabled for 5 minutes.

Full Description:

A daemon (background process) that is required by other programs and tasks that helps manage your Celerra system has unexpectedly terminated. The Master Control Daemon (MCD) has attempted restarting this daemon; however, a threshold has been reached where additional attempts will be suspended for the indicated period of time.

Recommended Action:

To resolve the problem, perform the following:

1. If you are using Unisphere:

Note: If Unisphere is not available, then go to step 2 and use the CLI.

a. Log in as root (requires the root password).

b. To reboot the Control Station, go to the 'Control Station' and 'Control Station Properties', and click the Reboot button.

IMPORTANT: The Reboot operation will disrupt management client access to the Control Station which includes temporary loss of access to the management application, but the normal work flow for Data Movers/blades should continue. Reboot the Control Station when no management clients are connected or inform the clients about the schedule outage.

c. Wait at least five minutes and click the browser Refresh button because management application access was terminated during the Control Station reboot.

d. Log in as nasadmin (or as a user with NAS administrative privileges).

e. To help diagnose the problem, go to 'Events', show the events for the Control Station, and look for error messages that occurred near the date and timestamp of this message.

f. If the problem persists and you continue to receive this message, go to step 3.

2. If you are using CLI:

a. Log in as nasadmin (or as a user with NAS administrative privileges) and "su" to root (requires the root password).

b. Reboot the Control Station by running the "reboot" command.

IMPORTANT: The Reboot operation will disrupt management client access to the Control Station which includes temporary loss of access to the management application, but the normal work flow for Data Movers/blades should continue. Reboot the Control Station when no management clients are connected or inform the clients about the schedule outage.

c. If the client that is used to connect to the Control Station supports a "ping" operation, wait five minutes and perform the following:

i. Run the "ping " command to determine if the reboot operation has completed.

ii. Continue running the "ping" command until the Control Station is contacted.

iii. Press Ctrl+C to exit the "ping" command, and then reconnect to the Control Station.

d. To help diagnose the problem, run "nas_logviewer -v /nas/log/sys_log | less" command and look for logged error messages that occurred near the date and timestamp of this message.

Note: Based on when the event occurred, the log messages for this particular event may be located in other generations of the sys_log file (for example, sys_log.1, sys_log.2, through sys_log.10).

3. If the problem persists and you continue to receive this message, search the Knowledgebase on Powerlink as follows:

a. Log in to http://powerlink.emc.com and go to Support > Knowledgebase Search > Support Solutions Search.

b. Use the message ID or text from the error message's brief description to search.

Celerra Name: wbwglnpxemc01.warnerbros.com (10.130.244.27)

Celerra Model: NS-480FC

Celerra Serial #: APM00095201026

NAS Version: 6.0.70-4

Severity: EMERGENCY

Component: CS_PLATFORM

Facility: MasterControl

Message ID: 70338543631

I have tried rebooting the CS, Data Movers, SP's and have confirmed that we are not out of disk space on the CS per many troubleshooting posts I have found. When I run #./nas_cs -info on the CS I get the following response - Critical 0: Query control stations.

I have run Nas_checkup & server_checkup and the results, other then some SSL error messages, seem normal to me. These are a sample of the SSL Error's:

Warning 17456169084: server_2 : The SSL feature 'DHSM' can not get certificate from the persona default. Because this feature needs a certificate and a private key, it can not start,