| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3520.1 | See documentation | STAR::VATNE | Peter Vatne, VMS Development | Wed Oct 24 1990 12:48 | 20 |
| >-SYSTEM-F-PATHLOST, path to network partner node lost
Direct from the VMS System Messages and Recovery Procedures
Reference Manual: Part II:
PATHLOST, path to network partner node lost
Facility: SYSTEM, VMS System Services
Explanation: The path to the remote node is lost due to too much network
activity or communications problems.
User Action: Wait, then check to see if the node is still reachable.
Unfortunately, I don't think this description goes far enough. You
should check with the system manager to see if there is some sort of
network problem on your machine. Typical problems include too much
paging for the NETACP process, too much routing, and hardware
problems on the ethernet devices.
|
| 3520.2 | | PSW::WINALSKI | Careful with that VAX, Eugene | Wed Oct 24 1990 15:51 | 17 |
| RE: .0, .1
Specifically, "path to network partner lost" means that your end of the DECnet
virtual circuit was expecting a message from the other end, got a timeout,
and exhausted its retry count. It therefore declared the connection as lost.
However, the underlying DECnet protocol layers still say that the remote node
is reachable.
All sorts of things can cause this problem. Popular causes include: remote
system crashed, system in the path between you and the remote system crashed,
hardware link between your node and the remote node suddenly got very busy,
hardware link somewhere between your node and the remote node suddenly got
very noisy or failed entirely. This isn't an X Windows problem, in any event.
If this problem persists, you should get your system manager and local network
support people involved in tracking it down.
--PSW
|
| 3520.3 | Symptomatic of some hardware? | MINIM::BAY | Jim CNF ENTP PPASEL DECterm | Thu Oct 25 1990 15:23 | 13 |
| re: <<< Note 3520.0 by CLARID::CHAMEROY >>>
>XIO: fatal IO error 65535 on X server "HEYDT::0.0"
65535 is a fairly common error message when using small, under-powered
workstations.
A particularly susceptible combination is a VS2000 with 14 MB which is
a satellite from a MVII/GPX. I can get most applications to fail with
this error just by starting too many applications (say 6-7).
Jim
|
| 3520.4 | | STAR::KLEINSORGE | Fred Kleinsorge, VMS Development | Fri Oct 26 1990 15:46 | 5 |
|
Yeah, it's kind-of common on 16mb PV0's with SPX's as well. Any
X11 workstation is an underpowered workstation.
|