Freenas jail Segmentation fault

Server
1

Hi All,
I have this server running for moth and working great suddenly i had no access to the urbackup web service. I decided to restart the jail and since I’m unable to start the server.

How can troubleshoot this further?
while starting the server via urbackupsrv run -v debug the maximum i can see is a few TEST FAILED and Error no permission to access a backup folder with specific date that does not exists but that doesn’t seems to be the issue. the last line is Segmentation fault.
freenas 9.10.2-u2
urbackup 2.1.19

Noticed another error LMDB: Failed to read (MDB_CURSOR_FULL: Internal error - cursor stack limit reached)

Thanks…

2

Please post the full error message.

3

Here it is,
root@urbackup:/ # urbackupsrv run --loglevel debug
2017-06-06 09:58:34: Starting HTTP-Server on port 55414
2017-06-06 09:58:34: HTTP: Server started up successfully!
2017-06-06 09:58:34: SQLite: recovered 32 frames from WAL file /usr/local/var/urbackup/backup_server_link_journal.db-wal code: 283
2017-06-06 09:58:34: SQLite: recovered 1 frames from WAL file /usr/local/var/urbackup/backup_server_settings.db-wal code: 283
2017-06-06 09:58:34: SQLite: recovered 1 frames from WAL file /usr/local/var/urbackup/backup_server_settings.db-wal code: 283
2017-06-06 09:58:34: SQLite: recovered 32 frames from WAL file /usr/local/var/urbackup/backup_server_link_journal.db-wal code: 283
2017-06-06 09:58:34: ERROR: LMDB: Failed to open LMDB database file (Permission denied)
2017-06-06 09:58:34: ERROR: LMDB error creating env
2017-06-06 09:58:34: Started UrBackup…
2017-06-06 09:58:34: Removing temporary files…
2017-06-06 09:58:34: ERROR: No permission to access “/data/urbackup_tmp_files”
2017-06-06 09:58:34: Recreating temporary folder…
2017-06-06 09:58:34: UrBackup Server start up complete.
2017-06-06 09:58:34: Server started up successfully!
2017-06-06 09:58:34: Looking for old Sessions… 0 sessions
2017-06-06 09:58:35: Downloading version file…
2017-06-06 09:58:39: Testing if backup destination can handle subvolumes and snapshots…
Testing for btrfs…
TEST FAILED: Creating test btrfs subvolume failed
Testing for zfs…
TEST FAILED: Dataset is not set via /etc/urbackup/dataset
2017-06-06 09:58:39: Backup destination cannot handle subvolumes and snapshots. Snapshots disabled.
2017-06-06 09:58:39: Testing if backup destination can handle filesystem transactions…
TEST FAILED: Please compile with mountvhd (./configure --with-mountvhd)
2017-06-06 09:58:39: Image mounting disabled: TEST FAILED: Please compile with mountvhd (./configure --with-mountvhd)
2017-06-06 09:58:39: WARNING: File backup [id=28815, path=170601-1302, backuptime=2017-06-01 13:09:39, clientid=74, client=XXX-cal04] is incomplete. Deleting it.
2017-06-06 09:58:39: WARNING: File backup [id=28993, path=170604-0718, backuptime=2017-06-04 07:20:24, clientid=76, client=XXX-cal02] is incomplete. Deleting it.
2017-06-06 09:58:39: WARNING: File backup [id=29055, path=170604-1407, backuptime=2017-06-04 14:10:37, clientid=60, client=XXX-R210] is incomplete. Deleting it.
2017-06-06 09:58:39: WARNING: Deleting file backup [id=28815, path=170601-1302, backuptime=2017-06-01 13:09:39, clientid=74, client=gpu-XXX04]…
2017-06-06 09:58:39: ERROR: No permission to access “/data/XXX-cal04/170601-1302”
2017-06-06 09:58:39: WARNING: Warning: Directory doesn’t exist: “/data/YYY-cal04/170601-1302”
Segmentation fault
root@urbackup:/ #

4

It probably doesn’t have permissions to write to /usr/local/var/urbackup/fileindex

5

Thank you,
I’m a little confused in freebsd the server should run with user root or urbackup?
Some of my files are with urbackup as owner and some as root. Probably because I migrated the data from linux box.

If the user should be root I will chmod it all.

Thanks

6

I have managed to fix this,
I don’t recall exactly what I have run but it was something that took a week,
Probably upgrade database.

Thank You…

7

I have a similar problem will not understand what was going on

[root@comp-fx-8320e-eight-core-033988 bin]# urbackupsrv run --loglevel debug
2017-07-19 17:40:33: Starting HTTP-Server on port 55414
2017-07-19 17:40:33: HTTP: Server started up successfully!
2017-07-19 17:40:33: SQLite: recovered 6 frames from WAL file /usr/local/var/urbackup/backup_server.db-wal code: 283
2017-07-19 17:40:33: SQLite: recovered 12 frames from WAL file /usr/local/var/urbackup/backup_server_link_journal.db-wal code: 283
2017-07-19 17:40:33: SQLite: recovered 25 frames from WAL file /usr/local/var/urbackup/backup_server_settings.db-wal code: 283
2017-07-19 17:40:33: SQLite: recovered 6 frames from WAL file /usr/local/var/urbackup/backup_server.db-wal code: 283
2017-07-19 17:40:33: SQLite: recovered 25 frames from WAL file /usr/local/var/urbackup/backup_server_settings.db-wal code: 283
2017-07-19 17:40:33: SQLite: recovered 12 frames from WAL file /usr/local/var/urbackup/backup_server_link_journal.db-wal code: 283
2017-07-19 17:40:33: Started UrBackup…
2017-07-19 17:40:33: Removing temporary files…
2017-07-19 17:40:33: ERROR: No permission to access “/home/fabryan/backups/urbackup_tmp_files”
2017-07-19 17:40:33: Recreating temporary folder…
2017-07-19 17:40:34: UrBackup Server start up complete.
2017-07-19 17:40:34: Server started up successfully!
2017-07-19 17:40:34: Looking for old Sessions… 0 sessions
2017-07-19 17:40:34: Downloading version file…
2017-07-19 17:40:35: Downloading version file…
2017-07-19 17:40:35: Downloading version file…
2017-07-19 17:40:35: Downloading server version info…
2017-07-19 17:40:35: Downloading dataplan database…
2017-07-19 17:40:38: Testing if backup destination can handle subvolumes and snapshots…
Backupfolder not set
2017-07-19 17:40:38: Backup destination cannot handle subvolumes and snapshots. Snapshots disabled.
2017-07-19 17:40:38: Testing if backup destination can handle filesystem transactions…
Backupfolder not set
2017-07-19 17:40:38: Image mounting disabled: Backupfolder not set
2017-07-19 17:40:38: WARNING: Backupfolder “/home/fabryan/backups” does not exist. Not running recovery.
2017-07-19 17:40:38: Binding to interface eth0 for broadcasting…
2017-07-19 17:40:38: Broadcasting on interface IP 192.168.1.33