Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments

Console messages

About console messages  Top

Some messages appear on the console but are not written to the /etc/messages file. Most of them are self-explanatory.

Troubleshooting a console message  Top

The following table explains the console message "The cluster partner appears not to be operational."

Message

Explanation

What you do

The cluster partner 
appears not to be 
operational.  You will 
be asked whether you 
want to continue.  If 
you answer "yes", the 
existing cluster 
monitor disk state 
will be overwritten 
and this node will be 
rebooted. Answering 
"no" will halt this 
node with no 
modification to the 
cluster monitor disk 
state.
WARNING: Answering 
"yes" while the 
cluster partner is 
operational will have 
unexpected and 
potentially 
catastrophic results:
YOUR FILESYSTEMS MAY 
BE DESTROYED
 
Do you wish to 
continue [y/n]? 

The local filer has been taken over but its partner appears to be not operational. This message is usually preceded by the following message:

This node was 
previously 
declared dead. 
Pausing to check 
cluster
partner status ... 
partner not 
responding.
 
Thu Aug 13 
16:58:37 GMT 
[kbd_login_mgr]: 
Login from console

Complete these steps:

  1. Verify that the partner is operational or repair it.
  2. Reboot it.
  3. Perform a giveback from the partner. Giveback is the only method of ensuring that data is consistent after a takeover.
  4. If you cannot repair the partner, perform one of the following actions:
    • Contact Network Appliance Technical Support.
    • Enter y to continue and override the takeover and allow the local filer to reboot.

      Caution
      If you enter y and override the takeover, client applications might lose data that was written before the reboot.

Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments