commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mladen Turk (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DAEMON-197) Output meaningful error log message when Procrun cannot start the service
Date Sat, 05 Nov 2011 18:58:51 GMT

     [ https://issues.apache.org/jira/browse/DAEMON-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mladen Turk resolved DAEMON-197.
--------------------------------

    Resolution: Not A Problem

There was lots of improvements in failure forensic and logging since 1.0.3. Also as described
this issues can never be actually resolved because there will always be a better way to describe
the actual problem beside just logging system error message.
If you came up with the actual problem that can be reproduced and the suggestion what should
be logged in that case I'll be happy to implement it.
                
> Output meaningful error log message when Procrun cannot start the service
> -------------------------------------------------------------------------
>
>                 Key: DAEMON-197
>                 URL: https://issues.apache.org/jira/browse/DAEMON-197
>             Project: Commons Daemon
>          Issue Type: Improvement
>          Components: Procrun
>    Affects Versions: 1.0.3
>            Reporter: Steve Ash
>            Priority: Minor
>
> If procrun cannot start the service (and I haven't investigated under which conditions
this technically occurs) SCM shows the user a message box with the message
> {panel}
> Windows could not start the _my service name_ service on Local Computer.  For more information,
review the System Event Log.  If this is a non-Microsoft service, contact the service vendor,
and refer to service-specific error code 0.
> {panel}
> The event then has nothing more than the generic "The _my service_ service terminated
with service-specific error 0 (0x0)."
> It turned out that the problem was related to another issue that I'm about to open where
there was some unexpected parsing going on of the //IS arguments and the start class and log
file paths weren't setup.  However, for customers-- this is really unsatisfying.  It would
be great if procrun could emit an event log message indicating exactly why it returned the
0 to SCM.  This would be consistent with Windows services and then the default windows error
message would be useful and make sense.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message