> Le 27 déc. 2017 à 15:52, Olivier Mascia <[email protected]> a écrit :
>
>> Le 27 déc. 2017 à 14:49, Olivier Mascia <[email protected]> a écrit :
>>
>> On one computer (running Server 2016), I have:
>>
>> fossil version -v
>> This is fossil version 2.5 [f4a9df4dd0] 2017-12-23 04:21:41 UTC
>> Compiled on Dec 27 2017 13:45:17 using msc-19.11 (64-bit)
>>
>> And I can run it as a service.
>> ...
>> On another computer (which is 2012 R2), the exact same binary fails to run
>> as a service.
>> ...
>> It is not started because upon attempt to start it, it fails and stops.
>> Attempting to start it by "fossil winery start fossil" displays dots
>> endlessly. But I have no clue as to what this happens without any kind of
>> log of what might go wrong. The Event Viewer simply confirms it started and
>> then failed to start (or stop).
>>
>> Running "C:\Develop\Fossil\fossil.exe" server --repolist "C:/Develop/Fossil"
>> from a command-line is OK though.
>>
>> Indeed the configuration is not rigorously the same between both machines,
>> the paths where fossil.exe is located (along with the repository) are
>> different. But that doesn't look suspect.
>>
>> So what would you suggest I look for?
>
> Just built a new binary out of branch-2.4, I see the exact same behaviour. OK
> on one server, fails to start on another. So it probably is related to some
> environmental / configuration detail differing between these two computers.
> But I'm still rather clueless to find what triggers the failure without any
> kind of logging or specific error code from the service startup. Works fine
> from command-line, fails to start when configured as service. Oh yes, I could
> make a debug build and attempt to start it as a service under debugger, but
> that is generally tricky to do, unless you can attach to the service
> executable *after* it started. Here it fails to start...
So as to give context to what I mean by not having clues to what's happening,
here is the exit code returned by the Windows service controller (1067, "The
process terminated unexpectedly"). It just means though it begins, it then
properly exits (unexpectedly for the service controller) or more probably
simply crash.
C:\Develop\Fossil>sc query fossil
SERVICE_NAME: fossil
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
WIN32_EXIT_CODE : 1067 (0x42b)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
C:\Develop\Fossil>net helpmsg 1067
The process terminated unexpectedly.
--
Best Regards, Meilleures salutations, Met vriendelijke groeten,
Olivier Mascia
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
