# The sa\_family of accept socket is equal 0

**URL:** <https://www.ruby-forum.com/t/the-sa-family-of-accept-socket-is-equal-0/243910>\
**Category:** NGINX\
**Created:** [January 25, 2016, 7:53am UTC](https://www.ruby-forum.com/t/the-sa-family-of-accept-socket-is-equal-0/243910 "2016-01-25T07:53:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rafa\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/958977/32.png) [@Rafa\_F](https://www.ruby-forum.com/u/Rafa_F)\
**Post date:** [January 25, 2016, 7:53am UTC](https://www.ruby-forum.com/t/the-sa-family-of-accept-socket-is-equal-0/243910/1 "2016-01-25T07:53:06Z")

</div>

nginx version: 1.63  
OS version: hp-ux B.11.23

Client connect server with telnet, by GDB, I find:

ngx\_event\_accept.c, function ngx\_event\_accept, line 279, the value of  
‘c-\>addr\_text.len’ is zero,  
but the server socket’s value is ok

who can get this problem?

thanks

Posted at Nginx Forum:

> **[\[core\] the sa\_family of accept socket is equal 0](https://forum.nginx.org/read.php?2,264090,264090#msg-264090)**
>
> nginx version: 1.63 OS version: hp-ux B.11.23 Client connect server with telnet, by GDB, I find: ngx\_event\_accept.c, function ngx\_event\_accept, line 279, the value of 'c-\>addr\_text.len' is zero, but the server socket's value is ok who ca

---

<div class="post-metadata">

**Author:** ![guitao\_w](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/a8b319/32.png) [@guitao\_w](https://www.ruby-forum.com/u/guitao_w)\
**Post date:** [January 25, 2016, 4:44pm UTC](https://www.ruby-forum.com/t/the-sa-family-of-accept-socket-is-equal-0/243910/2 "2016-01-25T16:44:43Z")

</div>

Hello!

On Mon, Jan 25, 2016 at 01:52:54AM -0500, guitao\_w wrote:

> nginx version: 1.63  
> OS version: hp-ux B.11.23
> 
> Client connect server with telnet, by GDB, I find:
> 
> ngx\_event\_accept.c, function ngx\_event\_accept, line 279, the value of  
> ‘c-\>addr\_text.len’ is zero,  
> but the server socket’s value is ok
> 
> who can get this problem?

Unfortunately, HP-UX B.11.23 isn’t something easy to find for  
testing. So I wouldn’t expect this can be debugged by anyone  
except you.

My best guess is that the problem is caused by multiple versions  
of socket functions on HP-UX, see this commit for some details (it  
was done after some basic testing on HP-UX B.11.31):

> **[hg.nginx.org is decommissioned](http://hg.nginx.org/nginx/rev/489839d07b38)**

Though given that 11.23 is quite old it is possible that the  
situation is different there.

–  
Maxim D.

> **[nginx](http://nginx.org/)**