Ignite-UX Permission Errors.

[Warren griggs]

Hi All,

I am getting strange errors from my Ignite-UX make_net_recovery. I have had this running for months with no problems and now I have started getting errors. (See attached file)

It mounts the nfs drive ok but when reading certain files in comes back with permission denied.

The first file it has trouble with is ...

/var/opt/ignite/clients/hostname1/recovery/client_status

Permissions for this file are...

-rw-r----- 1 root sys 290 Feb 10 00:46 client_status

The second file is ...

/var/opt/ignite/clients/hostname1/CINDEX

Permissions are ...

-rw-r----- 1 root sys 789 Feb 10 00:46 CINDEX

Obviously the client is having trouble reading these files with these permissions. What I don't understand is 1) Why has this suddenly changed? 2) Ignite is creating these files so why with the wrong perms?

Nothing has been changed on this system by an admin.

Any ideas on what I can do to sort this out?

Thanks in advance,
Colin.

[Robert-Jan Goossens]

Hi Colin,

Don't no what caused this, but your files should be with 666 permission.

Robert-Jan

[Alex Glennie · Accepted solution]

a) restrictive umask ? release notes for IUX 4.1.61 refer that this can cause problems

b) someone editted the files ?

c) /etc/exports: but contents should be defaults and created by IUX.

[Warren griggs]

Thanks for your speedy responses. It seems that the restrictive mask has caused the problem. I will change and see how I get on.

Thanks again,

Colin.

[Sundar_7]

Hi Colin,

Make sure u add the option "anon=-2" in the NFS export option in the Ignite-UX server.

Remember root in the NFS client will be treated as NOBODY by the NFS server for determining the permissions.

Thanks,

Sundar.