955078 - Log files often get lost during shutdown

Status: RESOLVED WORKSFORME

(Chat Core :: General, defect)

Description

[aleth [:aleth]]

*** Original post on bio 1649 at 2012-08-14 22:48:00 UTC ***

When IB shuts down incorrectly (e.g. because the process is killed during system shutdown), log files of open conversations/MUCs are completely lost (the file still exists, but is of zero length). This can be rather annoying. It would be nice if there was a nonexpensive way of making this less fragile.

Comment 1

[aleth [:aleth]]

*** Original post on bio 1649 at 2013-02-02 14:04:56 UTC ***

I've since confirmed that this doesn't just happen during system shutdowns, it's enough to quit IB with the conversation on hold. It doesn't always happen, but is quite frequent (multiple times a week).

I have no idea how to even begin to try to fix this, but it's pretty bad (frequent data loss).

Comment 2

[aleth [:aleth]]

*** Original post on bio 1649 at 2013-08-02 17:58:53 UTC ***

Less frequent than it used to be, but something like a power cut seems to cause it.

Comment 3

[Florian Quèze [:florian]]

*** Original post on bio 1649 at 2013-08-08 14:00:51 UTC ***

Any idea of what could be causing it? Is it that after an unclean shutdown your OS truncates all the files that were open for writing and never closed?
Should we close the log files after a short period of inactivity and reopen the same file if the conversation resumes?

Comment 4

[aleth [:aleth]]

This was on a network drive. It has to do with how files are written I think.
Here are some ideas and explanations for how to get around this problem: http://dutherenverseauborddelatable.wordpress.com/2014/02/05/is-my-data-on-the-disk-safety-properties-of-os-file-writeatomic/

Comment 5

[aleth [:aleth]]

nhnt11, can this be considered fixed?

Comment 6

[aleth [:aleth]]

I think due to the existing shutdown blocker the answer is "yes".