WSA-S170 filesystem full

[keithsauer507]

I already opened a ticket with TAC on this, but curious while I wait for them to get back to me, has anyone ever encountered this?

When you try to access the WSA configuration webpage you get:

Error Response

Error code 500: Server got itself in trouble: The application raised an exception.

Then if you try to either SSH or console in via serial you get

AsyncOS 8.8.0 for Web build 085

Welcome to the Cisco S170 Web Security Appliance

/data: write failed, filesystem is full
Please wait while appliance services start up...

Then (if SSH) it disconnects (if serial) it displays this:

Please wait while appliance services start up..............................Trace back (most recent call last):
File "/usr/build/iproot/ap/ipoe/ipoe/bootstrap.py", line 55, in <module>
File "/data/lib/python2.6_9_amd64_nothr/runpy.py", line 128, in _run_module_as _main
"__main__", fname, loader, pkg_name)
File "/data/lib/python2.6_9_amd64_nothr/runpy.py", line 34, in _run_code
exec code in run_globals
File "build/bdist.freebsd-9.2-RELEASE-amd64/egg/cli.py", line 537, in <module>
File "build/bdist.freebsd-9.2-RELEASE-amd64/egg/external_auth/__init__.py", li ne 207, in initialize

File "build/bdist.freebsd-9.2-RELEASE-amd64/egg/external_auth/__init__.py", li ne 119, in _setup_old_authentication

File "build/bdist.freebsd-9.2-RELEASE-amd64/egg/command_client.py", line 718, in quick_read_var
File "build/bdist.freebsd-9.2-RELEASE-amd64/egg/command_client.py", line 172, in connect
Commandment.CommunicationError: : Network communication e rror: Connection refused

and when you push enter it returns to login prompt.

[keithsauer507]

A reboot regains access to the webgui and cli / ssh, however the reporting disk was 106% full.  Rotated logs, got it down to 101% full (how can it be over 100 is anyones guess).

Still could not make any changes like activate FTP to retrieve logs (traceback crash occurs), or enable tunnel access for Cisco support (says /data: write failed, filesystem is full and boots you out).

Ended up doing a deletedb command to delete the reporting database.  Got the reporting disk down to 84% full.  Still could not activate FTP or tunnel access (module crashes).  Next day come in and the disk is 101% full.  Rotate all logs and do another delete db and only can get it down to 100%.

Cisco TAC is really slow and unacceptable.  The case was open Tuesday and the problem is still happening Thursday.  Anyone else on here with experience with this unit know how to access the root filesystem in asyncos so i can see where all this space is taken up from?

[Atazazuddin Shaikh]

Good Morning Keith

Thanks for reaching out, access to WSA file system is only open for TAC engineers - DE team at this time.  sorry for delay in response from TAC team.  I  have  requested TAC engineer to reach out to you ASAP re. SR # 637313711, and provide assistant.

Thanks
Zack

[keithsauer507]

Thank you for the response.  Look forward to getting it resolved.  They did try enabling the remote tunnel but could not conect.  I tried again today via the serial CLI and it just says /data full and logs me out.

If we cannot get the remote tunnel enabled for TAC to access the filesystem, I just hope there is another procedure in place, maybe via webex to a machine running putty with the serial console cable connected.  You have to at least build these devices to have a form of access locally if software or hardware prohibits remote access.

RMA was an option but I don't think its the correct option.  It simply says /data is full, so why spend the money to ship out a new device (and our time reconfiguring / rack and stack) when the existing hardware works, its just a software problem.