UMDS User Guide
UMDS Log Messages

This section is a single long page to ease searching for a message ID (e.g. "Core-5402-1"). For printing purposes, the PDF is recommended.

Umds-10372-10: unable to create umds cfg stat group: sFailure when creating daemon monitor umds config stats groupVerify all the attributes in the daemon-monitor section of the xml file are correct
Umds-10372-11: unable to create memory stat group: sFailure created while creating daemon monitor malloc info stat groupVerify all the attributes in the daemon-monitor section of the xml file are correct
Umds-10372-12: unable to schedule timer for gateway config stat group call back, sError setting up UMDS config stat group callback timerContact Informatica Support.
Umds-10372-13: unable to schedule timer for umds config stat group call back, sFailure setting up gateway config stat group callback timerContact Informatica Support.
Umds-10372-14: umdsd_publish_cfg: sUM was unable to publish dmon message.Contact Informatica Support.
Umds-10372-15: error trying to publish config recordFailure publishing config recordContact Informatica Support.
Umds-10372-16: error reading memory info recordError attempting to read daemon stats memory info recordThis is an information message only.
Umds-10372-17: unable to schedule timer for memory stat group callback: sFailure creating memory stat group callback timerContact Informatica Support.
Umds-10372-18: error reading malloc info recordError attempting to read daemon stats malloc info recordContact Informatica Support.
Umds-10372-19: unable to schedule timer for memory stat group call back, sfailure scheduling timer for memory stat group callback timerContact Informatica Support.
Umds-10372-1: pointer to stats_info is NULL: spointer to stats_info is NULLContact Informatica Support.
Umds-10372-20: Error reading memory recordError reading memory recordContact Informatica Support.
Umds-10372-21: worker id number is out of rangeWorker number is out of rangeContact Informatica Support.
Umds-10372-22: worker_list pointer is NULLworker_list pointer is NULLContact Informatica Support.
Umds-10372-23: stats_info pointer is NULLstats_info pointer is NULLContact Informatica Support.
Umds-10372-24: unable to schedule timer for gateway config stat group call back, sError setting up UMDS config stat group callback timerContact Informatica Support.
Umds-10372-25: unable to schedule timer for gateway config stat group call back, sError setting up UMDS config stat group callback timerContact Informatica Support.
Umds-10372-26: No workers defined in umdsd_dstat_allworker_stat_grp_createNo workers definedVerify that the number of workers defined in the xml file is > 0
Umds-10372-27: error initializing a worker stat objectError initializing a worker stat objectContact Informatica Support.
Umds-10372-28: unable to schedule timer for worker stat group call back, sfailure scheduling timer for worker stat group callback timerContact Informatica Support.
Umds-10372-29: unable to schedule timer for worker stat group call back, sfailure scheduling timer for worker stat group callback timerContact Informatica Support.
Umds-10372-2: unable to create context attributes: sFailure while creating context attributesContact Informatica Support.
Umds-10372-30: Worker ID number d is out of rangeWorker ID is out of rangeContact Informatica Support.
Umds-10372-31: error reading worker statsFailure reading worker statsThis is an information message only
Umds-10372-32: connection status read failedFailure reading connection statsThis is an information message only
Umds-10372-33: umdsd_dstat_send_thread_main: Unable to publish message of type d: sUM was unable to publish dmon message.Contact Informatica Support.
Umds-10372-34: invalid UMDS dmon message [s] from s [s]UM dmon received an invalid/corrupted immediate message.Verify that messages sent on the request port are valid.
Umds-10372-35: UMDS dmon failed to send error response [s]UM could not respond to a dmon immediate message.Contact Informatica Support.
Umds-10372-36: UMDS dmon failed to send success response [s]UM could not respond to a dmon immediate message.Contact Informatica Support.
Umds-10372-37: UMDS dmon received control message exceeding 255 bytesUM daemon monitor received an invalid control message exceeding 255 bytes.Verify that messages sent on the control channel are <= 255 bytes.
Umds-10372-38: UMDS dmon failed to send error response [s]UM could not respond to a dmon immediate message.Contact Informatica Support.
Umds-10372-39: UMDS received unknown lbm_msg_t type x [s][s]UM daemon monitor received unknown lbm_msg_t type.Stop the source of unknown messages to the daemon monitor.
Umds-10372-3: lbmaux_context_attr_setopt_from_file() failed, sFailure while setting up extra config opts for UMDS daemon monitorCheck attributes in "lbm-config" config file specified in the "daemonmonitor" section of the UMDS's xml file
Umds-10372-40: error from umdsd_dstat_mallinfo_stat_grp_snapshot()Failure reading malloc info stat group recordContact Informatica Support.
Umds-10372-41: error from umdsd_cfg_dstat_stat_grp_snapshot()Failure reading config info stat group recordVerify that the xml file has not been removed since starting the daemon.
Umds-10372-42: error from umdsd_dstat_workers_snapshot()Failure reading worker stat group recordThis is an information message only.
Umds-10372-43: error from umdsd_dstat_memory_stat_grp_snapshot()Failure reading malloc info stat group recordContact Informatica Support.
Umds-10372-44: error from umdsd_dstat_cfg_stat_grp_snapshot()Failure reading config info stat group recordThis is an information message only
Umds-10372-45: No connection ID specified for connection snapshotNo connection ID specified for the connections snapshotVerify that a valid connection ID was specified
Umds-10372-46: error from umdsd_dstat_conn_snapshot()Failure reading connection stat group recordThis is an information only message.
Umds-10372-47: bad worker ID returned from umdsd_getworkerID_fromstring()The worker ID is invalidVerify that the worker ID is within the range of Workers specified UMDS XML file
Umds-10372-48: error from umdsd_dstat_workers_snapshot()Failure reading worker stat group recordThis is an information only message
Umds-10372-49: error returned from umdsd_dstat_setinterval()Failure changing the publishing interval for config stat groupContact Informatica Support.
Umds-10372-4: lbm_context_attr_setopt() failed, sFailure setting up attributes for daemon monitor remote control handlerContact Informatica Support.
Umds-10372-50: error returned from umdsd_dstat_setinterval()Failure changing the publishing interval for mallinfo stat groupContact Informatica Support.
Umds-10372-51: bad worker ID returned from umdsd_getworkerID_fromstring()The worker ID is invalidVerify that the worker ID is within the range of workers specified in the UMDS XML file
Umds-10372-52: error returned from umdsd_dstat_setinterval()Failure changing the publishing interval for worksum stat groupContact Informatica Support.
Umds-10372-53: invalid command sAttempt to obtain snapshot of record for invalid stat groupContact Informatica Support.
Umds-10372-54: unable to schedule timerFailure to schedule callback timerContact Informatica Support.
Umds-10372-55: Worker ID d is out of rangeWorker ID out of rangeContact Informatica Support.
Umds-10372-56: Unable to start daemon stats monitorunable to start daemon stats monitor for UMDSVerify all daemon monitor related attributes are correct in xml and config files
Umds-10372-57: NULL webmon pointerNULL webmon pointerContact Informatica Support.
Umds-10372-58: monitor section lbm-config must have a valueExpecting a string that contains the path to the config file.Please specify a string that contains the path to the config file.
Umds-10372-59: monitor section xml-config must have a valueExpecting a string that contains the path to the config file.Please specify a string that contains the path to the config file.
Umds-10372-5: unable to create context attributes: sFailure creating lbm context for daemon stats monitorContact Informatica Support.
Umds-10372-60: lbmaux_src_topic_attr_setopt_from_file() failed, sFailure while setting up extra config opts for UMDS daemon monitor source objectCheck attributes in "lbm-config" config file specified in the "daemonmonitor" section of the UMDS's xml file
Umds-10372-6: unable to create src topic attributes: sError creating source attributes for daemon stats monitorContact Informatica Support.
Umds-10372-7: unable to alloc src topic: sError allocating src topic for daemon stats monitorContact Informatica Support.
Umds-10372-8: unable to create src: sError creating source for daemon stats monitorContact Informatica Support.
Umds-10372-9: unable to allworker stat groupFailure returned while creating allworker stats groupVerify all the attributes in the daemon-monitor section of the xml file are correct
Umds-10633-1: umdsd_main: Daemon setup failed. Exiting umdsd.There was a failure trying to setup the UMDS Daemon. The daemon cannot continue and exits.Check previous errors and correct appropriately.
Umds-10759-1: Unable to create daemon stats sender thread: sFailure to create sender thread for daemon statsContact Informatica Support.
Umds-10759-2: umdsd_dstat_send_thread_create() error creating TL queue: sUnable to create two-lock queueContact Informatica Support.
Umds-10759-3: umdsd_dstat_send_thread_main(): Error while dequeueingError while dequeueing from TL queueContact Informatica Support.
Umds-4892-1: Attempt to set use_late_join failed for attrs p err(d)ERROR: Attempt to turn use_late_join ON in the rcvr attrs failed.
Umds-4892-2: Attempt to set ume_use_store failed for attrs p err(d)ERROR: Attempt to turn ume_use_store ON in the rcvr attrs failed.
Umds-4892-3: Error creating Topic Queue: No Hash function found.FATAL: A hash function is required to create a Topic Queue. This is set from the resolver_string_hash_function in the topic queue map init function.Check that the Hash function for Topic Resolution has been set correctly.
Umds-4892-4: Attempt to get ume_session_id failed or session id is zero: luERROR: Trying to create a persistent receiver but the session id is either zero, or reading the attribute failed.Check that session ID sent by the UMDS client is not zero
Umds-4892-5: Attempt to set ume_explicit_ack_only failed for attrs p err(d)ERROR: The attempt to set ume_explicit_ack_only (to ON) failed while creating a persistent receiver.
Umds-5688-5609: umdsd_worker_api_mim_loss_advisory: worker(p<d>) not runningThe indicated worker is not in the RUNNING stateContact Informatica support with all relevant log files
Umds-5688-5617: PCRE exec [s][s][d] error dAn error occurred while trying to match the pattern listed in the first bracketed expression. The topic string attempting to be matched is supplied as the second bracketed expression, and its length is supplied as the third bracketed expression. The error that occurred was internal to PCRE, and the error code is listed in the PCRE documentation for return values of pcre_exec.
Umds-6033-635: Ultra Messaging UMDS server version " UMDS_VERSION " Build s, s (s)Reports the version of UMDS, build time and date, and version of the underlying UM library.No resolution, this in formation is provided for audit and debugging purposes.
Umds-6033-637: umdsd_main: webmon interface not found (s)The interface specified for the web monitor could not be found.Review the setting in the <web-monitor> tag in the server's xml configuration file.
Umds-6033-638: umdsd_main: client interface not found (s)The interface specified for the client connections could not be found.Review the setting for the bind-addr attribute in the <server> tag in the server's xml configuration file.
Umds-6033-641: umdsd_main: Error opening pidfile 's' (s)Opening (creating) the pid file failed.The error message includes the OS error message associated with the open attempt. Check that files can be created in the target directory and that the device is not full.
Umds-6033-656: umdsd_worker_cont_sending_cntl: sendb header error (s)Sending a UMDS Control message to the client resulted in an UM error.A description of the UM error is included in the message text.
Umds-6033-657: umdsd_worker_cont_sending_data: sendb data error (s)Sending on the client socket encountered an error.Included in the message text is a description of the particular error encountered.
Umds-6033-664: umdsd_webmon_api_create: failed to init web server (ip=s, port=s)The web monitor subsystem failed to start.The web server library will have reported additional details to the console.
Umds-6033-685: s: worker p<d> connection p<d> invalid conn_state (d)The indicated state for the client connection is inappropriate for the requested operation.The client connection will be deleted and if configured, the client will retry. If this error repeats, call Informatica support with all relevant server and client log files.
Umds-6033-705: umdsd_worker_internal_cmd_del_conn: worker p<d> connection p<d> (s:u) deleted, bytes_in=lld, bytes_out=lldThe indicated connection has been deletedNo resolution is required.
Umds-6033-706: umdsd_worker_internal_cmd_mim_loss_advisory: worker(p<d>) not runningThe indicated worker is not in the RUNNING stateContact Informatica support with all relevant log files
Umds-6033-708: umdsd_worker_keepalive_tmr_cb: worker(p<d>) not runningThe indicated worker is not in the RUNNING stateContact Informatica support with all relevant log files
Umds-6033-709: umdsd_worker_keepalive_tmr_cb: send_period=d, disconnecting worker p<d> connection p<d>The keep alive state has been PENDING for too long; it is being disconnected as unresponsive.This can occur if the client application is spending long periods of time in any of the library call back functions and preventing the client sid socket from being read.
Umds-6033-710: umdsd_worker_keepalive_tmr_cb: rcv_period=d, disconnecting worker p<d> connection p<d>The keep alive timer has expired for the indicated worker connection; it is being disconnected as unresponsive.This can occur if the keep alive threshold and intervals are not appropriate for the connection or if the client application is spending long periods of time in any of the library call back functions.
Umds-6033-711: umdsd_worker_api_conn_add: worker(p<d>) not runningThe indicated worker is not in the RUNNING stateContact Informatica support with all relevant log files
Umds-6033-712: umdsd_worker_api_conn_add: worker p<d> waiting to add new connectionThe client request to add a connection to this worker is still pending.The main UM context thread is unusually busy at this time but will eventually serve this request.
Umds-6033-715: umdsd_worker_api_delete: quit skipped (ctx=p, thrd_running=d)The context or worker thread has already shutdownShutdown is already in progress
Umds-6033-716: umdsd_worker_api_delete: error joining worker (p<d>) thread (d)An error occurred joining the worker thread during shutdown.It is likely this is a result of multiple shutdown requests. However if this error is seen on multiple occasions, please report it along with any applicable configuration and log files to GCS.
Umds-8218-1: s: error: 's', appl_name='s'The UMDS client failed to authenticate.Check authentication credentials and server auth configuration.
Umds-8366-1: Unknown receiver type deleting umdsd_rcv <p>An unknown receiver type was encountered while deleting a UMDS receiver object.This is an internal error and should be reported to customer support; please include all appropriate version numbers (UM and UMDS), associated configuration files and any other pertinent details.
Umds-8366-2: failed to free umds unique receiver pThe UMDS server (umdsd) encountered an error deleting the UM receiver associated with the umds_rcv objectThis is an internal error and should be reported to customer support; please include all appropriate version numbers (UM and UMDS), associated configuration files and any other pertinent details.
Umds-8366-3: failed to free umds wc receiver pThe UMDS server (umdsd) encountered an error deleting the UM wildcard receiver associated with the umds_rcv objectThis is an internal error and should be reported to customer support; please include all appropriate version numbers (UM and UMDS), associated configuration files and any other pertinent details.
Umds-8366-4: Unknown receiver type deleting umdsd_rcv <p>An unknown receiver type was encountered while freeing a UMDS receiver object.This is an internal error and should be reported to customer support; please include all appropriate version numbers (UM and UMDS), associated configuration files and any other pertinent details.
Umds-8366-5: Unknown receiver type deleting umdsd_rcv <p>An unknown receiver type was encountered while deleting a UMDS receiver object.This is an internal error and should be reported to customer support; please include all appropriate version numbers (UM and UMDS), associated configuration files and any other pertinent details.
Umds-8406-1: umdsd_stats_queue_internal_cmd_cb: src create before delete. is <d>The webmon statistics subsystem got a source create for an already existing source id (the intended src structure was not NULL in the source array).It is possible for creation and deletion to happen out of order.
Umds-8406-2: umdsd_stats_queue_internal_cmd_cb: src delete before create. id <d>The webmon statistics subsystem got a source delete for an already deleted source id (the intended src structure was NULL in the source array).It is possible for creation and deletion to happen out of order.
Umds-8406-3: umdsd_stats_queue_internal_cmd_cb: rcv create before delete. id <d>The webmon statistics subsystem got a receiver create for an already existing receiver id (the intended rcv structure was not NULL in the receiver array).It is possible for creation and deletion to happen out of order.
Umds-8406-4: umdsd_stats_queue_internal_cmd_cb: rcv delete before create. id <d>The webmon statistics subsystem got a receiver delete for an already deleted source id (the intended rcv structure was NULL in the receiver array).It is possible for creation and deletion to happen out of order.
Umds-8408-1: umdsd_worker_api_delete: waiting for worker p<d> to quitThe request to remove a worker is still pending.The worker thread is unusually busy at this time but will eventually serve this request.
Umds-8447-1: umdsd_worker_handle_blocked_msg: Parse ErrorThe client connection parser encountered an unrecoverable error.This is an internal error, if it recurs, please report it along with any relavant log files to GCS.
Umds-8499-1: LBM error while sending request: sLBM returned an unhandled error code.The LBM error code is given in the log message. Please refer to the LBM error code.
Umds-8499-2: LBM error while sending message: sLBM returned an unhandled error code.The LBM error code is given in the log message. Please refer to the LBM error code.
Umds-8499-3: LBM error while sending response: sLBM returned an unhandled error code.The LBM error code is given in the log message. Please refer to the LBM error code.
Umds-8519-1: Attempt to send without a valid source created: conn pThe UMDS client has sent a message before the umdsd server has created the corresponding source.This will result in the loss of the client message. Please notify GCS with all suitable logs (client and server).
Umds-8519-2: Attempt to send without a valid source created: conn pThe UMDS client has sent a message before the umdsd server has created the corresponding source.This will result in the loss of the client message. Please notify GCS with all suitable logs (client and server).
Umds-8519-3: Attempt to send without a valid source created: conn pThe UMDS client has sent a message before the umdsd server has created the corresponding source.This will result in the loss of the client message. Please notify GCS with all suitable logs (client and server).
Umds-8542-1: umdsd_worker_client_src_create: transport <s> not allowed, using TCP insteadThe UMDS server configuration file specified the use of LBT-SMX as a transport type, which is not supported. The server will use TCP instead.Change the server configuration file to specify one of the supported transport types.
Umds-8544-11: Error creating source: <d>: s An error occurred creating the request source.The text of the warning will provide additional information for the resolution of the problem.
Umds-8544-1: Error creating source: <d>: s An error occurred creating the request source.The text of the warning will provide additional information for the resolution of the problem.
Umds-8697-1: umdsd_worker_api_create: Error creating RO-Contex while creating worker p<d>Creating the reactor only context for a worker failed.This fatal error is usually due to specifying too many workers.
Umds-8697-2: umdsd_worker_api_create: Error creating thread while creating worker p<d>Creating the worker application thread failed.This fatal error is usually due to specifying too many workers.
Umds-8753-1: Attempt to send without a valid source created: conn pThe UMDS client has sent a message with a wrong or garbage tidx; either the client is buggy or t he server is receiving garbage data.This will result in the loss of the client message. Please notify GCS with all suitable logs (client and server).
Umds-8753-2: Attempt to send without a valid source created: conn pThe UMDS client has sent a message with a wrong or garbage tidx; either the client is buggy or the server is receiving garbage data.This will result in the loss of the client message. Please notify GCS with all suitable logs (client and server).
Umds-8757-1: s: malformed connect capabilitiesThe UMDS client sent a malformed capabilities string.Make sure the client and server versions are compatible and that data from another application isn't being erroneously sent to the UMDS server.
Umds-8796-100: Error creating umdsd_rcv_topic: <d>: s An internal error occurred while creating a receiver in the UMDS server.Contact Informatica support.
Umds-8894-1: umdsd_worker_internal_cmd_add_sock: worker(p<d>) not runningThe indicated worker is not in the RUNNING stateContact Informatica support with all relevant log files
Umds-8894-2: umdsd_worker_internal_cmd_add_sock: worker p<d> connection p<d> (s:u) createdNotification that a new client connection has been added.No resolution is required.
Umds-8896-1: umdsd_webmon_api_create: failed to init web server (ip=s, port=s)The web monitor subsystem failed to start.The web server library will have reported additional details to the console.
Umds-8909-1: UMDS Permissions are no longer appliedPermissions are no longer supported in the UMDS server XML configuration file.Remove any permissions sections from the server's XML config file.
Umds-8909-2: get_application: UMDS Permissions are no longer appliedPermissions are no longer supported in the UMDS server XML configuration file.Remove any permissions sections from the server's XML config file.
Umds-8909-3: get_user: UMDS Permissions are no longer appliedPermissions are no longer supported in the UMDS server XML configuration file.Remove any permissions sections from the server's XML config file.
Umds-8947-1: Error creating umdsd_rcv_topic: <d>: s An underlying regular receiver for a topic could not be created for a wildcard receiver.

This would usually imply an out of memory problem or some other internal error; contact Informatica support.