Hi,
I have a Windows 7 client that failed it’s backup weeks ago but still shows on the activities page.
I have tried stopping it from the server end and at the client.
I have also restarted both client and server but the damned client is always there on the activities page.
How can I kill it? 
Hi all,
I updated the server and the client finally disappeared.
When it tried to backup again it stops and once more it won’t go away.
Here’s the output from the show log button;
25/07/17 18:58 DEBUG GT: Linked file “Pkzip25.exe”
25/07/17 18:58 DEBUG GT: Linked file “Voucher.dll”
25/07/17 18:58 ERROR Error getting parallel hash for file “BNUM.DAT” line 875
25/07/17 18:58 DEBUG GT: Linked file “GL.INI”
25/07/17 18:58 DEBUG GT: Linked file “GUESTLINELOGO.bmp”
25/07/17 18:58 DEBUG GT: Linked file “Gl.bmp”
It will stay like that forever.
Here’s the last log entry for this client;
Level Time Message
Info
26/06/17 11:33
Starting unscheduled full file backup…
Info
26/06/17 11:34
Change block tracking active on volume c:
Info
26/06/17 11:34
Indexing of “Desktop” done. 8 filesystem lookups 0 db lookups and 0 db updates
Info
26/06/17 11:34
Indexing of “Contacts” done. 1 filesystem lookups 0 db lookups and 0 db updates
Info
26/06/17 11:34
Indexing of “Favorites” done. 5 filesystem lookups 0 db lookups and 0 db updates
Info
26/06/17 11:34
Indexing of “Documents” done. 33 filesystem lookups 0 db lookups and 0 db updates
Info
26/06/17 11:34
Indexing of “Music” done. 1 filesystem lookups 0 db lookups and 0 db updates
Info
26/06/17 11:34
Indexing of “Pictures” done. 2 filesystem lookups 0 db lookups and 0 db updates
Info
26/06/17 11:34
Indexing of “Videos” done. 1 filesystem lookups 0 db lookups and 0 db updates
Info
26/06/17 11:34
Indexing of “Guestline” done. 45 filesystem lookups 0 db lookups and 0 db updates
Info
26/06/17 11:34
PiedBull: Loading file list…
Info
26/06/17 11:34
PiedBull: Started loading files…
Errors
26/06/17 11:34
Error getting parallel hash for file “4580A3C3.tmp” line 262
Info
26/06/17 11:34
Waiting for parallel hash load stream to finish
Errors
26/06/17 11:34
Error during parallel hash load: TIMEOUT
Info
26/06/17 11:34
Waiting for file transfers…
Errors
26/06/17 11:35
Client calculated hash of “/mnt/backups/PiedBull/170626-1133/windows_components_config/{A65FAA63-5EA8-4EBC-9DBD-A0C4DB26912A}.xml” differs from server calculated hash. This may be caused by a bug or by random bit flips on the client or server hard disk. (Hash: tree-sparse, client hash: IM6F8JGDsTXuYPfuKlGg4VocfP0BAAAAAQAAAAEAAAABAAAAAQAAAAEAAAABAAAAAQAAAAEAAAABAAAAAQAAAA==, server hash: AaehcNYJR6jGHvBMyx4Ugg9WzMmGVMBRNdOMcgEAAAABAAAAAQAAAAEAAAABAAAAAQAAAAEAAAABAAAAAQAAAA==)
Errors
26/06/17 11:35
Client calculated hash of “/mnt/backups/PiedBull/170626-1133/windows_components_config/backupcom.xml” differs from server calculated hash. This may be caused by a bug or by random bit flips on the client or server hard disk. (Hash: tree-sparse, client hash: fFtDt3r2RBppcB6FoVx0mIohbdcBAAAAAQAAAAEAAAABAAAAAQAAAAEAAAABAAAAAQAAAAEAAAABAAAAAQAAAA==, server hash: z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==)
Errors
26/06/17 11:35
Client calculated hash of “/mnt/backups/PiedBull/170626-1133/windows_components_config/info.json” differs from server calculated hash. This may be caused by a bug or by random bit flips on the client or server hard disk. (Hash: tree-sparse, client hash: fFtDt3r2RBppcB6FoVx0mIohbdcBAAAAAQAAAAEAAAABAAAAAQAAAAEAAAABAAAAAQAAAAEAAAABAAAAAQAAAA==, server hash: qMu7qwMR168IUXiIHVJB77nMsIwBAAAAAQAAAAEAAAABAAAAAQAAAAEAAAABAAAAAQAAAAEAAAABAAAAAQAAAA==)
Info
26/06/17 11:35
Waiting for file hashing and copying threads…
Info
26/06/17 11:35
Saving file metadata…
Info
26/06/17 11:35
Writing new file list…
Info
26/06/17 11:35
Transferred 108.773 MB - Average speed: 12.3514 MBit/s
Info
26/06/17 11:35
(Before compression: 1.10108 GB ratio: 10.3656)
Info
26/06/17 11:35
Time taken for backing up client PiedBull: 2m 22s
Errors
26/06/17 11:35
Backup failed
Anyone got a clue what’s going on?
I still have this client on the activities page. It came back after a server update to 2.2.3
If you can, can you post stacktraces of active threads? E.g. via gdb attach PID, then thread apply all bt.
I think I have an issue with GDB…
root@UrBackup:/ # gdb attach 17092
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type “show copying” to see the conditions.
There is absolutely no warranty for GDB. Type “show warranty” for details.
This GDB was configured as “amd64-marcel-freebsd”…attach: No such file or directory.
Attaching to process 17092
/usr/src/gnu/usr.bin/gdb/libgdb/…/…/…/…/contrib/gdb/gdb/solib-svr4.c:1444: internal-error: legacy_fetch_link_map_offsets called without legacy link_map support enabled.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
Make sure it is a later version. That version is from 2004 
(pkg install gdb or something…)
Updating the Server version to 2.2.4 cleared the issue completely.
The client now backs up and disappears just like all the rest.
Many thanks for the help and the great software.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.