mariadb don't start, selinux context problem

[rnt]

Cookbook version

1.5.4

Chef-client version

14.8.12

Platform Details

CentOS Linux release 7.6.1810 (Core)
Running on azure

Scenario:

Start mariadb service

Steps to Reproduce:

On CentOS 7.6 with SELINUX=enforcing, running the recipe mariadb::server.

Expected Result:

Mariadb start

Actual Result:

Mariadb fail to start.

    Error executing action `restart` on resource 'service[mysql]'
    ================================================================================
    
    Mixlib::ShellOut::ShellCommandFailed
    ------------------------------------
    Expected process to exit with [0], but received '1'
    ---- Begin output of /bin/systemctl --system restart mariadb ----
    STDOUT: 
    STDERR: Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.
    ---- End output of /bin/systemctl --system restart mariadb ----
    Ran /bin/systemctl --system restart mariadb returned 1
    
    Resource Declaration:
    ---------------------
    # In /var/chef/cache/cache/cookbooks/mariadb/recipes/server.rb
    
    129: service 'mysql' do
    130:   service_name node['mariadb']['mysqld']['service_name']
    131:   supports restart: true, reload: true
    132:   action [:start, :enable]
    133: end
    134: 
    
    Compiled Resource:
    ------------------
    # Declared in /var/chef/cache/cache/cookbooks/mariadb/recipes/server.rb:129:in `from_file'
    
    service("mysql") do
      action [:enable, :restart]
      default_guard_interpreter :default
      service_name "mariadb"
      enabled true
      running false
      masked false
      pattern "mysql"
      declared_type :service
      cookbook_name "mariadb"
      recipe_name "server"
      supports {:restart=>true, :reload=>true}
    end
    
    System Info:
    ------------
    chef_version=14.8.12
    platform=centos
    platform_version=7.6.1810
    ruby=ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-linux]
    program_name=chef-client worker: ppid=11236;start=12:09:19;
    executable=/opt/chef/bin/chef-client

On .err log, we see:

181218 12:15:19 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
181218 12:15:19 [Note] /usr/libexec/mysqld (mysqld 5.5.60-MariaDB) starting as process 32445 ...
181218 12:15:19 [ERROR] mysqld: File '/var/log/mysql/mariadb-bin.index' not found (Errcode: 13)
181218 12:15:19 [ERROR] Aborting

181218 12:15:19 [Note] /usr/libexec/mysqld: Shutdown complete

The file /var/log/mysql/mariadb-bin.index exists, but with no the correct selinux context.

Running restorecon -vR /var/log/mysql the output was:

restorecon reset /var/log/mysql/mariadb-bin.index context system_u:object_r:var_log_t:s0->system_u:object_r:mysqld_log_t:s0
restorecon reset /var/log/mysql/mariadb-bin.000001 context system_u:object_r:var_log_t:s0->system_u:object_r:mysqld_log_t:s0
restorecon reset /var/log/mysql/mariadb-bin.000002 context system_u:object_r:var_log_t:s0->system_u:object_r:mysqld_log_t:s0
restorecon reset /var/log/mysql/mariadb-bin.000003 context system_u:object_r:var_log_t:s0->system_u:object_r:mysqld_log_t:s0
restorecon reset /var/log/mysql/mariadb-bin.000004 context system_u:object_r:var_log_t:s0->system_u:object_r:mysqld_log_t:s0
restorecon reset /var/log/mysql/mariadb-bin.000005 context system_u:object_r:var_log_t:s0->system_u:object_r:mysqld_log_t:s0
restorecon reset /var/log/mysql/mariadb-bin.000006 context system_u:object_r:var_log_t:s0->system_u:object_r:mysqld_log_t:s0

And then, mariadb start without problems.

[sinfomicien]

@rnt: Any chance you could submit a PR ? It would be awesome 🥇

[github-actions]

Marking stale due to inactivity. Remove stale label or comment or this will be closed in 7 days. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help! Thanks, Sous-Chefs.