connection errors in activity monitor after 7.7 upgrade

[Mohmec]

We are getting connection errors in Activity monitor after 7.7 upgrade. Backups are running fine. The opscenter collectors for this master server fail with NBSL. The evenet logs also indicate NBSL. This makes me think this has something to do with NBSL. We are working with support but still trying to find what is causing this.

Event Log:

Faulting application name: nbsl.exe, version: 7.700.15.620, time stamp: 0x55852e50
Faulting module name: ntdll.dll, version: 6.1.7601.18933, time stamp: 0x55a6a196
Exception code: 0xc0000374
Fault offset: 0x00000000000bffc2
Faulting process id: 0x1598
Faulting application start time: 0x01d0ec9a4e731e1d
Faulting application path: D:\Program Files\Veritas\NetBackup\bin\nbsl.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: a10a94b9-5899-11e5-a30b-78e3b5f4e870

JPB Log:

[14-09-2015 15:29:39:052] pbxiop:INFO: Created bound socket 0.0.0.0/0.0.0.0:15765
[14-09-2015 15:29:39:052] pbxiop:INFO: createSocket - Trying to connect to masterserver.com:1556:nbsl
[14-09-2015 15:29:39:052] pbxiop:INFO: Connected to exchange at:masterserver.com:1556:nbsl
[14-09-2015 15:29:39:052] pbxiop:ERROR: Connection rejected by PBX exchange

[Rob_Small]

I'm curious what you find, I'm getting similar crashes (core dumps) with NBSL on a RHEL7 master w/ 7.7

I can make mine crash predictably when looking at almost anything in the Media and Device Management area: Device Monitor, Drives, & Robots

I had a case open, but closed it thinking it was an OS problem (at the time, I was running my master on RHEL 5.9). If your Symantec tech wants a case# to reference with yours, then I can DM you that case number.

[Mohmec]

Rob,

Can you pass me your case #? It might be helpful. When you say you closed the case, you mean th eproblem is resolved now? How did you resolve the problem?

[Rob_Small]

I closed it because I thought it was an OS issue, and told them that I'd reopen later if it was still a problem.

I updated the OS last week: reformatted the OS partition, installed RHEL 7.1, installed NBU 7.7, then ran through the DR recovery

Sadly, I'm still having the issue, but I haven't yet reopened the case.

[Mohmec]

Thanks, I will keep you posted. Let me know if they are any developments on your side.

[Mohmec]

This issue is with engineering and they are still trying to figure this out. Issue could be with alias names for this master. There was no problem in previous 7.6.x versions with alias.  

[Marianne]

Please let us know when you have received a solution.

[Deeps]

Mohmec , by any chance you have app-cluster configured in your setup ?

DeepS

[Michal_Mikulik1]

Hello,

solving currently the same issue with support (NBU 7.7 on Windows 2008 R2). I was informed this week that a fix is currently developed.

Veritas case number # 20607402.

Michal

[Mohmec]

Yes. app-cluster was setup. Issue resolved with an eeb from engineering. Thank you if you are from engineering and resolved this issue.

[CRZ]

Say, what was the number of the Etrack/EEB, if you don't mind sharing?

[Mohmec]

3852777

[Marianne]

I am curious about the app_cluster - was this done for the master server? Never heard of such a config.

[Mohmec]

Issue simillar to TECH232491

https://www.veritas.com/support/en_US/article.TECH232491