Ignite not allowed to access folders owned by BIN

[Mike_316]

Hey Folks,

OK. Here's one that has stumped everyone. I have a new installation of Ignite on a K200 running HPUX 10.20.

When Ignite installs, all of its files and directories are installed as owned by bin:bin, with permissions of rwxr-xr-x so only the owner of bin can write to them. HOWEVER the system is not recognizing Ignite as having permissions to write to these files and directories as bin.

What I mean is, I was getting an error when attempting to add a new client for recovery that it could not create a file under the /var/opt/ignite/recovery directory which was owned by bin:bin with rwxr-xr-x permissions. As sson as I changed those permissions to rwxrwxrwx I could add the client.

I have run into a dozen errors like that and corrected tham all by simply changing the permissions to rwxrwxrwx...BUT (here's the kicker) everytime you run a net recovery, it creates a new directpry based on the date/time stamp (owned by bin:bin with rwxr-xr-x) which it them canot write to. If you stop and start the recovery it creates a new directpry, and it failes so soon after creating the directory that I do not have time to jump in and change the permissions.

SO I need to find out why it feels Ignite, run as root, does not have the rights to write to files and directories owned by bin:bin with permissions of rwxr-xr-x.

CRAZY! and urgent actually!

Thanks in advance for all the help!
Mike

[Bill McNAMARA_1 · Accepted solution]

if you're doing a network recovery it's probably going to run as nobody..

I'm looking around for some info on this, I came across it before..

Later,
Bill

[Mike_316]

I am trying at this point to only make an archive of systems across the network from an Ignite server, however I DID see a number of directpries owned by nobody:nogroup if that's a helpfull clue. However, the directories that are actually causing the issue are the ones owned by bin:bin...but if Ignite is runningas nobody, that might explain it.

I was on the phone with HP support till 9PM last night and they were stumped too. This is a hard one.

Thanks!

[Patrick Wallek]

I have Ignite installed and the directory ownerships are bin:bin with the 755 permissions and I have no problems creating a network recovery archive.

The first question that came to mind was are you sure you're running as root?

Another thing is to make sure that your /etc/exports is set up appropriately to allow access to the /var/opt/ignite/recovery/archives directory.

Here is an excerpt from mine:

var/opt/ignite/recovery/archives/worf -anon=2,access=worf

What version of Ignite/UX are you running? I don't recall this as being a problem anywhere, but if you're not on version 3.5.89 then I'd go ahead and upgrade and see if that helps.

[Paula J Frazer-Campbell]

Hi

Check out nobody and bin in the passwd file:-

nobody:*:-2:-2::/:
bin:*:2:2::/usr/bin:/sbin/sh


Are default settings.


Paula

[Bill McNAMARA_1]

NFS is doing the nobody:nogroup thing...

You must have the recovery directory exported anon

as mentioned above.
vi /etc/exports
lalala..
exportfs -av


Bill

[Bill McNAMARA_1]

nice Shark thing!
http://www.utr.net/RIGHTMIK.HTM

;)

[Mike_316]

Hey Gang!

OK! With your help and the help of a very able technician at HP by the name of Margarita (like the drink...very nice accent) we got it figured out.

You guys were on the right track with the exports and nobody thing. When Ignite added the lines to the exports file, it was using anon=2 (assuming it was trying to make anon to equal bin.) Margarita had me change all the entires inthe exports file to anon=0 (for root) and everything is working fine.

As I add new machines for backup hopwever, I will need to be sure to add/modify all the lines inthe exports file that relate to Ignite as anon=0.

Thanks for everything!

Mike

P.S. I'm glad you liked the shark picture. Forgot I had that one on there :-D