[Bacula-users] [RESOLVED] Bacula version 7 Server errors backing up Bacula 9 client on Debian 10

2018-05-05 Thread Matt Weatherford
Gary & others, Thank you for the reply - I was able to remove the Debian 10 bacula-common and bacula-fd packages, then manually grab the two .deb files for the bacula-7 series versions and install those. I've  prevented Debian from auto-upgrading to v9 with "apt-mark hold bacula-common bacula

[Bacula-users] automatic print of messages in bconsole

2018-05-05 Thread Thorsten Johannsen
Good morning :-) I was wondering... I'm debugging some things in bacula, running jobs manually via "run" directive in bconsole... ... is there a way to have bconsole automatically print all new messages while I'm waiting? I know this could "clutter" the bconsole if you're trying to do some

Re: [Bacula-users] Incorrect datetime value after Bionic Update

2018-05-05 Thread Sven Hartge
On 05.05.2018 21:07, Ken Mandelberg wrote: > All is working now, By the way, I wonder if the sql-mode change was > necessary, the update_mysql_table has a whole bunch of DROP DEFAULT for > the time and date columns for Mysql 5.7. All I can say is: the packages Ubuntu pulled in from Debian are not

[Bacula-users] creating RPM files from bacula source

2018-05-05 Thread Thorsten Johannsen
Hi, I'm currently trying to create a bacula RPM for CentOS from the latest source. I run configure with these options: sudo yum -y install gcc-c++ readline-devel zlib-devel lzo-devel libacl-devel mt-st mtx postfix openssl-devel mariadb-devel ./configure --with-readline=/usr/include/readlin

Re: [Bacula-users] Incorrect datetime value after Bionic Update

2018-05-05 Thread Ken Mandelberg
Phil Stracchino wrote on 05/05/2018 01:22 PM: At this point your best course of action might be to stop Bacula, drop and recreate your Bacula database, then restart Bacula. What I actually did was drop the bacula database and recreate it from /var/lib/bacula/bacula.sql. That was post upgrade, b

Re: [Bacula-users] Incorrect datetime value after Bionic Update

2018-05-05 Thread Phil Stracchino
On 05/05/18 12:55, Ken Mandelberg wrote: > Phil Stracchino wrote on 05/05/2018 12:48 PM: >> >> I would definitely restore the Bacula database from a recent DB dump >> (you *do* run regular DB dumps, right...?) and rerun the upgrade script. >> >> > Meaculpa, if its not a default I don't do it. All I

Re: [Bacula-users] Incorrect datetime value after Bionic Update

2018-05-05 Thread Ken Mandelberg
Phil Stracchino wrote on 05/05/2018 12:48 PM: I would definitely restore the Bacula database from a recent DB dump (you *do* run regular DB dumps, right...?) and rerun the upgrade script. Meaculpa, if its not a default I don't do it. All I'm aware of is the two jobs, the catalog and the files

Re: [Bacula-users] Incorrect datetime value after Bionic Update

2018-05-05 Thread Phil Stracchino
On 05/05/18 12:00, Ken Mandelberg wrote: > Well the backup I was counting on doesn't exist. I Duplicated the Ubuntu > 16.04 filesystem in another slice before doing the OS upgrade, assuming > I would have a copy of everything pre-update. It was a big surprise to > find that the update  updated b

Re: [Bacula-users] Incorrect datetime value after Bionic Update

2018-05-05 Thread Ken Mandelberg
Phil Stracchino wrote on 05/04/2018 03:03 PM: On 05/04/18 14:58, Ken Mandelberg wrote: [...] Looking at the script it should have added these fields but didn't. I wonder if that was because I ran it before the zero date issue was fixed. That is very likely the problem. Any suggestion on how

Re: [Bacula-users] scheduled job different that manually initiated job? --WAS: Re: Backup problem with 1 of 2 Raspberry PI using Raspbian (Debian)

2018-05-05 Thread Thorsten Johannsen
On 02.05.2018 11:56, Martin Simmons wrote: [...] heRPI02-fd: accurate.c:557-2073 Heap: heap=0 smbytes=1,155,867 max_bytes=1,155,867 bufs=95 max_bufs=95 heRPI02-fd: runscript.c:99-2073 runscript: running all RUNSCRIPT object (ClientAfterJob) JobStatus=f heRPI02-fd: runscript.c:120-2073 runscript: