HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- EV_AGENT[2915]:
Operating System - HP-UX
1836872
Members
2304
Online
110110
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
Forums
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
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
08-26-2007 09:13 AM
08-26-2007 09:13 AM
EV_AGENT[2915]:
Hi all,
we faced these problems in our hp clustered nodes
EV_AGENT[2915]: Agent cannot communicate with the storage system
cmgmsd[3145]: Unable to accept a connection (activation of keep alive option on socket failed): Invalid argument
moihp2 EV_AGENT[2915]: Agent Main --Estream construct failed. Err: RWSockErr: in RWSocket::accept: NOBUFS
inetd[1673]: vnetd/tcp: accept: No buffer space available
Aug 22 20:32:58 moihp2 EV_AGENT[2915]: Agent Main --Estream construct failed. Err: RWSockErr: in RWSocket::accept: NOBUFS
then the nodes hanged
we had rebooted both nodes then things came normal
are there any idea what would be the problem
thank you.
we faced these problems in our hp clustered nodes
EV_AGENT[2915]: Agent cannot communicate with the storage system
cmgmsd[3145]: Unable to accept a connection (activation of keep alive option on socket failed): Invalid argument
moihp2 EV_AGENT[2915]: Agent Main --Estream construct failed. Err: RWSockErr: in RWSocket::accept: NOBUFS
inetd[1673]: vnetd/tcp: accept: No buffer space available
Aug 22 20:32:58 moihp2 EV_AGENT[2915]: Agent Main --Estream construct failed. Err: RWSockErr: in RWSocket::accept: NOBUFS
then the nodes hanged
we had rebooted both nodes then things came normal
are there any idea what would be the problem
thank you.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2007 10:53 AM
08-26-2007 10:53 AM
Re: EV_AGENT[2915]:
seems like yuou may have had memory issues:
moihp2 EV_AGENT[2915]: Agent Main --Estream construct failed. Err: RWSockErr: in RWSocket::accept: NOBUFS
inetd[1673]: vnetd/tcp: accept: No buffer space available
moihp2 EV_AGENT[2915]: Agent Main --Estream construct failed. Err: RWSockErr: in RWSocket::accept: NOBUFS
inetd[1673]: vnetd/tcp: accept: No buffer space available
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2007 01:55 PM
08-26-2007 01:55 PM
Re: EV_AGENT[2915]:
i would also suspect the mem usage. Did you collect the MEM/CPU/SWAP statistics when the server got hung(Perfiew). Any thing special in syslog.log
whas is reporting from below command.
kmtune|egrep "dbc|shmmax"
I would say collect output of "kmeminfo" when you have a similar situation whihc can be a little helpful about the current memory allocation
whas is reporting from below command.
kmtune|egrep "dbc|shmmax"
I would say collect output of "kmeminfo" when you have a similar situation whihc can be a little helpful about the current memory allocation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2007 09:41 AM
08-28-2007 09:41 AM
Re: EV_AGENT[2915]:
how about the cluster is there any problem of the cluster componants like the switch or the network cards
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP