Xt Warning: Color Name not defined

[Sylvain CROUET]

Hi!

I try to open an OpenView Motif interface on an X station but it fails and I get errors such like:
ovw: Xt Warning: Color name "cyan" is not defined
ovw: Xt Warning: Missing charsets in String to FontSet conversion

Can someone help me?

[Peter Godron]

Sylvain,
have you had a look at:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=224569

and many others if you search the forums with
"Missing charsets in String to FontSet conversion"

Regards

[Sylvain CROUET]

I already checked some other threads on the subject, but I think the problem is due to the X station. I use it to connect on the OVOU management server and then start the Motif GUI as system user opc_adm. When I try the same action once connected to the OVOU manager through Exceed, no problem.

[Alex Glennie]

OK what tyoe of Xstation are we talking ?

As to the first error it suggests to me there maybe problems wrt the colormap ... are you using the cyan color for ovw ? If yes does changing it to something else work OK ?

Is there an OVw resource file on your system that defines color definitions ?

As to the second ... I agree a font server may help but you need to add the path to the xterminals font path for it to be of any use ... it may not be causing the Motif interface to fail though.

[Sylvain CROUET]

It is an NCD Thin Client workstation.

Ovw uses the cyan color but I get messages for all other colors too.

In fact there should be a file describing the color but I do not know where it is.

[Sylvain CROUET]

I found those error in the X-Terminal messages:
%FILE-E-NOREAD: unable to read RGB file: /usr/lib/X11/ncd/rgb.txt
The rgb.txt file exists as a link on the TFTP server and has 777 rights. The colors like "cyan" are defined within this file.

[Alex Glennie]

maybe worth checking /usr/xekxp/boot/config/rgb.txt instead ? along with it's contents ?

[Sylvain CROUET]

No xekxp directory under /usr.

[Ermin Borovac]

On the TFTP server check tftp entry in /etc/inetd.conf.

tftpd probably does chroot to something like /tftpboot so rgb.txt path is interpreted relative to this directory. Thus it's looking for, e.g. /usr/lib/X11/ncd/rgb.txt.

[Sylvain CROUET]

I found those entries within /etc/inetd.conf:
tftp dgram udp wait root /usr/lbin/tftpd tftpd\
/opt/ignite\
/var/opt/ignite
bootps dgram udp wait root /usr/lbin/bootpd bootpd

Should I add the /usr/lib/X11/ncd directory to the tftp entry? Should I then stop and restart inetd?

[Ermin Borovac]

Yes you can add /usr/lib/X11/ncd to tftp entry in /etc/inetd.conf and then run 'inetd -c'.

Also make sure you kill off any tftpd processes if there are any running so that inetd can spawn a copy with new arguments/paths.

For security reasons you are also advised to define tftp user in passwd file unless you already have one.

tftp:*:510:101:tftp server:/home/tftpdir:/usr/bin/false

[Sylvain CROUET]

It does not work better. I still get the %FILE-E-NOREAD message at boot.

[Ermin Borovac]

Is /usr/lib/X11/ncd/rgb.txt or any of the directories in the path symbolically linked someplace else? If so, try adding real paths to tftpd line in /etc/inetd.conf.

Test tftp from command line. Login as normal user, and try to retrieve rgb.txt.

$ cd $HOME
$ tftp localhost
tftp> get /usr/lib/X11/ncd/rgb.txt
tftp> quit

If you don't find rgb.txt in $HOME tftpd is not allowed access to /usr/lib/X11/ncd.

[Sylvain CROUET]

It works. I login onto the system as root and su - to a normal user:
$ tftp localhost
tftp> get /usr/lib/X11/ncd/rgb.txt
Received 17903 bytes in 0.1 seconds
tftp> quit
$ exit
logout

[Ermin Borovac]

Are there any tftp errors in /var/adm/syslog/syslog.log?

Run 'inetd -l' and watch syslog.log as X station reboots. You should see a connection attempt (tftp/udp: connection from ...). If you don't then X station is not using correct TFTP server or is not using TFTP to get the files. Check X station settings to make sure it's using TFTP and not some other method such as NFS to get files (rgb.txt etc).

If X station is really trying to get rgb.txt via TFTP, then you could try tracing tftpd with tusc.

If you don't have tusc you can get it from here.

ftp://ftp.cup.hp.com/dist/networking/tools/

Attach to running tftpd with

# tusc -fv -o /tmp/tusc.log

Search /tmp/tusc.log for rgb.txt, to see what's happening to TFTP request from X station.

[Sylvain CROUET]

The inetd daemon runs now with the -l option:
root 9622 1 0 12:25:29 ? 0:00 /usr/sbin/inetd -l

But it does not log anything within /var/adm/syslog/syslog.log. I check it with a local successfull tftp connection.

[Ermin Borovac]

How is your /etc/syslog.conf configured?

You can place the following line in /etc/syslog.conf to capture all syslog messages.

*.debug/var/adm/syslog/debug.log

where is tab character on the keyboard.

Signal syslogd to re-read config file.

# kill -HUP `cat /var/run/syslogd.pid`

debug.log should now contain record of tftp connections.

[Sylvain CROUET]

Here is what I found in debug.log when I reboot the X terminal:
Apr 19 07:54:21 cexibck inetd[14987]: registrar/tcp: Connection from cexibck (57.11.127.41) at Tue Apr 19 07:54:21 2005
Apr 19 07:55:28 cexibck inetd[9622]: bootps/udp: bind: Address already in use
Apr 19 07:55:28 cexibck inetd[9622]: bootps/udp: Service enabled
Apr 19 07:56:21 cexibck inetd[15181]: registrar/tcp: Connection from cexibck (57.11.127.41) at Tue Apr 19 07:56:21 2005
Apr 19 07:58:21 cexibck inetd[15500]: registrar/tcp: Connection from cexibck (57.11.127.41) at Tue Apr 19 07:58:21 2005

It seems it does not use tftp to boot...

[Ermin Borovac]

Does your X station have a keyboard with 'Setup' key? When pressed it should invoke configuration menu where you can check settings. Or you can try pressing Alt and Setup at the same time.

Otherwise, there might be a way to interrupt X station boot process with Esc key or similar. Then you might be able to access configuration menu with 'se'.

On your HP-UX server check if there is an entry for your X station in /etc/bootptab.

[Sylvain CROUET]

Yes, there is an entry in /etc/bootptab for my terminal and I have several TCP/IP Boot options in the graphical setup menu (the terminal can boot and run CDE). Primary and Previous Boot Sources are configured to TCPIP. TFTP directory is / and NFS directory is /tftpboot/

[Ermin Borovac]

Maybe it's using TFTP for boot file and NFS for other files.

Try creating /etc/exports with the following lines on the server.

/tftpboot
/usr/lib/X11

# exportfs -av

[Ermin Borovac]

Any options where you can assign order to TFTP, NFS?

[Sylvain CROUET]

It does not work better with the new directories in /etc/exports.
The only options to set order for boot are related to the source (Previous, Primary, Secondary and Tertiary). Previous and Primary are set to TCPIP, Secondary and Tertiary to NONE

[Ermin Borovac]

Have a look in /usr/lib/X11/ncd/configs. X terminal looks in this directory for a file whose name is hex equivalent of its IP address or if that files does not exist, it uses ncd_std. Check these files and see if you can find anything of interest.

[Ermin Borovac · Accepted solution]

Can you please check to see if you can find File Service submenu in the Setup menu?

Setup => Change Setup Parameters => File Service => Initial File Server 1 & 2

Please check what values are set for file server 1 & 2.