>>>>> On Thu, 16 Apr 2009 20:10:47 -0400, Dan Langille said: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Per olof Ljungmark wrote: > > Dan Langille wrote: > >> Per olof Ljungmark wrote: > >>> Dan Langille wrote: > >>>> Folks: > >>>> > >>>> sysutils/bacula-server-devel has been updated to 2.5.42.b2 (which is > >>>> pretty close to 3.0). > >>>> > >>>> http://www.freshports.org/sysutils/bacula-server-devel/ > >>>> > >>>> I'd appreciate some feedback on this upgrade. It's pretty close to > >>>> 3.x, > >>>> which is what I'll be working on next. > >>> After moving from 2.4.3 to 3.0.0 I had to grant user "bacula" > >>> priveligies to the "jobhisto" table. > >> > >>> The error was: > >> > >>> 16-Apr 23:55 candyman-dir JobId 19879: shell command: run BeforeJob > >>> "/usr/local/share/bacula/make_catalog_backup bacula bacula" > >>> 16-Apr 23:55 candyman-dir JobId 19879: BeforeJob: pg_dump: SQL command > >>> failed > >>> 16-Apr 23:55 candyman-dir JobId 19879: BeforeJob: pg_dump: Error message > >>> from server: ERROR: permission denied for relation jobhisto > >>> 16-Apr 23:55 candyman-dir JobId 19879: BeforeJob: pg_dump: The command > >>> was: LOCK TABLE public.jobhisto IN ACCESS SHARE MODE > >>> 16-Apr 23:55 candyman-dir JobId 19879: Error: Runscript: BeforeJob > >>> returned non-zero status=1. ERR=Child exited with code 1 > >>> 16-Apr 23:55 candyman-dir JobId 19879: Error: Bacula candyman-dir 3.0.0 > >>> (06Apr09): 16-Apr-2009 23:55:02 > >> > >>> I can't say if this is specific to FreeBSD (7-STABLE), Posgres (8.3.7) > >>> or my own fault but I thought I should mention it anyhow. > >> > >> What is the output of this command from with psql. I suspect the tables > >> and/or database are not owned by bacula. > >> > >> \dt > >> > > > > The database and all tables except "jobhisto" were owned by bacula and > > the problem was easily fixed by adding the priveligies. > > Who was/is the owner of this table? > > > I had no such problems before the upgrade so I just assumed that this > > table was added by the upgrade script but without adding the proper > > rights. I ran the script as pgsql but perhaps I should have done it as > > "bacula". > > Ahh, yes, I think so. I bet the owner is postgres.
Indeed, the regular installation procedure makes tables which are owned by postgres and uses the grant_bacula_privileges script to give permissions to the bacula user. __Martin ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users