root@pisces:/usr/local/share/bacula# ./update_postgresql_tables
Looks like you are running it as root. Do it as the bacula user/role, normally
called bacula
su - bacula
/usr/local/share/bacula/ update_postgresql_tables
Or use the -c su option if your security doesn't allow above.
Dave
This em
> On Thu, Oct 15, 2015 at 05:50:11PM -0400, Phil Stracchino wrote:
> > On 10/15/15 14:02, Doug Sampson wrote:
> > > I've revised the version to 14 and executed the script giving me this
> error message:
> > >
> > >
> > > root@pisces:/usr/local/share/bacula# ./update_postgresql_tables
> > >
>
> Jus
On Thu, Oct 15, 2015 at 05:50:11PM -0400, Phil Stracchino wrote:
> On 10/15/15 14:02, Doug Sampson wrote:
> > I've revised the version to 14 and executed the script giving me this error
> > message:
> >
> >
> > root@pisces:/usr/local/share/bacula# ./update_postgresql_tables
> >
Just to be cle
On 10/15/2015 05:54 PM, Doug Sampson wrote:
...
> psql::2: ERROR: duplicate key value violates unique constraint
> "status_pkey"
> DETAIL: Key (jobstatus)=(I) already exists.
...
> psql::23: NOTICE: CREATE TABLE will create implicit sequence
> "snapshot_snapshotid_seq1" for serial column "snap
> > I've revised the version to 14 and executed the script giving me this
> error message:
> >
> >
> > root@pisces:/usr/local/share/bacula# ./update_postgresql_tables
> >
> > This script will update a Bacula MySQL database from version 12-14 to 15
> >
> > Depending on the current version of your ca
On 10/15/15 14:02, Doug Sampson wrote:
> I've revised the version to 14 and executed the script giving me this error
> message:
>
>
> root@pisces:/usr/local/share/bacula# ./update_postgresql_tables
>
> This script will update a Bacula MySQL database from version 12-14 to 15
>
> Depending on
> >> This query should do it, assuming your Bacula schema is named 'bacula'
> >> and you haven't skipped any intervening DB versions before the current
> 15:
> >>
> >> update bacula.Version set VersionId = 14;
> >
> > Forgive my ignorance but at this point, I am unsure which choice to
> choose:
> >
On 10/15/15 13:21, Doug Sampson wrote:
You could manually revert the version table in the DB to the previous
version, run the update script again, and record the errors this time.
>>>
>>> How does one accomplish this? Is there a secret trick to revise the
>> version?
>>
>> This query shou
> >> You could manually revert the version table in the DB to the previous
> >> version, run the update script again, and record the errors this time.
> >
> > How does one accomplish this? Is there a secret trick to revise the
> version?
>
> This query should do it, assuming your Bacula schema is
On 10/15/15 13:04, Doug Sampson wrote:
>>
>> You could manually revert the version table in the DB to the previous
>> version, run the update script again, and record the errors this time.
>
> How does one accomplish this? Is there a secret trick to revise the version?
This query should do it, as
>
> You could manually revert the version table in the DB to the previous
> version, run the update script again, and record the errors this time.
How does one accomplish this? Is there a secret trick to revise the version?
~Doug
-
On 10/15/15 10:13, Doug Sampson wrote:
> I remember seeing a few errors while executing
> /usr/local/share/bacula/update_bacula_tables but I don't have the output.
> When I tried to rerun it, it stated that the table have been updated to
> version 15 so it didn't run.
>
> What are my options a
Hello-
Yesterday I upgraded Bacula from 7.0.5 to 7.2 running on a FreeBSD 10.1 system.
It appears that the upgrade didn't go well. All of my jobs failed overnight.
This is a sample of a failed job:
*mes
15-Oct 06:58 pisces-dir JobId 16576: Start Backup JobId 16576,
Job=mailfilter.2015-10-15_06
13 matches
Mail list logo
