# Strange backend message lastPgEvent (v2.0.3.6-2.0.3.6\_canary\_2018-04-23)
**URL:** https://forum.duplicati.com/t/strange-backend-message-lastpgevent-v2-0-3-6-2-0-3-6-canary-2018-04-23/3818
**Category:** Support
**Created:** [June 14, 2018, 5:43pm UTC](https://forum.duplicati.com/t/strange-backend-message-lastpgevent-v2-0-3-6-2-0-3-6-canary-2018-04-23/3818 "2018-06-14T17:43:16Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@dbddhkpde](https://forum.duplicati.com/u/dbddhkpde)
#### Post date: [June 14, 2018, 5:43pm UTC](https://forum.duplicati.com/t/strange-backend-message-lastpgevent-v2-0-3-6-2-0-3-6-canary-2018-04-23/3818/1 "2018-06-14T17:43:16Z")
Hi,
If I run the Version v2.0.3.6-2.0.3.6\_canary\_2018-04-23 I face same strange problems with the backend message lastPgEvent. It shows strange values for file processing and progress?
Here are two events:
```json
lastPgEvent : {
"BackupID":"7",
"TaskID":2,
"BackendAction":"List",
"BackendPath":null,
"BackendFileSize":-1,
"BackendFileProgress":0,
"BackendSpeed":-1,
"BackendIsBlocking":false,
"CurrentFilename":"E:\\!duplicati test\\Long-Subfolder-1\\even-longer-foldername\\final-folder-name-very-long-too\\testdumpfile1",
"CurrentFilesize":519045120,
"CurrentFileoffset":137,
"Phase":"Backup_ProcessingFiles",
"OverallProgress":0,
"ProcessedFileCount":0,
"ProcessedFileSize":0,
"TotalFileCount":5,
"TotalFileSize":231,
"StillCounting":false
}
```
and
```json
lastPgEvent : {
"BackupID":"7",
"TaskID":2,
"BackendAction":"List",
"BackendPath":null,
"BackendFileSize":-1,
"BackendFileProgress":0,
"BackendSpeed":-1,
"BackendIsBlocking":false,
"CurrentFilename":"E:\\!duplicati test\\Long-Subfolder-1\\even-longer-foldername\\final-folder-name-very-long-too\\testdumpfile2",
"CurrentFilesize":137,
"CurrentFileoffset":137,
"Phase":"Backup_ProcessingFiles",
"OverallProgress":0,
"ProcessedFileCount":0,
"ProcessedFileSize":0,
"TotalFileCount":5,
"TotalFileSize":231,
"StillCounting":false
}
```
FileSize of testdumpfile1 is correct (519.045.120 Byte) but the “CurrentFileoffset” of 137 never changes during backup. The second testdumpfile2 is significantly(!) bigger than indicated “CurrentFilesize” of 137 and with that file it was the same that the “CurrentFileoffset” of 137 never changed.
If I switch back to Version v2.0.3.5-2.0.3.5\_canary\_2018-04-13 everything is fine again. With both versions I can run a backups and a restore.
Can someone confirm this behavior or is there something wrong with my build?
---
### Author:  [@JonMikelV](https://forum.duplicati.com/u/JonMikelV)
#### Post date: [June 15, 2018, 3:59pm UTC](https://forum.duplicati.com/t/strange-backend-message-lastpgevent-v2-0-3-6-2-0-3-6-canary-2018-04-23/3818/2 "2018-06-15T15:59:48Z")
> [@dbddhkpde](#):
>
> Can someone confirm this behavior or is there something wrong with my build?
I can’t confirm the behavior but I can confirm that 2.0.3.6 is known to have some issues so I’d strongly recommend you stay with 2.0.3.5 for the moment.
I’m going to tag @kenkendk on this as I think he’s close to being ready to put out a new canary version but I don’t know whether or not he’s address this particular issue in what’s been fixed so far.
(Oh, and I edited your post to make the JSON more readable by starting the block with triple-tics and the word “json” (so: ```json) and ending it with just triple-tics. The line formatting I did manually.)
---
### Author:  [@kenkendk](https://forum.duplicati.com/u/kenkendk)
#### Post date: [June 15, 2018, 8:38pm UTC](https://forum.duplicati.com/t/strange-backend-message-lastpgevent-v2-0-3-6-2-0-3-6-canary-2018-04-23/3818/3 "2018-06-15T20:38:18Z")
Yes, it looks like a reporting issue with the canary.
The new code is running on multiple files in parallel, so maybe that is causing problems.
---
### Author:  [@kenkendk](https://forum.duplicati.com/u/kenkendk)
#### Post date: [June 16, 2018, 8:59pm UTC](https://forum.duplicati.com/t/strange-backend-message-lastpgevent-v2-0-3-6-2-0-3-6-canary-2018-04-23/3818/4 "2018-06-16T20:59:12Z")
I found the problem. The progress was also reporting on metadata, which caused problems because the metadata path is the same as the source data path. This explains the small number (137) being reported.
I have fixed it by ignoring metadata, as it tends to be very small.
---
### Author:  [@dbddhkpde](https://forum.duplicati.com/u/dbddhkpde)
#### Post date: [June 17, 2018, 2:23pm UTC](https://forum.duplicati.com/t/strange-backend-message-lastpgevent-v2-0-3-6-2-0-3-6-canary-2018-04-23/3818/5 "2018-06-17T14:23:47Z")
Thanks a lot for looking at it and fixing it!
---
### Author:  [@JonMikelV](https://forum.duplicati.com/u/JonMikelV)
#### Post date: [June 18, 2018, 4:39am UTC](https://forum.duplicati.com/t/strange-backend-message-lastpgevent-v2-0-3-6-2-0-3-6-canary-2018-04-23/3818/6 "2018-06-18T04:39:24Z")
I believe this fix has rolled with 2.0.3.7 canary, so if you happen to update to it please let us know whether or not it fixes the odd lastPgEvent messages you were getting. 🙂
> [@Release: 2.0.3.7 (canary) 2018-06-17](https://forum.duplicati.com/t/release-2-0-3-7-canary-2018-06-17/3844):
>
> [2.0.3.7-2.0.3.7\_canary\_2018-06-17](https://github.com/duplicati/duplicati/releases/tag/v2.0.3.7-2.0.3.7_canary_2018-06-17) Added option to exclude empty folders Added option to exclude folders based on the existence of a marker file Changed the generation of index files to avoid pulling them from a database query Fixed an issue that would create large index files Improved the recreate logic to work if some files are missing, but the data exists in other files Fixed spacing in the status bar UI, thanks @SanduRajapakse Optimized unittests for serialization, thanks @warwickmmImprov…
---
### Author:  [@dbddhkpde](https://forum.duplicati.com/u/dbddhkpde)
#### Post date: [June 18, 2018, 9:04pm UTC](https://forum.duplicati.com/t/strange-backend-message-lastpgevent-v2-0-3-6-2-0-3-6-canary-2018-04-23/3818/7 "2018-06-18T21:04:58Z")
Yes lastPgEvent is now back on track! Problem solved.
BUT: master progress bar at the top of the index.html is no longer updated, no speed indication nor number of remaining files. Try to figure it out myself, but if someone can step in 😊 I would be happy.
Seems to be a “cosmetic error” because backing up and restoring files work great so far!