Highlighted
vimalkumar_v Absent Member.
Absent Member.
1552 views

server umounts NSS volumes for no obvious reason

OES2 SP1, 2-node cluster

I had a server unmount an NSS volume with the message below in the logs.
Any ideas what could have caused this?

SAN_SERVER is the cluster pool.
USERAREA is an NSS volume in the pool.

May 21 10:21:21 vishnu ncs-resourced: resourceMonitor: SAN_SERVER.monitor failed 256
May 21 10:21:21 vishnu ncs-resourced: resourceMonitor: SAN_SERVER 1 failures in last 600 seconds
May 21 10:21:25 vishnu adminus daemon: umounting volume USERAREA lazy=1
May 21 10:21:25 vishnu adminus daemon: Failed to delete the directory /media/nss/USERAREA. Error=39(Directory not empty)
May 21 10:21:25 vishnu adminus daemon: Entries for Volume USERAREA from pool SAN are not removed during pool deactivation
May 21 10:21:25 vishnu kernel: Waiting for 2 Inuse beasts to unlink
... repeated multiple times
May 21 10:21:36 vishnu kernel: fastReadCache - Buffer's should always have an inode
May 21 10:21:36 vishnu kernel: isCached - Buffer's should always have an inode
May 21 10:21:36 vishnu kernel: isCached - Buffer's should always have an inode
... repeated multiple times

Labels (1)
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: server umounts NSS volumes for no obvious reason

This looks as if you have a monitor script that is looking at your
resource - spots a failure and then starts a unload/load routine.

I think that your cluster monitor script has been copied from another
resource and has not been edited to reflect the change


T


On Tue, 22 May 2012 09:46:01 GMT, vimalkumar v
<vimalkumar_v@no-mx.forums.novell.com> wrote:

>
>*OES2 SP1, 2-node cluster
>*
>I had a server unmount an NSS volume with the message below in the
>logs.
>Any ideas what could have caused this?
>
>SAN_SERVER is the cluster pool.
>USERAREA is an NSS volume in the pool.
>
>
>Code:
>--------------------
> May 21 10:21:21 vishnu ncs-resourced: resourceMonitor: SAN_SERVER.monitor failed 256
> May 21 10:21:21 vishnu ncs-resourced: resourceMonitor: SAN_SERVER 1 failures in last 600 seconds
> May 21 10:21:25 vishnu adminus daemon: umounting volume USERAREA lazy=1
> May 21 10:21:25 vishnu adminus daemon: Failed to delete the directory /media/nss/USERAREA. Error=39(Directory not empty)
> May 21 10:21:25 vishnu adminus daemon: Entries for Volume USERAREA from pool SAN are not removed during pool deactivation
> May 21 10:21:25 vishnu kernel: Waiting for 2 Inuse beasts to unlink
> ... repeated multiple times
> May 21 10:21:36 vishnu kernel: fastReadCache - Buffer's should always have an inode
> May 21 10:21:36 vishnu kernel: isCached - Buffer's should always have an inode
> May 21 10:21:36 vishnu kernel: isCached - Buffer's should always have an inode
> ... repeated multiple times
>--------------------

0 Likes
vimalkumar_v Absent Member.
Absent Member.

Re: server umounts NSS volumes for no obvious reason

Thanks. The SAN_SERVER monitor script was not modified after the cluster was setup. This has been working before. I did have to reconfigure clustering on one of the nodes but that completed successfully.

The script is identical on both nodes and here are the contents
#!/bin/bash
. /opt/novell/ncs/lib/ncsfuncs
exit_on_error status_fs /dev/evms/SAN /opt/novell/nss/mnt/.pools/SAN nsspool
exit_on_error status_secondary_ipaddress cluster_ip_here
exit_on_error ncpcon volume USERAREA
exit 0

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: server umounts NSS volumes for no obvious reason

But you can see the error from your earlier post

May 21 10:21:21 vishnu ncs-resourced: resourceMonitor:
SAN_SERVER.monitor failed 256
May 21 10:21:21 vishnu ncs-resourced: resourceMonitor: SAN_SERVER 1
failures in last 600 seconds

T

On Tue, 22 May 2012 11:56:02 GMT, vimalkumar v
<vimalkumar_v@no-mx.forums.novell.com> wrote:

>
>Thanks. The SAN_SERVER monitor script was not modified after the cluster
>was setup. This has been working before. I did have to reconfigure
>clustering on one of the nodes but that completed successfully.
>
>The script is identical on both nodes and here are the contents
>
>Code:
>--------------------
> #!/bin/bash
> . /opt/novell/ncs/lib/ncsfuncs
> exit_on_error status_fs /dev/evms/SAN /opt/novell/nss/mnt/.pools/SAN nsspool
> exit_on_error status_secondary_ipaddress cluster_ip_here
> exit_on_error ncpcon volume USERAREA
> exit 0
>--------------------

0 Likes
changju Absent Member.
Absent Member.

Re: server umounts NSS volumes for no obvious reason

When monitoring is enabled for a resource, NCS will run the monitor script (repeatedly) after a polling interval. If the accumulated number of failures has reached the maximum local failures in the time interval, NCS will take the failure action. Before that happens, NCS will try self-healing by unloading and loading the resource on the same node if the monitor script completes with an error. That’s the reason why your volumes are dismounted.

You can check /var/opt/novell/log/ncs/resour_name.monitor.out (or /var/log/messages) for clues why your monitor script failed.

Best regards,

Changju
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.