Cisco ESA - problem accessing GUI

[acleri]

Hi,

we experience problems accessing GUI on our ESA, SSH is working.

Reboot do not solve the problem.

Any suggestions?

Thanks 

Andy

Product: Cisco IronPort C170 Messaging Gateway(tm) Appliance
Model: C170
Version: 11.0.3-251
Build Date: 2019-08-27

[marc.luescherFRE]

Hi there,

try those steps using SSH first:

(Machine mvxx.fmcna.com)> diagnostic

Choose the operation you want to perform:
- RAID - Disk Verify Utility.
- DISK_USAGE - Check Disk Usage.
- NETWORK - Network Utilities.
- REPORTING - Reporting Utilities.
- TRACKING - Tracking Utilities.
- RELOAD - Reset configuration to the initial manufacturer values.
- SERVICES - Service Utilities.
[]> services

Choose one of the following services:
- ANTISPAM - Anti-Spam services
- ANTIVIRUS - Anti-Virus services
- DLP - Cisco Data Loss Prevention services
- ENCRYPTION - Encryption services
- GRAYMAIL - Graymail services
- REPORTING - Reporting associated services
- SBRS - Reputation Engine services
- TRACKING - Tracking associated services
- URLFILTERING - URL Filtering
- EUQWEB - End User Quarantine GUI
- WEBUI - Web GUI
- SMART_LICENSE - Smart Licensing Agent
- ETF - External Threat Feeds
- SDR - Sender Domain Reputation
[]> webui

Choose the operation you want to perform:
- RESTART - Restart the service
- STATUS - View status of the service
[]> restart

Restart command processed. The service Web UI should be up in a moment.

b) try accessing your Web GUI via the https:// protocol instead of http://

-Marc

[acleri]

On ssh I do not have the SERVICES function.

how can I restart the GUI?

thanks

Choose the operation you want to perform:
- RAID - Disk Verify Utility.
- DISK_USAGE - Check Disk Usage.
- NETWORK - Network Utilities.
- REPORTING - Reporting Utilities.
- TRACKING - Tracking Utilities.
- RELOAD - Reset configuration to the initial manufacturer values.
[]>

[marc.luescherFRE]

Looks like you are on an older ESA software Release which does not allow you to restart services.

To check what is/was happening you might need to inspect the status_logs and check for high CPU usage or paging as it can happen on very busy servers that the GUI task is no longer responding.

-Marc

[balaji.bandi]

what is the error you get? what browser you using ? have you tried other browsers ?

Can you post the URL you try to access an error screenshot?

[acleri]

I get the "classic" browser timeout page.

Tried with difference browser but same problem.

[marc.luescherFRE]

Can you check using CLI and ifconfig again if :

a) http is enabled

b) https is enabled

c) asynch API http enabled

d) asynch API https enabled

e) certificate you are using for http traffic (ESA or other)

-Marc

[acleri]

Today we were able to access without doing nothing....
at this point the problem could that an high cpu utilization do not let access to the GUI.
how can we test if the cpu is the problem and which process cause the spike?

[balaji.bandi]

first look at

> status

from command level check

> displayalerts

[Mathew Huynh]

Are you able to show a sanitized output of the gui_logs when you are attempting access by chance?

Thanks,

Mathew