> On Feb 8, 2019, at 2:02 PM, Michael Hendry <hendry.mich...@gmail.com> wrote: > >> On 8 Feb 2019, at 17:26, John Ralls <jra...@ceridwen.us> wrote: >> >> >> >>> On Feb 8, 2019, at 8:28 AM, Colin Law <clan...@gmail.com> wrote: >>> >>> On Fri, 8 Feb 2019 at 15:31, Michael Hendry <hendry.mich...@gmail.com> >>> wrote:> ... >>>> | => ls -lt >>>> total 84324 >>>> -rw-r--r-- 1 michaelhendry staff 221184 8 Feb 00:04 >>>> MDH.gnucash.tmp-ea6yhc >>>> -rw-r--r-- 1 michaelhendry staff 95629 8 Feb 00:04 >>>> MDH.gnucash.20190208000345.log >>>> -rw------- 2 michaelhendry staff 0 8 Feb 00:03 >>>> MDH.gnucash.0.82823.LNK >>>> -rw------- 2 michaelhendry staff 0 8 Feb 00:03 MDH.gnucash.LCK >>>> -rw-r--r-- 1 michaelhendry staff 809 8 Feb 00:01 >>>> MDH.gnucash.20190207202353.log >>>> -rwx------ 2 michaelhendry staff 1136826 7 Feb 20:23 MDH.gnucash >>>> -rw-r--r-- 1 michaelhendry staff 853 7 Feb 20:23 >>>> MDH.gnucash.20190207202200.log >>>> -rwx------ 2 michaelhendry staff 1136826 7 Feb 20:23 >>>> MDH.gnucash.20190208000443.gnucash >>>> -rw-r--r-- 1 michaelhendry staff 23810 7 Feb 20:22 >>>> MDH.gnucash.20190207185926.log >>>> -rwx------ 1 michaelhendry staff 1136752 7 Feb 20:22 >>>> MDH.gnucash.20190207202348.gnucash >>>> -rwx------ 1 michaelhendry staff 1136766 7 Feb 18:59 >>>> MDH.gnucash.20190207202153.gnucash >>>> >>>> There is no corresponding crash report, so I conclude that GC has failed >>>> to tidy up properly before closing. >>> >>> That looks odd. Notice that the last successful save was 7 Feb 20:23. >>> Then it appears that GC was started at 8 Feb 00:03, a log file of 95k > > Actually, the first file was modified on 8th Feb at 00:01, followed by the > lock file at 00:03. > > The MDH.gnucash.tmp-ea6yhc file isn’t a text file like the others, so I > suspect that it’s part of the compression process that eventually results in > a new MDH.gnucash file. > >>> bytes was created (which seems large) but the results of that work >>> were not saved. I don't know, but it may be that the file >>> MDH.gnucash.tmp-ea6yhc is the result of the first half of the save >>> before it is compressed and the files renamed but I don't know. How >>> you could get a log file that large in one minute I don't know. I see >>> you have posted some of the contents and suggested they don't look >>> right. >> >> Scheduled transactions is how he could get 95K of log file in milliseconds. >> >> Good eye, noticing the temp file: The save failed for some reason and left >> GnuCash in a state where it quit without removing the lock. It's too bad >> that we overwrite trace files on MacOS. It would be useful to see if >> anything got logged about the save failing. >> >> I think it's time to open a bug on this. >> >> Regards, >> John Ralls > > Thanks, John. > > Is it up to me to initiate this?
It works best if you do, but if you prefer not to I'll do it for you with the information in this thread. Regards, John Ralls _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
