ulog Logging Format and Interpretation

Contents


Introduction

While some LDM utilities are designed to write diagnostic and informational messages to standard output, most utilities (in particular the LDM server, ldmd) are designed to write such messages to a log file. The log file is $HOME/logs/ldmd.log.

In general, the format of most log-messages is

MMM DD hh:mm:ss localhost util[pid] level: msg

Associated with each log-message is a priority-level. The levels are: error, warning, notice, informational, and debug. The priority-level is used to decide whether or not to write the message to the log file. Most utilities log errors, warnings, and notices by default. This behavior can usually be changed when the utility is executed by using the "-v" (verbose) option. This option will cause the utility to also log informational messages (and cause the log file to grow more rapidly). Another common option is "-x", which will cause the utility to also log debug messages (and cause the log file to grow extremely fast). You should rarely, if ever, need to use the "-x" option.

Each LDM process ( server, upstream LDM, downstream LDM) has another way to alter its logging-level. Reception of a USR2 signal by the process will cause it to change the logging-level threshold in the following sequence:

notice -> informational -> debug -> notice -> ...
The kill(1) utility can be used to send a USR2 signal to an LDM process.

Message Templates

A message template is an abstract log-message in which concrete fields (e.g., UNIX process-ID, upstream host name) have been replaced with corresponding placeholders (e.g., pid, uphost). When searching this web page for the message template corresponding to an actual log-message, be sure to search for only that part of the message that doesn't vary (such parts are in a non-italic font in the templates).

In the following log-message templates, the timestamp (MMM DD hh:mm:ss) localhost, util[pid], and level fields have been omitted and only the msg fields are shown.

Message Templates for


Message Templates for the LDM Server (top-level ldmd)

Notices

Starting Up (version: maj.min.bug; built: MMM-DD-YYYY hh:mm:ss)
The top-level (i.e., parent) ldmd is starting. The package was built in month MMM day DD of year YYYY at hour hh minute mm and second ss, local time.
child child-pid stopped by signal number
The child process corresponding to the specified process-ID was stopped by the signal with the specified number. The command-line of the child process is unknown. The command kill -l can be used to determine the signal's name.
child child-pid stopped by signal number: command-line
The child process corresponding to the specified process-ID was stopped by the signal with the specified number. The command kill -l can be used to determine the signal's name.
child child-pid terminated by signal number
The child process corresponding to the specified process-ID was terminated by the signal with the specified number. The command-line of the child process is unknown. The command kill -l can be used to determine the signal's name.
child child-pid terminated by signal number: command-line
The child process corresponding to the specified process-ID was terminated by the signal with the specified number. The command kill -l can be used to determine the signal's name.
child child-pid exited with status status
The child process corresponding to the specified process-ID terminated with the specified exit-status. The command-line of the child process is unknown. An exit-status other than zero indicates an error.
child child-pid exited with status status: command-line
The child process corresponding to the specified process-ID terminated with the specified exit-status. An exit-status other than zero indicates an error.
Killing (SIGTERM) process group
A child process of the LDM server has terminated abnormally. Consequently, the LDM server has decided to terminate the LDM system by sending a TERM signal to its process group
Terminating process group
The LDM server has been told to terminate. Consequently, the LDM server will terminate the LDM system by signaling its process group
Using local address IP_addr:port
The LDM server will listen on the specified IP address using the specified port.
Denying connection from [IP_addr] because too many clients
The LDM server denied a connection attempt from the specified IP address because the maximum number of clients are already connected to the server. If this happens often, then you might want to increase the variable $max_clients in the ldmadmin configuration-file.
Denying connection from [IP_addr] because not allowed
The LDM server denied a connection attempt from the specified IP address because the IP address didn't match any ALLOW or ACCEPT entry in the LDM configuration-file ldmd.conf.
Denying connection from "hostame" [IP_addr] because not allowed
The LDM server denied a connection attempt from the specified host with the specified IP address because neither the hostname nor IP address matched any ALLOW or ACCEPT entry in the LDM configuration-file ldmd.conf.
ldmd[pid]: Adjusted pathological regular expression "ere" at line lineno, file pathname
The LDM configuration-file pathname contains the pathological regular-expression ere at line lineno. The LDM converted the pathological regular-expression to a non-pathological one, internally, and should work OK. At some time, however, you should edit the configuration-file to correct the regular-expression.

Warnings

Adjusted pathological regular expression "ERE" near line n, file "pathname"
The LDM server converted the pathological regular-expression near the specified line of the specified configuration-file into an equivalent, non-pathological form. You should change the regular-expression to avoid this warning.
Pathological regular expression "ERE" near line n, file "pathname"
The LDM server converted the pathological regular-expression near the specified line of the specified configuration-file into an equivalent, non-pathological form. You should change the regular-expression to avoid this warning.

Errors

run_requester: fork
The LDM server was unable to fork a downstream LDM child process.
fork
The LDM server was unable to fork a child process for an EXEC entry in its configuration-file, ldmd.conf.
execvp: command
The LDM server was unable to execute command from an EXEC entry in its configuration-file, ldmd.conf.
Error near line n, file "pathname": msg
The specified LDM configuration-file contained the error msg near the specified line.
Invalid feedtype expression "feedtype" near line n, file "pathname": msg"
The specified LDM configuration-file contained the error msg in the feedtype specification near the specified line.
Couldn't clone regular-expression "ERE" near line n, file "pathname": reason
The LDM server couldn't make a copy of the specified regular-expression near the specified line of the specified configuration-file due to system error reason.
Couldn't allocate n bytes for "regex_t" near line n, file "pathname"
The LDM server failed to allocate the given number of bytes for an object of type "regex_t" while parsing the specified configuration-file near the specified line.
Couldn't compile regular-expression ERE" near line n, file "pathname": reason
The LDM server failed to compile the specified regular-expression near the specified line of the specified configuration-file due to reason.
Couldn't clone string "string" near line n, file "pathname": reason
While parsing the specified configuration-file, the LDM server was unable to make a copy of the specified string near the specified line due to reason.
Couldn't create host-set for "spec" near line n, file "pathname": reason
While parsing the specified configuration-file, the LDM server was unable to convert the specified string near the specified line into a set of hosts due to reason.
Couldn't add ALLOW entry near line n, file "pathname": reason
While parsing the specified configuration-file, the LDM server was unable to add the ALLOW entry near the specified line to its internal list due to reason.
Couldn't get request-entry near line n, file "pathname": reason
While parsing the specified configuration-file, the LDM server was unable to convert the REQUEST entry near the specified line into a data-object due to reason.
Invalid hostname specification "hostname" near line n, file "pathname"
The specified hostname near the specified line of the specified configuration-file is invalid.
Invalid port specification "port" near line n, file "pathname"
The specified port near the specified line of the specified configuration-file is invalid.
Couldn't add host to request-entry near line n, file "pathname": reason
While parsing the specified configuration-file, the LDM server was unable to add the specified host of the REQUEST entry near the specified line to the internal data-object associated with that REQUEST entry's feedtype and ERE due to reason.
fopen: pathname: reason
The LDM server was unable to open the specified configuration-file due to reason.
Problem requesting data: reason
The LDM server was unable to create all the downstream LDMs corresponding to the REQUEST entries in its configuration-file due to reason.
Couldn't add ACCEPT entry near line n, file "pathname": reason
While parsing the specified configuration-file, the LDM server was unable to add the ACCEPT entry near the specified line to its internal list due to reason.
Couldn't decode command "command" near line n, file "pathname": reason
While parsing the specified configuration-file, the LDM server was unable to decode the specified command of the EXEC entry near the specified line due to reason.
String too long
While parsing its configuration-file, the LDM server encountered a string that was longer than it could handle.
Couldn't add EXEC entry near line n, file "pathname": reason
While parsing the specified configuration-file, the LDM server was unable to add the EXEC entry near the specified line to its internal list due to reason.
waitpid: reason
The waitpid() system-call failed due to reason.
pmap_unset(LDMPROG prog, LDMVERS vers) failed
The LDM server was unable to unregister itself with the portmapper.
Couldn't get socket for server: reason
The LDM server was unable to obtain a socket upon which to listen due to reason.
Couldn't obtain local address ip_addr:port for server: reason
The LDM server was unable to bind its listening socket to the given IP address and port number due to reason.
Couldn't obtain local address ip_addr:* for server: reason
The LDM server was unable to bind its listening socket to the given IP address -- even though it allowed the operating-system to determine the port number -- due to reason.
Couldn't get local address of server's socket: reason
The LDM server was unable to obtain from the operating-system the address to which its listening socket was bound due to reason. This is, basically, a failure of the getsockname() system-call.
Couldn't listen() on server's socket: reason
The LDM server was unable to listen on its socket due to reason. This is, basically, a failure of the listen() system-call.
accept: reason
The accept() system-call failed due to reason.
fork: reason
The fork() system-call failed due to reason.
Couldn't add child PID to set: reason
The LDM server was unable to save the fact that it successfully forked a child process due to reason.
Can't create fd service.
The LDM server was unable to create an RPC service on socket. This is, basically, a failure of the svcfd_create() RPC function.
unable to register LDM-n service.
The LDM server was unable to register itself with the RPC layer. This is, basically, a failure of the svc_register() RPC function.
sock select: reason
The LDM server was unable to receiving anything on the incoming socket due to reason. This is, basically, a failure of the select() system-call.
atexit: reason
The LDM server was unable to register a cleanup handler to be called when the process terminates normally due to reason. This is, basically, a failure of the atexit() system-call.
The product-queue "pathname" is inconsistent
The specified product-queue is internally inconsistent (i.e., corrupt). The queue will have to be deleted and recreated.
pq_open failed: pathname: reason
The LDM server was unable to open the specified product-queue due to reason.
getsockopt option: reason
The LDM server was unable to obtain a value for the specified socket option due to reason. This is, basically, a failure of the getsockopt() system-call.
setsockopt option value: reason
The LDM server was unable to set the specified socket option to the specified value due to reason. This is, basically, a failure of the setsockopt() system-call.

Message Templates for a Downstream LDM

Notices

Starting Up(maj.min.bug): uphost:port criteria
The downstream LDM 6 started. It should connect to the specified host using the specified port and data-product selection-criteria.
LDM-6 desired product-class: criteria
The downstream LDM 6 has adjusted its data-product selection-criteria according to the most recent data-product in the product-queue that matches the startup selection-criteria. This will be the selection-criteria that will be used in the FEEDME request to the upstream LDM
hiya6: criteria
The downstream LDM 6 received a HIYA message with the specified data-product selection-criteria from an upstream LDM 6.
nhits (n) >= MAXHITS (max)
The number of ACCEPT entries in the LDM configuration-file, ldmd.conf, that match an incoming HIYA message exceeds a fixed limit. This means that the configuration-file is way too complicated.
Upstream LDM-6 on uphost is willing to be a primary feeder
The downstream LDM 6 successfully negotiated with the upstream LDM 6 on the specified host for getting data-products via the primary transfer-mode.
Upstream LDM-6 on uphost is willing to be an alternate feeder
The downstream LDM 6 successfully negotiated with the upstream LDM 6 on the specified host for getting data-products via the alternate transfer-mode.
Product reclassification by upstream LDM: criteria -> criteria
The downstream LDM 6 received a RECLASS reply from the upstream LDM 6 in response to the downstream's FEEDME request.
Switching data-product transfer-mode to mode
The downstream LDM 6 has decided to change its data-product transfer-mode to mode.
Couldn't connect to LDM on uphost using either port port or portmapper: reason
The downstream LDM 6 couldn't connect to an upstream LDM 6 due to reason.
nullproc_n failure to uphost
The NULLPROC message that the downstream LDM n sent to the upstream LDM n in order to test the connection failed due to reason.
Connection aborted
The connection between the downstream LDM 5 subsystem and the upstream LDM 5 was terminated because:
  • The upstream LDM wasn't version 5;
  • An LDM wasn't running on the upstream host;
  • A request for information from the portmapper on the upstream host failed;
  • An LDM isn't registered with the RPC layer on the upstream host;
  • The upstream LDM doesn't have a matching ALLOW entry in its configuration-file, ldmd.conf for the downstream LDM;
  • The upstream LDM host is unknown to the downstream LDM host;
  • The upstream LDM was told to terminate; or
  • The downstream LDM 5 subsystem received an unexpected reply from the upstream LDM.
Connection closed by upstream LDM
The upstream LDM 5 terminated the connection with the downstream LDM 5 subsystem (typically because of no matching ALLOW entry in the upstream LDM's configuration-file, ldmd.conf).
Connection timed-out
The connection between the downstream LDM 5 subsystem and the upstream LDM 5 was terminated due to an RPC timeout.
Connection refused by upstream LDM
The upstream LDM 5 refused to connect with the downstream LDM 5 subsystem because
  • There is no matching ALLOW entry in the upstream LDM's configuration-file, ldmd.conf; or
  • The intersection of the set of requested data-products and the set of allowed data-products is the empty set.
Previous product-information file "path" doesn't exist
The file path that would hold the metadata of the last, successfully-received data-product doesn't exist. This message should only be seen when upgrading from version 6.5 (or earlier versions) or after modifying or adding a REQUEST entry in the LDM configuration-file and restarting the LDM.

Warnings

Future product from "uphost". Fix local or ingest clock. metadata
The system clock on ingest host uphost (the computer that created the data-product) is fast relative to the local system clock. If, during a reconnection attempt, a downstream LDM asks for data beginning with this data-product, then the performance of the LDM on the local host will be significantly degraded. The solution is to check the system clocks on the local and ingest hosts and to fix whichever one is incorrect by installing and running the Network Time Protocol Daemon (ntpd) on that system. If the ingest host is beyond your control, then you will have to communicate with the administrator of that host. If the ingest host is part of the Unidata IDD, then you can email support-idd at unidata.ucar.edu.

Because of the potential for receiving such data-products at a high rate, each downstream LDM process will print only one such message every hour for any given ingest host (unless the process is in verbose logging mode, in which case it will print a message for every such data-product). You can use a command like the following to extract a unique list of such ingest hosts from an LDM log file:

grep -F 'WARN: Future' ldmd.log.1 | sort -u -t ' ' -k 10,10
This command could be executed, for example, via the crontab utility just after the log files are rotated to notify the LDM administrator of problems via email.

Errors

Couldn't save product-information: reason
The downstream LDM 6 was unable to save the metadata of the just-arrived data-product because of reason.
Couldn't save acceptance of data-product: reason
The downstream LDM 6 was unable to save the fact that a data-product just arrived successfully because of reason.
pq_insert() failed: reason: metadata
The downstream LDM 6 was unable to insert a just-arrived data-product into the product-queue because of reason.
Couldn't save rejection of data-product: reason
The downstream LDM 6 was unable to save the fact that a data-product just was not inserted into the data-product because it was a duplicate because of reason.
Couldn't open product-queue "pathname" for writing: reason
The product-queue couldn't be opened for writing because of reason.
Couldn't initialize savedInfo module: reason
The software module that saves the metadata of just-arrived data-products could not be initialized because of reason.
Terminating due to system failure: reason
The downstream LDM cannot continue due to the operating-system failure reason.
Terminating due to LDM failure: reason
The downstream LDM cannot continue due to the LDM failure reason.
Unexpected forn5() return: errno
The downstream LDM cannot continue due to an unanticipated operating-system error in the LDM 5 function forn5(). The number of the error is errno.
Couldn't allocate new product-information structure: reason
The downstream LDM was unable to allocate an object to hold the metadata of a data-product due to reason.
Couldn't allocate new product-class: reason
The downstream LDM was unable to allocate an object to hold its data-product selection-criteria due to reason.
pqe_new() failed: reason: metadata
The downstream LDM 6 was unable to determine if a data-product corresponding to the just-arrived data-product metadata of a COMINGSOON message already exists in the product-queue because of reason.
Couldn't open product-queue "pathname": for writing: reason
The upstream LDM 6 was unable to open the specified product-queue for writing due to reason.
Couldn't initialize downstream LDM
The downstream LDM 6 couldn't initialize itself in response to a HIYA message from an upstream LDM 6.
Couldn't validate HIYA: reason
The downstream LDM couldn't match a HIYA message from an upstream LDM 6 against its ACCEPT entries due to reason.
Couldn't set product class: criteria: reason
The downstream LDM 6 couldn't set its internal data-product selection-criteria object to the specified value due to reason.
Couldn't clone product-information: reason
The downstream LDM couldn't make a copy of a data-product's metadata due to reason.
Request not allowed. Does it overlap with another?
The upstream LDM 6 reduced the data-product selection-criteria given to it to an empty subscription after first reducing it by the relevant ALLOW entries in the upstream LDM's configuration-file and then by the subscriptions from other, existing downstream LDM 6s that are executing on the same host. You should check your LDM configuration-file, ldmd.conf, for overlapping REQUESTs entries to the upstream host.
Product too big: metadata
The downstream LDM 6 was unable to insert a just-arrived data-product into the product-queue because it was larger than the largest data-product that the product-queue can hold. Tell the upstream site to stop sending such data-products or increase the size of your product-queue.

Message Templates for an Upstream LDM

Log-messages from upstream LDMs usually have the string "(feed)" or "(noti)" in the util field of the log-message, corresponding to FEEDME and NOTIFYME requests from the downstream LDM, repectively.

Notices

Starting Up(maj.min.bug/6): criteria, transfer-mode
The feeding upstream LDM 6 is starting in response to a FEEDME request from a downstream LDM 6. The specified data-product selection-criteria will be used to select data-products from the product-queue. Such products will be further filtered by the upstream filter. The specified transfer-mode will be used to send the products.
Starting Up(maj.min.bug/6): criteria
The NOTIFICATION-using upstream LDM 6 is starting in response to a FEEDME request from a downstream LDM 6. The specified data-product selection-criteria will be used to select data-products from the product-queue. Such products will be further filtered by the upstream filter.
Restricting request: criteria -> criteria
The upstream LDM 6 determined that the downstream LDM 6 was not allowed to receive the feedtype that it requested, based on ALLOW entries in the LDM configuration-file, ldmd.conf. The upstream LDM 6, consequently, restricted the data-product selection-criteria to that specified.
Terminated obsolete upstream LDM LDM_spec
The newly-created upstream LDM 6 process determined that an earlier upstream LDM process was supplying a subset (either proper or improper) of the requested data to the same downstream host; consequently, the other process was terminated.
topo: downhost upfilter
The upstream LDM 6 will send the data-products specified by the upstream filter to the downstream LDM 6 on the specified host.
Invalid signature (signature)
The upstream LDM 6 was unable to decode the data-product signature encoded in the data-product selection-criteria of a request for data from a downstream LDM 6.
Invalid signature (signature): reason
The upstream LDM 6 was unable to decode the data-product signature encoded in the data-product selection-criteria of a request for data from a downstream LDM 6 due to reason.
Data-product with signature sig wasn't found in product-queue
The upstream LDM 6 was unable to find the data-product whose signature was encoded in the data-product selection-criteria in the request-for-data from the downstream LDM 6. The upstream LDM will use the rest of the selection-criteria to determine which data-products to send.

Warnings

Couldn't terminate obsolete upstream LDM LDM_spec
The newly-created upstream LDM 6 process was unable to terminate an earlier upstream LDM 6 process that was supplying a subset (either proper or improper) of the requested data to the same downstream host.
Subscription reduced by one or more ALLOW entries: desired -> allowed
The data-product selection-criteria from the downstream LDM 6 was reduced by the ALLOW entries in the LDM configuration-file, ldmd.conf.
Subscription reduced by one or more existing subscriptions: desired -> allowed
The data-product selection-criteria from the downstream LDM 6 was reduced by existing previous subscriptions from the same host. in order to reduce bandwidth usage by the upstream site.

Errors

Couldn't duplicate product-class: reason
The upstream LDM 6 was unable to make a copy of the data-product selection-criteria of a request for data from a downstream LDM 6 due to reason.
Couldn't compute wanted/allowed product intersection: reason
The upstream LDM 6 was unable to compute the intersection of the set of requested data-products with the set of allowed data-products due to reason.
Couldn't duplicate socket n: reason
The upstream LDM 6 was unable to duplicate the specified socket due to reason.
Invalid product pattern: criteria
The upstream LDM 6 encountered an invalid ERE in the specified data-product selection-criteria from the downstream LDM 6.
Couldn't get "upstream" filter: reason
The upstream LDM 6 was unable to obtain its upstream filter due to reason.
Upstream filter prevents data-transfer
The upstream filter of the upstream LDM 6 prevented the transfer of all data-products. You should either modify the upstream filter to allow some transfer or remove the relevant ALLOW entry entirely.
svc_sendreply(...) failure
The upstream LDM 6 was unable to send an RPC reply to the downstream LDM 6.
Couldn't free arguments
The upstream LDM 6 was unable to free the arguments associated with an RPC message from a downstream LDM 6.
fcntl(F_GETFL) failure: reason
The upstream LDM 6 was unable to get the flags associated with its socket due to reason. This is, basically, a failure of the fcntl() system-call.
fcntl(F_SETFL) failure: reason
The upstream LDM 6 was unable to set the flags associated with its socket due to reason. This is, basically, a failure of the fcntl() system-call.
Couldn't connect to downstream LDM on reason
The RPC layer of the upstream LDM 6 was unable to connect to the RPC layer of the downstream LDM 6 on the specified host due to reason.
Couldn't set product-class in queue "pathname": reason
The upstream LDM 6 was unable to set the data-product selection-criteria in the specified product-queue due to reason.
Couldn't initialize autoshift module: reason
The upstream LDM 6 was unable to initialize the autoshift module due to reason.
Failure: reason
The upstream LDM 6 was unable to feed or notify its downstream LDM 6 due to reason.
Couldn't flush connection: reason
The upstream LDM 6 was unable to flush the TCP connection to the downstream LDM 6 due to reason.
Product send failure: reason
The upstream LDM 6 was unable to send a data-product to the downstream LDM 6 due to reason.
The product-queue "pathname" is inconsistent
The upstream LDM 6 determined that the specified product-queue was in an inconsistent state (i.e., corrupt). The queue will have to be deleted and recreated.
Couldn't open product-queue "pathname": reason
The upstream LDM 6 couldn't open the specified product-queue due to reason.
Couldn't adjust product-class specification (criteria): reason
The upstream LDM 6 couldn't adjust its data-product selection-criteria due to reason.

Message Templates for the pqact Utilty

Notices

Starting from insertion-time YYYY-MM-DD hh:mm:ss.ssssss UTC
The pqact process will start processing data-products beginning with the data-product that was inserted into the product-queue just after the indicated time, which is the insertion-time of the last, successfully-processed data-product from the previous LDM session.
child child-pid terminated by signal sig
The child process of a pqact process was terminated by signal sig. This had to have been done by somthing outside the LDM system.
unio_open: pathname: Interrupted system call
The pqact process was unable to create file pathname because the process was interrupted by a signal.
pipe_prodput: trying again
The pqact process was unable to write a data-product to an LDM decoder. Because this could be due to a temporary condition, the process will try again.
ReReading configuration file pathname
The pqact process received a HUP signal and will try to reread its configuration-file.
Filed in "pathname": metadata
The pqact process filed the data-product with the given metadata in file pathname as the result of a FILE action.
StdioFiled in "pathname": metadata
The pqact process filed the data-product with the given metadata in file pathname as the result of a STDIOFILE action.
Behind by n s
The pqact process is terminating and the time that the last, successfully-processed data-product was inserted into the product-queue was n seconds before the present time. This indicates how far behind the process was when it terminated. The larger the number is, the greater the risk of not processing a data-product before it is removed from the product-queue.

Warnings

write(fileno,,count) to decoder took n s: decoder
The pqact process took n seconds to write count bytes to decoder. The computer might be overloaded or the computer or decoder might be too slow. The file-descriptor of the pipe was fileno.
Processed oldest product in queue: n s
The pqact process just processed the oldest data-product in the product-queue, which was inserted into the queue n seconds before the present time. This warning indicates a high risk of not processing all the data-products in the queue before they are removed to make room for more. If this happens often, then you should 1) increase the size of the queue; 2) decrease the rate at which products are inserted into the queue; or 3) decrease the amount of processing of data-products.

Errors

pbuf_flush (fileno) Timed out
The pqact process was unable to flush a pipe to an LDM decoder because the flush timed-out. The computer or decoder is too slow or the computer is overloaded. The file-descriptor of the pipe was fileno.
pbuf_flush (fileno) write: Broken pipe
The pqact process was unable to write to an LDM decoder because the pipe was disconnected (the decoder process either closed the pipe or terminated). The decoder should have logged an error message. The file-descriptor of the pipe was fileno.
pipe_dbufput: pathname write error
The pqact process was unable to write to LDM decoder pathname.
pipe_put(): write error: pid=child-pid, cmd=(cmd)
The pqact process was unable to write to LDM decoder command cmd because the pipe is disconnected (the decoder process either closed the pipe or terminated). The decoder should have logged an error message.

Message Templates for the rtstats Utility

Notices

Starting Up (parent-pid)
The rtstats utility was started by the parent process whose process-ID is parent-pid (typically, the top-level ldmd).
Interrupt
The rtstats process received an interrupt signal.
Exiting
The rtstats process is exiting.

Message Templates for the scour Utilty

Notices

skipping, no recent files in pathname
The scour process skipped the directory pathname because it contained no recent files.

Key

blockno
Is the origin-0 block-number of an LDM 5 BLKDATA message.
child-pid
Is the UNIX process-ID number of the relevant child process.
command-line
Is the UNIX command-line of the relevant process.
criteria
Is the Data-product selection criteria in the form
start stop {{feedtype "pattern"} [,...]}
where:
start
Is the start-time in the form YYYYMMDDhhmmss.sss or the string TS_ZERO. The data-product creation-time must be equal-to or greater than this. The string TS_ZERO is, effectively, the beginning of time.
stop
Is the stop-time in the form YYYYMMDDhhmmss.sss or the string TS_ENDT. The data-product creation-time must be less-than or equal-to this. The string TS_ENDT is, effectively, the end of time.
pattern
Is the ERE for matching the data-product identifier.
DD
Is the day of the month when the message was generated (e.g., 08).
downhost
Is the downstream host. This can be a hostname, a fully-qualified hostname, or an IP address.
feedtype
Is the data-product feedtype.
fileno
Is the UNIX file descriptor of an open file.
elapsed-time
Is the elapsed-time interval in seconds.
hh:mm:ss
Is the time of day when the message was generated. A 24-hour UTC clock is used (e.g., 17:25:42).
localhost
Is the identifier of the host on which the LDM system generated the log-message.
MMM
Is the abbreviation of the month when the message was generated (e.g., Jan).
msg
Is the message from the utility.
pathname
Is the pathname of a file or directory.
pid
Is the UNIX process-ID number of the process that generated the message.
metadata
Is the metadata of a data-product in the form
[signature] size creation-time feedtype sequence_number identifier
prod-ID
Is the data-product identifier.
uphost
Is the upstream host identifier. This can be a hostname, a fully-qualified hostname, or an IP address.
util
Is the identifier of the utility that generated the message. This is usually the name of the program (e.g., ldmd, pqact). For a downstream LDM, however, the identifier is the name of computer that's running the upstream LDM. For an upstream LDM, the identifier has the form
downhost(mode)
where:
mode
Is (typically) "feed" or (atypically) "noti" to indicate that the upstream LDM results from a FEEDME or NOTIFYME request, respectively.
level
Is the priority-level of the log-message:
Value Meaning
ERROR An error occurred and the program cannot continue
WARN Something happened that wouldn't have if things were perfect
NOTE Something noteworthy but routine occurred
INFO Merely an informational message (-v option)
DEBUG A debugging message (-x option)
maj.min.bug
Is the major, minor, and bug-fix version numbers, respectively, of an LDM release.
srcloc
Is the location in the source-code where the log-message was generated in the form
filename:lineno
where:
filename
Is the name of the source-file where the log-message was generated.
lineno
Is the line-number in filename where the log-message was generated.
YYYYMMDDhhmmss.sss
Is a time composed of the year (YYYY) month (MM) day (DD) hour (hh) minute (mm) and second (ss.sss).