GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- errorno 226 indicates Address allready in use
Operating System - HP-UX
1849860
Members
1884
Online
104044
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
Forums
Discussions
back
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
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-24-2001 09:32 PM
08-24-2001 09:32 PM
errorno 226 indicates Address allready in use
Iam doing "dhcpclient -b lan0 -l 3"
on my machine and getting a error that says "Address allready in use.
The /etc/dhcpclient.data file created seem to have the right information.
Can some one help me!
Note: Iam also attaching the output of the "dhcpclient -b lan0 -l 3".
on my machine and getting a error that says "Address allready in use.
The /etc/dhcpclient.data file created seem to have the right information.
Can some one help me!
Note: Iam also attaching the output of the "dhcpclient -b lan0 -l 3".
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2001 06:21 PM
08-25-2001 06:21 PM
Re: errorno 226 indicates Address allready in use
The obvious first...the port is busy. Why? Probably because something was using the port and aborted, the port is not properly released and bang....the error.
To read it in more technical terms...from the following document (albeit old, but informative)
1993 Nov 11
Description : Socket and TCP port address can be left open if server program aborts
Document Id : 4701228098
"If a BSD IPC server program is aborted while there is an incoming
connection request in the listen queue, the VC socket and the TCP
path record associated with the incoming connection are not released.
Subsequent calls to bind() will fail with errno set to EADDRINUSE (226).
The socket and the TCP path record can only be released by shutting
down and restarting NS-ARPA.***Cause Text***
The so_down_pathref in a socket record normally contains the index
of the associated TCP path record.
When a BSD IPC socket is in the listen queue the field so_down_pathref
used for another purpose. The routine in OUTPRO which cleans up
sockets in the listen queue was expecting so_down_pathref to contain
a valid TCP path record index.
Looks like you've got some hunting ahead for you...but I hope this helped alittle at least,
Regards,
Rita
To read it in more technical terms...from the following document (albeit old, but informative)
1993 Nov 11
Description : Socket and TCP port address can be left open if server program aborts
Document Id : 4701228098
"If a BSD IPC server program is aborted while there is an incoming
connection request in the listen queue, the VC socket and the TCP
path record associated with the incoming connection are not released.
Subsequent calls to bind() will fail with errno set to EADDRINUSE (226).
The socket and the TCP path record can only be released by shutting
down and restarting NS-ARPA.***Cause Text***
The so_down_pathref in a socket record normally contains the index
of the associated TCP path record.
When a BSD IPC socket is in the listen queue the field so_down_pathref
used for another purpose. The routine in OUTPRO which cleans up
sockets in the listen queue was expecting so_down_pathref to contain
a valid TCP path record index.
Looks like you've got some hunting ahead for you...but I hope this helped alittle at least,
Regards,
Rita
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2001 01:20 AM
08-27-2001 01:20 AM
Re: errorno 226 indicates Address allready in use
For hpux11 there is a software package "lsof" available from hp software depot, which can help idnetify which process is already using your port number.
see also:
http://devresource.hp.com/CXX/Forums/hpux-devtools/hpux-devtools.0004/0021.html
(Try lsof -i|grep LISTEN).
Cheers, Klaus
There is a live before death!
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 2026 Hewlett Packard Enterprise Development LP