cancel
Showing results for 
Search instead for 
Did you mean: 

NBU 7.1 - Java Console give BA&R Only

Chuck_Stevens_2
Level 3

Yesterday it worked, today it doesn't.  When I fire up my NetBackup 7.1 Java Console and point it at my master server, I get "Backup, Archive, and Restore" only.

My master server is running NBU 7.1 on Windows Server 2008 R2; the Java Console is on a terminal server running Windows Server 2003 x64.  The native console on the master server works fine.

I see these entries in the bpjava-msvd log:

 11:52:28.725 [4944.540] <2> logparams:  -transient
11:52:29.458 [4944.540] <16> command_LOGON_TO_MSERVER: putenv(BPJAVA_MASTER_IPC_STRING=) failed
11:52:29.489 [4944.540] <2> acquireTerminationToken: hJobToken bpjava-msvc_11116 = 0000000000000230 for pid = 11116
11:52:29.489 [4944.540] <2> setUserServerTokens: server index = 0, hJobToken = 0000000000000230 for pid = 11116
11:52:29.583 [4944.540] <16> fillReadBuff: ReadFile failed readStat = 109 = The pipe has been ended. , pLength = 0
11:52:29.708 [4944.540] <16> poll_listen: can't find file descriptor 00000000000001EC in polling table
11:52:29.708 [4944.540] <4> bpjava-msvc: NEW_LOG closing debugFD and seting NB_INVALID 

Any ideas what to check?

-- Chuck

1 ACCEPTED SOLUTION

Accepted Solutions

CRZ
Level 6
Employee Accredited Certified

...which I bet was created from your case.  :)

The NetBackup Java Admin Console only shows "Backup Archive and Restore"
 http://www.symantec.com/docs/TECH158208

Looks like the short version is there's a permission problem when bpauthorize -M <master> -get_vxss_info is called and finds it can't write an output log.  The TechNote gives some guidance as to how to fix it.

Dunno if it's an O/S thing or a NBU 7.x thing - or a combination.
 

View solution in original post

13 REPLIES 13

Marianne
Level 6
Partner    VIP    Accredited Certified

Create  nbjava_install_path\java\auth.conf  file on the master.

Add entry similar to the following:

mydomain\ray ADMIN=ALL JBP=ALL 

Reference: http://www.symantec.com/docs/HOWTO34639
http://www.symantec.com/docs/HOWTO34636

Chuck_Stevens_2
Level 3

Sadly, creating the auth.conf file had no effect on the problem.

watsons
Level 6

The log looks like a required env. variable is not set:

 

11:52:29.458 [4944.540] <16> command_LOGON_TO_MSERVER: putenv(BPJAVA_MASTER_IPC_STRING=) failed

If you enable Debug.Properties file on the terminal server, and relaunch again see whether there will be anything pointing to that env. variable BPJAVA_MASTER_IPC_STRING.

That's my guess though.. I don't really know what that variable does. :p

Will_Restore
Level 6

Your log text was found in this technote: http://www.symantec.com/business/support/index?page=content&id=TECH140426&actp=search&viewlocale=en_...

Though you say both console and Master are at 7.1

 

Check the bpjava-susvc log for additional clues

nbutech
Level 6
Accredited Certified

Verify the server entries in the registry for Windows Server 2003 x64

Chuck_Stevens_2
Level 3

Yes, both Master and consoles are 7.1.

The bpjava-susvc logs exist but are zero bytes - no content.  I'll fiddle with raising the logging level.

Chuck_Stevens_2
Level 3

For grins I installed the java console directly on the master server; it's doing the same thing.

Chuck_Stevens_2
Level 3

Any other ideas?  Nothing here so far pans out.  I've got a case open with Symantec, but they're being slow to respond.

Chuck_Stevens_2
Level 3

Raising the logging level did not help for the bpjava-susvc logs. They remain zero bytes.

Marianne
Level 6
Partner    VIP    Accredited Certified

In all honesty it's been about 5 years since anyone asked me about Java Console to administer a Windows master. Back then the only way we could get it to work was to start the NBU services as the user specified in auth.conf (there were obviously a lot less services in those days...).

Everyone I know has been using Java for Unix masters and Windows Admin Console for Windows masters (or simply Remote Desktop to master).

As a matter of interest, I have just tried the same method that I've extracted from TN above and am seeing the exact same error as you. (Impossible to chance Services logon account on our production server.) My Java console and NBU master are both on 7.0.1.


Only BAR GUI opens with following in bpjava-msvc log (susvc log also empty):

21:44:16.554 [2104.5860] <2> logparams:  -transient
21:44:24.088 [2104.5860] <16> command_LOGON_TO_MSERVER: putenv(BPJAVA_MASTER_IPC_STRING=) failed
21:44:24.120 [2104.5860] <2> acquireTerminationToken: hJobToken bpjava-msvc_6616 = 0000000000000180 for pid = 6616
21:44:24.120 [2104.5860] <2> setUserServerTokens: server index = 0, hJobToken = 0000000000000180 for pid = 6616
21:44:24.182 [2104.5860] <16> fillReadBuff: ReadFile failed readStat = 109 = The pipe has been ended. , pLength = 0
21:44:25.368 [2104.5860] <16> poll_listen: can't find file descriptor 0000000000000178 in polling table
21:44:25.368 [2104.5860] <4> bpjava-msvc: NEW_LOG closing debugFD and seting NB_INVALID

 

Please let us know when you get something useful from Support.

Chuck_Stevens_2
Level 3

Will do, thanks!

The strange thing is that last week it worked just fine.  We've been using the Java console for years.

 

EDIT 4/14: Well, so far nothing. Opened a Critical case on 4/6, and nothing.  Ticket bouncing around and no one will help. On the phone now stuck on hold.  I have to say, I really miss the old Veritas support folks.  Why are we still paying for support?

CRZ
Level 6
Employee Accredited Certified

...which I bet was created from your case.  :)

The NetBackup Java Admin Console only shows "Backup Archive and Restore"
 http://www.symantec.com/docs/TECH158208

Looks like the short version is there's a permission problem when bpauthorize -M <master> -get_vxss_info is called and finds it can't write an output log.  The TechNote gives some guidance as to how to fix it.

Dunno if it's an O/S thing or a NBU 7.x thing - or a combination.
 

Chuck_Stevens_2
Level 3

Yep, that was me. :0

Permissions on D:\Program Files\Veritas\NetBackup\logs\admin were apparently screwed up, though they looked OK.  I deleted the directory and ran the mklogdir batch file to recreate it, then things worked just fine.  Even though they look the same now as before. Strange.

All this seems to be fallout from our recent Master Server migration from Windows Server 2003 R2 to Windows Server 2008 R2; when restoring the catalog from the 2003 box, it laid down directories with permissions that don't work well on 2008.