HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: network error
Operating System - HP-UX
1836420
Members
3186
Online
110100
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
02-09-2010 02:47 AM
02-09-2010 02:47 AM
network error
Hi,
Our application team is trying to send to NDC ATM by writing this on to the TCP IP buffer but getting below error.
0402 174522014 000001 028595 00039|0| Error Sending Msg : 28 <<== No space left on device
There are enough space on the disk
When i checked max tcp connections using ndd it shows 4096 and established tcp connections are 700.
whether the same related to message queue..
B.11.23
please suggest on this
Regards
himacs
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2010 03:19 AM
02-09-2010 03:19 AM
Re: network error
Hi Admin,
I am planning to raise the vale of shmmax , shmseg and shmmni.Please find the current value.
shmmax 6442450944 6442450944 Immed
shmseg 300 Default Immed
shmmni 512 512 Immed
Please telll any dependncies by doing the same.
Quick answer will be appreciated
Regards
himacs
I am planning to raise the vale of shmmax , shmseg and shmmni.Please find the current value.
shmmax 6442450944 6442450944 Immed
shmseg 300 Default Immed
shmmni 512 512 Immed
Please telll any dependncies by doing the same.
Quick answer will be appreciated
Regards
himacs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2010 06:46 AM
02-09-2010 06:46 AM
Re: network error
When you modify the kernel setting if there's a dependency it will let you know.
Time to smoke and joke
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2010 04:31 PM
02-09-2010 04:31 PM
Re: network error
There is no maximum number of TCP connections tunable in ndd. If you are looking at tcp_conn_request_max, that is a limit to the number of pending connections which may be queued to a listen endpoint waiting to be accept()ed.
Errno 28 is indeed ENOSPC:
$ grep 28 /usr/include/sys/errno.h
#define ENOSPC 28 /* No space left on device */
but the manpage for send() does not list that as a possible errno from the call. Does your application team know the precise system call getting the ENOSPC error? Perhaps a different errno is getting remapped through a write() or other system call.
Errno 28 is indeed ENOSPC:
$ grep 28 /usr/include/sys/errno.h
#define ENOSPC 28 /* No space left on device */
but the manpage for send() does not list that as a possible errno from the call. Does your application team know the precise system call getting the ENOSPC error? Perhaps a different errno is getting remapped through a write() or other system call.
there is no rest for the wicked yet the virtuous have no pillows
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