- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Ignite not allowed to access folders owned by BIN
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2002 07:02 AM
02-22-2002 07:02 AM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2002 07:06 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2002 07:12 AM
02-22-2002 07:12 AM
Re: Ignite not allowed to access folders owned by BIN
I was on the phone with HP support till 9PM last night and they were stumped too. This is a hard one.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2002 07:14 AM
02-22-2002 07:14 AM
Re: Ignite not allowed to access folders owned by BIN
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2002 07:21 AM
02-22-2002 07:21 AM
Re: Ignite not allowed to access folders owned by BIN
Check out nobody and bin in the passwd file:-
nobody:*:-2:-2::/:
bin:*:2:2::/usr/bin:/sbin/sh
Are default settings.
Paula
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2002 07:22 AM
02-22-2002 07:22 AM
Re: Ignite not allowed to access folders owned by BIN
You must have the recovery directory exported anon
as mentioned above.
vi /etc/exports
lalala..
exportfs -av
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2002 07:25 AM
02-22-2002 07:25 AM
Re: Ignite not allowed to access folders owned by BIN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2002 08:09 AM
02-22-2002 08:09 AM
Re: Ignite not allowed to access folders owned by BIN
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