Lost management after upgrade to 8.0.7 S170 WSA

[support0197]

No access the web GUI via HTTPS and was also not able to SSH to the box.

AsyncOS 8.0.7 for Web build 142

Welcome to the Cisco S170 Web Security Appliance
Please wait while appliance services start up..............................Traceback (most recent call last):
  File "/usr/build/iproot/ap/ipoe/ipoe/bootstrap.py", line 55, in <module>
  File "/data/lib/python2.6_8_amd64_nothr/runpy.py", line 128, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/data/lib/python2.6_8_amd64_nothr/runpy.py", line 34, in _run_code
    exec code in run_globals
  File "build/bdist.freebsd-8.2-RELEASE-amd64/egg/cli.py", line 497, in <module>
  File "build/bdist.freebsd-8.2-RELEASE-amd64/egg/external_auth/__init__.py", line 207, in initialize
    
  File "build/bdist.freebsd-8.2-RELEASE-amd64/egg/external_auth/__init__.py", line 119, in _setup_old_authentication
    
  File "build/bdist.freebsd-8.2-RELEASE-amd64/egg/command_client.py", line 674, in quick_read_var
  File "build/bdist.freebsd-8.2-RELEASE-amd64/egg/command_client.py", line 133, in connect
Commandment.CommunicationError: wsa.myth.com: Network communication error: Connection refused

AsyncOS wsa.myth.com (cuau0)

[Handy Putra]

Hi,

Does the traceback message occurs after you perform upgrade to 8.0.7 version and after the reboot process? or did you perform reboot in the appliance? if its reboot, did you hard reboot or graceful reboot (using reboot command from CLI)?

The traceback message normally occurs after the appliance was rebooted (not graceful reboot) and looks like its in race condition to run the boot sequence.

Can you try to log in via SSH and use "enablediag" as username instead of admin and use your usual admin password then issue reboot command to gracefully reboot the appliance.

or are you able to access to the appliance via console connection (connect directly to the physical appliance)?