 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
This chapter describes messages with the SDX prefix. They are generated by the Session and Resource Control (SRC) process (sdxd), which provides a user interface for deploying Internet services.
Graceful close of BEEP session failed
The Session and Resource Control (SRC) process (sdxd) could not send a request to the SRC server to close a Blocks Extensible Exchange Protocol (BEEP) session. It sends this request when the session becomes unconfigured.
Event: This message reports an event, not an error
notice
The usual cause is that the session was already partially or completely closed.
None required. The sdxd process recovers automatically in this situation.
BEEP initialization failed
The Session and Resource Control (SRC) process (sdxd) could not initialize the Blocks Extensible Exchange Protocol (BEEP), which it uses to connect to an SRC server.
Error: An error occurred
error
An internal software failure might have occurred.
Notification channel could not be started (error-code): message
The indicated Blocks Extensible Exchange Protocol (BEEP) channel could not be started for the indicated reason.
Event: This message reports an event, not an error
error
The usual cause is an abnormal operation, which might be described in the system log message.
Connection to SDX server failed: message
The Session and Resource Control (SRC) process (sdxd) could not connect to an SRC server for the indicated reason.
Event: This message reports an event, not an error
notice
There was a network problem or the server was not running.
Aborting, unable to run in the background as a daemon: error-message
The Service Deployment System process (sdxd) could not create a version of itself to run in the background as a daemon.
Error: An error occurred
emergency
function-name: error-message
The Service Deployment System process (sdxd) called the indicated function in the event library. The function failed with the indicated error.
Error: An error occurred
error
An internal software failure occurred.
No server keepalives received for three intervals
The Session and Resource Control (SRC) process (sdxd) and SRC server exchange keepalive messages at regular intervals. The process did not receive a keepalive from the server for three consecutive keepalive intervals. In this case, it closes the session and tries to connect to another SRC server.
Event: This message reports an event, not an error
notice
Unable to send keepalive
The Session and Resource Control (SRC) process (sdxd) could not send a keepalive message to the SRC server, which it does periodically to maintain its connection to the server.
Event: This message reports an event, not an error
notice
There might have been a network problem.
management daemon I/O failure: reason
The Service Deployment System process (sdxd) could not read from or write to the management socket that it uses to communicate with the JUNOS management process (mgd).
Error: An error occurred
error
The mgd process might have exited abnormally.
Insufficient memory during operation
The Service Deployment System (sdxd) attempted to allocate memory for an internal object during the indicated operation. The attempt failed.
Error: An error occurred
error
Unable to update process PID file: error-message
The Service Deployment System process (sdxd) attempted to update the file that records its process ID (PID), which serves to prevent multiple instances of sdxd from running simultaneously. The attempt failed.
Error: An error occurred
error
operation failed: error-message
The Service Deployment System process (sdxd) uses Transmission Control Protocol (TCP) sockets for communication with the SRC server. The indicated operation, which might be for socket creation or binding to a local address, failed with the indicated error.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
| Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |