| Title: | note 3 has pointer to current kit |
| Notice: | note 3 has pointer to current kit |
| Moderator: | PEACHS::GHEFF |
| Created: | Wed May 29 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3301 |
| Total number of notes: | 14905 |
Hello,
Our customer is having problems running an Xsession to an specific server
(Digital UNIX). He has no problems running any other application
(clock, paint, term, etc.) or even Xsessions on other servers.
We were able to run the Xsession remotely from the server (ie. running
dxsession with DISPLAY on Multia ).
The only difference between this server and the rest, is that the server
is been started with a terminal instead of a monitor. mwm and dxsession
are not running on the servers (xdm is running on both). I wouldn't
think this is a problem, since the xsession could run remotely.
I'm posting the message log from the Multia and xdm-errors file from the
server.
I originally entered this note in the Multia conference, but I haven't
had any luck with an answer yet.
Thanks for your help,
Regards,
Katya
-< message.log and xdm-errors >-
--------------------------------------------------------------------------------
xt112:0 is the multia
message.log
-----------
1/24/97 8:17:13 PM X Server Information Multia X Server V2.1.275 (Alpha) logging enabled.
1/24/97 8:17:14 PM Network Warning socket(12) failed, error=ENOBUFS
1/24/97 8:17:15 PM Network Warning socket(12) failed, error=ENOBUFS
1/24/97 8:17:15 PM Network Warning socket(14) failed, error=ENOBUFS
1/24/97 8:17:15 PM Network Warning getnodeadd() failed, error=EAFNOSUPPORT
1/24/97 8:17:15 PM Network Warning getnodeadd() failed, error=EAFNOSUPPORT
1/24/97 8:17:15 PM Network Warning setsockopt(172) failed, error=ENOPROTOOPT
1/24/97 8:18:35 PM X Server Error XDMCP fatal error: Session failed Session 14 failed for display xt112:0: Cannot open display
xdm-errors
-----------
Creating DECnet socket: Protocol not supported
error (pid 2822): server open failed for xt112:0, giving up
error (pid 491): Display xt112:0 cannot be opened
error (pid 491): Display xt112:0 is being disabled
error (pid 5472): server open failed for xt112:0, giving up
error (pid 491): Display xt112:0 cannot be opened
error (pid 491): Display xt112:0 is being disabled
error (pid 5479): server open failed for xt112:0, giving up
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3227.1 | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Wed Jan 29 1997 11:44 | 26 | |
The only difference between this server and the rest, is that the server
is been started with a terminal instead of a monitor. mwm and dxsession
are not running on the servers (xdm is running on both).
I'm a bit confused by the above paragraph, maybe by some things I don't
know yet. Is "xdm" the thing that allows the excursion control panel's
xdmcp to work ?
What does "started with a terminal" or "started with a monitor" mean ?
Is the terminal "xterm" ? is the monitor the display tube ?
What version of excursion are you using ? Use "about" in excursion main
menu to find out.
I had trouble yesterday with x session to digital unix but my trouble happened
when i merely did this on unix:
> setenv DISPLAY ...
> dxsession
The trouble I had seemed to have something to do with long node names in
the access control list so it might be a different problem (I described
it elsewhere in this conf)
/Eric
| |||||
| 3227.2 | PEACHS::GHEFF | Got a head with wings | Wed Jan 29 1997 12:44 | 17 | |
>1/24/97 8:18:35 PM X Server Error XDMCP fatal error:
> Session failed Session 14 failed for display xt112:0: Cannot open
> display
So you can open a display on this very PC if you telnet to the Unix
system and explicitly provide a -display?
If the above is true, then I guess it's not an issue with access
restrictions.
>Creating DECnet socket: Protocol not supported
This one really puzzles me. Why would xdm even be looking at DECnet?
Is the PC running DECnet? Is it listed in the xdm xservers file, by
any chance?
#Gary
| |||||
| 3227.3 | NEOV00::KLOPEZ | Ay Caramba! | Wed Jan 29 1997 17:49 | 26 | |
Thanks for your replies,
I believe the customer is using Multia software version 3.1, I don't
remember the eXcursion version.
1. We can telnet to unix, setenv DISPLAY to Multia, and run dxsession
on server (mtya).
2. We can launch Xsessions (xdmcp:query) to two different workstations.
3. We can launch x applications from server (mtya): xclock, dxterm,
etc.
Server mtya boots without a graphics console (VT420), and workstations
have their graphics monitor (certainly ;-) when booting.
>Creating DECnet socket: Protocol not supported
I think it's strange too, but I can't think of a reason for this message.
When we tried to run the Xsession from the Multia we used xdmcp:query,
broadcast and indirect and they all listed server mtya, but none of
them worked.
Thanks for your help,
Katya
| |||||
| 3227.4 | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Thu Jan 30 1997 16:08 | 10 | |
Please make sure you're using the latest pathworks excursion field test as advertised elsewhere in here (within the last two weeks). Older servers, such as those shipped on multias I really can't help with as I've got so much work just supporting the "official" excursion. Thanks. /Eric | |||||