Cisco Services Modules

Introduction

This document describes a problem that occurs when you use the CLI for an Application Control Engine (ACE) 4710 appliance, ACE20, or ACE30 module, and you receive this error message: "write error: No space left on device."

Problem

When you use the CLI for an ACE4710 appliance, an ACE20, or an ACE30 module, an error message, "write error: No space left on device," displays on the screen in one of these three formats:

?No Space left on device? error

# dir disk0:
  332286 Dec 20 2012 03:56:07 messages
grep: write error: No space left on device

           Usage for disk0: filesystem 
                -4611765850192518655 bytes total used
                -599397581558080000 bytes free
                -5211163431750598655 bytes total

# show tech cp: writing `/isan/vegas/logs/tech_details.11337': 
No space left on device
cat: write error: No space left on device
who: write error: No space left on device

In some situations, the previous symptom might also be accompanied by these errors that are triggered after a Fault Tolerance (FT) auto-sync:

NOTE: Configuration mode is enabled on all sessions
`no interface gigabitEthernet 1/4`
*** Context 0: cmd exec error ***
`no interface gigabitEthernet 1/3`
*** Context 0: cmd exec error ***
`no interface gigabitEthernet 1/2`
*** Context 0: cmd exec error ***
`no interface gigabitEthernet 1/1`
*** Context 0: cmd exec error **

The sync failure happens because the /isan internal filesystem is full. This problem might also result in some configuration loss in the standby ACE.

Solution

This problem is caused as a result of software defect Cisco bug ID CSCtx03563 or CSCue38032. Software defect CSCtx03563 is fixed in ACE Software (SW) Versions A4(2.3) and A5(2.0). Software defect CSCue38032 is fixed in ACE SW version A5(3.0).

Note: Do not save the running configuration, and do not reload the ACE while it is in this state. This action might potentially delete the entire configuration. You can confirm if this might occur if you run the show startup-config command. If the output shows the running configuration, it should be safe to reboot. If the startup configuration is missing, then a reboot is not safe.

Please contact the Cisco Technical Assistance Center (TAC) in order to apply the available workaround to your ACE.