HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Problems with ACL
Operating System - HP-UX
1834804
Members
2788
Online
110070
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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-15-2006 09:27 PM
02-15-2006 09:27 PM
Hi,
We have a strange problem with acl's for root, as a result the installation of products on the box is failing.
The acl on our box for root & host is as below.
TeMIP-nuncas02 # swacl -l root
#
# swacl Installed Software Access Control List
#
# For host: nuncas02:/
#
# Date: Thu Feb 16 10:17:50 2006
#
WARNING: An attempt to get the network host entry for "saj1" failed.
This may result in denial of access to users and agents at
this host. Check the spelling of this name, then your
"/etc/hosts" file, or your "/etc/resolv.conf" file and DNS
resolver configuration. The nslookup program may be helpful
in isolating this problem.
# Object Ownership: User= root
# Group=sys
# Realm=saj1
#
WARNING: An attempt to get the network host entry for "saj1" failed.
This may result in denial of access to users and agents at
this host. Check the spelling of this name, then your
"/etc/hosts" file, or your "/etc/resolv.conf" file and DNS
resolver configuration. The nslookup program may be helpful
in isolating this problem.
# default_realm=saj1
object_owner:crwit
user:root@nuncas01.reo.cpqcorp.net:crwit
user:root@nuncas02:crwit
user:root@nuncas03:crwit
any_other:-r---
===============================================
TeMIP-nuncas02 # swacl -l root
#
# swacl Installed Software Access Control List
#
# For host: nuncas02:/
#
# Date: Thu Feb 16 10:17:50 2006
#
WARNING: An attempt to get the network host entry for "saj1" failed.
This may result in denial of access to users and agents at
this host. Check the spelling of this name, then your
"/etc/hosts" file, or your "/etc/resolv.conf" file and DNS
resolver configuration. The nslookup program may be helpful
in isolating this problem.
# Object Ownership: User= root
# Group=sys
# Realm=saj1
#
WARNING: An attempt to get the network host entry for "saj1" failed.
This may result in denial of access to users and agents at
this host. Check the spelling of this name, then your
"/etc/hosts" file, or your "/etc/resolv.conf" file and DNS
resolver configuration. The nslookup program may be helpful
in isolating this problem.
# default_realm=saj1
object_owner:crwit
user:root@nuncas01.reo.cpqcorp.net:crwit
user:root@nuncas02:crwit
user:root@nuncas03:crwit
any_other:-r---
I have managed to update the acl for host and all the other global template files, however not able to do it for the root's acl.
Thanks in advance for all your suggestions.
Regards
Kaushik
We have a strange problem with acl's for root, as a result the installation of products on the box is failing.
The acl on our box for root & host is as below.
TeMIP-nuncas02 # swacl -l root
#
# swacl Installed Software Access Control List
#
# For host: nuncas02:/
#
# Date: Thu Feb 16 10:17:50 2006
#
WARNING: An attempt to get the network host entry for "saj1" failed.
This may result in denial of access to users and agents at
this host. Check the spelling of this name, then your
"/etc/hosts" file, or your "/etc/resolv.conf" file and DNS
resolver configuration. The nslookup program may be helpful
in isolating this problem.
# Object Ownership: User= root
# Group=sys
# Realm=saj1
#
WARNING: An attempt to get the network host entry for "saj1" failed.
This may result in denial of access to users and agents at
this host. Check the spelling of this name, then your
"/etc/hosts" file, or your "/etc/resolv.conf" file and DNS
resolver configuration. The nslookup program may be helpful
in isolating this problem.
# default_realm=saj1
object_owner:crwit
user:root@nuncas01.reo.cpqcorp.net:crwit
user:root@nuncas02:crwit
user:root@nuncas03:crwit
any_other:-r---
===============================================
TeMIP-nuncas02 # swacl -l root
#
# swacl Installed Software Access Control List
#
# For host: nuncas02:/
#
# Date: Thu Feb 16 10:17:50 2006
#
WARNING: An attempt to get the network host entry for "saj1" failed.
This may result in denial of access to users and agents at
this host. Check the spelling of this name, then your
"/etc/hosts" file, or your "/etc/resolv.conf" file and DNS
resolver configuration. The nslookup program may be helpful
in isolating this problem.
# Object Ownership: User= root
# Group=sys
# Realm=saj1
#
WARNING: An attempt to get the network host entry for "saj1" failed.
This may result in denial of access to users and agents at
this host. Check the spelling of this name, then your
"/etc/hosts" file, or your "/etc/resolv.conf" file and DNS
resolver configuration. The nslookup program may be helpful
in isolating this problem.
# default_realm=saj1
object_owner:crwit
user:root@nuncas01.reo.cpqcorp.net:crwit
user:root@nuncas02:crwit
user:root@nuncas03:crwit
any_other:-r---
I have managed to update the acl for host and all the other global template files, however not able to do it for the root's acl.
Thanks in advance for all your suggestions.
Regards
Kaushik
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2006 09:31 PM
02-15-2006 09:31 PM
Solution
Hi Kaushik,
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=192616
http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=5851
-Arun
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=192616
http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=5851
-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2006 10:31 PM
02-15-2006 10:31 PM
Re: Problems with ACL
Thanks Arun,
This solved my problem.
Regards
Kaushik
This solved my problem.
Regards
Kaushik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2006 11:08 PM
02-15-2006 11:08 PM
Re: Problems with ACL
Is the current hostname "nuncas02"?
Is the name "saj1" in any way related to this host?
This looks like the cases I've seen when the hostname, IP address or some other network parameter was changed without rebooting the server. Try to stop and restart the swagentd:
/sbin/init.d/swagentd stop
/sbin/init.d/swagentd start
It appears the swagentd reads the hostname and/or network parameters when it starts up and remembers them "forever". Restarting swagentd is often necessary after networking changes.
Is the name "saj1" in any way related to this host?
This looks like the cases I've seen when the hostname, IP address or some other network parameter was changed without rebooting the server. Try to stop and restart the swagentd:
/sbin/init.d/swagentd stop
/sbin/init.d/swagentd start
It appears the swagentd reads the hostname and/or network parameters when it starts up and remembers them "forever". Restarting swagentd is often necessary after networking changes.
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP