This weekend I upgraded a machine from Photon 1.13 to Photon 1.14A.
On this machine, Phindows logins spend 2 seconds after the Rx Connect
message and then 8 seconds before the login dialog appears.
On another machine, that was not upgraded, the Phindows login dialog
appears immediately, just as the first box responded before the
upgrade.
The machine descriptions follow:
Node CPU Speed Memory Hub/Switch
1 686 42465 103M/130M 100Mb
3 586 12810 23M/32M 10Mb
Node Photon PDM Phindows login time
1 1.14A 1.14 10 seconds
3 1.13 1.10 immediate
Furthermore, some users never get the Phindows login dialog after the
Rx Connect message when attempting to connect to Node 1.
However, they do connect instantly to Node 3.
Previously, Norman Branitsky wrote in qdn.public.qnx4:
Node Photon PDM Phindows login time
1 1.14A 1.14 10 seconds
3 1.13 1.10 immediate
Furthermore, some users never get the Phindows login dialog after the
Rx Connect message when attempting to connect to Node 1.
However, they do connect instantly to Node 3.
Looks exactly like my problem (see qdn.public.qnx4.photon, thread ‘phrelay timeout’)
I posted some debug outputs of ‘phrelay’ to Garry Turcotte from QSSL, but I didn’t get
any response, yet.
Basicly I found a ‘timeout’ in the logfiles of the V1.14 phrelay.
–
| / | __ ) | Karsten.Hoffmann@mbs-software.de MBS-GmbH
| |/| | _ _ \ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|| ||// Mobile: +49-172-3812373 D-47809 Krefeld
In article <ri4e0t0bfm9ao7dqlrj7ksoj49mhlgffev@4ax.com>,
Norman Branitsky <norman@cherniak.on.ca> wrote:
This weekend I upgraded a machine from Photon 1.13 to Photon 1.14A.
On this machine, Phindows logins spend 2 seconds after the Rx Connect
message and then 8 seconds before the login dialog appears.
I’ve been chasing this, unsuccessfully, on and off for the
last month…
Any chance you could get a network trace?
On another machine, that was not upgraded, the Phindows login dialog
appears immediately, just as the first box responded before the
upgrade.
The machine descriptions follow:
Node CPU Speed Memory Hub/Switch
1 686 42465 103M/130M 100Mb
3 586 12810 23M/32M 10Mb
Node Photon PDM Phindows login time
1 1.14A 1.14 10 seconds
3 1.13 1.10 immediate
Furthermore, some users never get the Phindows login dialog after the
Rx Connect message when attempting to connect to Node 1.
However, they do connect instantly to Node 3.
Try starting phrelay with -D/tmp/debugfile -VVVVVVVVV
(at least 8 V’s) and send me the debugfile for one of
the sessions that never get a login.
–
Garry Turcotte (R&D)
QNX Software Systems, Ltd.
In article <Voyager.001108095232.23744B@qnx-node9.mbs>,
Karsten P. Hoffmann <Karsten.Hoffmann@mbs-software.de> wrote:
Previously, Norman Branitsky wrote in qdn.public.qnx4:
Node Photon PDM Phindows login time
1 1.14A 1.14 10 seconds
3 1.13 1.10 immediate
Furthermore, some users never get the Phindows login dialog after the
Rx Connect message when attempting to connect to Node 1.
However, they do connect instantly to Node 3.
Looks exactly like my problem (see qdn.public.qnx4.photon, thread
‘phrelay timeout’)
I posted some debug outputs of ‘phrelay’ to Garry Turcotte from QSSL,
but I didn’t get
any response, yet.
I don’t have an answer, yet.
Basicly I found a ‘timeout’ in the logfiles of the V1.14 phrelay.
It seems to be something else that it’s waiting for, phrelay
has to be essentially idle to get the timeout…
–
Garry Turcotte (R&D)
QNX Software Systems, Ltd.
We have noticed similar things here.
The first is that the security upgrade did not successfully change the
phlogin binary first time. No idea why, but when we manually copied it
(phlogin.new to phlogin) all came good again.
But.
Now our right-click menu (photon windows manager workspace menu) also
accessible from the “QNX” button in the lower-left corner sometimes
doesn’t work The interesting things are that nothing works in the menu
except the shutdown button - all other selections just make the menu go
away. The other interesting thing is that it only sometimes doesn’t work.
We have a suspicion that the first phindows session started after a reboot
works as normal, but subsequent ones do not. We also have a suspicion as
to whether it makes a difference if the machines native (local) photon
session is running or not.
Garry Turcotte wrote:
In article <> ri4e0t0bfm9ao7dqlrj7ksoj49mhlgffev@4ax.com> >,
Norman Branitsky <> norman@cherniak.on.ca> > wrote:
This weekend I upgraded a machine from Photon 1.13 to Photon 1.14A.
On this machine, Phindows logins spend 2 seconds after the Rx Connect
message and then 8 seconds before the login dialog appears.
I’ve been chasing this, unsuccessfully, on and off for the
last month…
Any chance you could get a network trace?
On another machine, that was not upgraded, the Phindows login dialog
appears immediately, just as the first box responded before the
upgrade.
The machine descriptions follow:
Node CPU Speed Memory Hub/Switch
1 686 42465 103M/130M 100Mb
3 586 12810 23M/32M 10Mb
Node Photon PDM Phindows login time
1 1.14A 1.14 10 seconds
3 1.13 1.10 immediate
Furthermore, some users never get the Phindows login dialog after the
Rx Connect message when attempting to connect to Node 1.
However, they do connect instantly to Node 3.
Try starting phrelay with -D/tmp/debugfile -VVVVVVVVV
(at least 8 V’s) and send me the debugfile for one of
the sessions that never get a login.
–
Garry Turcotte (R&D)
QNX Software Systems, Ltd.