Problems with ACL

kaushikbramesh — Thu, 16 Feb 2006 05:27:20 GMT

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

Re: Problems with ACL

kaushikbramesh — Thu, 16 Feb 2006 06:31:46 GMT

Thanks Arun,

This solved my problem.

Regards
Kaushik

Re: Problems with ACL

Matti_Kurkela — Thu, 16 Feb 2006 07:08:29 GMT

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.

topic Re: Problems with ACL in Operating System - HP-UX

Problems with ACL

Re: Problems with ACL

Re: Problems with ACL

Re: Problems with ACL