When using the Remote Agent for Linux/Unix Servers (RALUS) in a Solaris 10 cluster, it is not possible to browse and make selections. 'None' appears when selecting [ROOT].

If RALUS is put into debug mode, the following can be seen in the RALUS debug log:

  6 Mon May 25 14:43:20 2009 : vx_stat_by_name: Getting stat of /
  6 Mon May 25 14:43:20 2009 : ===> gfsp vxms plugin: memory allocation failed
  6 Mon May 25 14:43:20 2009 : ===> gfsp vxms plugin: memory allocation failed
  6 Mon May 25 14:43:20 2009 : ===> vf_newpgn: couldn't initialize libgfsp.so
  6 Mon May 25 14:43:20 2009 : ===> gfsp vxms plugin: memory allocation failed
  6 Mon May 25 14:43:20 2009 : ===> gfsp vxms plugin: memory allocation failed
  6 Mon May 25 14:43:20 2009 : ===> vf_newpgn: couldn't initialize libgfsp.so
  6 Mon May 25 14:43:20 2009 : ===> ufs vxms plugin: memory allocation failed
  6 Mon May 25 14:43:20 2009 : ===> ufs vxms plugin: memory allocation failed
  6 Mon May 25 14:43:20 2009 : ===> vf_newpgn: couldn't initialize libufs.so
  6 Mon May 25 14:43:20 2009 : Function vfmStatFileName, VxMS resolved the error code to this message:  object not claimed by any plugin
  6 Mon May 25 14:43:20 2009 : vx_stat: objname is / returned 2059

To confirm you are experiencing this issue, try the following which can be used as a temporary workaround:

Boot the nodes in non-cluster mode using the boot -x command. For more information, please refer to the following article:

 https://docs.sun.com/app/docs/doc/819-0580/6n30eahab?a=view

Workaround:

1. On 'Node 1' use the following command: mount | grep node@2. This is an example output: /global/.devices/node@2 on /dev/lofi/126

2. Check the above device using the following command: ls -la /dev/lofi/126. This is likely to return a 'No such file or directory' message.

3. Either unmount the above device or create a 'dummy' device with the same name. Then stop/start RALUS.

Note: Please consult Sun Technical Support before making the above changes.

This issue is currently under investigation by Veritas Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.  For information on how to contact Veritas Sales, please see  https://www.veritas.com

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.