66.0 STREAMS Messages
The following includes messages from STREAMS.NLM.
STREAMS-X-6: The routine timeout could not allocate number bytes of memory. This may cause applications to lock up waiting for a timer event that will never happen.
Source:
STREAMS.NLM
Explanation:
The function could not allocate the requested number of bytes for the timer structure. Applications waiting for timer events might hang when these events do not occur.
Possible Cause:
The server might not have enough available memory.
STREAMS-X-9: Number invalid handles were passed to StreamCancel from StreamCleanup. A STREAMS protocol module or device may have been unloaded prematurely!
Source:
STREAMS.NLM
Explanation:
This is not a fatal error, but allocated memory pieces might become lost.
Possible Cause:
The indicated number of invalid file handles were passed to the function StreamCancel from StreamCleanup. A STREAMS protocol module might have been unloaded prematurely.
Action:
If the problem persists, contact a Novell support provider or the application developer.
STREAMS-X-16: An invalid streamtab pointer was used for protocol device name; device cannot be installed.
Source:
STREAMS.NLM
Explanation:
A called function could not install the device.
Possible Cause:
A pointer to the streamtab is invalid.
Action:
If you have access to developer documentation, consult it for the proper streamtab pointer format. If the problem persists, contact a Novell support provider or the application developer.
STREAMS-X-18:The protocol device name name is too long; device cannot be installed.
Source:
STREAMS.NLM
Explanation:
The device specified cannot be installed.
Possible Cause:
The name specified for the device is too long.
Action:
If you have access to developer documentation, consult it for the valid name length. If the problem persists, contact a Novell support provider or the application developer.
STREAMS-X-21: An invalid streamtab pointer was used for protocol module device_name; module cannot be installed.
Source:
STREAMS.NLM
Explanation:
A called function could not install the module.
Possible Cause:
A pointer to the streamtab is invalid.
Action:
If you have access to developer documentation, consult it for the proper streamtab pointer format. If the problem persists, contact a Novell support provider or the application developer.
STREAMS-X-23: The protocol module name device_name is too long; module cannot be installed.
Source:
STREAMS.NLM
Possible Cause:
The name specified for the module is too long.
Action:
If you have access to developer documentation, consult it for the valid name length. If the problem persists, contact a Novell support provider or the application developer.
STREAMS-X-28: Unable to allocate a queue within the sth_ipush function; module not added to stream.
Source:
STREAMS.NLM
Explanation:
The sth_ipush function could not allocate a queue, so the new module was not added to the stream.
Possible Cause:
The server does not have enough available memory.
STREAMS-X-29: Unable to unlink modules within the sth_osr_close function.
Source:
STREAMS.NLM
Explanation:
The sth_osr_close function could not unlink the modules.
Action:
If the problem persists, contact a Novell support provider or the application developer.
STREAMS-X-32: Could not perform the I/O control operation from within the sth_unlink function; closing anyway.
Source:
STREAMS.NLM
Explanation:
The sth_unlink function could not perform the ioctl operation, but it will continue closing the application or process anyway.
Action:
If the problem persists, contact a Novell support provider or the application developer.
STREAMS-X-87: Could not allocate a callback control structure within the bufcall function. This may cause applications to lock up waiting for a callback event that will never happen.
Source:
STREAMS.NLM
Explanation:
Bufcall could not allocate a callback control structure. Not having a callback control structure might cause the application to lock up while waiting for a callback event that will never happen.
Possible Cause:
The server does not have enough available memory.
STREAMS-X-88: An undetermined cleanup error occurred with device name; unloading will continue.
Source:
STREAMS.NLM
Explanation:
The unloading procedure for the device will continue.
Possible Cause:
The exact cause of this error is unknown.
Action:
No further action is required.
STREAMS-X-89: An undetermined cleanup error occurred with module name; unloading will continue.
Source:
STREAMS.NLM
Explanation:
The unloading procedure for the device will continue.
Possible Cause:
The exact cause of this error is unknown.
Action:
No further action is required.
STREAMS-X-90: The message name was too long to print using mi_printf.
Source:
STREAMS.NLM
Explanation:
The mi_printf function cannot print this message.
Possible Cause:
The messages is too long.
Action:
If the problem persists, contact a Novell support provider, the application developer, or the protocol developer.
STREAMS-X-91: An invalid handle was passed to StreamCancel from StreamCleanup. A STREAMS protocol module or device may have been unloaded prematurely!
Source:
STREAMS.NLM
Explanation:
The indicated number of invalid file handles were passed to the function StreamCancel from StreamCleanup. This is not a fatal error, but allocated memory might be lost.
Possible Cause:
A STREAMS protocol module might have been unloaded prematurely.
Action:
If the problem persists, contact a Novell support provider or the application developer.
STREAMS-X-95: Unable to locate signal structure in sig table list
Source:
STREAMS.NLM
Explanation:
The signal will be lost and the application might hang.
Possible Cause:
A function was unable to locate the signal structure from within the sig table list.
Action:
If the problem persists, contact a Novell support provider or the application developer.
STREAMS-X-113: An undetermined initialization error occurred with device name; STREAMS cannot load successfully.
Source:
STREAMS.NLM
Explanation:
An unknown error prevented the indicated device from being initialized. This device is necessary for STREAMS to operate correctly.
Action:
Try again. If the problem persists, contact a Novell support provider.
STREAMS-X-114: An undetermined initialization error occurred with module name; STREAMS cannot load successfully.
Source:
STREAMS.NLM
Explanation:
An unknown error prevented the indicated module from being initialized. This module is necessary for STREAMS to operate correctly.
Action:
Try again. If the problem persists, contact a Novell support provider or the application developer.
STREAMS-X-115: An undetermined cleanup error occurred with device name; unloading will continue.
Source:
STREAMS.NLM
Explanation:
The unloading procedure for the device will continue.
Possible Cause:
The exact cause of this error is unknown.
Action:
No further action is required.
STREAMS-X-116: An undetermined cleanup error occurred with module name; unloading will continue.
Source:
STREAMS.NLM
Explanation:
The unloading procedure for the device will continue.
Possible Cause:
The exact cause of this error is unknown.
Action:
No further action is required.
STREAMS-X-120: Attempted to send a signal to an NLM not initialized for signals; signal ignored.
Source:
STREAMS.NLM
Explanation:
The NLM program has not been initialized to receive the controlling signals.
Action:
Initialize the NLM program to receive and process signals. If the problem persists, contact a Novell support provider or the application developer.
STREAMS-X-121: NLM signal thread not waiting for a signal; number signals have been ignored.
Source:
STREAMS.NLM
Explanation:
This is an informational message explaining that the signal thread was not waiting for a signal, so it ignored the signals it received.
Action:
No further action is required.
STREAMS-X-131: Unable to create CLIB thread for controlling tty.
Source:
STREAMS.NLM
Possible Cause:
The controlling tty is used for some protocol management functions that will not be available.
Action:
If the problem persists, contact a Novell support provider or the application developer.