Async indexing process not found

general discussion
14

Exclusion resulted in same timeout.

06/07/17 08:12 INFO Starting unscheduled full file backup…
06/07/17 08:12 DEBUG HOOVER: Connecting for filelist…
06/07/17 08:12 DEBUG HOOVER: Waiting for filelist
06/07/17 08:13 ERROR Constructing of filelist of “HOOVER” failed - TIMEOUT(1)
06/07/17 08:13 ERROR Backup had an early error. Deleting partial backup.

15

Hmm, looks like a normal, but deep folder structure. I’ll run some tests.

16

Thank you.

17

Hi Uroni. Have your tests revealed anything?

18

Yeah, increasing the stack size for the indexing thread fixes it.

19

Thanks. What’s the recommended procedure for increasing the stack size or is that done in a patch to the client.

20

Any thoughts on this? Thanks.

21

i think he has to patch

1 Like
22

Hi guys,
I’m experiencing the same problems very often lately with several client (backup over Internet). I got Async indexing process not found both on windows and linux client. The problem happens randomly: sometimes the client return this error, sometimes it’s able to work fine.

My server is versione 2.1.19 working on Ubuntu 16.04, my clients are 2.1.16. I read what you wrote, are these releases patched?

What could I do to send you some relevant information in order you can discover if there is a bug?

Thanks

23

Hi, some news about this? Thanks

24

i remember seing a patch was commited in github.
You still got he issue in latest beta, if it s not there , it will be in the next one?

25

Now I cannot delete the folder structure I created for testing this :frowning:

I even managed to bluescreen in NTFS.sys (Windows 10).

26

Some Windows “unable to delete” errors involve pathnames too long. I suspect code introduced to support the Recycle Bin that runs even if the path is being purged. Try moving (cut/paste) a lower part of the structure to the root of the drive and see if that helps. I’ve experienced it with Server 2008r2 but Microsoft seldom rewrites from scratch. Breaking a long path up with cut/paste seems to follow a different code pathway that avoids the bug.

27

I had this error and installed 2.2.2 beta and resolved it.

28

I am concerned about installing a beta version in a production environment. Is there a plan to go to release with a new Windows client soon?

29

I have set up beta 2.2.4 and am using client 2.1.17 in the hopes of sorting this out. Still no go. On the client side I see:

2017-12-24 06:16:48: WARNING: Limiting number of DC users to 102
2017-12-24 06:19:42: WARNING: Limiting number of DC groups to 101
2017-12-24 06:21:29: ERROR: Fatal exception code 3221225725 at address 0x0000000077BADD43
2017-12-24 06:30:55: WARNING: Limiting number of DC users to 102

On the server side I see:

2017-12-24 06:35:32: HOOVER: Connecting for filelist (async)…
2017-12-24 06:35:32: Lost channel connection to HOOVER. has_error=true
2017-12-24 06:35:33: ERROR: Constructing of filelist of “HOOVER” failed: error - Async indexing process not found
2017-12-24 06:35:33: ERROR: Hint: The most likely explanation for this error is that the client was restarted/rebooted during indexing
2017-12-24 06:35:37: ERROR: Backup had an early error. Deleting partial backup.

The client was not restarted/rebooted during indexing.

I simply cannot back up this client.

Any help appreciated. Thanks.

30

You could send the client crashdump to bugreports@urbackup.org ? Also perhaps use the beta client as well, because the AD code is completely rewritten (improved) there.

31

I was unable to obtain a crashdump (none was generated as before), however this combination of server/client works.
Server 2.2.4 beta (Centos 7)
Client 2.2.3 beta (Windows 7)

Backup started quickly and 46.45GB in 61 min. No issues.

I have also tested the following with the same client machine:
Server 2.1.19 (Centos 6)
Client 2.2.3 beta (Windows 7)

Backup started and while the back up is much, much slower, it is running. Of course this may be due to the 5 other backups running at the same time.

So, I have a backup of the client which has alluded me for almost 6 months. How close are you to releasing these betas to production? It seems your updates have sorted the problem (at least for me).

32

Hi. This bug comeback
WARNING: Parent of file with FRN 1407374884224845 (Name “[140457]Scan_20200319181817.jpg”) with FRN 1407374884224844 not found. Searching via MFT as fallback.
and this client not backup automatic.
Manual increment backup Ok
win2012 2.4.10

33

Seconded, I’m getting this error on Win10 with the 2.4.10 client as well.

2020-07-21 11:06:34: ERROR: Could not open path in os_get_final_path for ":"
2020-07-21 11:11:04: WARNING: Parent of file with FRN 4785074604111844 (Name “00110000000077E42035E547”) with FRN 562949953510989 not found. Searching via MFT as fallback.
2020-07-21 11:11:04: WARNING: Parent directory not found in MFT. Was probably deleted.

… Repeats a bunch of times …

2020-07-21 11:11:05: WARNING: Parent of file with FRN 11821949021878406 (Name “002A00000000788605918F65”) with FRN 562949953510989 not found. Searching via MFT as fallback.
2020-07-21 11:11:05: WARNING: Parent directory not found in MFT. Was probably deleted.
2020-07-21 11:14:45: ERROR: Could not open path in os_get_final_path for ":"
2020-07-21 11:14:45: ERROR: Could not open path in os_get_final_path for ":"
2020-07-21 11:14:49: ERROR: backupcom->DeleteSnapshots(set_last ? scs.ssetid : scs.vssid, set_last ? VSS_OBJECT_SNAPSHOT_SET : VSS_OBJECT_SNAPSHOT, TRUE, &dels, &ndels) failed. VSS error code VSS_E_OBJECT_NOT_FOUND
2020-07-21 11:14:49: WARNING: Error deleting snapshot set {29017F96-706E-4190-91DF-890CC72367D1}

This is an internet client doing hashes locally.

I have the full debug log if it’s helpful, but there’s not much more to it than what’s above.