topic Re: Ignite UX in Operating System - HP-UX

Ignite UX

maggie Coffey — Mon, 23 Apr 2001 18:52:30 GMT

Has any one seen these errros when setting up an Ignite server

./make_net_recovery -s exeter
* Creating NFS mount directories for configuration files.
ERROR: Could not open log file. Logging will be displayed to stdout

======= 04/23/01 15:45:51 EDT Started ./make_net_recovery. (Mon Apr 23
15:45:51 EDT 2001)
@(#) Ignite-UX Revision A.3.2.45
@(#) net_recovery (opt) $Revision: 10.515 $

* Testing pax for needed patch
* Passed pax tests.
ERROR: copy_file: Cannot open "/var/opt/ignite/recovery/client_mnt/0x00108335
4FB1/recovery/latest/archive_content": Permission denied (errno = 13)
NOTE: Detected entries in the defaults file at
/var/opt/ignite/recovery/client_mnt/0x001083354FB1/recovery/defaults.

* Checking Versions of Recovery Tools
WARNING: Could not open default log file: /var/opt/ignite/recovery/client_mnt/0
x001083354FB1/recovery/2001-04-23,15:45/recovery.log: Permission
denied (errno = 13)
ERROR: Specified file '/var/opt/ignite/recovery/client_mnt/0x001083354FB1/rec
overy/latest/archive_content' does not exist: Permission denied (errno
= 13)
ERROR: The list_expander command failed. This could be due to a problem with
the file: "/var/opt/ignite/recovery/client_mnt/0x001083354FB1/recovery
/latest/archive_content" - see messages above.

======= 04/23/01 15:45:54 EDT make_net_recovery completed unsuccessfully

Re: Ignite UX

Bill McNAMARA_1 — Tue, 24 Apr 2001 13:51:21 GMT

you want to make sure the file exists, is owned by bin:bin and want created with a mkdir -p option.

You also need to make sure the /etc/exports allows the server in question to read....

Later,
Bill

Re: Ignite UX

maggie Coffey — Tue, 24 Apr 2001 15:34:02 GMT

Ignite-us was installed from a download from HP's web site. It was installed per the README and install instructions from docs.hp.com

The make_net_recovery is the program that is supposed to be creating these files and directories. They are not being created with bin as the owner. But as follows
drwxrwxrwx 3 4294967294 nogroup 1024 Apr 23 14:57 0x001083957B45.

There must be something that I am missing here. I am doing all of this as root and the acl's are coming up as above.

/etc/exports is set wide open
for read write and execute on the /var and /opt directories.

There seems to me that way the directories are structured is flawed.
I had to create links in a couple spots to get parts of this to work.

Any suggestions?

Thanks
Maggie Coffey

Re: Ignite UX

CHRIS_ANORUO — Tue, 24 Apr 2001 15:41:52 GMT

Have you checked you /etc/exports file. The user group of nobody is coming from an NFS related file.

Re: Ignite UX

maggie Coffey — Tue, 24 Apr 2001 15:53:42 GMT

Here is the setting from the
/etc/exports file per the instructions.

/var -anon=2,access=exeter

Re: Ignite UX

marc seguin — Wed, 25 Apr 2001 06:04:57 GMT

command from client : ./make_net_recovery -s exeter
So "exeter" is your Ignite server, isn't it ?

So on exeter, the /etc/exports file should contain :
/var -anon-2,access=
with different from exeter !!!!!!

Re: Ignite UX

Bill McNAMARA_1 — Wed, 25 Apr 2001 09:18:42 GMT

I think Marks got it,
Your ignite server is exeter, which would explain the file not found problem.

you should issue a chown -R bin:bin on the client directory in any case.... make sure that the pax patch is installed or you may have trouble with your ACLs...

Later,
Bill

Re: Ignite UX

maggie Coffey — Wed, 25 Apr 2001 15:29:23 GMT

That was it Mark

Thanks to All