Re: [rt-users] MySQL backups of RT 4.4.1 truncated

2017-01-31 Thread Thomas Bätzler
Hi Stephen, > It's fixed!!! Recap: large RT database (host Ubuntu 14.04LTS, database server > MySQL 5.7.x on Windows Server 2012). Backup .sql files became truncated at > ~18GB when the database is easily 20GB. Good to hear. Does your my.cnf file not have a "[mysqldump]" section? That's where

Re: [rt-users] MySQL backups of RT 4.4.1 truncated

2017-01-30 Thread Cena, Stephen (ext. 300)
It's fixed!!! Recap: large RT database (host Ubuntu 14.04LTS, database server MySQL 5.7.x on Windows Server 2012). Backup .sql files became truncated at ~18GB when the database is easily 20GB. It looks like (for whatever reason) the max_allowed_packet option is not carrying over to the backup

Re: [rt-users] MySQL backups of RT 4.4.1 truncated

2017-01-30 Thread Cena, Stephen (ext. 300)
The problem has become more interested. Switching from --results-file to > exposed the max packet problem but now, I can't seem to get around it. I currently have my max_allowed_packet set to 1024M and it's still dying. I have the approximate row & attachment ID where it's failing and if I'm

Re: [rt-users] MySQL backups of RT 4.4.1 truncated (Cena, Stephen (ext. 300))

2017-01-28 Thread Cena, Stephen (ext. 300)
It looks like I've found the problems. To recap: I've got MySQL Server 5.7 on a Windows Server 2012 host running an RT database of ~20GB. My mysqldump backups started becoming truncated for some reason. I'm not sure how much of this is relevant to Windows, but it turns out this is what was

Re: [rt-users] MySQL backups of RT 4.4.1 truncated (Cena, Stephen (ext. 300))

2017-01-26 Thread Cena, Stephen (ext. 300)
sts.bestpractical.com" <rt-users@lists.bestpractical.com> Subject: Re: [rt-users] MySQL backups of RT 4.4.1 truncated Message-ID: <87f81e27495dc8489147e34a4152e268a4966...@mailstore2010.ogp.qvii.com> Content-Type: text/plain; charset="us-ascii" Update on

Re: [rt-users] MySQL backups of RT 4.4.1 truncated

2017-01-25 Thread Cena, Stephen (ext. 300)
Update on my MySQL backup issue: no change. I've now moved the Windows TEMP folders to the larger drive to see if the issue was running out of temp space and it has not helped. I will keep the group updated to any developments, but will refrain if its not anything noteworthy. I'm going to try

Re: [rt-users] MySQL backups of RT 4.4.1 truncated

2017-01-24 Thread Cena, Stephen (ext. 300)
Excellent point. The MySQL TEMP folder was moved, but not the operating system ones. I'll see if I can move the OS temp locations to the larger drive today & see what that gets me. I've just gotten the last 30 lines of the "attachments" table .sql file so I'm checking that to see if maybe

Re: [rt-users] MySQL backups of RT 4.4.1 truncated

2017-01-23 Thread Cena, Stephen (ext. 300)
Fri, 20 Jan 2017 14:04:04 + From: "Cena, Stephen (ext. 300)" <s...@qvii.com> To: 'Jeffrey Pilant' <jeffrey.pilant@bayer.com>, "'rt-users@lists.bestpractical.com'" <rt-users@lists.bestpractical.com> Subject: Re: [rt-users] MySQ

Re: [rt-users] MySQL backups of RT 4.4.1 truncated

2017-01-20 Thread Cena, Stephen (ext. 300)
All the backups I'm doing are local to keep performance high. I sadly lost the "discussion" to keep the MySQL server on a Linux machine. What we're going to try is the following: We're snapshotting/backing up the system at regular intervals so I will always have a backup of the .sql files. I'm

Re: [rt-users] MySQL backups of RT 4.4.1 truncated

2017-01-20 Thread Cena, Stephen (ext. 300)
I just looked into this now. Got a little swamped yesterday. It looks like the system is using the OS drive which barely has 19GB free so it's possible that's what's tripping it up. I checked the error log & the only errors I'm seeing are dropped packets from my RT systems around the time of

Re: [rt-users] MySQL backups of RT 4.4.1 truncated

2017-01-19 Thread Cena, Stephen (ext. 300)
Jeff - No limit that I'm aware of. If I look at a VM backup in December, the SQL files actually hit 19GB+ versus the "18 and change". The only other possibility that it COULD be is I've had to turn on Windows folder compression because the backups are getting so large their filling the drive. I

Re: [rt-users] MySQL backups of RT 4.4.1 truncated

2017-01-19 Thread Cena, Stephen (ext. 300)
bringe.com] Sent: Thursday, January 19, 2017 8:36 AM To: Cena, Stephen (ext. 300) <s...@qvii.com>; 'rt-users@lists.bestpractical.com' <rt-users@lists.bestpractical.com> Subject: Re: [rt-users] MySQL backups of RT 4.4.1 truncated Hi Stephen, Am 19.01.2017 um 13:33 schrieb Cena, Steph

Re: [rt-users] MySQL backups of RT 4.4.1 truncated

2017-01-19 Thread Thomas Bätzler
Hi Stephen, Am 19.01.2017 um 13:33 schrieb Cena, Stephen (ext. 300): > I had that issue initially, and changed the value to 64MB. It was > originally 4MB, then I increased it to 16MB, it’s been at 64MB for some > time. You can check your RT database to see whether 64MB is enough by running

Re: [rt-users] MySQL backups of RT 4.4.1 truncated

2017-01-19 Thread Cena, Stephen (ext. 300)
Cena, Stephen (ext. 300) <s...@qvii.com> Subject: AW: [rt-users] MySQL backups of RT 4.4.1 truncated Hello Stephen, just a stab in the dark, but could you please check the value set for "max_allowed_packet" in the mysqldump section of /etc/mysql/my.cnf (or whatever your my.

Re: [rt-users] MySQL backups of RT 4.4.1 truncated

2017-01-19 Thread Thomas Bätzler
-users@lists.bestpractical.com' <rt-users@lists.bestpractical.com> Betreff: Re: [rt-users] MySQL backups of RT 4.4.1 truncated I just ran a test with the attachments table “ignored”, and the backup worked perfectly. As a “sanity check”, I also ran mysqlcheck on the schema & no errors

Re: [rt-users] MySQL backups of RT 4.4.1 truncated

2017-01-18 Thread Cena, Stephen (ext. 300)
:rt-users@lists.bestpractical.com>> Subject: [rt-users] MySQL backups of RT 4.4.1 truncated Message-ID: <87f81e27495dc8489147e34a4152e268a4950...@mailstore2010.ogp.qvii.com<mailto:87f81e27495dc8489147e34a4152e268a4950...@mailstore2010.ogp.qvii.com>> Content-

[rt-users] MySQL backups of RT 4.4.1 truncated

2017-01-18 Thread Cena, Stephen (ext. 300)
I'm currently running RT 4.4.1 on Ubuntu 14.04 LTS with MySQL 5.6 on Windows Server 2012. Recently, we enabled full-text indexing in native MySQL & everything is great. After doing some work on the server over the weekend, I discovered that the .sql files being generated for the backup are