[Bacula-users] "column "volabytes" does not exist"

2015-10-15 Thread Doug Sampson
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,

Re: [Bacula-users] "column "volabytes" does not exist"

2015-10-15 Thread Phil Stracchino
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

Re: [Bacula-users] "column "volabytes" does not exist"

2015-10-15 Thread Doug Sampson
> > 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

[Bacula-users] Redhat's RHEL bacula rpms/installation

2015-10-15 Thread Thing
Hi, Has anyone used RH's RHEL packages? So I have yum installed then I am following digitalocean's webpage. https://www.digitalocean.com/community/tutorials/how-to-install-bacula-server-on-centos-7

Re: [Bacula-users] "column "volabytes" does not exist"

2015-10-15 Thread Dimitri Maziuk
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

[Bacula-users] Bconsole format dates

2015-10-15 Thread Wanderlei Huttel
I'm running bacula 7.2.0 in Debian 8.1 with portuguese brazilian (pt_BR) UTF8 encode; Per example bconsole "status dir" list a month as short month (3 digits) and "status schedule days=1" list month and week day short (3 digits) Is there a way to compile bacula to show dates as en_US by

Re: [Bacula-users] "column "volabytes" does not exist"

2015-10-15 Thread Phil Stracchino
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

Re: [Bacula-users] Bconsole format dates

2015-10-15 Thread Jari Fredriksson
On 16.10.2015 1:45, Wanderlei Huttel wrote: > I'm running bacula 7.2.0 in Debian 8.1 with portuguese brazilian (pt_BR) UTF8 encode; > > Per example bconsole "status dir" list a month as short month (3 digits) and "status schedule days=1" list month and week day short (3 digits) > > Is

Re: [Bacula-users] "column "volabytes" does not exist"

2015-10-15 Thread Doug Sampson
> > 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

Re: [Bacula-users] "column "volabytes" does not exist"

2015-10-15 Thread Doug Sampson
> >> 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

Re: [Bacula-users] "column "volabytes" does not exist"

2015-10-15 Thread Phil Stracchino
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,

Re: [Bacula-users] "column "volabytes" does not exist"

2015-10-15 Thread Doug Sampson
> >> 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: >

Re: [Bacula-users] "column "volabytes" does not exist"

2015-10-15 Thread Phil Stracchino
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