mysqld_safe Can't log to error log and syslog at the same time
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mylvmbackup |
Fix Released
|
Medium
|
Lenz Grimmer |
Bug Description
Hi,
I get a non-fatal warning message when I run mylvmbackup with InnoDB recovery. Platform is Lucid Lynx, mysql 5.1.66, mylvmbackup 0.13. The message is:
mysqld_safe Can't log to error log and syslog at the same time. Remove all --log-error configuration options for --syslog to take effect.
After some investigation, I think the invocation of mysqld_safe by mylvmbackup should also include a --skip-syslog switch (approximately line 625).
Here are the results prior ...
Line 625:
my $command="echo 'select 1;' | $mysqld_safe --socket=
Output:
20121218 23:16:54 Info: Recovering InnoDB...
20121218 23:16:54 Info: Running: echo 'select 1;' | mysqld_safe --socket=
121218 23:16:54 mysqld_safe Can't log to error log and syslog at the same time. Remove all --log-error configuration options for --syslog to take effect.
121218 23:16:54 mysqld_safe Logging to '/tmp/mylvmback
121218 23:16:55 mysqld_safe Starting mysqld daemon with databases from /var/cache/
121218 23:17:00 mysqld_safe mysqld from pid file /var/run/
20121218 23:17:00 Info: DONE: InnoDB recovery on snapshot
... and after I include the --skip-syslog switch ...
Line 625:
my $command="echo 'select 1;' | $mysqld_safe --socket=
Output:
20121218 23:15:18 Info: Recovering InnoDB...
20121218 23:15:18 Info: Running: echo 'select 1;' | mysqld_safe --socket=
121218 23:15:18 mysqld_safe Logging to '/tmp/mylvmback
121218 23:15:18 mysqld_safe Starting mysqld daemon with databases from /var/cache/
121218 23:15:24 mysqld_safe mysqld from pid file /var/run/
20121218 23:15:24 Info: DONE: InnoDB recovery on snapshot
Any comments? Or perhaps you can think of a cleaner solution?
Thanks.
Changed in mylvmbackup: | |
status: | Fix Committed → Fix Released |
Makes sense. Thanks for the report, I'll look into fixing this for the next release.