No prompt for backup folder on install/config

Server
#1

I’m re-installing urbackupsrv 2.4.15.0-1ubuntu1~focal amd64 on an Ubuntu 20.04 desktop because the original install was messed up, and since it was a new install I didn’t feel I needed the one backup that was run.

I ran sudo apt-get purge urbackup-server because I need to change the settings, then made sure there was nothing left behind in passwd, shadow, group, /var/log, /etc, /etc/urbackup and /etc/init.d. Then ran sudo apt-get install urbackup-server -y from a gnome-terminal again.
But when it finished installing and should have prompted me for the backup location, instead it just exited back to the terminal.
Running ps -ef | grep backup I see the process /usr/bin/urbackupsrv run --config /etc/default/urbackupsrv --daemon --pidfile /var/run/urbackupsrv.pid run by the urbackup user that was just created. But it is disconnected from my terminal.

Can someone suggest my next move? Manually edit the config file and /etc/urbackup/backupfolder, chown urbackup:urbackup the folders and see if I can get the server process to start with servicectl start urbackupsrv?

At this point, nothing is set up.

Floundering

#2

I killed the config job, manually edited /etc/default/urbackupsrv to set DAEMON_TMPDIR and SQLITE_TMDIR to folders on different partitions that have lots of space, edited /etc/urbackup/backupfolder to where the backups are to go, changed ownership of these two files to urbackup, and rebooted.

When I logged back in and checked running processes, the urbackupsrv run --config job was running again.

I would really appreciate some suggestions without havint to completely reinstall Ubuntu which I have spent a lot of time setting up the way I want. What do I need to do to complete the configuration task and move forward?

Plimster

#3

Here is the /var/log/urbackup.log file which has important information:

2022-02-20 17:01:48: WARNING: Upgrading…
2022-02-20 17:01:48: WARNING: Upgrading database to version 8
2022-02-20 17:01:48: WARNING: Upgrading database to version 9
2022-02-20 17:01:48: WARNING: Upgrading database to version 10
2022-02-20 17:01:48: WARNING: Upgrading database to version 11
2022-02-20 17:01:48: WARNING: Upgrading database to version 12
2022-02-20 17:01:49: WARNING: Upgrading database to version 13
2022-02-20 17:01:49: WARNING: Upgrading database to version 14
2022-02-20 17:01:49: WARNING: Upgrading database to version 15
2022-02-20 17:01:49: WARNING: Upgrading database to version 16
2022-02-20 17:01:49: WARNING: Upgrading database to version 17
2022-02-20 17:01:49: WARNING: Upgrading database to version 18
2022-02-20 17:01:49: WARNING: Upgrading database to version 19
2022-02-20 17:01:49: WARNING: Upgrading database to version 20
2022-02-20 17:01:49: WARNING: Upgrading database to version 21
2022-02-20 17:01:49: WARNING: Upgrading database to version 22
2022-02-20 17:01:49: WARNING: Upgrading database to version 23
2022-02-20 17:01:49: WARNING: Upgrading database to version 24
2022-02-20 17:01:49: WARNING: Upgrading database to version 25
2022-02-20 17:01:49: WARNING: Upgrading database to version 26
2022-02-20 17:01:49: WARNING: Upgrading database to version 27
2022-02-20 17:01:49: WARNING: Upgrading database to version 28
2022-02-20 17:01:49: WARNING: Upgrading database to version 29
2022-02-20 17:01:49: WARNING: Upgrading database to version 30
2022-02-20 17:01:49: WARNING: Upgrading database to version 31
2022-02-20 17:01:49: WARNING: Upgrading database to version 32
2022-02-20 17:01:49: WARNING: Upgrading database to version 33
2022-02-20 17:01:49: WARNING: Upgrading database to version 34
2022-02-20 17:01:49: WARNING: Upgrading database to version 35
2022-02-20 17:01:49: WARNING: Upgrading database to version 36
2022-02-20 17:01:49: WARNING: Upgrading database to version 37
2022-02-20 17:01:49: WARNING: Upgrading database to version 38
2022-02-20 17:01:49: WARNING: Upgrading database to version 39
2022-02-20 17:01:49: WARNING: Upgrading database to version 40
2022-02-20 17:01:49: WARNING: Upgrading database to version 41
2022-02-20 17:01:49: WARNING: Upgrading database to version 42
2022-02-20 17:01:49: WARNING: Upgrading database to version 43
2022-02-20 17:01:49: WARNING: Upgrading database to version 44
2022-02-20 17:01:49: WARNING: Upgrading database to version 45
2022-02-20 17:01:49: WARNING: Upgrading database to version 46
2022-02-20 17:01:49: WARNING: Upgrading database to version 48
2022-02-20 17:01:49: WARNING: Upgrading database to version 49
2022-02-20 17:01:49: WARNING: Upgrading database to version 50
2022-02-20 17:01:49: WARNING: Upgrading database to version 51
2022-02-20 17:01:49: WARNING: Upgrading database to version 52
2022-02-20 17:01:49: WARNING: Upgrading database to version 53
2022-02-20 17:01:49: WARNING: Upgrading database to version 54
2022-02-20 17:01:49: WARNING: Upgrading database to version 55
2022-02-20 17:01:49: WARNING: Upgrading database to version 56
2022-02-20 17:01:49: WARNING: Upgrading database to version 57
2022-02-20 17:01:49: WARNING: Upgrading database to version 58
2022-02-20 17:01:49: WARNING: Upgrading database to version 59
2022-02-20 17:01:49: WARNING: Done.
2022-02-20 17:01:49: WARNING: Creating file entry index. This might take a while…
2022-02-21 06:00:45: ERROR: Sending broadcast failed!
2022-02-21 06:00:45: ERROR: Sending broadcast failed! (ipv6)
2022-02-21 06:22:48: WARNING: Shutting down (Signal 15)
2022-02-21 07:45:19: ERROR: Copy on write mode is disabled, because the filesystem does not support it anymore.

#5

Both my DAEMON_TMPDIR and SQLITE_TMPDIR are on different btrfs drives. /var and /etc are on the root drive formatted as ext3.

Plimster

#6

OK, so I updated /etc/default/urbackupsrv and specifed the 3 interfaces that I have. The server is running now and I was able to go in and set it up and add my Ubuntu desktop as a client.

I didn’t get any display of commands to run to install the client from the web interface, so I went to www.urbackup.org and got the command to install the Linux client: success!

It looks good. I will add one last comment when I have a backup overnight.