NSS error : Error fixing visibility of trustees that were being added or removed when the system crashed.

  • 7017061
  • 09-Dec-2015
  • 02-Jun-2016

Environment

Novell Open Enterprise Server 11 (OES 11) Linux
Novell Open Enterprise Server 2015 (OES 11) Linux

Situation

It is possible to encounter the following messages while activating volumes  :

[code/]
Activating volume "DATA"...
  ** Volume layout v36.03
  ** Volume creation layout v36.03
  ** Processing volume purge log
  ** ................................................................................
Error fixing visibility of trustees that were being added or removed when the system crashed
  ..Error fixing visibility of trustees that were being added or removed when the system crashed
...........Error fixing visibility of trustees that were being added or removed when the system crashed
......Error fixing visibility of trustees that were being added or removed when the system crashed
Error fixing visibility of trustees that were being added or removed when the system crashed
..Error fixing visibility of trustees that were being added or removed when the system crashed
....Error fixing visibility of trustees that were being added or removed when the system crashed
..Error fixing visibility of trustees that were being added or removed when the system crashed
..
Sep 2, 2015  11:20:21 pm  NSS<COMN>-4.16a-714: zasAuthModel098]
    Error removing visibility for trustees just removed

[/code]

Resolution

This has now been resolved with the release of the May '16 Scheduled Maintenance update for OES.

Cause

The root cause for this message to be displayed, was when files, and/or folders with trustee assignments are being salvaged.
The message indicates there is a NSS visibility rights problem.

Additional Information

The problem is a NSS visibility problem.

Basically the solution released in May 16 ' Scheduled Maintenance update will prevent this NSS visibility problem from being introduced when files/folders with trustee assignments are salvaged going forward.
The catch here is that it will not fix existing NSS visibility problems, but that it will prevent new problems from occurring.

As long as any messages as this has been observed in for example 'nsscon', a NSS visibility rebuild for needs to be performed for the volume reporting this behavior :
"Error fixing visibility of trustees that were being added or removed when the system crashed"

Please note, depending on the size of the volume, and the amount of data, this may be a long and time-consuming process to go through the entire file system and walk through all trustees.

For example, running a NSS Visibility Rebuild for a volume named DATA from a terminal session :

 --- cut here ---
server01 #  nsscon /VisibilityRebuild=DATA

Visibility rebuild started on volume "DATA".
Visibility rebuild: Removing visiblity information from DATA
Visbility rebuild: Rebuilding visiblity information on DATA
Visibility rebuild finished on volume DATA
Objects examined: xxxxxx
Objects cleaned: xx
Overflow objects removed: 0
Trustees re-added: xx
--- cut here ---

This will execute the rebuild within the NSS Console itself, as such, so following the rebuild, type 'exit'  to leave the nsscon session and be taken back to the terminal prompt.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.