Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error when NETWORKER start

Status
Not open for further replies.

pporteau

Technical User
Jan 30, 2007
33
0
0
FR
Is some body knew those errors? [ponder]

09/13/07 14:28:18 nsrd: WARNING: NSR configuration database detected invalid resource /nsr/res/nsrdb/05/005f4811441fb52791f80da7~09/13/07 14:28:18 nsrd: Invalid resource saved at /nsr/res/nsrdb/dbg/005f4811441fb52791f80da7~
09/13/07 14:28:18 nsrd: WARNING: NSR configuration database detected invalid resource /nsr/res/nsrdb/06/01bb03424603ea5091f80da7~09/13/07 14:28:18 nsrd: Invalid resource saved at /nsr/res/nsrdb/dbg/01bb03424603ea5091f80da7~
09/13/07 14:28:18 nsrd: WARNING: NSR configuration database detected invalid resource /nsr/res/nsrdb/07/00bb03424603ea5091f80da7~09/13/07 14:28:18 nsrd: Invalid resource saved at /nsr/res/nsrdb/dbg/00bb03424603ea5091f80da7~
09/13/07 14:28:18 nsrd: WARNING: NSR configuration database detected invalid resource /nsr/res/nsrdb/08/01f903424603ea5091f80da7~09/13/07 14:28:18 nsrd: Invalid resource saved at /nsr/res/nsrdb/dbg/01f903424603ea5091f80da7~
09/13/07 14:28:19 nsrd: WARNING: NSR configuration database detected invalid resource /nsr/res/nsrdb/09/00c7507746bb3c9491f80da7~09/13/07 14:28:19 nsrd: Invalid resource saved at /nsr/res/nsrdb/dbg/00c7507746bb3c9491f80da7~
09/13/07 14:28:19 nsrd: WARNING: NSR configuration database detected invalid resource /nsr/res/nsrdb/09/023303424603ea5091f80da7~09/13/07 14:28:19 nsrd: Invalid resource saved at /nsr/res/nsrdb/dbg/023303424603ea5091f80da7~
09/13/07 14:28:19 nsrd: server notice: started
09/13/07 14:28:45 nsrmmdbd: media db is checking btrees
09/13/07 14:28:45 nsrmmdbd: media db is consistency checking the database
09/13/07 14:28:48 nsrd: @(#) Product: NetWorker
09/13/07 14:28:48 nsrd: @(#) Release: 7.2.Build.494
09/13/07 14:28:48 nsrd: @(#) Build number: 494
09/13/07 14:28:48 nsrd: @(#) Build date: Tue Nov 28 14:50:39 2006
09/13/07 14:28:48 nsrd: @(#) Build arch.: solaris7n
09/13/07 14:28:48 nsrd: @(#) Build info: DBG=0,OPT=-O
09/13/07 14:28:48 nsrindexd: Running nsrck to check client file indices
09/13/07 14:28:49 nsrd: index notice: checking index for 'panet001'
09/13/07 14:28:54 nsrmmdbd: media db is open for business


thank you [wink]
 
If NetWorker detects 'defect' resources, it creates a new subdirectory (/nsrdb/dbg) and isolates them. This is what these messages are all about.

Despite the fact that the resources might be corrupt, the most obvious reason is that the "resource id" - the last entry in a resource does not match the resource's filename. The name is nothing else but the hexadecimal translation of the "resource id" attribute.
 
Dear Instructor

How can I correct this problèm .....
 
There is a possibility if you correct the resource file and place it into the original location. However, as we do not know what is interpreted as wrong, the only solution is to recreate the resource(s).
 
Dear Instructor

I know how to recreate the resource(s).[ponder]
 
So how can i help you?

The only thing i can easily verify is the discrepancy between the resource id and the resource file name. I do not know what else will cause this behavior. If you know how to fix this problem, you can of course do this and move the file back to one of the hash directories. To the best of my knowledge, it should not matter to which one.

If you ask how to prevent the effect, i do not know. And i think the idea behind the concept is o.k. - a corrupt file (name) may always happen somehow. And by using this mechanism it will be isolated. But of course it may harm your setup as resource(s) will disappear.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top