Re: [Bacula-users] Upgraded to MySQL 5.7, and now Bacula is upset over it.

2016-10-28 Thread Michael Munger
Quick and dirty fix for now. "Correct" fix later. Thank you! Michael Munger, dCAP, MCPS, MCNPS, MBSS High Powered Help, Inc. Microsoft Certified Professional Microsoft Certified Small Business Specialist Digium Certified Asterisk Professional mich...@highpoweredhelp.com On 10/28/2016 06:16 AM, Ke

Re: [Bacula-users] Upgraded to MySQL 5.7, and now Bacula is upset over it.

2016-10-28 Thread Kern Sibbald
The cleaner but more complicated fix is when you upgrade to a newer version of MySQL, update to the latest version of Bacula, which should solve your problem. On 28/10/2016 02:45, Phil Stracchino wrote: > On 10/27/16 20:14, Michael Munger wrote: >> Upgraded to MySQL 5.7 today. Now Bacula is upse

Re: [Bacula-users] Upgraded to MySQL 5.7, and now Bacula is upset over it.

2016-10-27 Thread Phil Stracchino
On 10/27/16 20:14, Michael Munger wrote: > Upgraded to MySQL 5.7 today. Now Bacula is upset. When I tried to run a > job, I got an instant failure: > > 27-Oct 20:10 d8-dir JobId 0: Fatal error: sql_create.c:86 Create DB Job > record INSERT INTO Job > (Job,Name,Type,Level,JobStatus,SchedTime,JobTDa

[Bacula-users] Upgraded to MySQL 5.7, and now Bacula is upset over it.

2016-10-27 Thread Michael Munger
Upgraded to MySQL 5.7 today. Now Bacula is upset. When I tried to run a job, I got an instant failure: 27-Oct 20:10 d8-dir JobId 0: Fatal error: sql_create.c:86 Create DB Job record INSERT INTO Job (Job,Name,Type,Level,JobStatus,SchedTime,JobTDate,ClientId,Comment) VALUES ('SERVER01.2016-10-27_20.