osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 61666] regression on httpd reload (could not bind to address 0.0.0.0:80)


https://bz.apache.org/bugzilla/show_bug.cgi?id=61666

--- Comment #9 from Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx> ---
(In reply to Joe Orton from comment #8)
> All you've shown us is a conflict error message from :80.  If there is some
> issue here other than a config error you need to show full Listen config &
> strace output I indicated above.

the "Listen" lines have been provided in comment #5, here they are again:

Listen 80
Listen 447

# strace -ebind httpd -f /etc/httpd/conf/httpd.conf 
bind(3, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
bind(3, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
bind(4, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
bind(5, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
bind(5, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
bind(5, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
bind(5, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
bind(3, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("0.0.0.0")},
16) = 0
bind(4, {sa_family=AF_INET, sin_port=htons(447),
sin_addr=inet_addr("0.0.0.0")}, 16) = 0
bind(5, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0

The output is from httpd 2.4.29 + revert of the commit mentioned in comment #1.


I've been running the mod_proxy tests on two machines in a loop all afternoon.
So far no single failure. If I stick to vanilla httpd 2.4.29 or 2.4.27, it
fails on "httpd reload". Note: This is no *startup* failure, httpd starts fine.
The graceful restart during "httpd reload" -> SIGHUP dies.

What's the normal control flow once a SIGHUP is received in the event mpm?

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: bugs-help@xxxxxxxxxxxxxxxx