You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2010/12/16 16:39:01 UTC
[jira] Commented: (TS-563) Incorrectly returned 0 status code from
startup script even when TS fails to start
[ https://issues.apache.org/jira/browse/TS-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972113#action_12972113 ]
Leif Hedstrom commented on TS-563:
----------------------------------
Hmmm, well, this would be problematic to detect, since the startup script only starts traffic_cop. traffic_cop then starts traffic_manager, which then starts traffic_server. At this point, I don't think there's any way for failures in TM or TS startup to get propagated back to the RC scripts (it has most likely already exited).
> Incorrectly returned 0 status code from startup script even when TS fails to start
> ----------------------------------------------------------------------------------
>
> Key: TS-563
> URL: https://issues.apache.org/jira/browse/TS-563
> Project: Traffic Server
> Issue Type: Bug
> Affects Versions: 2.1.5
> Environment: Linux
> Reporter: Marcus Clyne
> Priority: Trivial
> Fix For: 2.1.5
>
>
> When using proxy.config.log2 values in records.config rather than the new proxy.config.log values, TS fails to start (server/manager/cop), but a return code of 0 is returned rather than 1 or something more meaningful.
> I have also noticed instances when config errors have prevented server from starting, even though manager and cop do. It would probably make sense to have a non-zero error code for these two.
> Perhaps it might be useful to have different return codes for whether cop/manager/server start or not (e.g. 1=server not started, 2=manager not started, 3=cop not started?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.