Help us understand the problem. What is going on with this article?

メモ(RHEL7.2)

More than 3 years have passed since last update.

journalctl -p warning を潰していく

dumpable

kernel: Unsafe core_pattern used with suid_dumpable=2. Pipe handler or fully qualified core dump path required.

Linux 3.6 以降では、/proc/sys/fs/suid_dumpable が 2 ("suidsafe") に設定されている場合、テンプレートは、絶対パス名 (先頭に '/' 文字があるパス名) かパイプ (以下で説明) のどちらかでなければならない。

https://linuxjm.osdn.jp/html/LDP_man-pages/man5/core.5.html

対応

sysctl.conf
kernel.core_pattern=/export/cores/core.%e.%t.%p
fs.suid_dumpable=2

設定したけど変わらず…なぜ?

anaconda-generator failed

systemd[449]: /usr/lib/systemd/system-generators/anaconda-generator failed with error code 1.

対応

This message can be ignored.
As a workaround, anaconda-core can be uninstalled.
https://access.redhat.com/solutions/2077823

anacondaは使用するため無視

lpユーザー削除時の対応 

lpを削除すると以下のメッセージが出力。(これ以外にもある)

dbus-daemon[575]: Unknown group "lp" in message bus configuration file

systemd-udevd[508]: specified group 'lp' unknown

以下のファイルを削除。

  • /usr/lib/tmpfiles.d/cups-lp.conf
  • /usr/lib/tmpfiles.d/cups.conf
  • /etc/dbus-1/system.d/bluetooth.conf

以下のファイルを変更(lp部分をコメントアウトする)

  • /usr/lib/udev/rules.d/50-udev-default.rules
  • /usr/lib/udev/rules.d/56-hpmud.rules
  • /usr/lib/udev/rules.d/99-systemd.rules
/usr/lib/udev/rules.d/50-udev-default.rules
#KERNEL=="parport[0-9]*", GROUP="lp"
#SUBSYSTEM=="printer", KERNEL=="lp*", GROUP="lp"
#SUBSYSTEM=="ppdev", GROUP="lp"
#KERNEL=="lp[0-9]*", GROUP="lp"
#KERNEL=="irlpt[0-9]*", GROUP="lp"
#SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{ID_USB_INTERFACES}=="*:0701??:*", GROUP="lp"
/usr/lib/udev/rules.d/99-systemd.rules
#SUBSYSTEM=="printer", TAG+="systemd", ENV{SYSTEMD_WANTS}+="printer.target"
#SUBSYSTEM=="usb", KERNEL=="lp*", TAG+="systemd", ENV{SYSTEMD_WANTS}+="printer.target"
#SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="systemd", ENV{SYSTEMD_WANTS}+="printer.target"
/usr/lib/udev/rules.d/56-hpmud.rules
#SUBSYSTEM=="ppdev", OWNER="root", GROUP="lp", MODE="0660"
#ATTR{idVendor}=="03f0", ATTR{idProduct}=="????", OWNER="root", GROUP="lp", MODE="0660", ENV{sane_hpaio}="yes", ENV{libsane_matched}="yes", ENV{hp_test}="yes", ENV{ID_HPLIP}="1"

Host SMBus controller

journal
kernel: piix4_smbus 0000:00:07.3: Host SMBus controller not enabled!

対応

The message means to fail getting property information from SMBus while booting a system. However, since the system is a virtual guest machine, seems that was failed.
You can try blacklisting the i2c-piix4 kernel module as follows:
https://access.redhat.com/solutions/42741

→VM固有のエラー。initramfsの修正が入るのでエラーみたら無視対応。

systemd-tmpfilesのエラー

systemd-version
host# rpm -q  systemd
systemd-219-19.el7.x86_64
jounarl
 systemd-tmpfiles[95]: Failed to parse ACL "d:group:adm:r-x,d:group:wheel:r-x": Invalid argument. Ignoring
 systemd-tmpfiles[95]: Failed to parse ACL "group:adm:r-x,group:wheel:r-x": Invalid argument. Ignoring
 systemd-tmpfiles[95]: Failed to parse ACL "d:group:adm:r-x,d:group:wheel:r-x": Invalid argument. Ignoring
 systemd-tmpfiles[95]: Failed to parse ACL "group:adm:r-x,group:wheel:r-x": Invalid argument. Ignoring

対応

This happens in the initramfs, where some groups are not defined, and acl parsing fails. Unfortunately the parsing code (libacl) does not return meaningful error codes, so we don't have a way to differentiate between a "non-error" like missing groups, which we would simply ignore, and other errors. Some solution will have to be implemented in systemd upstream to deal with this properly.
https://bugzilla.redhat.com/show_bug.cgi?id=1241997

→systemdの改修待ち
GitHubでは改修完了
https://github.com/haraldh/dracut/commit/1bcb63f97c0168ff91b9d930bb31ad32fb1f2976

SSHログイン時に出力

/var/log/messages
dbus-daemon: dbus[591]: [system] Activating service name='org.freedesktop.problems' (using servicehelper)
dbus[591]: [system] Successfully activated service 'org.freedesktop.problems'
dbus-daemon: dbus[591]: [system] Successfully activated service 'org.freedesktop.problems'

D-Bus

D-Bus とは、アプリケーション間で通信を行う「プロセス間通信」の機構のひとつです。

HAL や NetworkManager などのデーモンとの通信で用いられる他、 KDE や GNOME といったデスクトップ環境でも使われています。
http://www.usupi.org/sysad/175.html

bashでorg.freedesktop.problems.GetProblemsを実施
dbus-send --system --type=method_call --print-reply --dest=org.freedesktop.problems /org/freedesktop/problems org.freedesktop.problems.GetProblems

journalctl

オプション 機能
--no-pager pager機能無し
--full 出力を plain text にする
-a/--all 出力を完全表示
-f/--follow tail -fのように表示
-n number numberで指定した行数を最新から表示
-r 新しい順に表示

http://1bed.saloon.jp/?p=684

Gin
Why not register and get more from Qiita?
  1. We will deliver articles that match you
    By following users and tags, you can catch up information on technical fields that you are interested in as a whole
  2. you can read useful information later efficiently
    By "stocking" the articles you like, you can search right away
Comments
No comments
Sign up for free and join this conversation.
If you already have a Qiita account
Why do not you register as a user and use Qiita more conveniently?
You need to log in to use this function. Qiita can be used more conveniently after logging in.
You seem to be reading articles frequently this month. Qiita can be used more conveniently after logging in.
  1. We will deliver articles that match you
    By following users and tags, you can catch up information on technical fields that you are interested in as a whole
  2. you can read useful information later efficiently
    By "stocking" the articles you like, you can search right away
ユーザーは見つかりませんでした