Can't login to webinterface anymore


#1

After the 2.3.8 update I’m not able to log into the interface anymore. I can connect to the interface site, but than the interface won’t come up presenting the login. On the left I do see the logo and on the right te blue circle is running and that’s it.

I am running a Linux 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13) x86_64 GNU/Linux with Urbackup latest version (clients are also up-to-date), nothing more.

Going to the default log’s doesn’t reveal anything.

If I check the server status than the server is running. If i check nginx than this is running too. If I restart nginx the interface is again available for a couple of hours. Than this is all starting again.

Has some one any idea where to look?

Thanx,

Chris


#2

Has no one any idea where to look? I tried to find something but no luck. Re-installing the server is no option for me as a have bad experiences with my client to re-engage them. Would be nice if someone has any idea.

Many thanks in advance.


#3

Ok, found some more information in the logging. It seems that I have to re-install the servers as the SQLite DB might be corrupt. The logging states:

2019-06-16 14:35:22: HTTP: Server started up successfully!

2019-06-16 14:35:22: SQLite: recovered 11652 frames from WAL file /var/urbackup/backup_server.db-wal code: 283

2019-06-16 14:35:24: SQLite: recovered 83607 frames from WAL file /var/urbackup/backup_server_files.db-wal code: 283

2019-06-16 14:35:24: SQLite: recovered 9547 frames from WAL file /var/urbackup/backup_server_link_journal.db-wal code: 283

2019-06-16 14:35:25: SQLite: recovered 48839 frames from WAL file /var/urbackup/backup_server_links.db-wal code: 283

2019-06-16 14:35:25: SQLite: recovered 36 frames from WAL file /var/urbackup/backup_server_settings.db-wal code: 283

2019-06-16 14:35:25: SQLite: recovered 11652 frames from WAL file /var/urbackup/backup_server.db-wal code: 283

2019-06-16 14:35:25: SQLite: recovered 36 frames from WAL file /var/urbackup/backup_server_settings.db-wal code: 283

2019-06-16 14:35:25: SQLite: recovered 83607 frames from WAL file /var/urbackup/backup_server_files.db-wal code: 283

2019-06-16 14:35:26: SQLite: recovered 48839 frames from WAL file /var/urbackup/backup_server_links.db-wal code: 283

2019-06-16 14:35:26: SQLite: recovered 9547 frames from WAL file /var/urbackup/backup_server_link_journal.db-wal code: 283

WARNING: SQLite: database corruption at line errorcode: 11

If someone has any idea how to save this I’m open to suggestions otherwise I have to re-install everything and that is the last I want.

Many thanks for any suggestions you might have,

Cheers,

Chris


#4

Restore urbackup dbs from backup. If nightly backup was enabled (default) e.g. from /media/BACKUP/urbackup (urbackup sub-folder on backup storage).

If that doesn’t help try running urbackupsrv repair-database.


#5

Of course! :flushed: Why couldn’t I think of this… you’re right!

Many thanks for your hint. I just ran the command and it seems that the DB is fixed now. Up to now no outages on the web-interface.

Many thanks for your support! :grinning:


#6

Ok, ran into some trouble again after everything went fine, I’ve again an issue. So ran the urbackupsrv repair-database and got this message:

ERROR: SQL: UNIQUE constraint failed: files.id Stmt: [

INSERT INTO “files” VALUES(0,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL)]

ERROR: Importing database failed

Ran the command again and it seems that it’s working again. Not sure why I had this error again, but I will keep an eye on this for a couple of day’s and report back on this topic.

Again many thanks for helping me.

Cheers,

Chris


#7

It also doesn’t (usually) corrupt itself. So I’d check for hardware issues (db storage device and/or RAM)


#8

Sure, totally agree, but it started after the last update. Probably something went wrong there. I just moved to new hardware and already checked this. RAM’s ok, Disks are ok too… not really a hardware issue.

Do you know if I re-install de server if all clients will come up again automatically or do I have to adapt the settings of all clients again?

Many thanks in advance again for your support.

Cheers,

Chris