commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mladen Turk (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DAEMON-254) Logfile corrupted. Service won't start until logfile is deleted.
Date Wed, 21 Nov 2012 08:15:58 GMT

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

Mladen Turk resolved DAEMON-254.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0.11

Fixed in the trunk by using file flush function on log write.
This should ensure data is written to disk.

                
> Logfile corrupted. Service won't start until logfile is deleted.
> ----------------------------------------------------------------
>
>                 Key: DAEMON-254
>                 URL: https://issues.apache.org/jira/browse/DAEMON-254
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Procrun
>    Affects Versions: 1.0.10
>         Environment: Windows 7 64-bit, 32-bit prunsrv.exe
>            Reporter: Hannes Schwarz
>             Fix For: 1.0.11
>
>
> Sometimes trying start the service fails (it seems to stop automatically) until the logfile
is deleted. The file seems to be corrupt, but I could not determine what's wrong yet.
> "Interestingly", notepad.exe displays the logfile as usual, while other tools (e.g. Wordpad,
Notepad++) report an error or show an empty file. Eclipse text editor reports "error retrieving
content description".
> The last entry in the logfile shown by notepad.exe is "[info]  Commons Daemon procrun
(1.0.10.0 32-bit) started".
> The bug is not present in version 1.0.9.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message