- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: IPC Error
StoreEver Tape Storage
1753797
Members
7597
Online
108799
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-10-2008 04:42 AM
01-10-2008 04:42 AM
IPC Error
Hallo,
we have a problem with HP DataProtector5.5:
When the backupjob is running the job is killed by a timeout. This happens with different clients(WinXP and linux), but not always. Cell and Clients are actually patched(CorePacket Cell-Server (DPWIN_00273 16.8.2007), Cell Server Packet(DPWIN_00333 22.8.2007), CellConsole Packet(DPWIN_00258 9.10.2007), DiskAgent Packet (DPWIN_00345 7.12.2007), MediaAgent Packet (DPWIN_00289 3.8.2007)
ErrorMessage:
From: BSM@wbbi027.biozentrum.uni-wuerzburg.de "wbz3094_conf" Time: 10.01.2008 11:46:25
Lost connection to VBDA named "wbz3094.zoologie3.biozentrum.uni " on host wbz3094.zoologie3.biozentrum.uni-wuerzburg.de.
Ipc subsystem reports: "IPC Read Error System error: Verbindung von Peer zurückgesetzt
description:
The mechanism used in Data Protector for the communication is TCP. The error describes, that there
are some problems with the network/networking system software or with the remote host.
actions:
* Check your network operation and the remote host operation. Also check that the
agent on the client did not die ungracefully due to a lack of system resources.
* If the problem persists, reproduce it with the debug option and contact support.
Could someone help ?
we have a problem with HP DataProtector5.5:
When the backupjob is running the job is killed by a timeout. This happens with different clients(WinXP and linux), but not always. Cell and Clients are actually patched(CorePacket Cell-Server (DPWIN_00273 16.8.2007), Cell Server Packet(DPWIN_00333 22.8.2007), CellConsole Packet(DPWIN_00258 9.10.2007), DiskAgent Packet (DPWIN_00345 7.12.2007), MediaAgent Packet (DPWIN_00289 3.8.2007)
ErrorMessage:
From: BSM@wbbi027.biozentrum.uni-wuerzburg.de "wbz3094_conf" Time: 10.01.2008 11:46:25
Lost connection to VBDA named "wbz3094.zoologie3.biozentrum.uni " on host wbz3094.zoologie3.biozentrum.uni-wuerzburg.de.
Ipc subsystem reports: "IPC Read Error System error: Verbindung von Peer zurückgesetzt
description:
The mechanism used in Data Protector for the communication is TCP. The error describes, that there
are some problems with the network/networking system software or with the remote host.
actions:
* Check your network operation and the remote host operation. Also check that the
agent on the client did not die ungracefully due to a lack of system resources.
* If the problem persists, reproduce it with the debug option and contact support.
Could someone help ?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-14-2008 11:05 AM
01-14-2008 11:05 AM
Re: IPC Error
Hello ;o)
There may be several solutions.
1. DNS must be running fine
2. The NIC's must be configured correctly
(Duplex auto or full? Switch Port configured correctly?)
3. Do you use Fibre channel NIC's?
4. Are there running some old Processes on the Cell Server or Client? Kill all Processes and restart the services.
5. Did you disable the Windows Media Change
(Wechselmedien) service? You should do so running a library. Only the Cell Server should be able to run the robotic by Data Protector.
6. Running a library are the scsi addresses correct for the drives or did they change after a reboot?
7. Did you disable the drives (fibre channel)in the windows device manager for the client? You should do so.
8. Is the DP service running on the clients configured as domain\administrator account?
You should do this.
I've got this error by using a fibre NIC Sysconnect running at fill duplex.
After using another fibre NIC running auto duplex(other model) all works fine.
Check first Network connection and DNS.
Greets Martin
There may be several solutions.
1. DNS must be running fine
2. The NIC's must be configured correctly
(Duplex auto or full? Switch Port configured correctly?)
3. Do you use Fibre channel NIC's?
4. Are there running some old Processes on the Cell Server or Client? Kill all Processes and restart the services.
5. Did you disable the Windows Media Change
(Wechselmedien) service? You should do so running a library. Only the Cell Server should be able to run the robotic by Data Protector.
6. Running a library are the scsi addresses correct for the drives or did they change after a reboot?
7. Did you disable the drives (fibre channel)in the windows device manager for the client? You should do so.
8. Is the DP service running on the clients configured as domain\administrator account?
You should do this.
I've got this error by using a fibre NIC Sysconnect running at fill duplex.
After using another fibre NIC running auto duplex(other model) all works fine.
Check first Network connection and DNS.
Greets Martin
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP