Re: [Bacula-users] Verify jobs and "Warning: sql_get.c:186 More than one Filename!"

2021-12-21 Thread Phil Stracchino

On 12/21/21 04:25, Mark Dixon wrote:

On Fri, 17 Dec 2021, Phil Stracchino wrote:
...

I've been running my Bacula jobs in parallel for literally decades now
and have never seen it result in a duplicate Path or Filename warning.
And they ARE only warnings.

I would not worry about it as long as it is only a warning.  You could
manually clean up the duplicates, but it is probably not worth your while.

When did you last run a dbcheck?  The dbcheck tool should clean up most
orphaned and duplicate records.


Hi Phil,

Great, I'd rummaged around the create/update table scripts in etc, but
hadn't spotted dbcheck - thanks for that. Alternatively, I might just
comment-out the warning in the source.


You really should be running dbcheck on a regular basis.  Weekly is a 
good idea.  It's also a good idea to stop the Director while dbcheck 
runs.  That is easy to automate as long as it is not constantly busy.



--
  Phil Stracchino
  Babylon Communications
  ph...@caerllewys.net
  p...@co.ordinate.org
  Landline: +1.603.293.8485
  Mobile:   +1.603.998.6958


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Verify jobs and "Warning: sql_get.c:186 More than one Filename!"

2021-12-21 Thread Mark Dixon

On Fri, 17 Dec 2021, Phil Stracchino wrote:
...

I've been running my Bacula jobs in parallel for literally decades now
and have never seen it result in a duplicate Path or Filename warning.
And they ARE only warnings.

I would not worry about it as long as it is only a warning.  You could
manually clean up the duplicates, but it is probably not worth your while.

When did you last run a dbcheck?  The dbcheck tool should clean up most
orphaned and duplicate records.


Hi Phil,

Great, I'd rummaged around the create/update table scripts in etc, but 
hadn't spotted dbcheck - thanks for that. Alternatively, I might just 
comment-out the warning in the source.


This does seem to be hit when running verify inits in parallel on multiple 
almost-identically-configured hosts at the same time. I really must update 
to a more recent version.


Cheers,

Mark


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Verify jobs and "Warning: sql_get.c:186 More than one Filename!"

2021-12-17 Thread Phil Stracchino

On 12/17/21 05:16, Mark Dixon wrote:

Hi all,

I find the verify job feature of bacula really useful to see what has
changed since the last verifyinit job, but the job output is becoming
difficult to read as it's clustered with lots and lots of messages of the
form:

17-Dec 18:28 foo-dir JobId 67663: Warning: sql_get.c:186 More than one 
Filename!: 2 for file: AnySimpleTypeDatatypeValidator.hpp

And:

17-Dec 18:28 foo-dir JobId 67663: Warning: sql_get.c:236 More than one Path!: 2 
for path: /usr/include/xercesc/validators/common/


Looking at the database, the messages are absolutely right:


select * from Filename where Name = "AnySimpleTypeDatatypeValidator.hpp";

+++
| FilenameId | Name   |
+++
|6421754 | AnySimpleTypeDatatypeValidator.hpp |
|6421755 | AnySimpleTypeDatatypeValidator.hpp |
+++
2 rows in set (0.00 sec)



select * from Path where Path = "/usr/include/xercesc/validators/common/";

+-+-+
| PathId  | Path|
+-+-+
| 2518839 | /usr/include/xercesc/validators/common/ |
| 2518840 | /usr/include/xercesc/validators/common/ |
+-+-+
2 rows in set (0.00 sec)


I've been using the verify job feature for years (thanks!), but have only
come across this relatively recently - presumably it's a race condition
since switching to running jobs in parallel.

Firstly:

1) Should I be worried about these messages?

2) If not, is there a good way to get rid of them?!

I'm using bacula 9.6.5 + mariadb on centos7.



In current Bacula versions:
* The Filename table is gone; filenames are now in the File table
* Duplicate Filenames are fine, you can have multiple Files with the 
same name and different paths

* The Path table now has a unique index over Path


I've been running my Bacula jobs in parallel for literally decades now 
and have never seen it result in a duplicate Path or Filename warning. 
And they ARE only warnings.


I would not worry about it as long as it is only a warning.  You could 
manually clean up the duplicates, but it is probably not worth your while.


When did you last run a dbcheck?  The dbcheck tool should clean up most 
orphaned and duplicate records.




--
  Phil Stracchino
  Babylon Communications
  ph...@caerllewys.net
  p...@co.ordinate.org
  Landline: +1.603.293.8485
  Mobile:   +1.603.998.6958


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


[Bacula-users] Verify jobs and "Warning: sql_get.c:186 More than one Filename!"

2021-12-17 Thread Mark Dixon

Hi all,

I find the verify job feature of bacula really useful to see what has 
changed since the last verifyinit job, but the job output is becoming 
difficult to read as it's clustered with lots and lots of messages of the 
form:


17-Dec 18:28 foo-dir JobId 67663: Warning: sql_get.c:186 More than one 
Filename!: 2 for file: AnySimpleTypeDatatypeValidator.hpp

And:

17-Dec 18:28 foo-dir JobId 67663: Warning: sql_get.c:236 More than one Path!: 2 
for path: /usr/include/xercesc/validators/common/


Looking at the database, the messages are absolutely right:


select * from Filename where Name = "AnySimpleTypeDatatypeValidator.hpp";

+++
| FilenameId | Name   |
+++
|6421754 | AnySimpleTypeDatatypeValidator.hpp |
|6421755 | AnySimpleTypeDatatypeValidator.hpp |
+++
2 rows in set (0.00 sec)



select * from Path where Path = "/usr/include/xercesc/validators/common/";

+-+-+
| PathId  | Path|
+-+-+
| 2518839 | /usr/include/xercesc/validators/common/ |
| 2518840 | /usr/include/xercesc/validators/common/ |
+-+-+
2 rows in set (0.00 sec)


I've been using the verify job feature for years (thanks!), but have only 
come across this relatively recently - presumably it's a race condition 
since switching to running jobs in parallel.


Firstly:

1) Should I be worried about these messages?

2) If not, is there a good way to get rid of them?!

I'm using bacula 9.6.5 + mariadb on centos7.

Thanks!

Mark


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users