Could you try if it is fixed with 2.0.24 now?
@uroni - yes, my backups are working now again like normal (as far as I can tell) after upgrading to server 2.0.24 beta. Thanks again! On one client, I just did a manual full image backup, and it successfully completed. On another client, I just did a manual incremental image backup, and it successfully completed.
2.0.24 still ignores the Max simultaneous backups setting.
7 backups are running at the moment altough its set to 3
Hi,
today my urbackup server crashed.
Taking a look a dmesg I see:
[833676.528211] show_signal_msg: 9 callbacks suppressed [833676.528216] ibackup main[49062]: segfault at 50 ip 00000000005af10a sp 00007f054effa660 error 4 in urbackupsrv[400000+640000]
Instead in /var/log/urbackup.log today I’ve only
2016-05-30 03:51:03: ERROR: Error downloading server version information: HTTP response code said error(ec=22), The requested URL returned error: 404 Not Found
What’s the matter?
Thanks
Do you have Temporary files as image backup buffer on?
No, it’s not flagged. I rebooted the server and the urbackup server started but then after some minutes I had a segfault again. Also trying to reboot the service it did not work, I have to reboot the machine.
Now seems the situation is stable…
I’m using 2.0.22 beta. Some ideas?
Thanks
Upgrade to 2.0.24beta.
I just done it.
I just got this email yesterday:
UrBackup just did an incremental image backup of “volt”.
Report:
( 4 infos, 0 warnings, 2 errors )
2016-05-31 18:07:16(info): Starting incremental image backup…
2016-05-31 18:07:27(info): Basing image backup on last full image backup
2016-05-31 18:09:30(error): Pipe to client unexpectedly closed has_error=true
2016-05-31 18:09:30(info): Transferred 29.5722 MB - Average speed: 2.12792 MBit/s
2016-05-31 18:09:34(info): Time taken for backing up client volt: 2m 18s
2016-05-31 18:09:34(error): Backup failed
What about these messages in /var/log/urbackup.log ?
2016-05-31 04:20:42: ERROR: Error decompressing stream(2): -3 Err: invalid code lengths set
2016-05-31 04:20:42: WARNING: Received unknown block number: 473322999689669112 (max: 15638528). Retrying...
2016-05-31 04:20:42: WARNING: Received unknown block number: -1203152400656296563 (max: 15638528). Retrying...
2016-05-31 04:20:42: WARNING: Received unknown block number: 47391175982535173 (max: 15638528). Retrying...
2016-05-31 04:20:43: WARNING: Received unknown block number: 294251379157897749 (max: 15638528). Retrying...
2016-05-31 04:20:43: WARNING: Received unknown block number: 32659189009783 (max: 15638528). Retrying...
2016-05-31 04:20:43: WARNING: Received unknown block number: 5010648452914755178 (max: 15638528). Retrying...
2016-05-31 04:20:43: WARNING: Received unknown block number: 13685735239956 (max: 15638528). Retrying...
2016-05-31 04:20:43: WARNING: Received unknown block number: -5272458335256812661 (max: 15638528). Retrying...
2016-05-31 04:20:43: WARNING: Received unknown block number: -7373950108671069089 (max: 15638528). Retrying...
2016-05-31 04:20:43: WARNING: Received unknown block number: -4006336075001023096 (max: 15638528). Retrying...
2016-05-31 04:20:45: WARNING: Checksum for image block wrong. Retrying...
2016-05-31 04:20:45: WARNING: Checksum for image block wrong. Retrying...
2016-05-31 04:20:45: WARNING: Checksum for image block wrong. Retrying...
2016-05-31 04:20:46: WARNING: Checksum for image block wrong. Retrying...
2016-05-31 04:20:47: WARNING: Checksum for image block wrong. Retrying...
2016-05-31 04:20:47: WARNING: Checksum for image block wrong. Retrying...
2016-05-31 04:20:48: WARNING: Checksum for image block wrong. Retrying...
2016-05-31 04:20:48: WARNING: Checksum for image block wrong. Retrying...
2016-05-31 04:20:48: WARNING: Checksum for image block wrong. Retrying...
2016-05-31 04:20:49: WARNING: Checksum for image block wrong. Retrying...This happen at the same time in different backups that are running.
In backup reports for few clients we have 2 warnings, e.g :
Report:
( 7 infos, 2 warnings, 0 errors )
2016-06-01 04:03:58(info): Starting full image backup...
2016-06-01 04:12:47(info): Basing image backup on last incremental or full image backup
2016-06-01 04:12:57(info): Creating writable snapshot of previous image backup...
2016-06-01 04:34:15(warning): Received unknown block number: 7589133822802470142 (max: 15638528). Retrying...
2016-06-01 04:34:18(warning): Checksum for image block wrong. Retrying...
2016-06-01 09:16:39(info): Transferred 6.85259 GB - Average speed: 3.23303 MBit/s
2016-06-01 09:16:39(info): (Before compression: 12.3973 GB ratio: 1.80914)
2016-06-01 09:16:39(info): Time taken for backing up client SV203: 5h 12m 40s
2016-06-01 09:16:39(info): Backup succeededRegards,
Another strange thing this morning, look at the “ratio” value :
Report:
( 7 infos, 2 warnings, 0 errors )
2016-06-02 04:01:40(info): Starting full image backup...
2016-06-02 04:09:10(info): Basing image backup on last incremental or full image backup
2016-06-02 04:09:23(info): Creating writable snapshot of previous image backup...
2016-06-02 05:55:13(warning): Received unknown block number: -811579524519612219 (max: 15638528). Retrying...
2016-06-02 05:55:19(warning): Checksum for image block wrong. Retrying...
2016-06-02 07:23:33(info): Transferred 6.46714 GB - Average speed: 4.77074 MBit/s
2016-06-02 07:23:33(info): (Before compression: 5.63579 GB ratio: 0.87145)
2016-06-02 07:23:33(info): Time taken for backing up client SV203: 3h 21m 53s
2016-06-02 07:23:33(info): Backup succeededRegards,
@TomTomGo
That is probably the network corruption which crashed the server previously. Now it copes with it. Do not know what is going n with your compression ratio… Perhaps you have encrypted or already compressed changes?
@Manley23
Are you backing up to a btrfs raw file? If yes that problem may be fixed with 2.0.25.
@uroni
My UrBackup server program is on Windows Server 2008 R2. And my UrBackup client programs are all installed on Windows Server 2008 R2, also.