QNX RTOS v4 Knowledge Base
QNX RTOS v4 Knowledge Base
| Title |
Phindows Error Messages |
| Ref. No. |
QNX.000009515 |
| Category(ies) |
Configuration |
| Issue |
1: Phindows server failing with "Connection Error 19"
2: I just set up a system and I get connection error 89
3: Launching Phindows yields a dialog box indicating it could not connect to IP xxx.xxx.xxx.xxx
4: Trying to start Phindows, I get the message "could not link phlib_s11, no such file or directory".
|
| Solution |
Issue 1: Phindows server failing with "Connection Error 19"
Error 19 is ENODEV, which means phrelay was unable to connect to or create a Photon session. This can have various meanings:
1. There are not enough Photon licenses on the QNX node.
2. You may have run out of memory, or processes, or sessions -- check the output of sin, and adjust the appropriate resource in your boot image.
3. You may have run out of Pseudo Terminals (PTY's). To increase the number of pty's, add the -n option to Dev.pty. There is a maximum of 16 ptys' for each Dev.pty. Each connection will take 1 pty. If you need more then 16 connections, you can start mutliple instances of Dev.pty. Simply add the -l option to Dev.pty: Dev.pty -l c -n16 &
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Issue 2: I just set up a system and I get connection error 89
You are not using compatible versions. Phindows version 1.10 will ONLY work with the phrelay which is shipped with Photon 1.10. Phindows 1.20 will fail to connect to a 1.10 phrelay, and the 1.10 version of phindows will fail to connect to a 1.0 version of phrelay.
These unsuccessful connections display the rather unfriendly error message "Connection error 89". This is defined in /usr/include/errno.h as ENOSYS -- "Unknown system call".
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Issue 3: Launching Phindows yields a dialog box indicating it could not connect to IP xxx.xxx.xxx.xxx
1) There is a bug in the version of inetd that ships with 4.23 Socket. If you define an RPC service in your inetd.conf file, all subsequent services (including phrelay):
a) display an RPC version number,
b) don't work.
The workaround is to define all rpc services at the end of the inetd.conf file. This bug was fixed with the version of inetd that ships with the 4.24 Socket.
2) Make sure you restart inetd, or at least hit it with a SIGHUP after you add phrelay to the inetd.conf file, and before you fire up Phindows.
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Issue 4: Trying to start Phindows, I get the message "could not link phlib_s11, no such file or directory". This only happens when Photon has not already been run on the server machine.
This was the result of a custom installation of Photon on the Phindows server node by the customer. As a result, the library was not the expected '/qnx4/photon/bin/phlib_s11' location. The customer had set thing up so that the ph script which started Photon used the correct location, which is why the object file in /dev/shmem/ was available if Phindows started after Photon.
The workaround is to either:
a) change your path to include the current location of the Photon libraries, or
b) before you start inetd from your sysinit.<node> file,run the library explicitly on its own. This will create the /dev/shmem/phlib_s11 object file.
|
|
