Only three of six differential backup jobs completed last night. The
Director reports:
11-Jan 04:33 minbar-dir JobId 28397: Fatal error: sql_create.c:1015
Create db Filename record INSERT INTO Filename (Name) VALUES
('gjs-1.66.2.ebuild') failed. ERR=Duplicate entry 'gjs-1.66.2.ebuild'
for key 'Name'
11-Jan 04:33 minbar-dir JobId 28397: Fatal error: catreq.c:664 attribute
create error. ERR=sql_create.c:1015 Create db Filename record INSERT
INTO Filename (Name) VALUES ('gjs-1.66.2.ebuild') failed. ERR=Duplicate
entry 'gjs-1.66.2.ebuild' for key 'Name'
11-Jan 04:34 minbar-dir JobId 28400: Fatal error: sql_create.c:1015
Create db Filename record INSERT INTO Filename (Name) VALUES
('aegisub-3.2.2_p20160518-avoid-conveying-positional-parameters-to-source-builtin.patch')
failed. ERR=Duplicate entry
'aegisub-3.2.2_p20160518-avoid-conveying-positional-parameters...' for
key 'Name'
11-Jan 04:34 minbar-dir JobId 28400: Fatal error: catreq.c:664 attribute
create error. ERR=sql_create.c:1015 Create db Filename record INSERT
INTO Filename (Name) VALUES
('aegisub-3.2.2_p20160518-avoid-conveying-positional-parameters-to-source-builtin.patch')
failed. ERR=Duplicate entry
'aegisub-3.2.2_p20160518-avoid-conveying-positional-parameters...' for
key 'Name'
And Director Status correctly shows that both of those jobs have fatal
errors. But they're still running. Despite logging fatal errors they
did not terminate.
The Director is configured to send all DB queries to the local DB node
so that Bacula will never encounter local commit conflicts. This should
not have happened unless, again, there is a race condition between
threads running different jobs.
--
Phil Stracchino
Babylon Communications
ph...@caerllewys.net
p...@co.ordinate.org
Landline: +1.603.293.8485
Mobile: +1.603.998.6958
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
