Not logging to syslog even though configured to by default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-5.5 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
STR:
1. Install mysql-server.
2. start mysql
3. Look into /var/log/syslog
Expected results:
Feb 27 08:13:49 sabre mysqld: 130227 8:13:49 [Note] /usr/sbin/mysqld: ready for connections.
Feb 27 08:13:49 sabre mysqld: Version: '5.5.29-
Actual results:
Only lines from debian-start are visible.
The reason for that is that upstart job calls /usr/sbin/mysqld and not /usr/bin/
In my case it prevents configuration of X509 client certificate checks because "X509 issuer mismatch: should be 'C=IL, O=StartCom Ltd., OU=Secure Digital Certificate Signing, CN=StartCom Class 1 Primary Intermediate Server CA' but is '/C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom Class 1 Primary Intermediate Server CA'" message is never seen in the logs and this is important because of http://
WORKAROUND:
Create /etc/init/
exec /usr/bin/
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: mysql-server 5.5.29-
ProcVersionSign
Uname: Linux 3.2.0-38-
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: i386
Date: Wed Feb 27 08:14:52 2013
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release i386 (20120424.1)
Logs.var.
Logs.var.
Feb 27 06:58:38 sabre-clone kernel: [76625.775253] type=1400 audit(136194831
Feb 27 06:59:41 sabre-clone kernel: [76688.595429] type=1400 audit(136194838
Feb 27 07:13:38 sabre-clone kernel: [77525.967644] type=1400 audit(136194921
MarkForUpload: True
MySQLConf.
[mysqld_safe]
syslog
MySQLVarLibDirL
PackageArchitec
SourcePackage: mysql-5.5
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for taking the time to report this bug and helping to make Ubuntu better.
This sounds simliar to bug 1014732. Please could you take a look and see what you think? The fix for that bug is currently in precise-proposed and on its way to precise-updates. It won't log to syslog, but will log to /var/log/ mysql/error. log.
Once that bug is fixed, what do you think about the status of and your proposed fix to this bug?