Bareos Bug Tracker
Bareos Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000977bareos-core[All Projects] storage daemonpublic2018-06-30 12:102018-07-03 02:30
Reporterstevec 
Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
StatusnewResolutionopen 
PlatformLinuxOSUbuntuOS Version16.04
Product Version17.2.6 
Target VersionFixed in Version 
Summary0000977: Authorization key rejected by Storage Daemon upon upgrade from 16.2.6 to 17.2.6
DescriptionWas running 16.2.6 under ubuntu 16.04.4 self-contained (director; storage daemon and file daemon all on same system) for several months. Upgraded to 17.2.6; upgraded database format (sqlite3). No changes to configuration files or password keys.

When running the first batch of incremental backups usually one of them will run and write to tape. all others fail with "Fatal error: Authorization key rejected by Storage daemon ."

All backups use the same storage device; The one that seems to work is the first backup.
Steps To Reproducerun any backup.
Additional InformationOnly item that comes to mind as a difference between the working and non working backup under 17.2.6 is the length of time to do the backups. the one that works is the shortest length (minutes) backup the others take much longer. still they were working under 16.2.6.
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action
Attached Fileslog file icon bareos-17.2.6.log [^] (10,373 bytes) 2018-06-30 12:10
log file icon bareos-17.2.6-02.log [^] (25,603 bytes) 2018-07-01 23:08
log file icon config.log [^] (510,658 bytes) 2018-07-01 23:15
? file icon config.out [^] (3,506 bytes) 2018-07-01 23:16

- Relationships

-  Notes
(0003058)
stevec (reporter)
2018-06-30 12:13

If there are other debug items that I can try to help pinpoint this please let me know.
(0003059)
stevec (reporter)
2018-07-01 23:07

since I am still using monolithic config files I moved out the bareos-dir.d; bareos-fd.d and bareos-sd.d directories so as to force only reading the bareos-dir.conf; bareos-sd.conf and bareos-fd.conf files. This did not have any real effect (besides just removing the possibility the new auto genned files from 17.2.6 comming into play). From the log (attached) from the run 0000002 (bareos-17.2.6-02.log) you can see that more than one backup completed but got errors in authentication to the SD and got the errors:

01-Jul 11:55 loki-fd JobId 11413: Fatal error: Failed to authenticate Storage daemon.
01-Jul 11:55 loki-dir JobId 11414: Fatal error: Bad response to Storage command: wanted 2000 OK storage
, got 2902 Bad storage
(0003060)
stevec (reporter)
2018-07-03 02:30

It appears that the name lookup has changed between 16.2.x and 17.2.x. The error:

01-Jul 11:55 loki-fd JobId 11413: Fatal error: Failed to authenticate Storage daemon.
01-Jul 11:55 loki-dir JobId 11414: Fatal error: Bad response to Storage command: wanted 2000 OK storage
, got 2902 Bad storage


Can be avoided by coding the client & director (in my system; loki-dir; loki-fd; loki-sd; loki-mon) in /etc/hosts. This has not been needed from 12.x through 16.2 code but now seems a requirement in 17.2. going back to 16.2.6 I can remove the entries in /etc/host and it works without the error above.


Second item on 17.2.6; even with coding the entries in /etc/hosts to get past the error above I am seeing at LEAST a 12x decrease in speed for spooling data (probably much longer as had to cancel since they would never complete in a day). For example, incrementals on 16.2.6 & 16.2.7 take about 2 hours. Swapping over to the 17.2.6 code this has taken more than 16 hours and I barely see the spooling starting. bareos-dir is taking 100% cpu the entire time. wonder if this may be related to the database changes between 16.2 and 17.2 in relation to sqlite3 databases?

Falling back to 16.2.7 I'm back to a normal spooling times.

- Issue History
Date Modified Username Field Change
2018-06-30 12:10 stevec New Issue
2018-06-30 12:10 stevec File Added: bareos-17.2.6.log
2018-06-30 12:13 stevec Note Added: 0003058
2018-07-01 23:07 stevec Note Added: 0003059
2018-07-01 23:08 stevec File Added: bareos-17.2.6-02.log
2018-07-01 23:15 stevec File Added: config.log
2018-07-01 23:16 stevec File Added: config.out
2018-07-03 02:30 stevec Note Added: 0003060


Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker