Go to primary content
Oracle® Communications EAGLE Commands Error Recovery Reference
Release 46.8
F11879 Revision 1
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

E2368 Cmd Rej: System busy - try again later

The command cannot be entered because another process is occuring. Table 2-3 shows the conditions and recovery procedures for the various commands that can generate this error message.

Table 2-3 Commands that cannot be entered because another process is running

Commands Issue and Recovery
act/dact-ip-lnk

No other action command can be in progress when this command is entered.

Re-enter the command after all other action commands have completed.

canc-cmd:trm= The command was entered on the same terminal that is running the command to be canceled.
  1. Verify the user and terminal number that has the command to be canceled. Enter the rept-stat-user command.

  2. Perform one of the following:
    • Enter the command from another terminal.

      OR

    • Enter the canc-cmd command without specifying the trm parameter.

rept-stat-xxxx

No other rept-stat-xxxx command can be in progress when this command is issued.

Wait for all rept-stat-xxxx commands to complete, then re-enter the command.

tst-imt

A related IMT command cannot be in progress. Only one Fault Isolation Test or Extended Bit Rate Extenstion Test (BERT) can be active at a time.

An Extended BERT cannot be performed if the init-sys, act-upgrade, init-flash, act-flash, init-network, flash-card or init-card (when initializing multiple cards using the appl parameter) command is running.

Wait for all of the above commands or tests to complete, then re-enter the tst-imt command.

all other commands using this error

Heavy disk activity (e.g. database maintenance or measurement collection) may prevent access to the system.

Action commands (used to change the state of entities within the system) cannot execute because another action command is in progress.

For more information on action commands, refer to the Commands User's Guide.

  1. Wait for some of the disk activity to subside or for the action command to complete.
  2. Re-enter the command that generated this error message.