As of today, when trying to reach asdm on /admin/, I get:
The flash device is in use by another task. The flash device is in use by another task. HTTP/1.1 404 Not Found Date: Thu, 13 Oct 2011 12:19:02 UTC Connection: close Content-Type: text/html
The requested URL /admin/public/index.html was not found on this server.
Debugging does not reveal more information:
asa01# debug http 255
debug http enabled at level 255.
asa01# HTTP: session verified = 
HTTP: processing GET URL '/admin/public/index.html' from host 18.104.22.168
HTTP: authentication not required
HTTP: file not found: public/index.html
ASA 8.2 and ASDM 6.31
I don't see how it's relevant, I tried with a different ASDM image but with no go. I cannot save config either.
On another forum, it was claimed that a logged in user could cause this somehow, but "who" on the device does not show any logged on users.
I think that one of our technicians might have been using the console cable, and possible left without scrolling until the end of a 'show run' - do you think this might have locked the flash?
Could be possible if another user is logged into the firewall, you would need to verify that. "show asp table socket" might help you.
Thanks for the tip, I see various connections there:
Protocol Socket Local Address Foreign Address State
SSL 0001ea8f asa01:443 0.0.0.0:* LISTEN
TCP 0002b5bf asa01:23 0.0.0.0:* LISTEN
TCP 0003ec6f 10.5.5.1:23 0.0.0.0:* LISTEN
TCP 0004ba9f 10.1.0.1:23 0.0.0.0:* LISTEN
TCP 0005ac4f asa01:22 0.0.0.0:* LISTEN
TCP 0006ad7f 10.1.0.1:22 0.0.0.0:* LISTEN
DTLS 00076def asa01:443 0.0.0.0:* LISTEN
TCP 01fd80cf 10.4.4.1:23 0.0.0.0:* LISTEN
TCP 01ff2c6f 10.4.4.1:22 0.0.0.0:* LISTEN
SVC 251248b8 asa01:443 22.214.171.124:5807 ESTAB
SVC_UDP 251294b8 asa01:443 126.96.36.199:5152 CONNECTED
SSL 252129cf 10.4.4.1:443 0.0.0.0:* LISTEN
SSL 2521c88f 10.5.5.1:443 0.0.0.0:* LISTEN
TCP 252cc818 asa01:22 188.8.131.52:50859 ESTAB
TCP 25368a78 asa01:22 184.108.40.206:51189 ESTAB
How can I determine which one it is, and how could it be forced shut?
Yes, we can terminate the sessions, by"
First do :
show asdm session
Pick the session from there, and use:
This would disconnect the session.
It proved to be the left and unfinished "show run" by a colleague of mine. He had to go there and manually press space until it quit.
Could the console session have been killed/resetted too somehow?
Not sure if we can terminate thde console session, but you can definitely set a timeout for it by "console timeout