MySQL logs don't go to syslog are not in the diagnostic logs snapshot

Bug #1575777 reported by Bogdan Dobrelya
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Incomplete
Critical
Fuel Toolbox
Mitaka
Incomplete
Critical
Fuel Toolbox
Newton
Incomplete
Critical
Fuel Toolbox

Bug Description

MySQL logs are not in the diagnostic logs snapshot because syslog is not configured for MySQL deployment. The command "rgrep syslog /etc/mysql/" gives no results for nodes.

Example CI job https://ci.fuel-infra.org/job/master.fuel-library.pkgs.ubuntu.neutron_vlan_ha/8815/

UX is critical, we have found many bugs to mysql, and troubleshooting is impossible w/o logs

Tags: area-library
Changed in fuel:
importance: Undecided → Critical
milestone: none → 10.0
tags: added: galera
Changed in fuel:
assignee: nobody → Fuel Library Team (fuel-library)
description: updated
summary: - MySQL logs are not in the diagnostic logs snapshot
+ MySQL logs don't go to syslog are not in the diagnostic logs snapshot
Changed in fuel:
status: New → Confirmed
tags: added: area-library
Changed in fuel:
assignee: Fuel Library (Deprecated) (fuel-library) → Fuel for Openstack (fuel)
Changed in fuel:
assignee: Fuel for Openstack (fuel) → Fuel Toolbox (fuel-toolbox)
Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote :

Should we assign 9.0 milestone to the issue?

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

This should be a regression after we switched to mysql-puppet, which was in the 9.0, IIRC. So, yes - we should

Revision history for this message
Alex Schultz (alex-schultz) wrote :

The configuration for syslog is still there for 9 and 10.

https://github.com/openstack/fuel-library/blob/stable/mitaka/deployment/puppet/osnailyfacter/manifests/database/database.pp#L145-L156

Please clarify this bug as I also have an environment with syslog configuration. The bug seems to indicate logs not sent to syslog are not captured which is different than the syslog configuration.

[mysqld_safe]
nice = 0
socket = /var/run/mysqld/mysqld.sock
syslog

Revision history for this message
Peter Zhurba (pzhurba) wrote :

As I can see there are 3 files on live environment

   nailgun:/var/log/remote/node-1.test.domain.local/mysqld.log
   nailgun:/var/log/remote/node-1.test.domain.local/mysqld_safe.log

and

 node-1:/var/log/mysqld.log

and there is nothing in snapshot

Revision history for this message
Alex Schultz (alex-schultz) wrote :

I'm not sure this was a regression as the configuration has been inconsistent for a long time. Rsyslog puts the logs in /var/log/mysqld{_safe}.log due to:

https://github.com/openstack/fuel-library/blob/master/deployment/puppet/openstack/templates/04-mysql.conf.erb

The shotgun capture only gets /var/log/mysql/ due to:

https://github.com/openstack/fuel-web/blob/master/nailgun/nailgun/settings.yaml#L899-L900

The mysql logs weren't even attempted to be captured prior to 9.0 until bug 1550984. I'll be marking this as a dupe of 1550984 and reopening because it was not properly implemented.

tags: removed: galera
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.