On 9 Jan 2007 at 17:23, Dan Langille wrote:

> On 9 Jan 2007 at 14:08, Doug Sampson wrote:
> 
> > > On 9 Jan 2007 at 13:52, Doug Sampson wrote:
> > > 
> > > > I'm getting an PGSQL error each time I attempt to dump 
> > > bacula to a SQL file
> > > > during catalog backup as follows:
> > > > 
> > > > [EMAIL PROTECTED]:/usr/local/share/bacula#
> > > > /usr/local/share/bacula/make_catalog_backup1 bacula bacula
> > > > pg_dump: attempt to lock table "location" failed: ERROR:  
> > > permission denied
> > > > for relation location
> > > 
> > > Sounds like insufficient permisison.  Get into psql and issue this 
> > > command please:
> > > 
> > > \dp location
> > > 
> > > It will show us the permissions for that table.  My bet: bacula has 
> > > insufficient rights.
> > > 
> > > Please also show \dp files
> > 
> > A friend told me to use PGAdmin on my Windows machine to fix the permission
> > errors. I found that three tables were missing permissions for bacula-
> > location, locationlog, & log. I added privileges for bacula (as well as
> > root) to these 3 tables. The 'make_catalog_backup1' file now executes
> > properly.
> > 
> > Did the file grant_bacula_privileges overlook these three tables? Did I not
> > properly update privileges in the first place? I stopped PGSQL before
> > portupgrading Bacula to 2.0. I then ran ./update_bacula_tables. Edited the
> > config files to remove any references to 'AcceptAnyVolume=Yes' before
> > starting Bacula.
> 
> These tables were introduced in Bacula 2.0 and during an upgrade, 
> will be created by src/cats/update_postgresql_tables.in.  I will test 
> and patch the code if I can replicate your problem.  I'll also apply 
> the patch to the FreeBSD port.

I know you've fixed your problem, and for the record, I've been able 
to duplicate the conditions, but not the error.  This output will be 
scrambled, but it will show the lack of permission on various tables.

 public | jobmedia_jobmediaid_seq   | sequence | 
{bacula=rwU/bacula,dan=rwU/bacula}
 public | location                  | table    |
 public | location_locationid_seq   | sequence |
 public | locationlog               | table    |
 public | locationlog_loclogid_seq  | sequence |
 public | log                       | table    |
 public | log_logid_seq             | sequence |
 public | media                     | table    | 
{bacula=arwdxt/bacula,dan=arwdxt/bacula}

But the dump was OK:

$ pg_dump -U bacula -d bacula > ~/dumped_bacula.sql

No errors.  But I will commit the mentioned changes now.

-- 
Dan Langille : Software Developer looking for work
my resume: http://www.freebsddiary.org/dan_langille.php
PGCon - The PostgreSQL Conference - http://www.pgcon.org/



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to