NetApps 740 running 6.4.5.
All of a sudden starting to get permission denied errors on some of our NFS shares from our Tru64 Unix servers, not all of them but just some of them. And with some other weirdness where we could go into the top level but then get permission denied when trying to list the contents. The messages file had the following:
SamrGetGroupsForUsers: Exception rpc_s_unknown_reject caught. SamrCloseHandle: Exception rpc_s_connection_closed caught.
and then had a bunch of the following afterwards:
LsaOpenPolicy2: Exception rpc_s_assoc_grp_max_exceeded caught. SamrConnect2: Exception rpc_s_assoc_grp_max_exceeded caught.
CIFS was working fine, but I couldn't hit the filer throught the Computer Management console on the MMC. I checked processes and auditing on the Unix side and couldn't tie it down to a specific instance. Though I hated to do it, we ended up rebooting to restore services. I've tried Googling for this in reference to a NetApp box but am coming up empty handed. Can someone enlighten me on what might have occurred?
________________________________
Paul Maglinger, A+, CA, CCA, CET, MCSE
Systems Administrator Shoe Carnival Inc. (812)867-4674 pmaglinger@scvl.com
________________________________
6.4.5?? Looks like you hit the bug we saw in 2004. Upgrading to 6.5.2 fixed it. Workaround was to add entries in the /etc/hosts file of the filer. look for Bug 139351 related to name resolution. -G
On 12/7/06, Maglinger, Paul PMAGLINGER@scvl.com wrote:
NetApps 740 running 6.4.5.
All of a sudden starting to get permission denied errors on some of our NFS shares from our Tru64 Unix servers, not all of them but just some of them. And with some other weirdness where we could go into the top level but then get permission denied when trying to list the contents. The messages file had the following:
SamrGetGroupsForUsers: Exception rpc_s_unknown_reject caught. SamrCloseHandle: Exception rpc_s_connection_closed caught.
and then had a bunch of the following afterwards:
LsaOpenPolicy2: Exception rpc_s_assoc_grp_max_exceeded caught. SamrConnect2: Exception rpc_s_assoc_grp_max_exceeded caught.
CIFS was working fine, but I couldn't hit the filer throught the Computer Management console on the MMC. I checked processes and auditing on the Unix side and couldn't tie it down to a specific instance. Though I hated to do it, we ended up rebooting to restore services. I've tried Googling for this in reference to a NetApp box but am coming up empty handed. Can someone enlighten me on what might have occurred?
Paul Maglinger, A+, CA, CCA, CET, MCSE
Systems Administrator Shoe Carnival Inc. (812)867-4674 pmaglinger@scvl.com
bug 139351 does not affect 6.4.5 because it didn't use the same export cache method that 6.5.x does.
6.4 does forward dns lookups the moment you run exportfs -a 6.5 does reverse dns lookups the moment a client sends an RPC, then matches it according to the exportfs access list. Then it addes the IP to its exports cache.
It sounds like trying 'cifs resetdc' might be something to do next time, as it looks like it had trouble communicating with the domain controller.
On Thu, 7 Dec 2006, Sto Rage© wrote:
6.4.5?? Looks like you hit the bug we saw in 2004. Upgrading to 6.5.2 fixed it. Workaround was to add entries in the /etc/hosts file of the filer. look for Bug 139351 related to name resolution. -G
On 12/7/06, Maglinger, Paul PMAGLINGER@scvl.com wrote:
NetApps 740 running 6.4.5.
All of a sudden starting to get permission denied errors on some of our NFS shares from our Tru64 Unix servers, not all of them but just some of them. And with some other weirdness where we could go into the top level but then get permission denied when trying to list the contents. The messages file had the following:
SamrGetGroupsForUsers: Exception rpc_s_unknown_reject caught. SamrCloseHandle: Exception rpc_s_connection_closed caught.
and then had a bunch of the following afterwards:
LsaOpenPolicy2: Exception rpc_s_assoc_grp_max_exceeded caught. SamrConnect2: Exception rpc_s_assoc_grp_max_exceeded caught.
CIFS was working fine, but I couldn't hit the filer throught the Computer Management console on the MMC. I checked processes and auditing on the Unix side and couldn't tie it down to a specific instance. Though I hated to do it, we ended up rebooting to restore services. I've tried Googling for this in reference to a NetApp box but am coming up empty handed. Can someone enlighten me on what might have occurred?
Paul Maglinger, A+, CA, CCA, CET, MCSE
Systems Administrator Shoe Carnival Inc. (812)867-4674 pmaglinger@scvl.com
-
Maglinger, Paul -
Myles Uyema -
Sto Rage©