Re: [Wrapper-user] Service started by Windows cluster does not work properly

[Christian M. <chr...@ta...>]

George,

could you try to activate the syslog and re-run the situation you
explained in your first mail?

Activating the syslog will result in the wrapper sending the output to
the syslog as well.
Just put this line into your conf file(s):
wrapper.syslog.loglevel=WARN

This should display at least all warnings (for instance the log file
was not accessible).

For diagnostics you can also try setting the loglevel to INFO which
will send all outputs (except DEBUG) to the syslog.

Cheers,
Christian


2010/8/12 Christian Mueller <chr...@ta...>:
> George,
>
> I'm sorry for the delay.
> I unfortunately couldn't reproduce the problem you were seeing.
>
> However when the Cluster Management Tool as well as the Windows
> Service say that the service is started then I assume that the wrapper
> wasn't been able to write the log file has for some reason to the
> location you expected.
> In this case the Wrapper will log output to a file called wrapper.log
> in the current working directory. The current working directory will
> most likely be the directory containing the binary. However, in some
> cases, when running as a Windows Service, the wrapper.log file may be
> placed in your system directory (WinNT\System32).
>
> Are you having any storage dependencies for the service?
>
> Sincerely,
> Christian
>
>
> 2010/8/9 波波 . <gw...@ho...>:
>> Dear all,
>>
>> I've used Java Serivce Wrapper 3.3.6 to wrap my application as a service,
>> and I installed my service on 2 machines which are nodes of a Windows
>> cluster.Then I configured my service as a resource in Windows cluster
>> manager, so if one node fails, the cluster service can start my service on
>> another node automatically.
>>
>> My service worked properly until the last system rebooting. After the system
>> rebooted, I saw the resource of my service was online in cluster manager,
>> and I also saw my service started in Windows' Services. But my service did
>> not functioning - there were no output of it. I checked the log of my
>> service (wrapper.log), it is strange that the log was not updated since the
>> system shut down - neither the wrapper itself nor my application wrote any
>> messages into the log file.
>>
>> To resume the production ASAP, I stopped my service and the cluster service
>> detected this action and started my service automatically. After that, I
>> could saw the output of my service.
>>
>> I'm confused that why my service did not work after system reboot - it was
>> started by Windows cluster service, but it worked after restarting - it was
>> also started by cluster service. And why was the log file not updated while
>> the service was running after system reboot? Thanks for any clues.
>>
>> The configuration of my service is attached.
>>
>> Regards,
>> George
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>