Unsolved

This post is more than 5 years old

1 Rookie

 • 

2 Posts

4099

January 6th, 2015 07:00

I'm getting random VM EBR backup failures all with similar messages

Extracted 13 lines, suppressed 3054 lines.

2015-01-05 18:02:30 avvcbimage Warning <0000>: [IMG0014] Problem logging into URL 'https://********.*****:443/sdk' with session cookie.
2015-01-05 18:02:31 avvcbimage Warning <0000>: [IMG0014] Problem logging into URL 'https://********.*****:443/sdk' with session cookie.
2015-01-05 18:02:31 avvcbimage Warning <0000>: [IMG0014] Problem logging into URL 'https://********.*****:443/sdk' with session cookie.
2015-01-05 18:02:34 avvcbimage Warning <0000>: [IMG0014] Problem logging into URL 'https://********.*****:443/sdk' with session cookie.
2015-01-05 18:02:35 avvcbimage Warning <14669>: The datastore 'PALLJCIAPp01' could not be located on the datacenter
2015-01-05T18:05:56.638+03:00 avnwcomm Error <0000>: Timed out waiting for wrapup summary
2015-01-05T18:05:56.638+03:00 avnwcomm Error <0000>: Failed to process workorder because of Never received value for labelnum
2015-01-05T18:10:30.363+03:00 avnwcomm FATAL <5889>: Fatal signal 11 in pid 28952
2015-01-05T18:10:30.363+03:00 [nwcomm_ctl_sup]  FATAL ERROR: <0001> Fatal signal 11
2015-01-05T18:10:30.363+03:00 avnwcomm Error <5891>: handlefatal: exiting thread pid=28952, sig=11
2015-01-05T18:10:30.486+03:00 avnwcomm FATAL <5889>: Fatal signal 6 in pid 28952
2015-01-05T18:10:30.487+03:00 [nwcomm_ctl_sup]  FATAL ERROR: <0001> Fatal signal 6
2015-01-05T18:10:30.487+03:00 avnwcomm Error <5891>: handlefatal: exiting thread pid=28952, sig=6

Not always the same VM's. We're running NW 8.2.0.2, VMWare 5.5, EBR 1.1.0.149

January 8th, 2015 08:00

Rebooting Vcenter fixed this issue for me.

if you still getting this error, i'll restart the appliances afterwards.

Shutdown all proxies (guest shutdown)

Restart EBR (guest restart)

When EBR is up, power up the proxies

Hope this Helps.

16 Posts

July 5th, 2015 20:00

Hi Guys,

I am also getting very random Policy failures with below errors, hope anybody give some clues :

Env info : NW 8.1.1.5, VMWare 5.5, EBR: 1.0.1.9

xtracted 22 lines, suppressed 1949 lines.

See file "/nsr/logs/policy/temp_0800/133393-S575MJESD126-2015-7-6-8-4-24" for complete logs.

Extracted Lines:

2015-07-06 08:03:38 avnwcomm FATAL <5889>: Fatal signal 11 in pid 7933

2015/07/05-23:03:38.03500 [nwcomm_ctl_sup]  FATAL ERROR: <0001> Fatal signal 11

2015-07-06 08:03:38 avnwcomm Error <5891>: handlefatal: exiting thread pid=7933, sig=11

2015-07-06 08:03:38 avnwcomm FATAL <5889>: Fatal signal 6 in pid 7933

2015/07/05-23:03:38.03551 [nwcomm_ctl_sup]  FATAL ERROR: <0001> Fatal signal 6

2015-07-06 08:03:38 avnwcomm Error <5891>: handlefatal: exiting thread pid=7933, sig=6

2015-07-06 08:03:38 avnwcomm Warning <6690>: CTL workorder "temp_0800-1436137201513" non-zero exit status 'code 158: cannot establish connection with server (possible network or DNS failure)'

2015-07-06 08:03:38 avnwcomm FATAL <5889>: Fatal signal 11 in pid 8352

2015-07-06 08:03:38 avnwcomm Error <5891>: handlefatal: exiting thread pid=8352, sig=11

2015-07-06 08:03:38 avnwcomm FATAL <5889>: Fatal signal 6 in pid 8352

2015-07-06 08:03:38 avnwcomm Error <5891>: handlefatal: exiting thread pid=8352, sig=6

2015-07-06 08:03:38 avnwcomm FATAL <5889>: Fatal signal 11 in pid 7976

2015/07/05-23:03:38.06345 [nwcomm_assist]  FATAL ERROR: <0001> Fatal signal 11

2015-07-06 08:03:38 avnwcomm Error <5891>: handlefatal: exiting thread pid=7976, sig=11

2015-07-06 08:03:38 avnwcomm FATAL <5889>: Fatal signal 6 in pid 7976

2015/07/05-23:03:38.06382 [nwcomm_assist]  FATAL ERROR: <0001> Fatal signal 6

2015-07-06 08:03:38 avnwcomm Error <5891>: handlefatal: exiting thread pid=7976, sig=6

2015-07-06 08:00:18 avvcbimage Warning <6788>: Found unknown section 'browse-from-catalog' in workorder, ignoring

2015-07-06 08:00:23 avvcbimage Warning <6788>: Found unknown section 'browse-from-catalog' in workorder, ignoring

2015-07-06 08:00:48 avvcbimage Warning <6788>: Found unknown section 'browse-from-catalog' in workorder, ignoring

2015-07-06 08:03:38 avtar Error <6658>: Unable to connect to 127.0.0.1:36178 for CTL messages

2015-07-06 08:03:38 avtar FATAL <10790>: Unable to connect to 127.0.0.1:36178 with proprietary encryption

1 Rookie

 • 

2 Posts

July 6th, 2015 04:00

After consulting with EMC support, it was recommended that I add more external proxies, disable internal proxies,  and upgrade to the latest Networker and EBR.

I am now running Networker 8.2.1.3 and EBR 1.1.1.50

VM backups are much more stable now haven't had any inexplicable failures since upgrading.

0 events found

No Events found!

Top