Duplicity full backup after incremental doesn't finish

I am using duplicity as backup solution. At first launch my backup finished successfully. Then I am making 2 incremental backups. that ok too. Then I want to make full backup again and it doesn't end. I can not catch error because I am using bash script. I've tested this 3 times. So thats my manifest files at home dir:

-rw------- 1 root root 272915 Jan 21 07:01 duplicity-full.20140120T190439Z.manifest
-rw------- 1 root root 273653 Jan 24 07:05 duplicity-full.20140123T190433Z.manifest.part
-rw------- 1 root root 2112444910 Jan 21 07:07 duplicity-full-signatures.20140120T190439Z.sigtar.gz
-rw------- 1 root root 4763863040 Jan 24 07:05 duplicity-full-signatures.20140123T190433Z.sigtar.part
-rw------- 1 root root 1607 Jan 22 01:39 duplicity-inc.20140120T190439Z.to.20140121T190355Z.manifest
-rw------- 1 root root 229 Jan 23 01:37 duplicity-inc.20140121T190355Z.to.20140122T190359Z.manifest
-rw------- 1 root root 42040363 Jan 22 01:39 duplicity-new-signatures.20140120T190439Z.to.20140121T190355Z.sigtar.gz
-rw------- 1 root root 41841288 Jan 23 01:37 duplicity-new-signatures.20140121T190355Z.to.20140122T190359Z.sigtar.gz

As you can see it doesn't end. How can I debug? I tried to use loglevel 8 but it doesn't show anything interesting. But this log file is old. :

DEBUG 1
. File duplicity-full.20140111T190430Z.vol731.difftar.gz is part of known set

DEBUG 1
. File duplicity-full.20140117T190431Z.vol175.difftar.gz is part of known set

DEBUG 1
. File duplicity-full.20140111T190430Z.vol503.difftar.gz is part of known set

DEBUG 1
. File duplicity-full.20140111T190430Z.vol38.difftar.gz is part of known set

DEBUG 1
. File duplicity-full.20140111T190430Z.vol398.difftar.gz is part of known set

DEBUG 1
. Found backup chain [Thu Jan 9 01:04:32 2014]-[Thu Jan 9 01:04:32 2014]

INFO 1
. Added incremental Backupset (start_time: Thu Jan 9 01:04:32 2014 / end_time: Fri Jan 10 01:03:20 2014)

DEBUG 1
. Added set Fri Jan 10 01:03:20 2014 to pre-existing chain [Thu Jan 9 01:04:32 2014]-[Fri Jan 10 01:03:20 2014]

INFO 1
. Added incremental Backupset (start_time: Fri Jan 10 01:03:20 2014 / end_time: Sat Jan 11 01:03:54 2014)

DEBUG 1
. Added set Sat Jan 11 01:03:54 2014 to pre-existing chain [Thu Jan 9 01:04:32 2014]-[Sat Jan 11 01:03:54 2014]

DEBUG 1
. Found backup chain [Sun Jan 12 01:04:30 2014]-[Sun Jan 12 01:04:30 2014]

DEBUG 1
. Found backup chain [Sat Jan 18 01:04:31 2014]-[Sat Jan 18 01:04:31 2014]

DEBUG 1
. Removing still remembered temporary file /tmp/duplicity-EgcT07-tempdir/mkstemp-JrkoqF-1

and that's all. BTW my list of backups:

Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Fri Jan 24 01:04:33 2014
Collection Status
-----------------
Connecting with backend: LocalBackend
Archive dir: /root/.cache/duplicity/b6ed4b7700a42eeebc48fa9578e929d1

Found 1 secondary backup chain.
Secondary chain 1 of 1:
-------------------------
Chain start time: Tue Jan 21 01:04:39 2014
Chain end time: Thu Jan 23 01:03:59 2014
Number of contained backup sets: 3
Total number of contained volumes: 954
 Type of backup set: Time: Num volumes:
                Full Tue Jan 21 01:04:39 2014 946
         Incremental Wed Jan 22 01:03:55 2014 7
         Incremental Thu Jan 23 01:03:59 2014 1
-------------------------

Found primary backup chain with matching signature chain:
-------------------------
Chain start time: Fri Jan 24 01:04:33 2014
Chain end time: Fri Jan 24 01:04:33 2014
Number of contained backup sets: 1
Total number of contained volumes: 948
 Type of backup set: Time: Num volumes:
                Full Fri Jan 24 01:04:33 2014 948

and the command I am executing:
duplicity --tempdir /backup/tmp --volsize 150 --full-if-older-than $FULL_BACKUP_PERIOD"D" --no-encryption $INCLUDE --exclude '**' / $BACKUP_EXCLUDES $DUP_ARCHIVE >> $LOGFILE