IPC Read Error - Lost connection to BMA - DP9.05

Hello everybody,

Since the upgrade from 7.03 to 9.05 I get the following error message when the tape library had to load a new tape, 'cause the used one was full.

[Normal] From: BMA@backupserver.domain.org "IBM:ULTRIUM-TD5_2"  Time: 1/28/2016 7:41:29 PM
	Tape1:0:0:0C
	Medium header verification completed, 0 errors found.

[Normal] From: BMA@backupserver.domain.org "IBM:ULTRIUM-TD5_2"  Time: 1/28/2016 7:41:44 PM
	Ejecting medium '5'.

[Normal] From: BMA@backupserver.domain.org "IBM:ULTRIUM-TD5_2"  Time: 1/28/2016 7:41:44 PM
	=> UMA@backupserver.domain.org@Changer2147483646:0:0:1
	Unloading medium to slot 5 from device Tape1:0:0:0C

[Normal] From: BMA@backupserver.domain.org "IBM:ULTRIUM-TD5_2"  Time: 1/28/2016 7:42:06 PM
	=> UMA@backupserver.domain.org@Changer2147483646:0:0:1
	Loading medium from slot 8 to device Tape1:0:0:0C

[Critical] From: BDA-NET@iclient.domain.org "SID"  Time: 1/28/2016 7:42:43 PM
	IPC failure reading NET message (IPC Read Error
	System error: [10054] Connection reset by peer
) => aborting.

[Critical] From: OB2BAR_SAPBACK@iclient.domain.org "SID"  Time: 1/28/2016 7:42:43 PM
	Unexpected close reading NET message => aborting.

[Major] From: BSM@backupserver.domain.org "SID_Tape"  Time: 1/28/2016 7:42:43 PM
[61:3003]  	Lost connection to BMA named "IBM:ULTRIUM-TD5_2"
	on host backupserver.domain.org.
	Ipc subsystem reports: "IPC Read Error
	System error: [10054] Connection reset by peer
"
[Normal] From: BMA@backupserver.domain.org "IBM:ULTRIUM-TD5_1"  Time: 1/30/2016 7:14:36 AM
	Tape0:0:0:0C
	Medium header verification completed, 0 errors found.

[Normal] From: BMA@backupserver.domain.org "IBM:ULTRIUM-TD5_1"  Time: 1/30/2016 7:14:52 AM
	Ejecting medium '7'.

[Normal] From: BMA@backupserver.domain.org "IBM:ULTRIUM-TD5_1"  Time: 1/30/2016 7:14:52 AM
	=> UMA@backupserver.domain.org@Changer2147483646:0:0:1
	Unloading medium to slot 7 from device Tape0:0:0:0C

[Normal] From: BMA@backupserver.domain.org "IBM:ULTRIUM-TD5_1"  Time: 1/30/2016 7:15:16 AM
	=> UMA@backupserver.domain.org@Changer2147483646:0:0:1
	Loading medium from slot 2 to device Tape0:0:0:0C

[Critical] From: BDA-NET@client.domain.org "SID"  Time: 1/30/2016 7:15:57 AM
	IPC failure reading NET message (IPC Read Error
	System error: [10054] Connection reset by peer
) => aborting.

[Major] From: BSM@backupserver.domain.org "SID_Tape"  Time: 1/30/2016 7:15:57 AM
[61:3003]  	Lost connection to BMA named "IBM:ULTRIUM-TD5_1"
	on host backupserver.domain.org.
	Ipc subsystem reports: "IPC Read Error
	System error: [10054] Connection reset by peer
"

[Critical] From: BDA-NET@client.domain.org "SID"  Time: 1/30/2016 7:15:57 AM
	IPC failure reading NET message (IPC Read Error
	System error: [10054] Connection reset by peer
) => aborting.

[Critical] From: BDA-NET@client.domain.org "SID"  Time: 1/30/2016 7:15:57 AM
	IPC failure reading NET message (IPC Read Error
	System error: [10054] Connection reset by peer
) => aborting.

[Critical] From: BDA-NET@client.domain.org "SID"  Time: 1/30/2016 7:15:57 AM
	IPC failure reading NET message (IPC Read Error
	System error: [10054] Connection reset by peer
) => aborting.

[Critical] From: OB2BAR_SAPBACK@client.domain.org "SID"  Time: 1/30/2016 7:15:57 AM
	Unexpected close reading NET message => aborting.

[Critical] From: OB2BAR_SAPBACK@client.domain.org "SID"  Time: 1/30/2016 7:15:57 AM
	Received ABORT request from SM => aborting.

[Critical] From: OB2BAR_SAPBACK@client.domain.org "SID"  Time: 1/30/2016 7:15:57 AM
	Unexpected close reading NET message => aborting.

[Critical] From: OB2BAR_SAPBACK@client.domain.org "SID"  Time: 1/30/2016 7:15:57 AM
	Unexpected close reading NET message => aborting.

[Critical] From: OB2BAR_SAPBACK@client.domain.org "SID"  Time: 1/30/2016 7:15:57 AM
	Unexpected close reading NET message => aborting.

[Critical] From: OB2BAR_SAPBACK@client.domain.org "SID"  Time: 1/30/2016 7:15:57 AM
	Received ABORT request from SM => aborting.

[Critical] From: OB2BAR_SAPBACK@client.domain.org "SID"  Time: 1/30/2016 7:15:57 AM
	Received ABORT request from SM => aborting.

[Critical] From: OB2BAR_SAPBACK@client.domain.org "SID"  Time: 1/30/2016 7:15:57 AM
	Received ABORT request from SM => aborting.

The tape library (Overland NEO2000e LTO5 FC) is directly connected to the backup server via fibrechannel (two tape drives > FC > FC-card on backup server)

The abort comes within a minute, so I didn't found a parameter in the global file, which match that one.

Anyone an idea, what it can be?

 

 

Best regards,

Tobias

Parents
  • Hi Tobias,

    that could be crashing media agent, in which case you need to open up a support case. Please check event logs on 

    backupserver.domain.org 

     

  • Hi,

    Faulting application name: bma.exe, version: 9.0.105.0, time stamp: 0x565f6de6
    Faulting module name: omnilibeay32.dll_unloaded, version: 0.0.0.0, time stamp: 0x55e9ae80
    Exception code: 0xc0000005
    Fault offset: 0x000000000fb6cd70
    Faulting process id: 0x1648
    Faulting application start time: 0x01d15b041ea4e270
    Faulting application path: D:\Program Files\OmniBack\bin\bma.exe
    Faulting module path: omnilibeay32.dll
    Report Id: e9029cbd-c718-11e5-a9dd-002655564198
    Fault bucket , type 0
    Event Name: BEX64
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: bma.exe
    P2: 9.0.105.0
    P3: 565f6de6
    P4: omnilibeay32.dll_unloaded
    P5: 0.0.0.0
    P6: 55e9ae80
    P7: 000000000fb6cd70
    P8: c0000005
    P9: 0000000000000008
    P10: 
    
    Attached files:
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_bma.exe_9fdfdc989cbdbaf616488bf5e51d89955b2f143_12aac064
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e9029cbd-c718-11e5-a9dd-002655564198
    Report Status: 4

    Hmm, ok .. the next support request.

     

    Greetings

    Tobias

Reply
  • Hi,

    Faulting application name: bma.exe, version: 9.0.105.0, time stamp: 0x565f6de6
    Faulting module name: omnilibeay32.dll_unloaded, version: 0.0.0.0, time stamp: 0x55e9ae80
    Exception code: 0xc0000005
    Fault offset: 0x000000000fb6cd70
    Faulting process id: 0x1648
    Faulting application start time: 0x01d15b041ea4e270
    Faulting application path: D:\Program Files\OmniBack\bin\bma.exe
    Faulting module path: omnilibeay32.dll
    Report Id: e9029cbd-c718-11e5-a9dd-002655564198
    Fault bucket , type 0
    Event Name: BEX64
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: bma.exe
    P2: 9.0.105.0
    P3: 565f6de6
    P4: omnilibeay32.dll_unloaded
    P5: 0.0.0.0
    P6: 55e9ae80
    P7: 000000000fb6cd70
    P8: c0000005
    P9: 0000000000000008
    P10: 
    
    Attached files:
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_bma.exe_9fdfdc989cbdbaf616488bf5e51d89955b2f143_12aac064
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e9029cbd-c718-11e5-a9dd-002655564198
    Report Status: 4

    Hmm, ok .. the next support request.

     

    Greetings

    Tobias

Children