Wow,

You will not believe it, I had Device monitor open on the master from 
earlier and did a 'refresh' when it was down, but the jnbSA was still up 
on the master, the 'refresh' was holding a LOCK on the media server, 
causing it to be 'PERMISSION DENIED' below, I cannot believe it!

To confirm this is the case--

I rebooted the media server (now that the media server is no longer in the 
"refreshing..." state and after it came back up I ran vmoprcmd -d ds and 
it came right back, no errors!

Wow, first time I have seen that as the culprit (jnbSA), something to keep 
in mind when not only troubleshooting problems but when it also can be the 
problem itself.

I have a case open with Symantec I'll let them know about this bug 
(6.5.6).

Justin.

On Thu, 14 Oct 2010, Justin Piszcz wrote:

> Hi,
>
> I have been re-provisioning some servers, from an older OS to a newer one,
> same hostname of course and all media servers work great, except one, the
> last one, I get the following errors:
>
> 14:04:37.955 [5813] <16> InitializeOrb: CORBA::EXCEPTION connection to host 
> master-server failed. exception = NO_PERMISSION
> 14:04:37.955 [5813] <16> qmgmt_releaseMediaServerResources: ERROR: failed to 
> initialize RB orb
> 14:04:37.955 [5813] <3> logstderrmsg: Failed to reset the device allocations 
> for this host, status=3000000
>
> I tried -resetMediaServer and -resetAll, has anyone seen this issue?
> Also tried vmglob -delete -devhost media-server and set it up from scratch.
> Still having this problem.
>
> Justin.
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu