| Summary: | backup fail | ||
|---|---|---|---|
| Product: | [Applications] kmymoney | Reporter: | Leslie Brothers <leslie.brothers> |
| Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | ralf.habacker |
| Priority: | NOR | ||
| Version: | 4.6.4 | ||
| Target Milestone: | --- | ||
| Platform: | Mint (Ubuntu based) | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | AnonymousKMM.anon.xml.gz | ||
|
Description
Leslie Brothers
2015-01-25 17:58:57 UTC
What eventually happened? Did the program become responsive again or did you kill it? Have you tried again? Can you specify what you mean by backup file mounted in home directory? Do you just mean you backup to your home directory or to a subfolder there? Is that folder always mounted, or do you mount it just to do the backup? If it is explicitly mounted, what type of mount is it - external USB, NFS, SMB, ....? How long does it usually take to do the backup, and how long did you wait this time? After the backup failure, I closed KMyMoney without any problem.
However, my machine seemed to thrash for a while, then all back to
normal.
I looked in my backup folder (/home/leslie/Backups/KMM) -- which is
always mounted -- to verify that the attempted backup was indeed not
there.
I restarted KMyMoney without a problem. I then re-tried a backup as
before, and this time it worked fine.
Usually it takes a second or so for the backup.
When I reported the failure, I had waited half a minute or so with no
backup occurring. I tried to get it to backup several times and nothing
happened no matter how long I waited (minutes).
That's when I filed the report.
After reporting it, I closed KMyMoney and proceeded as I have described
to you above.
Thank you.
On Sun, 2015-01-25 at 20:28 +0000, Jack wrote:
> https://bugs.kde.org/show_bug.cgi?id=343291
>
> --- Comment #1 from Jack <ostroffjh@users.sourceforge.net> ---
> What eventually happened? Did the program become responsive again or did you
> kill it? Have you tried again?
>
> Can you specify what you mean by backup file mounted in home directory? Do you
> just mean you backup to your home directory or to a subfolder there? Is that
> folder always mounted, or do you mount it just to do the backup? If it is
> explicitly mounted, what type of mount is it - external USB, NFS, SMB, ....?
>
> How long does it usually take to do the backup, and how long did you wait this
> time?
>
Is /home/leslie/Backups/KMM a regular folder? Since you say it is always mounted, I suspect somthing else - a separate hard disk partition, a USB thumb drive, an NSF mount, and SMB mount, ...? For a normal folder, I can't think of any reason for KMM to not create the backup and not give some error message. Since it seems OK now, there is not much point in running KMM from the command line to see if it outputs any error that way. However, I can imagine problems with a mount (particularly a network mount) causing issues. Is there anything that might be relevant in the system logs (dmesg or /var/log/messages or wherever Mint puts them? Thank you for your diligence.
/home/leslie/Backups/KMM is a regular folder and, given that, I agree it
is strange for KMM to not create a backup and not give an error message.
(Sorry I was misleading by saying it is always mounted. It's just a
regular folder so mounted by definition.)
I will try to reproduce the behavior by doing what I did in the KMM
session when the backup failed -- namely, do a multi-year report, then
save and try to back up.
If the backup fails again as it did when I sent the bug report, I'll
comb through dmesg and the logs for clues and send the results to you.
I am going out of town in a few minutes, but will return and do this on
Tuesday night or Wednesday.
On Sun, 2015-01-25 at 21:48 +0000, Jack wrote:
> https://bugs.kde.org/show_bug.cgi?id=343291
>
> Jack <ostroffjh@users.sourceforge.net> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |ostroffjh@users.sourceforge
> | |.net
>
> --- Comment #3 from Jack <ostroffjh@users.sourceforge.net> ---
> Is /home/leslie/Backups/KMM a regular folder? Since you say it is always
> mounted, I suspect somthing else - a separate hard disk partition, a USB thumb
> drive, an NSF mount, and SMB mount, ...? For a normal folder, I can't think
> of any reason for KMM to not create the backup and not give some error message.
> Since it seems OK now, there is not much point in running KMM from the command
> line to see if it outputs any error that way. However, I can imagine problems
> with a mount (particularly a network mount) causing issues. Is there anything
> that might be relevant in the system logs (dmesg or /var/log/messages or
> wherever Mint puts them?
>
In case the report creation allows to duplicate the problem, we are interested in an anonymous version of your data to figure out what might be causing the mis-behaviour. See https://docs.kde.org/stable/en/extragear-office/kmymoney/details.formats.anonymous.html for details on how to create an anonymized version of your data. Created attachment 90732 [details] AnonymousKMM.anon.xml.gz (In my previous reply, I said: "/home/leslie/Backups/KMM is a regular folder and, given that, I agree it is strange for KMM to not create a backup and not give an error message. (Sorry I was misleading by saying it is always mounted. It's just a regular folder so mounted by definition.) I will try to reproduce the behavior by doing what I did in the KMM session when the backup failed -- namely, do a multi-year report, then save and try to back up.") 1. I have reproduced the conditions that create the backup problem. a. If I do an Income and Expense by Year report only, I do not need to save KMM before exiting. In that case, I can do a backup with no problem and the program exits nicely. b. If I save anything else (an entry, even a memo in a check) and ALSO do the Income and Expense by Year report in the same session, then I have to save before exiting. When I save, it is slow. If I then try the backup, it stalls as previously reported. Note, it doesn't even get to the point of telling me there is already a backup for today's date. c. Of possible relevance is that my years (for income and expense) start for some reason in 1959, although there are no figures until 1993. d. If the backup fails as just described in (b), I can close the KMM interface, but then the CPU goes and goes. I had to run top to see that the active process was kmymoney, then kill it for the machine to settle down. e. I verified that changing an entry and saving it did not cause the backup failure. The changing and saving had to occur in the same session as the income and expense by year report. Likewise, as I noted in (a), Income and Expense by itself did not cause a backup problem. It is the combination of both a change somewhere, and invoking the report, that causes the problem. 2. As requested by Thomas Baumgart, I made an anonymous file. I ran it and the problem was reproduced exactly as with my own file. I have attached the anonymous file. 3. I did not see any output in dmesg after the error occurred. I looked in syslog but did not know what I was looking for. I did not see anything obvious. Thank you. On Sun, 2015-01-25 at 21:48 +0000, Jack wrote: > https://bugs.kde.org/show_bug.cgi?id=343291 > > Jack <ostroffjh@users.sourceforge.net> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| | ostroffjh@users.sourceforge > | |.net > > --- Comment #3 from Jack <ostroffjh@users.sourceforge.net> --- > Is /home/leslie/Backups/KMM a regular folder? Since you say it is always mounted, I suspect somthing else - a separate hard disk partition, a USB thumb drive, an NSF mount, and SMB mount, ...? For a normal folder, I can't think of any reason for KMM to not create the backup and not give some error message. Since it seems OK now, there is not much point in running KMM from the command line to see if it outputs any error that way. However, I can imagine problems with a mount (particularly a network mount) causing issues. Is there anything that might be relevant in the system logs (dmesg or /var/log/messages or wherever Mint puts them? > On Sun, 2015-01-25 at 21:48 +0000, Jack wrote: > https://bugs.kde.org/show_bug.cgi?id=343291 > > Jack <ostroffjh@users.sourceforge.net> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |ostroffjh@users.sourceforge > | |.net > > --- Comment #3 from Jack <ostroffjh@users.sourceforge.net> --- > Is /home/leslie/Backups/KMM a regular folder? Since you say it is always > mounted, I suspect somthing else - a separate hard disk partition, a USB thumb > drive, an NSF mount, and SMB mount, ...? For a normal folder, I can't think > of any reason for KMM to not create the backup and not give some error message. > Since it seems OK now, there is not much point in running KMM from the command > line to see if it outputs any error that way. However, I can imagine problems > with a mount (particularly a network mount) causing issues. Is there anything > that might be relevant in the system logs (dmesg or /var/log/messages or > wherever Mint puts them? > Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! I don't know if the OP is still watching, but Transaction T000000000000000001 is dated 5/12/1959. I don't know if that was just a typo or not, but that's why the report goes back that far. Did you never notice this, even though it was likely mentioned in the Consistency Check every time you saved the file. If you can't find that transaction do a transaction search (Ctl-Shift-F) and type T000000000000000001 in the search box. Using current git master KMM, changing one transaction, saving the file, running the Income and Expense by Year Report, closing the report, and doing a backup worked just fine, with no delay or problem. Dear Jack,
Hello and thank you for this follow up on the bug I initially reported
in 2015.
In more recent versions of KMM I saw this anomalous entry reported (a
typo!) in the consistency check and I have fixed the entry.
So I am sure that the check you did, showing the problem is resolved,
will also work for me now.
Thank you for the work you and your team do.
- Leslie
On Fri, 2022-12-02 at 22:00 +0000, Jack wrote:
> https://bugs.kde.org/show_bug.cgi?id=343291
>
> Jack <ostroffjh@users.sourceforge.net> changed:
>
> What |Removed |Added
> -------------------------------------------------------------------
> ---------
> CC|ostroffjh@users.sourceforge |
> |.net |
>
> --- Comment #8 from Jack <ostroffjh@users.sourceforge.net> ---
> I don't know if the OP is still watching, but Transaction
> T000000000000000001
> is dated 5/12/1959. I don't know if that was just a typo or not, but
> that's
> why the report goes back that far. Did you never notice this, even
> though it
> was likely mentioned in the Consistency Check every time you saved
> the file
> If you can't find that transaction do a transaction search (Ctl-
> Shift-F) and
> type T000000000000000001 in the search box.
> Using current git master KMM, changing one transaction, saving the
> file,
> running the Income and Expense by Year Report, closing the report,
> and doing a
> backup worked just fine, with no delay or problem.
>
Yes, the consistency check continues to be improved to identify more and more different issues. However, what typo? If it's in my message, I plead too much hurry. If it's in the program, we can fix it. Jack,
You referenced a typo in your message. I may have been reading too
quickly but I thought you meant my date of an entry, 1959, might have
been a typo. Indeed, it was. So I was saying, yes, it was a typo on
my part. Nothing wrong with your message or the program!!
KMM is great, I use it constantly, and have relied on it for years,
although not all the way back to 1959.
-Leslie
On Sat, 2022-12-03 at 03:28 +0000, Jack wrote:
> https://bugs.kde.org/show_bug.cgi?id=343291
>
> --- Comment #10 from Jack <ostroffjh@users.sourceforge.net> ---
> Yes, the consistency check continues to be improved to identify more
> and more
> different issues.
> However, what typo? If it's in my message, I plead too much
> hurry. If it's in
> the program, we can fix it.
>
My apologies, I just got this as it was diverted to spam.
Yes, I will see if I can reproduce the issue (I need a few days..).
I replied to a subsequent email from Jack saying I believe it is
probably resolved but I will do an actual test and report back.
-Leslie
On Wed, 2022-11-30 at 05:28 +0000, Justin Zobel wrote:
> https://bugs.kde.org/show_bug.cgi?id=343291
>
> Justin Zobel <justin.zobel@gmail.com> changed:
>
> What |Removed |Added
> -------------------------------------------------------------------
> ---------
> Status|REPORTED |NEEDSINFO
> Resolution|--- |WAITINGFORINFO
>
> --- Comment #7 from Justin Zobel <justin.zobel@gmail.com> ---
> Thank you for reporting this issue in KDE software. As it has been a
> while
> since this issue was reported, can we please ask you to see if you
> can
> reproduce the issue with a recent software version?
>
> If you can reproduce the issue, please change the status to
> "REPORTED" when
> replying. Thank you!
>
Justin,
I just checked to see if I could reproduce the issue I reported.
Before doing so, I removed the entry that was dated 1959 (which now
shows up on consistency checks when I Save).
The problem I reported did not occur. So it was caused by that
anomalous (typo) 1959 entry, causing the Income and Expense by Year
report to malfunction.
All clear.
Thank you.
-Leslie
On Wed, 2022-11-30 at 05:28 +0000, Justin Zobel wrote:
> https://bugs.kde.org/show_bug.cgi?id=343291
>
> Justin Zobel <justin.zobel@gmail.com> changed:
>
> What |Removed |Added
> -------------------------------------------------------------------
> ---------
> Status|REPORTED |NEEDSINFO
> Resolution|--- |WAITINGFORINFO
>
> --- Comment #7 from Justin Zobel <justin.zobel@gmail.com> ---
> Thank you for reporting this issue in KDE software. As it has been a
> while
> since this issue was reported, can we please ask you to see if you
> can
> reproduce the issue with a recent software version?
>
> If you can reproduce the issue, please change the status to
> "REPORTED" when
> replying. Thank you!
>
So my best guess is that the old date on a transaction alone did not cause the hang, but only in concert with something else, which has since been fixed. However, since we don't have any idea of what change resolved the problem, I'll close as WORKSFORME. An excellent choice of status in my opinion. Thanks for your analysis.
Time to close!
-Leslie
On Tue, 2022-12-06 at 00:42 +0000, Jack wrote:
> https://bugs.kde.org/show_bug.cgi?id=343291
>
> Jack <ostroffjh@users.sourceforge.net> changed:
>
> What |Removed |Added
> -------------------------------------------------------------------
> ---------
> Status|NEEDSINFO |RESOLVED
> Resolution|WAITINGFORINFO |WORKSFORME
>
> --- Comment #14 from Jack <ostroffjh@users.sourceforge.net> ---
> So my best guess is that the old date on a transaction alone did not
> cause the
> hang, but only in concert with something else, which has since been
> fixed.
> However, since we don't have any idea of what change resolved the
> problem, I'll
> close as WORKSFORME.
>
|