The USP trace process (nstraced) could not allocate the indicated number of bytes of memory.
The problem related to this syslog message is described in the following sections:
The NSTRACED_MEMORY_ALLOC_FAILED message is logged each time the nstraced process fails in its attempt to allocate memory.
When a NSTRACED_MEMORY_ALLOC_FAILED event occurs, a message similar to the following is reported:
mstraced: NSTRACED_MEMORY_ALLOC_FAILED: Unable to allocate <count> bytes of memory
The cause is due to system memory being exhausted. There is not sufficient memory available for allocation.
Examine the following output to help determine the cause of this message:
show log messages
show log nsd_chk_only
show system processes extensive
Look for any related events that occurred at or just before the NSTRACED_MEMORY_ALLOC_FAILED message. For example, there may be another process that is using a substantial portion of memory. The system processes output will show how much memory is being used by the processes JunOS is running. The nsd_chk_only file is overwritten each time you perform a commit check and contains detailed failure information.
Perform these steps:
- During a maintenance window, as it will impact transit traffic, try rebooting the router to force its internal tables to be rebuilt. This may free up enough memory to resolve the issue.
- Increase that amount of memory installed in the routing engine.
- If the failure messages continue, open a case with your technical support representative to investigate the issue further.