Urbackup server 2.4.9 crashed on Linux

Server
1

I was using urbackup from a while, but after the update to last release, not urbackup crashed on my Ubuntu machine.

The only logs I got when I run the command /usr/bin/urbackupsrv run -d is:

    2019-10-17 14:06:17: Starting HTTP-Server on port 55414
2019-10-17 14:06:17: HTTP: Server started up successfully!
2019-10-17 14:06:17: SQLite: recovered 5349 frames from WAL file /var/urbackup/backup_server.db-wal code: 283
2019-10-17 14:06:17: SQLite: recovered 1793 frames from WAL file /var/urbackup/backup_server_files.db-wal code: 283
2019-10-17 14:06:17: SQLite: recovered 20848 frames from WAL file /var/urbackup/backup_server_link_journal.db-wal code: 283
2019-10-17 14:06:17: SQLite: recovered 25526 frames from WAL file /var/urbackup/backup_server_links.db-wal code: 283
2019-10-17 14:06:17: SQLite: recovered 2 frames from WAL file /var/urbackup/backup_server_settings.db-wal code: 283
2019-10-17 14:06:18: SQLite: recovered 5349 frames from WAL file /var/urbackup/backup_server.db-wal code: 283
2019-10-17 14:06:18: SQLite: recovered 2 frames from WAL file /var/urbackup/backup_server_settings.db-wal code: 283
2019-10-17 14:06:18: SQLite: recovered 1793 frames from WAL file /var/urbackup/backup_server_files.db-wal code: 283
2019-10-17 14:06:18: SQLite: recovered 25526 frames from WAL file /var/urbackup/backup_server_links.db-wal code: 283
2019-10-17 14:06:18: SQLite: recovered 20848 frames from WAL file /var/urbackup/backup_server_link_journal.db-wal code: 283
2019-10-17 14:06:18: Started UrBackup...
2019-10-17 14:06:18: Removing temporary files...
2019-10-17 14:06:18: Recreating temporary folder...
2019-10-17 14:06:18: Backup destination cannot handle subvolumes and snapshots. Snapshots disabled.
2019-10-17 14:06:18: Reflink ioctl failed. errno=25
2019-10-17 14:06:22: Starting HTTP-Server on port 55414
2019-10-17 14:06:22: HTTP: Server started up successfully!
2019-10-17 14:06:22: SQLite: recovered 5349 frames from WAL file /var/urbackup/backup_server.db-wal code: 283
2019-10-17 14:06:22: SQLite: recovered 1793 frames from WAL file /var/urbackup/backup_server_files.db-wal code: 283
2019-10-17 14:06:22: SQLite: recovered 20849 frames from WAL file /var/urbackup/backup_server_link_journal.db-wal code: 283
2019-10-17 14:06:23: SQLite: recovered 25526 frames from WAL file /var/urbackup/backup_server_links.db-wal code: 283
2019-10-17 14:06:23: SQLite: recovered 2 frames from WAL file /var/urbackup/backup_server_settings.db-wal code: 283
2019-10-17 14:06:23: SQLite: recovered 5349 frames from WAL file /var/urbackup/backup_server.db-wal code: 283
2019-10-17 14:06:23: SQLite: recovered 2 frames from WAL file /var/urbackup/backup_server_settings.db-wal code: 283
2019-10-17 14:06:23: SQLite: recovered 1793 frames from WAL file /var/urbackup/backup_server_files.db-wal code: 283
2019-10-17 14:06:23: SQLite: recovered 25526 frames from WAL file /var/urbackup/backup_server_links.db-wal code: 283
2019-10-17 14:06:23: SQLite: recovered 20849 frames from WAL file /var/urbackup/backup_server_link_journal.db-wal code: 283
2019-10-17 14:06:23: Started UrBackup...
2019-10-17 14:06:23: Removing temporary files...
2019-10-17 14:06:23: Recreating temporary folder...
2019-10-17 14:06:23: Backup destination cannot handle subvolumes and snapshots. Snapshots disabled.
2019-10-17 14:06:23: Reflink ioctl failed. errno=25
(END)

If I run urbackup server with command /usr/bin/urbackupsrv run I’ve this output:

root@backup:/var/log# /usr/bin/urbackupsrv run
2019-10-17 14:12:58: Starting HTTP-Server on port 55414
2019-10-17 14:12:58: HTTP: Server started up successfully!
2019-10-17 14:12:58: SQLite: recovered 5349 frames from WAL file /var/urbackup/backup_server.db-wal code: 283
2019-10-17 14:12:58: SQLite: recovered 1793 frames from WAL file /var/urbackup/backup_server_files.db-wal code: 283
2019-10-17 14:12:58: SQLite: recovered 20851 frames from WAL file /var/urbackup/backup_server_link_journal.db-wal code: 283
2019-10-17 14:12:58: SQLite: recovered 25526 frames from WAL file /var/urbackup/backup_server_links.db-wal code: 283
2019-10-17 14:12:58: SQLite: recovered 2 frames from WAL file /var/urbackup/backup_server_settings.db-wal code: 283
2019-10-17 14:12:58: SQLite: recovered 5349 frames from WAL file /var/urbackup/backup_server.db-wal code: 283
2019-10-17 14:12:58: SQLite: recovered 2 frames from WAL file /var/urbackup/backup_server_settings.db-wal code: 283
2019-10-17 14:12:58: SQLite: recovered 1793 frames from WAL file /var/urbackup/backup_server_files.db-wal code: 283
2019-10-17 14:12:59: SQLite: recovered 25526 frames from WAL file /var/urbackup/backup_server_links.db-wal code: 283
2019-10-17 14:12:59: SQLite: recovered 20851 frames from WAL file /var/urbackup/backup_server_link_journal.db-wal code: 283
2019-10-17 14:12:59: Started UrBackup...
2019-10-17 14:12:59: Removing temporary files...
2019-10-17 14:12:59: Recreating temporary folder...
MOUNT TEST OK
Testing for btrfs...
ERROR: not a btrfs filesystem: /home/BACKUP/urbackup/testA54hj5luZtlorr494
TEST FAILED: Creating test btrfs subvolume failed
Testing for zfs...
TEST FAILED: Dataset is not set via /etc/urbackup/dataset
2019-10-17 14:12:59: Backup destination cannot handle subvolumes and snapshots. Snapshots disabled.
2019-10-17 14:12:59: Reflink ioctl failed. errno=25
Segmentation fault (core dumped)

As you see there is a segmentation fault.

Any idea how to fix the problem?

Thanks

2

Could you run it in gdb like decribed here: https://urbackup.atlassian.net/wiki/spaces/US/pages/8323075/Debugging+with+gdb+on+Linux ?

5

Here you go:

    [New Thread 0x742c91cfc700 (LWP 13440)]
2019-10-17 16:44:32: Started UrBackup...
[New Thread 0x742c91431700 (LWP 13441)]
2019-10-17 16:44:32: Removing temporary files...
2019-10-17 16:44:32: Recreating temporary folder...
MOUNT TEST OK
2019-10-17 16:44:32: Testing if backup destination can handle subvolumes and snapshots...
Testing for btrfs...
ERROR: not a btrfs filesystem: /home/BACKUP/urbackup/testA54hj5luZtlorr494
TEST FAILED: Creating test btrfs subvolume failed
Testing for zfs...
TEST FAILED: Dataset is not set via /etc/urbackup/dataset
2019-10-17 16:44:32: Backup destination cannot handle subvolumes and snapshots. Snapshots disabled.
2019-10-17 16:44:32: Testing if backup destination can handle filesystem transactions...
2019-10-17 16:44:32: Testing for hardlinks in backup destination...
2019-10-17 16:44:32: Could create hardlink at backup destination. Hardlinks enabled.
2019-10-17 16:44:32: Testing for reflinks in backup destination...
2019-10-17 16:44:32: Reflink ioctl failed. errno=25
2019-10-17 16:44:32: Could not create reflink at backup destination. Reflinks disabled. Inappropriate ioctl for device (code: 25)

Thread 5 "urbackupsrv" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x742c91431700 (LWP 13441)]
0x000000000056c6b8 in ?? ()
(gdb) bt
#0  0x000000000056c6b8 in ?? ()
#1  0x000000000056eeea in ?? ()
#2  0x00000000005cb4f1 in ?? ()
#3  0x000000000045b0fa in ?? ()
#4  0x0000742c987826ba in start_thread (arg=0x742c91431700) at pthread_create.c:333
#5  0x0000742c984b841d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
(gdb)
6

Should I downgrade urbackup to the previous version? Is there a safe way to do that?

Thanks

7

I have here a similar problem after upgrade to version 2.4.9: on my ubuntu 16.04 32bit server urbackupsrv starts in daemon mode (and is active) but no connection to :55414 is available.

If I stop the service (service urbackupsrv stop) and run urbackupsrv run -v debug I get:

: Starting HTTP-Server on port 55414
: Server started up successfully!
Speicherzugriffsfehler (Speicherabzug geschrieben)

Speicherzugriffsfehler = segmentation fault

In my dmesg-messages I get:

urbackupsrv[5805] general protection ip:b751bc8a sp:bf80b81c error:0 in libcrypto++.so.9.0.0[b7289000+36f000]

I installed urbackup-server from the urbackup ubuntu-repos.

8

Glad to know someone has the same problem. Still not sure if we have to wait or downgrade…

9

See here https://urbackup.atlassian.net/wiki/spaces/US/pages/8323075/Debugging+with+gdb+on+Linux on what information would be helpful to fix this issue.

@drenda81 stack trace unfortunately does not contain debug symbols, so it is of limited use.

10

I did exactly what the guide suggests and the result is that.

What do you suggest to do to get more debug info?

Thanks

11

You’d have to compile it yourself, or get the debug symbols. E.g. for the amd64 debian package they are there: https://hndl.urbackup.org/Server/2.4.10/urbackup-server-dbg_2.4.10_amd64.deb (they need to match the installed package!)

12

I’m using:

ii  urbackup-server                  2.4.10.0-1ubuntu1~xenial                   amd64        Server for backing up clients

via PPA repository. Can I use the debug debian version as well?

BTW: I gave a try to the 2.4.10 version and the segmentation fault is still present.

Thanks

13

No, it doesn’t match. And the ppa doesn’t seem to publish any debug symbols.

14

Ok, so what should I do? Can I do a downgrande in a safe way? Thanks

15

Any hint about this topic? Thanks