OpenSwitch log messages main to os_set_bind

Message text	Explanation and action
`main: Error calling srv_run().`	Check that you do not have a server already running on the same port and the same host.
`main: Unable to initialize context.`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`main: Unable to install shutdown handler.`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`main: Unable to install start-up handler.`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mem_dbg_alloc: Memory allocation failure`	OpenSwitch encountered a memory allocation failure. Check available memory on the OpenSwitch host and increase memory available to the OpenSwitch process, then restart OpenSwitch.
`mem_dbg_alloc: Ran out of free tracking nodes`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mem_dbg_init: Unable to allocate <N> bytes for hash table`	OpenSwitch encountered a memory allocation failure. Check available memory on the OpenSwitch host and increase memory available to the OpenSwitch process, then restart OpenSwitch.
`mem_dbg_init: Unable to allocate <N> bytes for heap`	OpenSwitch encountered a memory allocation failure. Check available memory on the OpenSwitch host and increase memory available to the OpenSwitch process, then restart OpenSwitch.
`mempool_alloc: Bogus memory handle!`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mempool_free: Bogus memory handle!`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mempool_free: Freeing unassigned block!`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mempool_getblock: Internal memory allocate error!`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mempool_getblock: mem_alloc() failed!`	OpenSwitch encountered a memory allocation failure. Check available memory on the OpenSwitch host and increase memory available to the OpenSwitch process, then restart OpenSwitch.
`mempool_init: Default_block_size <= 0!`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mempool_init: mem_alloc() failed!`	OpenSwitch encountered a memory allocation failure. Check available memory on the OpenSwitch host and increase memory available to the OpenSwitch process, then restart OpenSwitch.
`msgq__spid_alloc: Memory allocation failure`	OpenSwitch encountered a memory allocation failure. Check available memory on the OpenSwitch host and increase memory available to the OpenSwitch process, then restart OpenSwitch.
`msgq_clear: <QUEUE>: Unable to wake sleepers on spid <ID>`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`msgq_create: Memory allocation failure`	OpenSwitch encountered a memory allocation failure. Check available memory on the OpenSwitch host and increase memory available to the OpenSwitch process, then restart OpenSwitch.
`msgq_destroy: <QUEUE>: Unable to wake for spid <ID>`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`msgq_get: <QUEUE>: Unable to create entry for spid <ID>`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`msgq_put: <QUEUE>: Queue for spid <ID> is full`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`msgq_put: <QUEUE>: Unable to create entry for spid <ID>`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`msgq_put: <QUEUE>: Unable to wake sleepers on spid <ID>`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mtx__lock: Unable to lock global mutex`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`mtx__unlock: Unable to unlock global mutex`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mtx_create: <MUTEX/ADDRESS>: Unable to destroy mutex`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mtx_create: <MUTEX/ADDRESS>: Unable to unlock global list!`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mtx_create: <MUTEX>: Error while creating mutex <object name>`	OpenSwitch may have temporarily run out of memory or other resources for creating a mutex. Check previous errors in the OpenSwitch log file. Contact Sybase Technical Support if needed.
`mtx_create: <MUTEX>: Memory allocation failure`	OpenSwitch encountered a memory allocation failure. Check available memory on the OpenSwitch host and increase memory available to the OpenSwitch process, then restart OpenSwitch.
`mtx_create: <MUTEX>: Unable to create mutex`	OpenSwitch may have temporarily run out of memory or other resources for creating a mutex. Check previous errors in the OpenSwitch log file. Contact Sybase Technical Support if needed.
`mtx_create: <MUTEX>: Unable to unlock global list!`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mtx_create: Unable to lock global list`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`mtx_destroy: <MUTEX/ADDRESS>: Unable to lock global list`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`mtx_destroy: <MUTEX/ADDRESS>: Unable to unlock mutex`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`mtx_destroy: <MUTEX>: Attempt to destroy non-existant mutex <ADDRESS>`	An error during thread processing resulted in thread thrashing and some threads may have been corrupted. Contact Sybase Technical Support for assistance.
`mtx_destroy: Unable to destroy addr #<MUTEX> (mutex)`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mtx_destroy: Unable to unlock global list!`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`mtx_dump_all: Unable to lock global list`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`mtx_dump_all: Unable to unlock global list`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mtx_exit: Unable to destroy global mutex`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mtx_exit: Unable to destroy mutex #addr (mutex)`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mtx_exit: Unable to lock global mutex`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`mtx_init: Error while creating mutex <MUTEX>`	OpenSwitch may have temporarily run out of memory or other resources for creating a mutex. Check previous errors in the OpenSwitch log file. Contact Sybase Technical Support if needed.
`mtx_init: Unable to create mutex`	OpenSwitch may have temporarily run out of memory or other resources for creating a mutex. Check previous errors in the OpenSwitch log file. Contact Sybase Technical Support if needed.
`mtx_lock: NULL mutex handle passed`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mtx_sleep(<LABEL>): <MUTEX/ADDRESS>: Called from thread that does not own mutex`	An error during thread processing resulted in thread thrashing and some threads may have been corrupted. Contact Sybase Technical Support for assistance.
`mtx_sleep(<LABEL>): <MUTEX/ADDRESS>: Error unlocking mutex`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`mtx_sleep(<LABEL>): <MUTEX/ADDRESS>: Reference count must be 1 (rc=<N>)`	An error during thread processing resulted in thread thrashing and some threads may have been corrupted. Contact Sybase Technical Support for assistance.
`mtx_sleep(<LABEL>): <MUTEX/ADDRESS>: sleep failed, info=<info>`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mtx_sleep(<LABEL>): <MUTEX/ADDRESS>: tsleep_wait() failed`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`mtx_sleep(<LABEL>): <MUTEX/ADDRESS>: Unable to re-lock mutex`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`mtx_sleep(<LABEL>): <MUTEX/ADDRESS>: Unable to re-lock mutex after sleep fails.`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`mtx_unlock: <MUTEX/ADDRESS/ADDRESS>: Unable to unlock (rc=<N>)`	An error during thread processing resulted in thread thrashing and some threads may have been corrupted. Contact Sybase Technical Support for assistance.
`mtx_unlock: <MUTEX/ADDRESS/ADDRESS>: Unlock attempt by non-owner (rc=<N>)`	An error during thread processing resulted in thread thrashing and some threads may have been corrupted. Contact Sybase Technical Support for assistance.
`mtx_unlock: Invalid argument`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`opt_alloc: Memory allocation failure.`	Check available memory on the OpenSwitch host and limits, if any, on memory available to the OpenSwitch process.
`opt_exit: Error destroying opt_mtx.`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`opt_exit: Unable to lock opt_mtx.`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`opt_get: CONNECT_LOGIN_TIMEOUT is obsolete. Please use 'LOGIN_TIMEOUT' instead.`	Use the LOGIN_TIMEOUT property instead of the CONNECT_LOGIN_TIMEOUT property to specify the login time-out for the connection between OpenSwitch and Adaptive Server.
`opt_get: CONNECT_TIMEOUT is obsolete. Please use 'RESPONSE_TIMEOUT' instead.`	Use the RESPONSE_TIMEOUT property instead of the CONNECT_TIMEOUT property to specify the response time-out for the connection between OpenSwitch and Adaptive Server.
`opt_get: Error unlocking opt_mtx.`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`opt_get: Unable to lock opt_mtx.`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`opt_get_bool: Unable to get bool property`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`opt_init: Error creating option mutex.`	This is an internal OpenSwitch error. Check available memory on the OpenSwitch host and limits, if any, on memory available to the OpenSwitch process. Contact Sybase Technical Support for assistance.
`opt_parse: illegal option - <FLAG>.`	Check the validity of OpenSwitch command-line startup options. See the OpenSwitch Administration Guide for more information.
`opt_parse: option does not take an argument - <FLAG>.`	Check the validity of OpenSwitch command-line startup options. See the OpenSwitch Administration Guide for more information.
`opt_parse: option requires an argument -<FLAG>.`	Check the validity of OpenSwitch command-line startup options. See the OpenSwitch Administration Guide for more information.
`opt_set: Error unlocking opt_mtx.`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`opt_set: Memory allocation failure.`	Check the total memory on the OpenSwitch host and the memory available for the OpenSwitch process.
`opt_set: Unable to lock opt_mtx.`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`os_doneerror: srv_senddone(SRV_DONE_FINAL \| ERROR) failed!`	The client may have disconnected due to time-out or network errors. If the client connection is intact, contact Sybase Technical Support for assistance.
`os_doneerror: srv_thread_props(CS_GET, SRV_T_IODEAD) failed!`	This message is usually raised when a client disconnects abruptly due to time-out or some other reason. If OpenSwitch operation is not affected, you can ignore this message. Otherwise, contact Sybase Technical Support for assistance.
`os_get_bool: Unable to get bool property`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`os_get_params: Can't bind argument`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`os_get_params: Unable to transfer data from client`	The client may have disconnected due to time-out or network errors. If the client connection is intact, contact Sybase Technical Support for assistance.
`os_raise_error: srv_props(SRV_S_SERVERNAME) failed.`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`os_regexec: <REGISTERED_PROCEDURE_NAME>: Unable to bind parameters`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`os_regexec: <REGISTERED_PROCEDURE_NAME>: Unable to describe parameters`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`os_regexec: <REGISTERED_PROCEDURE_NAME>: Unable to execute`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`os_regexec: <REGISTERED_PROCEDURE_NAME>: Unable to initialize`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`os_regproc: Unable to create '<REGISTERED_PROCEDURE_NAME>'`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`os_regproc: Unable to define '<REGISTERED_PROCEDURE_NAME>'`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`os_regproc: Unable to register arg <ARGUMENT_NAME> of <REGISTERED_PROCEDURE_NAME>`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`os_sendmsg: i18n_xlate failed`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`os_sendmsg: Unable to get context`	Call to srv_thread_props (CS_GET, SRV_T_CONTEXT) failed. internal OpenSwitch message. Contact Sybase Technical Support to report this error.
`os_set_bind: Can't bind row data`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`os_set_bind: Unable to describe row format`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.