 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
This chapter describes messages with the UI prefix. They are generated by the JUNOS command-line interface (CLI) and management process (mgd), which together form the JUNOS user interface that accepts and processes input from users and client applications.
Authenticated user 'username' at permission level 'authentication-level'
The management process (mgd) authenticated the indicated user.
Event: This message reports an event, not an error
info
Received invalid authentication challenge for user 'username': response
When a user logs onto the routing platform and attempts to authenticate, the CLI and management process (mgd) use a challenge-and-response system to limit the exposure of sensitive information such as passwords and keys. The format of the challenge generated by mgd was incorrect.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Unable to fetch boot time: error-message
The management process (mgd) could not retrieve the system boot time from the kernel.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
User 'username' action: pathname new-name
The indicated user created a new configuration object by copying or renaming an existing object as indicated.
Event: This message reports an event, not an error
info
User 'username' action: pathname delimitervalue
The indicated user deleted, activated, or deactivated a configuration object, as indicated. The JUNOS configuration log facility logged the change.
Event: This message reports an event, not an error
info
User 'username' action: pathname delimiterdata -> "value"
The indicated user set a value for a configuration object, as indicated.
Event: This message reports an event, not an error
info
User 'username' action: pathname
The indicated user set a value for a configuration object, as indicated. For security, the actual value (which might be an authentication key or password, for example) is not recorded.
Event: This message reports an event, not an error
info
Too many arguments for child process 'command'
The management process (mgd) invokes some commands on behalf of users. It supplied more arguments than the command's syntax statement specifies.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Unable to switch to local user: username
The management process (mgd) invokes some commands on behalf of users. Its attempt to adopt the UID of the indicated user failed.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Child exec failed for command 'command': error-message
The management process (mgd) invoked the exec() system call while creating a child processes to execute the indicated command on its behalf. The system call failed.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Child exited: PID pid, status return-valuecore-dump-status, command 'command'
The management process (mgd) created a child process to execute the indicated command for it. The child process exited unexpectedly with the indicated status code.
Error: An error occurred
notice
An internal software failure occurred.
Contact your technical support representative.
Unable to append to log 'filename': error-message
The management process (mgd) attempted to save the output from a command in the indicated log file, but could not open the file.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Unable to create pipe for command 'command': error-message
The management process (mgd) created a child process to execute the indicated command for it. Its attempt to create pipes for communication with the child process failed.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Child stopped: PID pid, signal=signal-namecore-dump-status, command='command')
The management process (mgd) created a child process to execute the indicated command for it. The child process received the indicated signal and stopped.
Error: An error occurred
notice
An internal software failure occurred.
Contact your technical support representative.
waitpid failed: PID pid, rc return-value, status status-code: error-message
The management process (mgd) created a child process to execute a command for it. It could not wait for the child process to finish.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
User 'username', command 'command'
The indicated user typed the indicated command at the CLI prompt and pressed the Enter key, sending the command string to the management process (mgd).
Event: This message reports an event, not an error
info
Invalid 'allow-deny' command authorization regular expression 'regular-expression': error-message
An operation that attempted to set command or configuration authorization included the indicated regular expression. The operation failed because the expression syntax was invalid.
Error: An error occurred
error
Correct any errors in the regular expression.
User 'username' requested 'command' operation (comment: message)
The indicated user requested the indicated type of commit operation on the candidate configuration and added the indicated comment. The 'commit' operation applies to the local Routing Engine and the 'commit synchronize' operation to both Routing Engines.
Event: This message reports an event, not an error
notice
reason, will try again
An attempt to complete a pending commit operation was cancelled for the indicated reason.
Error: An error occurred
error
'commit at' was successful
Changes to the candidate configuration were activated at the time scheduled by a 'commit at' operation.
Event: This message reports an event, not an error
notice
reason, scheduled commit cleared
A 'commit at' operation did not complete, for the indicated reason.
Error: An error occurred
error
Unable to compress file 'filename'
As part of committing a new configuration, the management process (mgd) compresses and saves a copy of the configuration. mgd saved the configuration file in regular format because it could not compress it.
Error: An error occurred
error
The Routing Engine is low on resources.
An internal software failure occurred.
Contact your technical support representative.
'commit confirmed' must be confirmed within duration minutes
A 'commit confirmed' operation has activated the candidate configuration temporarily. If the commit is not confirmed within the indicated number of minutes (for example, by the command-line interface (CLI) 'commit' command), the management process (mgd) will roll back to the previous configuration.
Event: This message reports an event, not an error
notice
Skipped empty object 'node-name'
Some container objects are marked for automatic removal from the configuration hierarchy if they are empty when the user who created them changes to the top ([edit]) level of the hierarchy or exits configuration mode. While committing the candidate configuration, the management process (mgd) encountered such an object that was empty but not removed.
Event: This message reports an event, not an error
info
When the commit operation began, the user who created the new container object had not populated it and was in configuration mode but not at the top level of the hierarchy.
Populate or remove the empty object before committing the configuration. The user who created the object can remove it by exiting configuration mode or issuing the 'top' command to move to the top level of the hierarchy.
Commit was not confirmed; message
The 'commit confirmed' operation commits a configuration but requires confirmation within a defined number of minutes for the commit to become permanent. If the commit is not confirmed (by the 'commit' command, for example), the management process (mgd) automatically rolls back to the previously committed configuration. The automatic rollback restores management access to the routing platform in case an error in the configuration blocks access.
Event: This message reports an event, not an error
notice
Commit operation in progress: message
As it performed a commit operation, the management process (mgd) recorded its execution of the indicated step.
Event: This message reports an event, not an error
info
Automatic rollback failed
The 'commit confirmed' operation commits a configuration but requires confirmation within a defined number of minutes for the commit to become permanent. If the commit is not confirmed (by the 'commit' command, for example), the management process (mgd) automatically rolls back to the previously committed configuration. The 'commit confirmed' operation was not confirmed, but mgd could not roll back the configuration. The configuration might be in an indeterminate state.
Error: An error occurred
error
The cause of the problem might be recorded in messages that precede this message in the system log.
All logins to local configuration database were terminated because forced 'commit synchronize' operation was invoked on other Routing Engine
The 'commit synchronize force' command was issued on the other Routing Engine on the router. All login sessions in the local configuration database were terminated and the configuration from the other Routing Engine was committed on the local Routing Engine.
Event: This message reports an event, not an error
notice
Process: process-name, path: pathname, statement: configuration-statement, error-message
The indicated process found a problem in its configuration.
Error: An error occurred
error
Process: process-name, path: pathname, statement: configuration-statement, warning-message
The indicated process found a problem in its configuration.
Error: An error occurred
warning
connection-type socket connection accept failed: error-message
The management process (mgd) did not accept an incoming connection request.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Unable to create session child: error-message
The management process (mgd) invokes the fork() system call to create a copy of itself for each CLI session. The system call failed.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
select failed: error-message
The management process (mgd) uses the select() system call to listen for incoming connection requests on a socket. The system call failed.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
connection-type socket create failed: error-message
The management process (mgd) uses sockets to communicate with other JUNOS software processes running on the routing platform. It could not allocate a socket.
Error: An error occurred
error
System resources are exhausted.
Contact your technical support representative.
Unable to reaccess configuration database file 'filename', address address, size size: reason
To increase the size of the configuration database, the management process (mgd) must unmap the database from its address space, change the database size, and remap the database. The remapping operation failed.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Database 'filename' is out of data and needs to be rebuilt
When the routing platform boots, the management process (mgd) checks the configuration database for internal consistency. It found one or more inconsistencies.
Event: This message reports an event, not an error
alert
mgd restarted after new JUNOS software was installed.
None; mgd will rebuild the database.
Unable to extend configuration database file 'filename' to size requested-size: reason
The management process (mgd) could not increase the configuration database to the indicated size.
Error: An error occurred
error
The hard disk is defective or is not installed in the routing platform.
Repair or replace the hard disk.
There is insufficient disk space on the /var partition on the hard disk.
Delete user files from the /var/homes directory to increase the available disk space.
User 'username' entering configuration mode
The indicated user entered configuration mode (logged into the configuration database).
Event: This message reports an event, not an error
notice
User 'username' exiting configuration mode
The indicated user exited configuration mode (logged out of the configuration database).
Event: This message reports an event, not an error
notice
Database header extent mismatch for file 'filename': expecting expected-value, got received-value
The header in the configuration database records the highest address allocated in the database. The management process (mgd) discovered that the highest address actually allocated in the database does not match the header value.
Error: An error occurred
error
The database file is corrupted.
Contact your technical support representative.
Database header major version number mismatch for file 'filename': expecting expected-value, got received-value
For compatibility, the version number recorded in the header of the configuration database must match the version of JUNOS software running on the routing platform. The management process (mgd) discovered that the major parts (for example, '5' in '5.x') of the version numbers do not match.
Error: An error occurred
error
A recent software upgrade did not complete successfully.
Issue the 'show version' command to check the JUNOS version. If necessary, issue the 'request system reboot' command to reboot the routing platform and complete the software installation.
The database file is corrupted.
Contact your technical support representative.
Database header minor version number mismatch for file 'filename': expecting expected-value, got received-value
For compatibility, the version number recorded in the header of the configuration database must match the version of JUNOS software running on the routing platform. The management process (mgd) discovered that the minor parts (for example, '2' in 'x.2') of the version numbers do not match.
Error: An error occurred
error
A recent software upgrade did not complete successfully.
Issue the 'show version' command to check the JUNOS version. If necessary, issue the 'request system reboot' command to reboot the routing platform and complete the software installation.
The database file is corrupted.
Contact your technical support representative.
Database header sequence numbers mismatch for file 'filename'. If a package has just been added or deleted, please verify and commit the configuration.
The header of the configuration database records the version number of the configuration schema (possible set of statements) used when the database was created. To prevent corruption, all JUNOS processes that access the database must use the same schema. The management process (mgd) discovered that the version number for the JUNOS software installed on the routing platform does not match the header value.
Error: An error occurred
warning
A recent software upgrade did not complete successfully.
Issue the 'show version' command to check the JUNOS version. If necessary, issue the 'request system reboot' command to reboot the routing platform and complete the software installation.
The database file is corrupted.
Contact your technical support representative.
Database header size mismatch for file 'filename': expecting expected-value, got received-value
The header of the configuration database records the database size. The management process (mgd) discovered that the size of the actual database file does not match the header value.
Error: An error occurred
error
The database file is corrupted.
Contact your technical support representative.
Database open failed for file 'filename': reason
The management process (mgd) could not open the indicated configuration database file.
Error: An error occurred
error
The database file does not exist.
Select a different filename or create a new configuration.
The /config directory does not have sufficient space for a new database.
Remove files from the /config directory to make more space available.
modeusername rebuild of the database 'filename' failed
The management process (mgd) could not rebuild the configuration database file.
Error: An error occurred
alert
An internal software failure occurred.
Contact your technical support representative.
Automatic rebuild of the database failed
The management process (mgd) could not rebuild the schema for the configuration database.
Error: An error occurred
alert
An internal software failure occurred.
Contact your technical support representative.
modeusername rebuild/rollback of the database 'filename' started
The management process (mgd) began to rebuild the configuration database file or its schema because that object was not current. The operation will complete shortly.
Event: This message reports an event, not an error
alert
User 'username' attempting database re-creation
The management process (mgd) discovered that the version of JUNOS software running on the routing platform does not match the version of the current configuration database. In response to a prompt from mgd, the indicated user initiated a rebuilding of the database.
Event: This message reports an event, not an error
notice
Reopen of the database failed
After rebuilding the schema file for the configuration database, the management process (mgd) closes the file and reopens it in read-only mode to prevent corruption. It could not reopen the file.
Error: An error occurred
alert
An internal software failure occurred.
Contact your technical support representative.
Users username1 and username2 have the same UID uid
The JUNOS software allows multiple user login accounts to share the same UID. This message was logged in case site policy dictates that users should not share UIDs.
Event: This message reports an event, not an error
notice
Assign different UIDs to the affected users.
Committing factory default configuration because CONFIG button was pressed and held
The management process (mgd) began a commit operation to activate the factory default configuration, because the CONFIG button on the chassis was pressed and held for 15 seconds or more.
Event: This message reports an event, not an error
notice
Committing EZsetup configuration as EZsetup option is chosen
The management process (mgd) began a commit operation to activate the pre initial setup configuration, because the initial-setup option was selected from the LCD Menu.
Event: This message reports an event, not an error
notice
invalid permissions from authorization server: permission-name
RADIUS and TACACS+ authorization servers use Juniper Networks vendor-specific attributes (VSAs) to specify user permissions. A VSA included the indicated permission name, which is invalid.
Error: An error occurred
error
User 'username' used JUNOScript client to run command 'command'
The indicated user ran the indicated command using the JUNOScript application programming interface (API).
Event: This message reports an event, not an error
info
JUNOScript error: error-message
The management process (mgd) normally sends an error message to the JUNOS CLI or JUNOScript API client in an <xnm:error> tag. It could not send the tag, so it sent the indicated error message in an XML comment instead.
Error: An error occurred
warning
No master Routing Engine defined for LCClcc
By default, the JUNOS software installed on the TX Matrix platform in a routing matrix is automatically copied to and installed on all T640 routing nodes in the routing matrix. The software was not installed on the indicated T640 routing node (line-card chassis, or LCC), because the management process (mgd) on the TX Matrix platform could not determine which Routing Engine on the LCC was the master.
Error: An error occurred
error
Resolve the mastership situation on the T640 routing node and install the software on its Routing Engines.
User 'username' is performing a 'operation'
The indicated user requested the indicated operation ('rollback, ' or 'load' or one of its variants) on the configuration database. The existing configuration database was deleted and a new database was created based on a text file.
Event: This message reports an event, not an error
notice
Loading the default config from pathname
The system is loading junos default configuration from file.
Event: This message reports an event, not an error
info
User 'username' login, class 'class-name' local-peer[pid]
The indicated user started a JUNOS CLI session.
Event: This message reports an event, not an error
info
User 'username' logout
The indicated user exited from a JUNOS CLI session.
Event: This message reports an event, not an error
info
Lost connection to daemon 'process-name'
The management process (mgd) uses sockets to communicate with other JUNOS software processes. The socket it was using for the indicated process closed prematurely.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
mastership-event card-name mastership by 'username'
Some redundant routing platform components use a master/standby system in which the master component is active and the standby is inactive but ready to assume mastership. The indicated user performed the indicated operation to modify component mastership.
Event: This message reports an event, not an error
warning
Terminating operation: exit status return-value
The management process (mgd) encountered an error and exited, returning the indicated code as its exit status code.
Error: An error occurred
error
The cause of the problem might be recorded in messages that precede this message in the system log.
Unable to propagate login announcement (motd) to pathname
The management process (mgd) could not create or write to the indicated file, which was the intended location for the message of the day (MOTD) configured at the [edit system login announcement] hierarchy level.
Error: An error occurred
error
User 'username' used NETCONF client to run command 'command'
The indicated user ran the indicated command using the NETCONF application programming interface (API).
Event: This message reports an event, not an error
info
NETCONF error: error-message
The management process (mgd) normally sends error messages to the NETCONF client in the <rpc-error> tag element. It could not send that tag element, and instead sent the indicated error message in an XML comment.
Error: An error occurred
warning
Error parsing attributes in client junoscript tag
The management process (mgd) encountered an error and exited while attempting to parse the XML attributes in the <junoscript> tag submitted by a client application.
Error: An error occurred
error
read failed for peer peer-name: error-message
The management process (mgd) uses the read() system call to access data sent by other JUNOS processes running on the routing platform (referred to as its peers). The system call failed for the indicated process.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Timeout on read of peer 'peer-name'
When communicating with other JUNOS processes running on the routing platform (referred to as peers), the management process (mgd) waits only a defined period for responses to arrive. The timeout period passed for the indicated process.
Event: This message reports an event, not an error
notice
System halt-reboot by 'username'
The indicated software process restarted as requested by the indicated user.
Event: This message reports an event, not an error
warning
Committing rescue configuration because CONFIG button was pressed
The management process (mgd) began a commit operation to activate the rescue configuration, because the CONFIG button on the chassis was pressed.
Event: This message reports an event, not an error
notice
User 'username' restarting daemon 'process-name'description
The indicated software process restarted as requested by the indicated user.
Event: This message reports an event, not an error
warning
Schema is out of date and needs to be rebuilt
The JUNOS user interface schema file records all CLI commands and configuration statements available in the JUNOS software. While initializing, the new management process (mgd) determined that the schema's sequence number means that the schema is incompatible with the JUNOS software installed on the routing platform.
Error: An error occurred
alert
The schema is out of date.
None; mgd will rebuild the schema based on the current JUNOS version.
Schema major version mismatch for package package-name (expected-value vs. received-value)
The JUNOS user interface schema file records all CLI commands and configuration statements available in the JUNOS software. While initializing, the management process (mgd) discovered that the major part (for example, '5' in '5.x') of the schema version number does not match the major version number of the JUNOS software installed on the routing platform. The mismatch could lead to corruption of the configuration database.
Error: An error occurred
error
The schema is incompatible with the installed JUNOS software.
None; mgd will rebuild the schema based on the current JUNOS version.
An internal software failure occurred.
Contact your technical support representative.
Schema header sequence numbers mismatch for package package-name
The JUNOS user interface schema file records all CLI commands and configuration statements available in the JUNOS software. Schema sequence numbers serve as a checksum of the configuration data schema and ensure that the software used to access the database understands the data. The value in the database file did not match the expected value.
Error: An error occurred
error
The JUNOS software installation did not succeed, possibly because of an internal software error.
Contact your technical support representative.
Schema sequence number mismatch
The JUNOS user interface schema file records all CLI commands and configuration statements available in the JUNOS software. The management process (mgd) rebuilds the schema as necessary to be compatible with the JUNOS software installed on the routing platform. A sequence number in the schema acts as a checksum that represents its content and format. A JUNOS process attempted to access the schema but determined that the schema's sequence number means that it is incompatible with the process.
Error: An error occurred
alert
An internal software failure occurred.
Contact your technical support representative.
TACACS+ failure: error-message
The management process (mgd) failed to send a record to TACACS+.
Error: An error occurred
notice
Unable to fetch system version: error-message
The management process (mgd) could not retrieve version information from the kernel.
Error: An error occurred
error
Contact your technical support representative.
Re-establishing connection to peer 'peer-name'
The management process (mgd) reconnected to the indicated JUNOS process running on the routing platform.
Event: This message reports an event, not an error
notice
| Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |