| Bug #45839 | Segmentation Fault when running mabackup | ||
|---|---|---|---|
| Submitted: | 30 Jun 2009 3:09 | Modified: | 20 Oct 2009 6:01 |
| Reporter: | Stuart Bury | Email Updates: | |
| Status: | Unsupported | Impact on me: | |
| Category: | MySQL Administrator | Severity: | S2 (Serious) |
| Version: | 14.12 | OS: | Linux (Ubuntu 9.04) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Backup, crash, mabackup, segmentation fault | ||
[30 Jun 2009 4:19]
Valeriy Kravchuk
Please, specify the exact version of MySQL server (5.x.y?) used. Send also your my.cnf file content and error log of MySQL server.
[30 Jun 2009 11:03]
Stuart Bury
my.cnf
Attachment: my.cnf (application/octet-stream, text), 4.09 KiB.
[30 Jun 2009 11:09]
Stuart Bury
Full version string is "mysql Ver 14.12 Distrib 5.0.75, for debian-linux-gnu (i486) using readline 5.2" I have a mysql.log and a mysql.err, and mysql.log.1.gz through mysql.log.7.gz, but they're all empty. That is, the first two are zero bytes, and the .gz files are 20 bytes and - when opened - contain logfiles of zero bytes. I'm quite willing to follow any instructions you wish; provided of course they will not break my system further.
[30 Jun 2009 12:59]
MySQL Verification Team
If I understood is mabackup which is crashing right?. Thanks in advance.
[30 Jun 2009 16:07]
Stuart Bury
Yes, that's right. When I type the mabackup command at the shell it crashes with a segmentation fault. Whatever that is.
[8 Jul 2009 11:59]
Susanne Ebrecht
Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Administrator into MySQL Workbench. Unfortunately you are using an unsupported platform. More informations about supported platforms you will find here: http://www.mysql.com/support/supportedplatforms/tools.html More informations about MySQL Workbench you will find here: http://dev.mysql.com/workbench/
[8 Jul 2009 22:02]
Stuart Bury
I've just checked the list of supported platforms. Windows is the only one listed. So, basically, what you're telling me is that, if your software falls over and DIES because it's badly written and full of bugs, you're going to do sod-all about it and it's all my fault because I should be using Windows? Have I understood you correctly? Surely MySQL is primarily a Linux-based product? If people are going to use Windows, they're going to use Microsoft SQL Server. I think this is a disgusting attitude on your part. If that's how you treat your customers, I for one won't be using your product or paying for your technical support.
[4 Aug 2009 19:25]
MySQL Verification Team
Thank you for the bug report. Verified on Ubuntu 9.04 64-bit.
[9 Sep 2009 8:03]
burak us
I'm on Ubuntu 9.04 64bit and have had the same problem. I set up a backup using the MySQL Administrator and scheduled it. But the backups didn't work. I tried running the command that was written in cron and I got a "Segmentation Fault". I noticed that the command that was written to cron was wrong. I had selected a directory which contains a space character but the path on cron was cut from the first space character in the path. It was like: 20 11 * * 1,2,3,4,5 /usr/bin/mabackup -d /home/user/some -c connection backup It should have been: 20 11 * * 1,2,3,4,5 /usr/bin/mabackup -d /home/user/some\ directory -c connection backup I renames my folder names without the spaces now the cron works without a problem. It seems that Mysql Administrator cannot handle paths with spaces in them.
[20 Oct 2009 6:01]
Susanne Ebrecht
Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Administrator into MySQL Workbench. We won't fix this anymore. Lots of functionalities of MySQL Administrator are already implemented in Workbench 5.2 which will get GA soon. More informations about MySQL Workbench you will find here: http://dev.mysql.com/workbench/
Description: While trying to run mabackup manually at the commandline in an attempt to figure out why your MySQL Administrator COMPLETELY FAILS to set up scheduled backups (HINT! HINT!), mabackup caused a segmentation fault. How to repeat: Create a backup profile *.mbp file in the usual place with the following content (although this wasn't the content I was trying to use, it does demonstrate the problem quite well, and it refers to a table that should exist for everyone; the one I was using was auto-generated by MySQL Administrator): <?xml version="1.0"?> <backup_profile> <version>1.2</version> <profile_name>Full backup</profile_name> <last_used/> <options>2372</options> <backup_type>0</backup_type> <entities> <entity> <name>help_keyword</name> <schema>mysql</schema> <catalog>def</catalog> <entity_type>table</entity_type> </entity> </entities> </backup_profile> Type the following at a shell: $ /usr/bin/mabackup -d [any location] -x [any prefix] -h localhost -uroot -pxxxxx [backup profile name] Result: Segmentation fault This happens even if I sudo the command. And yes, the user ROOT has access to the DB and the table(s) in question. I can access 'em fine in MySQL Admin. Suggested fix: Uhmm...maybe fix the damn MySQL Administrator so it can actually SCHEDULE BACKUPS itself like it SHOULD, mebbe? Then, running "mabackup" at the command line and suchlike wouldn't be necessary in the first place!