Marking Fix Released since rdiff-backup 1.2.5-1 is now in Jaunty
** Changed in: rdiff-backup (Ubuntu)
Status: Fix Committed = Fix Released
--
rdiff-backup crashed with IOError in read()
https://bugs.launchpad.net/bugs/304659
You received this bug notification because you are a member of
** Tags removed: need-duplicate-check
--
rdiff-backup crashed with IOError in read()
https://bugs.launchpad.net/bugs/304659
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have now added /sys to my exclude list, but it's good to see 1.2.3
will handle this case and I look forward to its release. Marking Fix
Committed since the fix exists in upstream CVS. Thanks Andrew for your
great work yet again :-)
** Changed in: rdiff-backup (Ubuntu)
Status: New = Fix
Hew,
I have to tell you: If you are really getting the exact same error
IOError: [Errno 110] Connection timed out with the same traceback,
then I don't see how the problem can't be in rdiff-backup. The problem
is occurring while it is reading from a file.
Do you upgrade *anything* else when you
don't see how the problem *can* be in rdiff-backup. :-)
--
rdiff-backup crashed with IOError in read()
https://bugs.launchpad.net/bugs/304659
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I truly only replace the rdiff-backup package.
It looks like it's having a problem in /sys. Excluding this directory
results in a successful backup. I have attached the -v5 log of the
problem.
** Attachment added: rdiff-backup-v5.log.gz
Right, /sys shouldn't be backed-up. :-)
So, why did 1.1.16 pass over this problem, and 1.2.2 choke? In 1.1.16,
it failed to read any information about the files in /sys, and thus
skipped over it. By 1.2.2, some bugs had been fixed to make rdiff-backup
better able to read information about
I have just upgraded back to 1.2.2-1 and the exact same error is
occuring. This is very reproducible, occurring all the time with
1.2.2-1, and never with 1.1.16-2. Please let me know what further
information would be useful, I am happy to continue testing.
--
rdiff-backup crashed with IOError in
Hew,
I don't think the version of rdiff-backup is connected to this problem;
the fact that you downgraded and it worked again was probably only a
coincidence.
The error message indicates that the backup process Timed Out while
reading a file. Unfortunately, I haven't seen that situation give
I reproduced the problem when trying to run the backup again.
Downgrading to rdiff-backup 1.1.16-2 (Intrepid version) and trying again
completed the backup successfully. I haven't seen anything that says
compatibility is intentionally broken, and in any case a crash should
not occur.
--
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/20158542/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/20158543/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/20158544/ProcStatus.txt
** Attachment
11 matches
Mail list logo
