【メモ】Redmineセットアップ備忘録

はじめに

旧さくらVPS→新さくらVPSに移行するにあたり、Redmine本体もアップグレードしてデータだけ元の環境から持ってこようとした際の作業備忘録です。
Nginx + Unicorn + MariaDB + Postfixでの動作を想定。
前提としては、GitとかNginxが入っている以外はほぼデフォルト状態……のはず。
OSはAlmaLinux 8です。

rbenv、ruby

既にGitは入っているので割愛。
参考リンク：
https://mebee.info/2021/04/10/post-33002/

#rbenvのインストール
$ git clone https://github.com/sstephenson/rbenv.git ~/.rbenv

#pathを通す
$ echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bash_profile

#初期化
$ rbenv init

#初期化処理をbash_profileに追記、反映
$ echo 'eval "$(rbenv init - bash)"' >> ~/.bash_profile
$ source ~/.bash_profile

#ruby-buildのインストール
$ git clone https://github.com/sstephenson/ruby-build.git ~/.rbenv/plugins/ruby-build

#依存パッケージをインストール
$ sudo dnf install gcc openssl-devel readline-devel zlib-devel

#rubyのバージョンリストを確認してインストール
$ rbenv install --list
$ rbenv install 3.1.2

#インストールしたバージョンをglobalに設定
$ rbenv global 3.1.2

MariaDB

MariaDBはAlmaLinuxだと、標準のdnfリポジトリからインストールすることができないので、MariaDBリポジトリを追加してそこから取得するように設定する。

MariaDB公式のリポジトリ追加およびインストール手順：
https://mariadb.org/download/?t=repo-config&d=Red+Hat+EL+9+(x86_64)&v=10.9&r_m=yamagata-university

参考リンク：
https://shimaichi.blog/almalinux-8-4-minimal-mariadb-10-6/
https://www.server-memo.net/server-setting/mariadb/centos8_mariadbrepo_install.html
https://qiita.com/ponsea/items/9578659009b434c60959

#MariaDBリポジトリの追記
$ sudo vi /etc/yum.repos.d/mariadb.repo

# MariaDB 10.6 RedHat repository list - created  UTC
# https://mariadb.org/download/
[mariadb]
name = MariaDB
baseurl = https://ftp.yz.yamagata-u.ac.jp/pub/dbms/mariadb/yum/10.6/rhel8-amd64
module_hotfixes=1
gpgkey=https://ftp.yz.yamagata-u.ac.jp/pub/dbms/mariadb/yum/RPM-GPG-KEY-MariaDB
gpgcheck=1
enable=1

#MariaDB関係のパッケージをインストール
$ sudo dnf install MariaDB-devel MariaDB-client MariaDB-server

#MariaDBのステータス確認、起動、自動起動設定
$ systemctl status mariadb
$ sudo systemctl start mariadb
$ sudo systemctl enable mariadb

#mariadb-secure-installationによる基本的なセキュリティ設定
$ sudo mariadb-secure-installation

mysql_secure_installation」では下記の設定を行う。

1. Enter current password for root (enter for none)
MariaDBのrootユーザのパスワードを入力
インストール直後は何も設定されていないので「Enter」キーを押下する

2. Switch to unix_socket authentication [Y/n]
MariaDBのrootユーザの認証を「unix_socket」プラグインを使用した認証に切り替えるかどうかの設定
MariaDB 10.4からはデフォルトで「unix_socket」は有効になっているので「n」で切り替え処理をskipする

3. Change the root password? [Y/n]
MariaDBのrootユーザを変更するかの設定
従来通りのパスワードでの認証を行いたいので「y」を入力してパスワードを設定
パスワードを設定しない場合はOSの「root」ユーザのみがMariaDBの「root」ユーザとして接続可能という設定となる

4. New password:
MariaDBのrootユーザに設定するパスワードを入力

5. Re-enter new password:
設定したパスワードを再入力

6. Remove anonymous users? [Y/n]
anonymousユーザを削除するかどうかの設定
削除するので「y」を入力

7. Disallow root login remotely? [Y/n]
MariaDBの「root」ユーザのリモートログインを禁止するかの設定
禁止するので「y」を入力

8. Remove test database and access to it? [Y/n]
初期設定で作成されている「test」データベースを削除するかの設定
削除するので「y」を入力

9. Reload privilege tables now? [Y/n]
これまので設定をすぐに反映させるかどうかの設定
反映させるので「y」を入力

# サーバー設定を変更するので元の設定ファイルのバックアップを取ってから編集
$ sudo cp -p /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.org
$ sudo vi /etc/my.cnf.d/server.cnf

絵文字に対応させるために、設定ファイル内の以下のセクションに文字コード設定を追加。
該当セクションが存在しない場合は、セクションそのものも追加する。

[mariadb]
character-set-server = utf8mb4

[client-mariadb]
default-character-set = utf8mb4

#設定読み込みのためにMariaDBを再起動
$ sudo systemctl restart mariadb

#一旦設定が反映されているかDBにログインして確認
$ mysql -u root -p

以下のように表示されていればOK。

MariaDB [(none)]> show variables like "chara%"; #文字コードの設定を参照
+--------------------------+----------------------------+
| Variable_name            | Value                      |
+--------------------------+----------------------------+
| character_set_client     | utf8mb4                    |
| character_set_connection | utf8mb4                    |
| character_set_database   | utf8mb4                    |
| character_set_filesystem | binary                     |
| character_set_results    | utf8mb4                    |
| character_set_server     | utf8mb4                    |
| character_set_system     | utf8mb3                    |
| character_sets_dir       | /usr/share/mysql/charsets/ |
+--------------------------+----------------------------+
8 rows in set (0.00 sec)

#redmineからDBに接続するためのユーザーを作成
$ sudo useradd redmine
$ sudo passwd redmine　（パスワードはteampassに保存）

#redmine用のDBを作成するために再度ログイン
$ mysql -u root -p

#redmine用のDBを作成
MariaDB [(none)]> CREATE DATABASE redmine;

#DBが作成できているか確認
MariaDB [(none)]> SHOW DATABASES;

#MariaDB上に上記で作成したユーザーと同様にユーザー作成、権限付与
MariaDB [(none)]> GRANT ALL ON redmine.* TO 'redmine'@'localhost' IDENTIFIED BY 'redmineユーザーの接続パスワード' WITH GRANT OPTION;

Redmine

Redmineアプリケーションを  /var/www/redmine 以下に配置することを前提とする。
Redmineは公式サイトから5.0.3のバージョンをダウンロード。

参考リンク：
Redmineのインストール - Redmineガイド
RedmineをCentOS 8上で動かすーUnicornとNginx編 - ソフトウェアエンジニアリング - Torutk
AlmaLinux8でRedmine(4.2.5)サーバー構築 – supilog

#redmineアプリ配置用のディレクトリを作成
$ sudo mkdir -p /var/www/redmine

#redmineを適当なディレクトリにダウンロードして解凍
$ wget https://www.redmine.org/releases/redmine-5.0.3.tar.gz -P /tmp
$ sudo tar xzf /tmp/redmine-5.0.3.tar.gz -C /var/www/redmine --strip-components 1

#redmineディレクトリにパーミッションを設定
$ sudo chmod 775 /var/www/redmine/
$ sudo chown -R hoge:hoge /var/www/redmine/

#一応rubyのバージョンをローカルで指定
$ cd /var/www/redmine/
$ rbenv local 3.1.2

#database.yml.exampleをコピーしてdatabase.ymlを編集
$ cp /var/www/redmine/config/database.yml{.example,}
$ vi /var/www/redmine/config/database.yml

productionセクションに下記の項目を追加

production:
  adapter: mysql2
  database: redmine
  host: localhost
  username: "<%= ENV['REDMINE_DB_USERNAME'] %>"
  password: "<%= ENV['REDMINE_DB_PASSWORD'] %>"
  # Use "utf8" instead of "utfmb4" for MySQL prior to 5.7.7
  encoding: utf8mb4

#暫定的に環境変数をbash_profileに設定
$ vi ~/.bash_profile

下記の項目を追加

# Redmine
export REDMINE_DB_USERNAME="redmine"
export REDMINE_DB_PASSWORD="redmineユーザーのパスワード"

#環境変数反映
$ source ~/.bash_profile

#configuration.yml.exampleをコピーしてconfiguration.ymlを編集
$ cp /var/www/redmine/config/configuration.yml{.example,}
$ vi /var/www/redmine/config/configuration.yml

productionセクションに下記の項目を追加

production:
  email_delivery:
    delivery_method: :sendmail  #後述するPostfixの設定と合わせる
    smtp_settings:
      address: "localhost"
      port: 25

#bundlerとgemのインストール（今回はdevelopmentとtestグループのgemを除外）。
$ gem install bundler
$ bundle config set --local without 'development test'
$ bundle install

#セッションストア秘密鍵の生成
$ bundle exec rails generate_secret_token

#DBマイグレーション
$ bundle exec rails db:migrate RAILS_ENV=production

#Redmineに用意されているデフォルトデータを流し込む
$ bundle exec rails redmine:load_default_data RAILS_ENV=production REDMINE_LANG=ja

#システムで利用するフォルダを作成、パーミッションを設定
$ mkdir -p tmp/pdf
$ sudo chown -R redmine:redmine files log tmp public/plugin_assets
$ sudo chmod -R 755 files log tmp public/plugin_assets

Unicorn

今回は元のGemfileは弄らずにGemfile.localを別に作ってそちらからインストールしてみる。
参考リンク：
【CentOS 7】Nginx + Unicorn で Rails アプリケーションを本番環境で立ち上げる方法

$ vi Gemfile.local

下記の行を追加

gem "unicorn"

#gemインストールついでに一応アップデート
$ bundle update

#unicornの設定ファイルを作成
$ vi config/unicorn.rb

下記の項目を追加


worker_processes Integer(ENV["WEB_CONCURRENCY"] || 3)
timeout 30
preload_app true

listen '/var/www/redmine/tmp/unicorn/unicorn.sock'
pid    '/var/www/redmine/tmp/unicorn/unicorn.pid'

before_fork do |server, worker|
  Signal.trap 'TERM' do
    puts 'Unicorn master intercepting TERM and sending myself QUIT instead'
    Process.kill 'QUIT', Process.pid
  end

  defined?(ActiveRecord::Base) and
    ActiveRecord::Base.connection.disconnect!
end

after_fork do |server, worker|
  Signal.trap 'TERM' do
    puts 'Unicorn worker intercepting TERM and doing nothing. Wait for master to send QUIT'
  end

  defined?(ActiveRecord::Base) and
    ActiveRecord::Base.establish_connection
end

stderr_path File.expand_path('log/unicorn.log', ENV['RAILS_ROOT'])
stdout_path File.expand_path('log/unicorn.log', ENV['RAILS_ROOT'])


#unicorn起動taskの作成
#（下記コマンドで、RAILS_ENV=productionのオプションは末尾に付けてしまうとtaskコマンドの引数として判定され、正常にgenerateできないようなので注意）
$ RAILS_ENV=production bundle exec rails g task unicorn
$ vi lib/tasks/unicorn.rake

下記の項目を追加

namespace :unicorn do

  # Tasks
  desc "Start unicorn"
  task(:start) {
    config = Rails.root.join('config', 'unicorn.rb')
    sh "unicorn -c #{config} -E production -D"
  }

  desc "Stop unicorn"
  task(:stop) {
    unicorn_signal :QUIT
  }

  desc "Restart unicorn with USR2"
  task(:restart) {
    unicorn_signal :USR2
  }

  desc "Increment number of worker processes"
  task(:increment) {
    unicorn_signal :TTIN
  }

  desc "Decrement number of worker processes"
  task(:decrement) {
    unicorn_signal :TTOU
  }

  desc "Unicorn pstree (depends on pstree command)"
  task(:pstree) do
    sh "pstree '#{unicorn_pid}'"
  end

  # Helpers
  def unicorn_signal signal
    Process.kill signal, unicorn_pid
  end
  
  def unicorn_pid
    begin
      File.read("/var/www/redmine/tmp/unicorn/unicorn.pid").to_i
    rescue Errno::ENOENT
      raise "Unicorn does not seem to be running"
    end
  end

end

#後述の作業のために、作業用ユーザーがディレクトリを触れるようredmineグループに追加
$ sudo gpasswd -a 作業用ユーザー名 redmine

#unicornのpidとソケットを保存するディレクトリを作成
#併せてpid、ソケット、ログファイルの作成が行えるよう関連ディレクトリにパーミッション設定
$ cd tmp
$ sudo mkdir unicorn
$ sudo chown -R redmine:redmine unicorn
$ sudo chmod 775 unicorn
$ cd /var/www/redmine
$ sudo chmod 775 log

#unicorn起動確認。プロセスが表示されていればOK
$ bundle exec rails unicorn:start
$ ps -ef | grep unicorn | grep -v grep
$ bundle exec rails unicorn:stop

Nginx

今回はnginxが既にインストールされている前提。

#nginxやアプリの実行ユーザー向けに各フォルダのパーミッションの設定を修正
$ cd /var/www/redmine
$ sudo chmod -R 775 files log tmp public/plugin_assets
$ sudo chmod 777 tmp/unicorn

#redmineアプリ用のnginxの設定ファイルを作成、記述
$ sudo vi /etc/nginx/conf.d/redmine.conf

以下の項目を追加

upstream unicorn {
    server unix:/var/www/redmine/tmp/unicorn/unicorn.sock;
}

server {
    listen 80;
    server_name example.com;

    root /var/www/redmine/public;
    access_log /var/log/nginx/redmine_access.log;
    error_log  /var/log/nginx/redmine_error.log;
    client_max_body_size 1G;

    location / {
        try_files $uri/index.html $uri.html $uri @unicorn;
    }

    location @unicorn {
        proxy_redirect off;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $http_host;
        proxy_connect_timeout 60;
        proxy_read_timeout 60;
        proxy_send_timeout 600;
        proxy_pass http://unicorn;
    }

    error_page 404 /404.html;
    error_page 500 502 503 504 /500.html;
}

#nginxの再起動、ステータス確認
$ sudo systemctl restart nginx
$ systemctl status nginx

Postfix

Redmineアプリからメール送信を行うために、Postfixをインストールしてメール転送エージェントとして利用する。
前述のconfiguration.ymlで設定したように、Postfixのsendmailコマンドでメール送信を行う。（Sendmailアプリのsendmailコマンドで送信しているわけではないので注意）
迷惑メールに振り分けられないように、DNSレコードをTXTレコードでドメインに対して設定している。

今回のメールサーバーの設定の前提として、基本的にはローカルから外部へとメールを送信するために利用することを目的とする。
受信設定はデフォルトから変更していないので、恐らくローカルからの受信だけ許可している形になっているはず。
参考リンク：
» メールの設定例 - Redmineガイド
Postfix のインストールと設定 〜 CentOS6 | EasyRamble
CentOSとPostfixを使って送信専用のメールサーバーを構築する方法 - レムシステム エンジニアブログ

#Postfixのインストール
$ sudo dnf install postfix

#このサーバーで利用するMTAをPostfixに設定する
#（現段階だとサーバーにはPostfixしかメールソフトが入っていないはずなので、デフォルトでMTAに設定されているはず）
$ sudo alternatives --config mta

#設定ファイルをコピーしてバックアップを取っておく
$ sudo cp -p /etc/postfix/main.cf /etc/postfix/main.cf.org

#postfixの自動起動設定、ステータスの確認
$ sudo systemctl enable postfix
$ systemctl status postfix

#設定ファイルの編集
$ sudo vi /etc/postfix/main.cf

下記項目の設定を変更する
- myhostname
- mydomain
- myorigin
- inet_protocols
- mydestination
- smtpd_banner

# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
#
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/BASIC_CONFIGURATION_README.html etc.
#
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.

# COMPATIBILITY
#
# The compatibility_level determines what default settings Postfix
# will use for main.cf and master.cf settings. These defaults will
# change over time.
#
# To avoid breaking things, Postfix will use backwards-compatible
# default settings and log where it uses those old backwards-compatible
# default settings, until the system administrator has determined
# if any backwards-compatible default settings need to be made
# permanent in main.cf or master.cf.
#
# When this review is complete, update the compatibility_level setting
# below as recommended in the RELEASE_NOTES file.
#
# The level below is what should be used with new (not upgrade) installs.
#
compatibility_level = 2

# SOFT BOUNCE
#
# The soft_bounce parameter provides a limited safety net for
# testing.  When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#
#soft_bounce = no

# LOCAL PATHNAME INFORMATION
#
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
#
queue_directory = /var/spool/postfix

# The command_directory parameter specifies the location of all
# postXXX commands.
#
command_directory = /usr/sbin

# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
#
daemon_directory = /usr/libexec/postfix

# The data_directory parameter specifies the location of Postfix-writable
# data files (caches, random numbers). This directory must be owned
# by the mail_owner account (see below).
#
data_directory = /var/lib/postfix

# QUEUE AND PROCESS OWNERSHIP
#
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes.  Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM.  In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
#
mail_owner = postfix

# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#
#default_privs = nobody

# INTERNET HOST AND DOMAIN NAMES
# 
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
myhostname = mail.example.com  #メールサーバー用に独自のホスト名を設定するため、hostnameコマンドで出力されたものに接頭辞としてmail.を付与

# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#
#mydomain = domain.tld
mydomain = example.com  #ドメイン名。とりあえず仮ドメインをそのまま設定

# SENDING MAIL
# 
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites.  If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# user@that.users.mailhost.
#
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#
#myorigin = $myhostname
myorigin = $mydomain  #ドメイン名と同一の設定を利用する

# RECEIVING MAIL

# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on.  By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
#
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
#
# Note: you need to stop/start Postfix when this parameter changes.
#
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
inet_interfaces = localhost

# Enable IPv4, and IPv6 if supported
#inet_protocols = all
inet_protocols = ipv4  #IPv4とIPv6の両方を許可していると（恐らくhostsとの設定の兼ね合いで）エラーになるのでIPv4だけ許可する

# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
#
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4

# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
#
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
#
# The default is $myhostname + localhost.$mydomain + localhost.  On
# a mail domain gateway, you should also include $mydomain.
#
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
#
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
#
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
#
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
#
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#
#mydestination = $myhostname, localhost.$mydomain, localhost
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain  #mydomainを含む形にしてアンコメント化
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
#	mail.$mydomain, www.$mydomain, ftp.$mydomain

# REJECTING MAIL FOR UNKNOWN LOCAL USERS
#
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
#
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
#
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
#
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
#
# - You define $mydestination domain recipients in files other than
#   /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
#   For example, you define $mydestination domain recipients in    
#   the $virtual_mailbox_maps files.
#
# - You redefine the local delivery agent in master.cf.
#
# - You redefine the "local_transport" setting in main.cf.
#
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
#   feature of the Postfix local delivery agent (see local(8)).
#
# Details are described in the LOCAL_RECIPIENT_README file.
#
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
#
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a user@domain.tld address.
# 
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =

# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
#
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
#
unknown_local_recipient_reject_code = 550

# TRUST AND RELAY CONTROL

# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
#
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix.  See the smtpd_recipient_restrictions parameter
# in postconf(5).
#
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
#
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this works correctly only with interfaces specified
# with the "ifconfig" command.
# 
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network.  Instead, specify an explicit
# mynetworks list by hand, as described below.
#  
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
# 
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host

# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
#
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
#
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table

# The relay_domains parameter restricts what destinations this system will
# relay mail to.  See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
#
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
#   subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# 
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# 
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace.  Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
#
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#
#relay_domains = $mydestination

# INTERNET OR INTRANET

# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
#
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
#
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
#
# If you're connected via UUCP, see also the default_transport parameter.
#
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]

# REJECTING UNKNOWN RELAY USERS
#
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
#
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
#
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a user@domain.tld address.
# 
#relay_recipient_maps = hash:/etc/postfix/relay_recipients

# INPUT RATE CONTROL
#
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# 
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# 
# Specify 0 to disable the feature. Valid delays are 0..10.
# 
#in_flow_delay = 1s

# ADDRESS REWRITING
#
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.

# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
#
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.

# "USER HAS MOVED" BOUNCE MESSAGES
#
# See the discussion in the ADDRESS_REWRITING_README document.

# TRANSPORT MAP
#
# See the discussion in the ADDRESS_REWRITING_README document.

# ALIAS DATABASE
#
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
#
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# 
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
#
# It will take a minute or so before changes become visible.  Use
# "postfix reload" to eliminate the delay.
#
#alias_maps = dbm:/etc/aliases
alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases

# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi".  This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases

# ADDRESS EXTENSIONS (e.g., user+foo)
#
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#
#recipient_delimiter = +

# DELIVERY TO MAILBOX
#
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user.  Specify
# "Maildir/" for qmail-style delivery (the / is required).
#
#home_mailbox = Mailbox
#home_mailbox = Maildir/
 
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail

# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception:  delivery for root is done as $default_user.
#
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
#
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
#
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
#
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"

# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
#
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf.  The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for    
# non-UNIX accounts with "User unknown in local recipient table".
#
# Cyrus IMAP over LMTP. Specify ``lmtpunix      cmd="lmtpd"
# listen="/var/imap/socket/lmtp" prefork=0'' in cyrus.conf.
#mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp

# If using the cyrus-imapd IMAP server deliver local mail to the IMAP
# server using LMTP (Local Mail Transport Protocol), this is prefered
# over the older cyrus deliver program by setting the
# mailbox_transport as below:
#
# mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
#
# The efficiency of LMTP delivery for cyrus-imapd can be enhanced via
# these settings.
#
# local_destination_recipient_limit = 300
# local_destination_concurrency_limit = 5
#
# Of course you should adjust these settings as appropriate for the
# capacity of the hardware you are using. The recipient limit setting
# can be used to take advantage of the single instance message store
# capability of Cyrus. The concurrency limit can be used to control
# how many simultaneous LMTP sessions will be permitted to the Cyrus
# message store.
#
# Cyrus IMAP via command line. Uncomment the "cyrus...pipe" and
# subsequent line in master.cf.
#mailbox_transport = cyrus

# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
#
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf.  The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for    
# non-UNIX accounts with "User unknown in local recipient table".
#
#fallback_transport = lmtp:unix:/var/lib/imap/socket/lmtp
#fallback_transport =

# The luser_relay parameter specifies an optional destination address
# for unknown recipients.  By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
#
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
#
# luser_relay works only for the default Postfix local delivery agent.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for    
# non-UNIX accounts with "User unknown in local recipient table".
#
#luser_relay = $user@other.host
#luser_relay = $local@other.host
#luser_relay = admin+$local
  
# JUNK MAIL CONTROLS
# 
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.

# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
#
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
#
# For details, see "man header_checks".
#
#header_checks = regexp:/etc/postfix/header_checks

# FAST ETRN SERVICE
#
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# 
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
# 
#fast_flush_domains = $relay_domains

# SHOW SOFTWARE VERSION OR NOT
#
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
#
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
smtpd_banner = $myhostname ESMTP $mail_name unknown  #メールサーバーソフト名を隠蔽化する

# PARALLEL DELIVERY TO THE SAME DESTINATION
#
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# 
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter.  The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.

#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20

# DEBUGGING CONTROL
#
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
#
debug_peer_level = 2

# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain

# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
#
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
#
debugger_command =
	 PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
	 ddd $daemon_directory/$process_name $process_id & sleep 5

# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
#
# debugger_command =
#	PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
#	echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
#	>$config_directory/$process_name.$process_id.log & sleep 5
#
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen session, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
#
# debugger_command =
#	PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
#	-dmS $process_name gdb $daemon_directory/$process_name
#	$process_id & sleep 1

# INSTALL-TIME CONFIGURATION INFORMATION
#
# The following parameters are used when installing a new Postfix version.
# 
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
# 
sendmail_path = /usr/sbin/sendmail.postfix

# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
#
newaliases_path = /usr/bin/newaliases.postfix

# mailq_path: The full pathname of the Postfix mailq command.  This
# is the Sendmail-compatible mail queue listing command.
# 
mailq_path = /usr/bin/mailq.postfix

# setgid_group: The group for mail submission and queue management
# commands.  This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
#
setgid_group = postdrop

# html_directory: The location of the Postfix HTML documentation.
#
html_directory = no

# manpage_directory: The location of the Postfix on-line manual pages.
#
manpage_directory = /usr/share/man

# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
#
sample_directory = /usr/share/doc/postfix/samples

# readme_directory: The location of the Postfix README files.
#
readme_directory = /usr/share/doc/postfix/README_FILES

# TLS CONFIGURATION
#
# Basic Postfix TLS configuration by default with self-signed certificate
# for inbound SMTP and also opportunistic TLS for outbound SMTP.

# The full pathname of a file with the Postfix SMTP server RSA certificate
# in PEM format. Intermediate certificates should be included in general,
# the server certificate first, then the issuing CA(s) (bottom-up order).
#
smtpd_tls_cert_file = /etc/pki/tls/certs/postfix.pem

# The full pathname of a file with the Postfix SMTP server RSA private key
# in PEM format. The private key must be accessible without a pass-phrase,
# i.e. it must not be encrypted.
#
smtpd_tls_key_file = /etc/pki/tls/private/postfix.key

# Announce STARTTLS support to remote SMTP clients, but do not require that
# clients use TLS encryption (opportunistic TLS inbound).
#
smtpd_tls_security_level = may

# Directory with PEM format Certification Authority certificates that the
# Postfix SMTP client uses to verify a remote SMTP server certificate.
#
smtp_tls_CApath = /etc/pki/tls/certs

# The full pathname of a file containing CA certificates of root CAs
# trusted to sign either remote SMTP server certificates or intermediate CA
# certificates.
#
smtp_tls_CAfile = /etc/pki/tls/certs/ca-bundle.crt

# Use TLS if this is supported by the remote SMTP server, otherwise use
# plaintext (opportunistic TLS outbound).
#
smtp_tls_security_level = may
meta_directory = /etc/postfix
shlib_directory = /usr/lib64/postfix


#Postfixの起動
$ sudo systemctl start postfix

DBダンプの取得&リストア

旧さくらサーバーでの操作手順。

#「redmine_production」DBからダンプファイルを作成
$ mysqldump -u root -p redmine_production > ~/backup/redmine/dump.sql

#一旦ログアウト
$ exit

ローカルマシンから旧さくらVPSと新さくらVPSにリモートで接続し、ダンプファイルをコピーする。

#作成したダンプファイルを新サーバーに移す。(ssh configの設定部分は適宜読み替え）
$ scp -3 old_sakura:/home/hoge/backup/redmine/dump.sql new_sakura:/home/hoge/tmp/

サーバーに接続して引き続きリストア作業を行う。

#redmineのディレクトリに移動して稼働中のunicornを停止する
$ cd /var/www/redmine/
$ bundle exec rails unicorn:stop

#元々のDB名が「redmine_production」のため、対応するDBに接続するようdatabase.ymlの設定を修正する
$ sudo vi /var/www/redmine/config/database.yml

productionセクションのdatabaseを redmine → redmine_production に変更

production:
  adapter: mysql2
  database: redmine_production
  host: localhost
  username: "<%= ENV['REDMINE_DB_USERNAME'] %>"
  password: "<%= ENV['REDMINE_DB_PASSWORD'] %>"
  # Use "utf8" instead of "utfmb4" for MySQL prior to 5.7.7
  encoding: utf8mb4

#mysql接続
$ mysql -u root -p

#「redmine_production」DBの作成、確認
MariaDB [(none)]> create database redmine_production;
MariaDB [(none)]> show databases;

#作成したredmine_productionにアクセスできるようredmineユーザーに権限を付与
MariaDB [(none)]> grant all privileges on redmine_production.* to redmine@localhost;

#終了
MariaDB [(none)]> quit;

#ダンプファイルをredmine_productionにリストア
$ mysql -h localhost -u root -p redmine_production < ~/tmp/dump.sql

#リストアしたDBを再度マイグレーション
$ bundle exec rails db:migrate RAILS_ENV=production

#unicorn起動
$ bundle exec rails unicorn:start

logrotate設定

Railsアプリはそのままだとproduction.logやunicorn.logが肥大化していくので、Linuxのデフォルト機能であるlogrotateコマンドを利用して、ログのローテートを行う。
設定ファイルは `/etc/logrotate.d/redmine`に配置。内容は以下の通り。
参考リンク：https://autovice.jp/articles/115

#設定ファイルの作成
$ sudo vi /etc/logrotate.d/redmine

/var/www/redmine/log/*log {
  daily
  missingok
  rotate 60
  dateext
  dateformat _%Y%m%d
  compress
  copytruncate
  ifempty

  su root root
}

#テストコマンドを実行してエラーや記述ミスがないか確認する
$ sudo /usr/sbin/logrotate -d /etc/logrotate.d/redmine

番外：旧さくらVPSのMySQLにおけるrootパスワードリセット

サーバーにデータをリストアする過程で、移行前のさくらVPSでRedmineのデータが保存されているMySQLのDBに接続しようとしたところ、rootユーザーのパスワード情報が失われていたので再設定を行った。
以下はその手順。
参考リンク：
https://daybydaypg.com/2017/12/11/post-807/

#mysqlの動作確認。動作しているなら一旦停止する
$ service mysqld status
$ sudo service mysqld stop

#mysqlをセーフモードでバックグラウンド起動
$ sudo mysqld_safe --skip-grant-tables &

#rootユーザーでmysqlに接続
$ mysql -u root

#mysqlデータベースに接続
mysql> use mysql;

#userテーブルの定義を確認。mysqlのバージョンによってはパスワードを管理するカラムがpasswordだったりauthentication_stringだったりするので注意する。
mysql> desc user;

+-----------------------+-----------------------------------+------+-----+---------+-------+
| Field                 | Type                              | Null | Key | Default | Extra |
+-----------------------+-----------------------------------+------+-----+---------+-------+
| Host                  | char(60)                          | NO   | PRI |         |       |
| User                  | char(16)                          | NO   | PRI |         |       |
| Password              | char(41)                          | NO   |     |         |       |
| Select_priv           | enum('N','Y')                     | NO   |     | N       |       |
| Insert_priv           | enum('N','Y')                     | NO   |     | N       |       |
| Update_priv           | enum('N','Y')                     | NO   |     | N       |       |
| Delete_priv           | enum('N','Y')                     | NO   |     | N       |       |
| Create_priv           | enum('N','Y')                     | NO   |     | N       |       |
| Drop_priv             | enum('N','Y')                     | NO   |     | N       |       |
| Reload_priv           | enum('N','Y')                     | NO   |     | N       |       |
| Shutdown_priv         | enum('N','Y')                     | NO   |     | N       |       |
| Process_priv          | enum('N','Y')                     | NO   |     | N       |       |
| File_priv             | enum('N','Y')                     | NO   |     | N       |       |
| Grant_priv            | enum('N','Y')                     | NO   |     | N       |       |
| References_priv       | enum('N','Y')                     | NO   |     | N       |       |
| Index_priv            | enum('N','Y')                     | NO   |     | N       |       |
| Alter_priv            | enum('N','Y')                     | NO   |     | N       |       |
| Show_db_priv          | enum('N','Y')                     | NO   |     | N       |       |
| Super_priv            | enum('N','Y')                     | NO   |     | N       |       |
| Create_tmp_table_priv | enum('N','Y')                     | NO   |     | N       |       |
| Lock_tables_priv      | enum('N','Y')                     | NO   |     | N       |       |
| Execute_priv          | enum('N','Y')                     | NO   |     | N       |       |
| Repl_slave_priv       | enum('N','Y')                     | NO   |     | N       |       |
| Repl_client_priv      | enum('N','Y')                     | NO   |     | N       |       |
| Create_view_priv      | enum('N','Y')                     | NO   |     | N       |       |
| Show_view_priv        | enum('N','Y')                     | NO   |     | N       |       |
| Create_routine_priv   | enum('N','Y')                     | NO   |     | N       |       |
| Alter_routine_priv    | enum('N','Y')                     | NO   |     | N       |       |
| Create_user_priv      | enum('N','Y')                     | NO   |     | N       |       |
| Event_priv            | enum('N','Y')                     | NO   |     | N       |       |
| Trigger_priv          | enum('N','Y')                     | NO   |     | N       |       |
| ssl_type              | enum('','ANY','X509','SPECIFIED') | NO   |     |         |       |
| ssl_cipher            | blob                              | NO   |     | NULL    |       |
| x509_issuer           | blob                              | NO   |     | NULL    |       |
| x509_subject          | blob                              | NO   |     | NULL    |       |
| max_questions         | int(11) unsigned                  | NO   |     | 0       |       |
| max_updates           | int(11) unsigned                  | NO   |     | 0       |       |
| max_connections       | int(11) unsigned                  | NO   |     | 0       |       |
| max_user_connections  | int(11) unsigned                  | NO   |     | 0       |       |
+-----------------------+-----------------------------------+------+-----+---------+-------+
39 rows in set (0.00 sec)

#rootユーザーのパスワードを再設定
mysql> update user set password=PASSWORD('*******') where User='root';

#mysqlを終了
mysql> quit;

#mysqlのプロセスを確認し、セーフモードで起動しているmysqlプロセスをキルする。（念の為キルできたかも確認）
$ ps aux | grep mysql
$ sudo kill *****
$ ps aux | grep mysql

#mysqlを通常起動してステータスを確認
$ sudo service mysqld start
$ service mysqld status

#再設定したパスワードで接続できるかテスト。ログインできればOK
$ mysql -u root -p