cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
359
Views
0
Helpful
3
Replies

Permission denied for ftp access on OLD HW WSAs

spacemeb
Level 1
Level 1

Hello,

We have some old hardware WSAs which we are receiving permission denied errors. 

The WSAs are running an ancient Asyncos 11.8, we are going to upgrade them soon.

Nevertheless, we need ftp access on these WSAs because the disk is full:

Disk space has exceeded threshold value. Disk usage is above 97 percent.

Recording of reporting events will soon become limited and reporting data may be lost if disk space is not freed up (by removing old logs, etc).

Once disk usage drops below 97 percent, full processing of reporting data will be restarted automatically.

So, we were in the process of deleting some old but the ftp access is denied. 

The telnet is successful so it's not a network issue.

Every time we are trying to login via ftp, we are receiving the following alert on WSA:

An application fault occurred: ('ftpd/main.py authorize|182', "<class 'socket.gaierror'>", '[Errno 8] hostname nor servname provided, or not known', '[ftpd/server.py _run|243] [ftpd/server.py cmd_pass|789]
[ftpd/main.py authorize|182]') fun: <bound method ironport_acl_ftp_channel.cmd_pass of  server: <ftpd.server.ftp_server instance at 0x8101f22d8> current_mode: a addr: ('10.1.100.217', 51779) conn: <sock fd=87/87 domain=2 type=1 at
0x810eb2eb8> session_id: 5 thread_id: 244173 closing: 0 authorized: 0 user: 'admin'>

It seems that it must be a bug, but if anyone else has faced that, please drop a message with recommending actions/advises

 

3 Replies 3

balaji.bandi
Hall of Fame
Hall of Fame

11.8 is quite old and end of support long back - i only suggestion here is upgrade or reboot appliance and test it.

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Hello there!

Rebooting did not help, I am upgrading the appliance right now, so we will see if that helps

amojarra
Cisco Employee
Cisco Employee

Hi

Check this defect please : CSCvr82493 : Bug Search Tool (cisco.com)

 

Workaround:

Make sure that WSA can resolve its own hostname by (1) Adding entry to your DNS srever or (2) Adding a static entry in WSA CLI: dnsconfig > localhosts In some cases WSA needs to be rebooted

 

and the fixed versions are: 12.5.1-011 , 12.0.1-334 , 12.0.1-268

 

 

FYI 11.8 is still supported by us, Feel free to open a new Service Request, if you need any help from Cisco 

 

Regards,

Amirhossein Mojarrad

+++++++++++++++++++++++++++++++++++++++++++++++++++

++++   If you find this answer helpful, please rate it as such  ++++

+++++++++++++++++++++++++++++++++++++++++++++++++++