Operating System - OpenVMS
1748125 Members
3218 Online
108758 Solutions
New Discussion юеВ

Re: What kills X sessions?

 
Selden Ball
Advisor

Re: What kills X sessions?

Thanks to all who've been trying to help.

The network traces are very strange. Here's what our Linux expert reports.
===============================
Theproblem now seems to be jumping between cesr27 and cesr28.
Various logs of packets can be found in /home/dab66/xdmcp_packets/.

I captured packets for two separate attempts using:
tshark -R "ip.addr == 192.168.1.27"

I started an XDMCP sesssion on cesr27 as follows.
/usr/X11R6/bin/X -ac -once -query cesr27

On both attempts, the login window for cesr27 appeared for more than
10 seconds before the session terminated automatically. You can find
the packet captures in cesr27.log and cesr27.1.log.

Later on, the connections succeeded. A log of the packets from a
successful session can be found at cesr27_successful.log.

And finally, a log of packets from a successful connection to cesr28
is in cesr28_successful.log.
========================
Some of the failing sessions have keepalives in the packetlogs and some do not.
Some of the working sessions have keepalives in the packetlogs and some do not.

I can provide the logs to anyone who is willing to take a look.

*sigh*

Richard W Hunt
Valued Contributor

Re: What kills X sessions?

Take a look at the release notes for DWMOTIF ECO05, which includes information regarding problems with X connections between OpenVMS an a UNIX-class system. If you haven't applied that patch, it might be useful to you.
Sr. Systems Janitor
Olivier B
Advisor

Re: What kills X sessions?

I used to loose also windows after a short delay. I don't remember if it was the same error as yours but my solution was to recreate the display in sys$sylogin with these few commands :

$ if (f$trnlnm ("Decw$Display") .nes. "")
$ then
$ TmpSetOn = (f$environ ("ON_SEVERITY") .nes. "NONE")
$ Set NoOn
$
$ Define /User Sys$output NLA0:
$ Show Display /Symbol
$ if (DECW$DISPLAY_TRANSPORT .nes. "LAT")
$ then
$ Set Display /Create /Node= "''DECW$DISPLAY_NODE'" -
/Transport= "''DECW$DISPLAY_TRANSPORT'" -
/Screen= "''DECW$DISPLAY_SCREEN'" -
/Server= "''DECW$DISPLAY_SERVER'"
$ endif
$
$ if (TmpSetOn) then Set On
$ endif

Selden Ball
Advisor

Re: What kills X sessions?

@Richard: we've updated to eco 5. no change :(
(we were at 3)

@Olivier: the timeouts happen even with just the login prompt on the screen, before logging in, so I fear that setting the display variables won't help :(

I sent a tcpdump to Process software (the Multinet vendors). They're puzzled, too.

More *sigh*s.
Steve Reece_3
Trusted Contributor

Re: What kills X sessions?

Stupid thought but...
have you looked at what OPCOM is telling you when the jobs die?
have you tried increasing quotas to see if it's actually a quotas related issue?