Xterm

[HU Wen]

Hello, everybody.

When I use the Xterm from my PC telnet, it appears often this message as follow,
fatal IO error 232 (Connection reset by peer) or KillClient on
X server "134.214.149.24:0.0". The X server on my PC is SCO Xvision7.0. Sometimes I use the text editor "NEDIT", it gave a warning message like this " Name: Xmdisplay
Classe:_MOTIF_GRAG_WINDOWDS has been destroyed". I wonder whether there is anybody who can help me? Thank you very much.

[Alex Glennie]

No but i can give you some general pointers =>

Applications running in the X Window System periodically get errors similar to the following:
# XIO: fatal IO error 232 (Connection reset by peer) on X server "jerryzx:0.0"
after 2330830 requests (2330526 known processed) with 69 events remaining.
What do these mean, and how can they be corrected?
RESOLUTION
An "XIO Fatal Error 232: Connection Reset By Peer" indicates that at some level the connection between the application that is running and the X server that is displaying the application was unexpectedly terminated. This can happen for a number of reasons, many of which are external to the program. These include (but are not limited to) the following:

Temporary loss of network connectivity
Poor network performance between the application and X server
Unexpected reset or termination of the X server
Unexpected behaviour of the X server

NOTE: The "X server" refers to the program or application that controls the graphics display and is responsible for managing the keyboard, mouse, and graphics display. Depending on the situation, this may refer to the "/usr/bin/X11/X" executable (on HP-UX and other versions of UNIX), an Xterminal, or a Windows-based X terminal emulator (such as Reflection/X or eXceed).


Unfortunately, this particular error is not very informative when it occurs by itself; however, it is often caused by other more fundamental problems that, if corrected, will also correct this error.

If this is a problem that has happened a single time and cannot be realistically repeated, this error is likely something that will be infeasible to trace down to a single cause (if there is one single cause. Sometimes this error is the culmination of several otherwise minor factors). However, if this error occurs on a semi-regular or (even better) a repeatable basis, then consider investigating and gathering additional information from the system (such as additional error logs (depending on the context of the application), possible X server and network troubleshooting information, and the like).

If this does fall in the latter case, consider the following events:

If this occurs while logging into CDE or HP-VUE, or as a result of abnormal termination of an X Window session, then investigate that problem.
Under what circumstances does this problem occur? What application(s) are running? Are any of them network-intensive?
How frequently does this occur? Can this be repeated "at will", or are there a certain set of circumstances that will increase the chances of this error occuring?
If the application is displayed remotely to the X server, what does the network topology "look like" between the application server and the X server? Are they on the same subnet? If they are not, approximately how "far" are they apart (both geographically and how many "hops" on the network).
Unfortunately none of these offer a single, definitive solution to this error message, but this particular error message has no single cause nor does it have a single solution (or set of solutions).

For further information, you consult "The Definitive Guides to the X Window System: Volume 1. The Xlib Programming Manual", specifically section 2.6.3.1 "Errors".

[HU Wen]

Thank you very for your kind responses.
In fact, this problem dispear when I restart my SCO Xvision server. I think that it maybe take place with my Xvision appilication. On the other hand, there is no proble when I work directly on the workstation console CDE. I will try it according to your advices.
Thanks again!!

[HU Wen]

Thank you very for your kind responses.
In fact, this problem dispear when I restart my SCO Xvision server. I think that it maybe take place with my Xvision appilication. On the other hand, there is no proble when I work directly on the workstation console CDE. I will try it according to your advices.
Thanks again!!

[Andreas Voss]

Hi,

this may be the cause that the kernel parameters npty and nstrpty are too low.
Try increasing this parameters on the HP box (rebooting is required).

Regards

[Rick Beldin]

I think the error is probably complaining about the lack of the property _MOTIF_DRAG_WINDOW which is used by the Motif toolkit as part of the drag and drop implmentation. I would suspect that the NEDIT application is looking for this property and not finding it. This is a window that is created offscreen for the purpuse of doing drag and drop transfers.

You should be able 'see' this property by doing:

xprop -root | grep _MOTIF_DRAG_WINDOW

The value of the property should be a window id, something like 0x1000001 - it will vary.

One thing you might check is to see if the window DOES exist by doing:

xwininfo -id -all

if it doesn't, then that would indicate that the window 'disappeared'.

It could be that some application that created this window has died or that some program killed it. I'm not sure how you would track it, other than to verify that the
property existed and validate what it points to.