UrBackup Client at idle time it uses one core per 100%

Thanks! Could you send the client log file as well?

debug.7z (47.9 KB)

Sorry, no hints yet w.r.t. the cause :confused:

Could you capture a bit of what UrBackupClientBackend.exe does with https://docs.microsoft.com/de-de/sysinternals/downloads/procmon and send that as well?

I am experiencing the exact same issue. Windows Client version 2.4.8, Windows 7 64-bit PC.

Logfile.7z (559.4 KB)

Windows 10 x64 1903 18362.418

No hints either. Could be it is caused by ipv6. If you add

--disable_ipv6
true

to C:\Program files\UrBackup\args.txt and it doesn’t occur that would confirm this.

Well I’ll try. If I restart the service it stops using the CPU at 100% for a while.

After IPv6 is disabled, everything is fine.

1 Like

Hi,
Same issue here.
I have UrBackup client running for 1 or 2 years and the CPU issue didn’t occur so far.
Problem started just yesterday, UrBackup client was stuck as using a full CPU thread all day long. I wasn’t sure if it was actually working on idle.

Disabling IPv6 resolved the issue.
(and restarting the client backend service)

Grégory

Could someone create a few memory dumps while the thread is at 100%? (see https://docs.microsoft.com/en-gb/archive/blogs/debugger/what-is-a-dump-and-how-do-i-create-one#to-create-a-dump-using-task-manager how)

Hopefully that shows where it loops…

  • I have two computers having the same problem, both at the same location, same network, almost same windows 10 configuration.
  • debug.log contains many of these entries:
  • WARNING: Parent of file with FRN 30680772461791824 (Name “006D000000050A507278AC03”) with FRN 281474976710685 not found. Searching via MFT as fallback.
  • WARNING: Parent directory not found in MFT. Was probably deleted.
  • the internet access was updated to Deutsche Glasfaser a few months ago which uses ipv6 natively.
  • backup over internet is not configured.
  • This problem only occured recently.
  • It appeared only file backups were affected by this (verified by seeing that an image backup was made after the problem was reported to me)
  • Updating the server to the latest version did not help.
  • A fresh reinstallation, making sure there were no files left in installation directoy before installation results in the same symptoms.
  • Disabling ipv6 via args.txt helped making the 100% load go away.

I will send you the memory dump via email.

I cannot send you any email:

info@infscape.com: host mail.infscape.com[46.101.244.189] said: 550 5.1.1
info@infscape.com: Recipient address rejected: User unknown in virtual
mailbox table (in reply to RCPT TO command)

Disabling ipv6 via args.txt did not fully resolve the problem. No backup could be done.
Disabling ipv6 on the network adapter (and restoring args.txt) helped. Backups are working normally again.

Here is one dump.

Edit: Removed. Thanks. got it.

Try bugreports@urbackup.org . Thanks!

Can’t see a problem yet :confused:

What would also be helpful would be a procmon log of the UrBackupClientBackend.exe process. Please restart the service while procmon is logging, so it logs the startup:

I have sent the the dump to bugreports@
I can try to log a procmon dump the next time I have time to check on the affected computers.

I had a look with procmon on UrBackupClientBackend.exe before but I did it without restarting the process. Nothing was logged.

Sorry for digging up this old issue, but I observe exactly the same behaviour:

  • One core is utilized by UrBackupClientBackend.exe.
  • In Procmon I see high frequent access to backup_client.db at different offsets.
  • In debug.log I see many warnings “Couldn’t follow up to root via Database. Falling back to MFT.”

I have already disabled ipv6 which seemed to solve the issue for a while, but not permanently. There is no backup in progress, nor has been recently executed.

Any idea?

I am sorry for bumping too however there is another, additional major issue. I had this setting (ipv6 disable) I do remember. Once I noticed 100% CPU I checked other things however when I checked, the configuration setting was gone. Did an update/upgrade cause it? I am kinda OK with fixing it (2 machines which are 2 meters away) but on a large installation this could become a nightmare.