Entria X-Terminal, Permission Denied when downloading file.

[Ben Williams]

I hope I am in the right area!?!. On booting up the XT try's to download the following file: /usr/lib/X11/700X/bin/c3231A, Permission Denied. BOOT FAILED. I have checked the permissions and everthing seems OK. The server from which it is trying to download is a HP9000 (10.2). What can I check?. I am a novice with these 'things'!.

Thanks in advance.

[Alex Glennie]

Try the following :

remsh get log : check for obvious errors !
remsh get config : will show current config

maybe worth you factory defaulting the xterminal , if its an HP box you can do this via the config GUI or by at boot time ( requires you to keep your fingers pressed down for some secs though !) Re-enter networking info and reboot.

If someones been editting the config this will return it to defaults.

Or : use the xtadm tool under the enware dir to test various settings etc... it may be networking ?

[Alex Glennie]

you could also try resetting the basepath to /opt/hpxt/enware/xthome/
and seeing if using NFS over TFTP makes any difference under the network config section of the config GUI.

best of luck !

[devin]

I too am having the same problem, I tried holding down shift-f9 and now my monitor does not come up correctly. It looks like the refresh rate is wrong or something and I can't see the gui to change the settings. Is there a way to do this manually or via command line?

[Bill McNAMARA_1]

I should really shut up...

To get your monitor back,
hold Alt then 1 0 2 4 on numeric keypad, try 800 or your monitor number.

Make sure that /opt/enware in NFS exported to world.

the Xterms root is over network. Make sure you have no network problems..

The file it's trying to download is it's kernel.

Shift 0 between the first beep and second will issue a Bootp request. Make sure that the Xterm is defined in your /etc/bootptab. If not there should be an /opt/hpxt/enware/ / xtadm confile script that will add it, or you can just edit the bootptab by hand.

On old entria pluses there is a slight problem.. is this an entria +? There's a good work around if it is.

Later,
Bill

[Kenneth Platz]

Ben,

The "Permission denied, boot failed" error usually occurs when either the TFTP or NFS settings on your file server are not configured correctly.

The NFS settings can be verified by checking the /etc/exports file. You should have a line similar to:

/opt/hpxt

In there. If you have a line similar to:

/opt/hpxt access=host1,host2,host3

You need to make sure that the hostname of your Entria is in the access list. If you make any changes to this file, you need to reread the exports file with the command:

exportfs -a

Now to check your TFTP settings, you need to check the TFTP configuration in /etc/inetd.conf. You should have a line similar to the following:

tftp dgram udp wait root /usr/lbin/tftpd tftpd /opt/hpxt /usr/lib/X11/700X

If you do NOT have the /opt/hpxt and/or /usr/lib/X11/700X entries at the end of this, you will need to add them. If the entry is commented out, you will need to uncomment it. If you make any changes to this file you will need to do an "inetd -c". Afterwards, check for any "tftp" processes running and kill them.

I hope this helps.

[Vincenzo Restuccia]

If You Receive a "Permission Denied" Message



Check the mount options in the /etc/fstab file on the NFS client. A directory you are attempting to write to may have been mounted read-only.
Issue the ls -l command to check the HP-UX permissions on the server directory and on the client directory that is the mount point. You may not be allowed access to the directory.
Issue the following command on the NFS server:
/usr/sbin/exportfs
Or, issue the following command on the NFS client:
/usr/sbin/showmount -e server_name
Check the export permissions on the exported directory. The directory may have been exported read-only to your client. The system administrator of the NFS server can use the remount mount option to mount the directory read/write without unmounting it. See To Change the Default Mount Options.

If you are logged in as root to the NFS client, check the export permissions to determine whether root access to the directory is granted to your NFS client.
If you are logged in as root to the NFS client, and your client is not allowed root access to the exported directory, check the passwd database on the NFS server to determine whether it contains an entry for user nobody. Without root access, the root user on an NFS client is given the access permissions of user nobody. Also, check whether anonymous users are denied access to the directory (with the anon=65535 export option).

If your client is not allowed root access or anonymous user ID access to the exported directory, log in as a non-root user to get access to the directory.
If you are not running NIS, or if the server is in a different domain from the client, check the passwd databases on the server and the client to make sure you have a valid login on both machines and that your user ID is the same on both machines. If your user ID is unrecognized on the NFS server, you will be granted the permissions of user nobody.
If you were attempting to run a program when you received the "permission denied" message, issue the ls -l command on the NFS server to check whether the program you tried to run has the setuid bit set. If it does, check /etc/fstab to determine whether the directory was mounted with the nosuid mount option. If necessary, remove the nosuid option from the /etc/fstab file, then unmount and remount the directory.

[Bill McNAMARA_1]

You can also from the config screen of the xterm, (F12), issue a telnet to any server on your network, just to ensure network is okay.

It is best however to use BOOTP for the terminals, and/or statically insert boot data from F12.

Once you get it up and running. remsh term get config and redirect it into the enware/config/terminal_IP.cfg file.
Edit the file and add the word SAVE to the end
remsh terminal reconfig to make sure the eeprom is burned.

If using tftp, enter the host twice in the server configuration... because of timeout problems.

You may also want to think of getting the latest Xterm software. Lots of bugs have been fixed in these guys over the years.

Later,
Bill

[Bill McNAMARA_1]

does your terminal boot yet?

How did you resolve ?

Bill