[
https://issues.apache.org/jira/browse/TS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom resolved TS-247.
------------------------------
Resolution: Fixed
Fixed, we now issue a MachineFatal early on when failing to bind, with a
descriptive error message. We still segfault on "exit", but that is an entirely
different issue.
> Poor error message/handling when attempt to bind port fails
> -----------------------------------------------------------
>
> Key: TS-247
> URL: https://issues.apache.org/jira/browse/TS-247
> Project: Traffic Server
> Issue Type: Bug
> Environment: FreeBSD 7-STABLE on i386
> Reporter: James Henderson
> Assignee: Leif Hedstrom
> Priority: Minor
> Fix For: 2.1.2
>
>
> When attempting to run the server, if one of the needed listening ports is in
> use (tested for http and ssl), then the follow error is returned.
> [Mar 15 14:40:09.427] Server {682633120} FATAL: <HttpAccept.cc:98
> (mainEvent)> HTTP accept received fatal error: errno = 9
> NOTE: Traffic Server received Sig 11: Segmentation fault: 11
> It seems to me that a) this error is not very readable b) the program
> probably shouldn't be segfaulting under any conditions.
> I'm not certain if these are considered to be issues or not to the Traffic
> Server team, but I figured it would be worth reporting.
> It is possible that this has something to do with the way that I am running
> traffic server, since the freebsd trafficserver rc script is not ported yet.
> I am just executing the traffic_server binary directly for testing purposes.
> I don't have Traffic Server running in any other environments to test though.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
