The following messages are written to the Dpush log file. Each message contains a time stamp in the form "MMM dd hh:mm:ss" followed by the message text. The messages are listed below in alphabetic order .

CDS proprietary data requested
Meaning: Identifies the NDS version of Dpush.
Action: This is an informational message. No actions need be taken.

Data check failed on frame.
Meaning: One or more errors were found while checking the frame. The frame is rejected.  See the data checker messages below for an explanation of the reason for the data check failure.
Action: Error resulted in loss of frame. Notify a DMT expert.

Dpush terminating. Error log closed.
Meaning: Dpush is terminating.
Action: This is an informational message. No actions need be taken.

Error getting CID.
Meaning: An error occurred while promoting the data pusher to real-time priority.
Action: This is a non-fatal error. It should be reported by E-mail to a DMT expert.

Error setting priority.
Meaning: An error occurred while promoting the data pusher to real-time priority.
Action: This is a non-fatal error. It should be reported by E-mail to a DMT expert.

File output is not supported by Dpush.
Meaning: Indicates that an output file argument was specified, but the current Dpush version doesn't support file writing.
Action: This is a fatal error, and should be reported to a DMT expert immediately.

First frame read, GPS: <gps-time> Frame: <frame-id>
Meaning: This message is written after the first frame has been read successfully. The GPS time of the frame and the frame identifier supplied by the frame broadcaster are indicated.
Action: This message is purely informational. No action need be taken.

Frame broadcaster restarted, first GPS= <gps-time> previous= <gps-time>
Meaning: The frame broadcaster was restarted (as evidenced by a frame ID of 1). The current and previous time stamps are recorded.
Action: This is an informational message. No actions need be taken.

Frame data requested.
Meaning: Identifies the NDS/Frame version of Dpush.
Action: This is an informational message. No actions need be taken.

Frame length (<length>) too long for buffer.
Meaning: The shared memory partition buffer is too short for the frame received.
Action: Reallocate the shared memory partition with a bugger size greater than the indicated length. For processes running under the process manager, this requires setting the SMPBUFFLEN variable in the LxO_Monitor_Initial script.

Frame read: length/sequence/GPS/duration = <length>/<id>/<gps>/<duration>
Meaning: Debugging message reporting a successfully read frame.
Action: None needed.

Frame received out of order, Frame= <frame-id> expected <frame-id>
Meaning: This message indicates that the identifiers of successive frames were not in sequential order.
Action: This message is most often written after a restart of the frame broadcaster. In this case, the frame identifier found is 1. In all other cases this message should be reported to a DMT expert.

Frame received out of order, GPS=<gps-time> expected <gps-time>
Meaning: This message indicates that the GPS times of successive frames were not in sequential order.
Action: This error should be reported to a DMT expert.

Framerecv error 0. Retry.
Meaning: Framerecv returned a zero length record.
Action: No action needed. Dpush will try to get another frame.

Invalid data array.
Meaning: framerecv received invalid data.
Action: This is a fatal error, and should be reported to a DMT expert immediately.

Lock delay count = <count>
Meaning: This message is produced only when the debug option is specified in the Dpush command line. The "Lock delay count" gives the number of times during the statistics period when Dpush had to wait for a shared memory buffer to be freed. This message is for use in timing studies only, and non-zero counts do not indicate the loss of a buffer or a significant load on the processing machine.
Action: Information only. No action need be taken.

Missing frame <gps-time>[-<gps-time>]
Meaning: This message is produced when a gap is discovered in the frame times. This message is only produced when the verbose option is specified in the Dpush command line. If a single frame is missing, the time of the missing frame is indicated. If multiple frames are found to be missing, the time stamps of the first and last missing frames are printed.
Action: Information only. No action need be taken.

Opening connection to frame multicaster at <ip_addr> on network with <addr>
Meaning: Identifies the multicast version of Dpush.
Action: This is an informational message. No actions need be taken.

Receive buffer allocation failed.
Meaning: framerecv failed to allocate an input buffer.
Action: This is a fatal error, and should be reported to a DMT expert immediately.

Receive error, rc = <code>
Meaning: An error occurred when receiving a broadcast frame.
Action: This is a fatal error, and should be reported to a DMT expert immediately.

Retransmission request failed.
Meaning: framerecv was unable to request a missing packed from the frame broadcaster.
Action: Check that the frame broadcaster is operational. If the frame broadcaster is working normally, or Dpush doesn't restart when the frame broadcaster is restarted, notify a DMT expert.

Setting RT priority.
Meaning: The program has determined that it has the privileges to promote itself to Real-Time priority. It will attempt to do so.
Action: This is an informational message. No actions need be taken.

Socket assignment failed: <message>
Meaning: Framerecv failed in its attempt to allocate a socket. The message indicates the reason for the socket failure.
Action: This is a fatal error, and should be reported to a DMT expert immediately.

Starting...
Meaning: Message written to the log file at the very start of a Dpush run.
Action: Information only. No action need be taken.

Statistics - Frames read: <count> Lost: <lost> Unsent: <unsent> Rate: <rate>
Meaning:  A statistics function is run periodically (usually every 20 mins.). The above message is produced if one or more frames are found to be missing or if the inferred data rate differs from 1 Hz by more than 2%. The following statistics are written:
    count    is the total number of frames read during the statistics period.
    lost  is the number of lost frames. A frame is assumed to be lost if the a gap is found in both the GPS time stamp and the frame ID sequence.
    unsent    is the number of frames not sent by the frame broadcaster. A frame is considered unsent if there is a gap in the GPS time stamps but no gap in the frame ID sequence.
    rate         is the average rate (per second) that frames were received.
Action: Some frame losses may be expected. However, they are usually infrequent (<2%) unless they are caused by e.g. a reboot of one or more CDS systems. If the losses are large (i.e. > 10%) or continuous (i.e. 2% - 10% for several successive statistics periods) inform a DMT expert.

Unable to access partition <name>: <error>.
Meaning: Dpush was unable to access the named partition as a producer. The error message gives additional information. The most common errors are "Existing partition is incompatible with request" indicating that a smaller partition exists with the same name, and "Unable to create a new partition" which usually indicates that the system parameters will not allow allocation of a partition of the requested size.
Action: This is a fatal error, and should be reported to a DMT expert immediately.

Unable to get packet
Meaning: framerecv was unable to get a packet from the socket.
Action: This is a fatal error, and should be reported to a DMT expert immediately.

The following errors are produced by the frame checker. A specific error message is usually produced with the "Data check failed" message.

Data left after end-of-frame.
Meaning: Data exists after the frame end-of-file structure.
Action: Error resulted in loss of frame. Notify a DMT expert.

Illegal or undefined structure ID <id> at offset <off>
Meaning: A structure header was found with an undefined structure ID.
Action: Error resulted in loss of frame. Notify a DMT expert.

Illegal structure length <length> at offset <off>
Meaning: The structure length found was either longer than the frame or less than the structure header length.
Action: Error resulted in loss of frame. Notify a DMT expert.

Invalid IGWD header
Meaning: The first 5 bytes of the buffer do not contain "IGWD\0".
Action: Error resulted in loss of frame. Notify a DMT expert,

Invalid structure instance <inst> of ID <id>, expected <inst> at offset <off>
Meaning: The instance number of a structure was not one larger than the previous instance.
Action: Error resulted in loss of frame. Notify a DMT expert.

Unexpected EOD.
Meaning: The end of data was found before an end-of-file structure.
Action: Error resulted in loss of frame. Notify a DMT expert.