質問編集履歴

情報の追加

2020/10/13 06:22

投稿

syosinnsya_

スコア5

test CHANGED Viewed

File without changes

test CHANGED Viewed

@@ -4,6 +4,10 @@
+OS:CentOS 7.2
 色々なサイトに載っている手順を参考にして構築を進めていたのですが、
 named.confを編集し、ゾーンファイルを作成してサービスを再起動した際に
@@ -64,14 +68,6 @@
-###CentOS version
-CentOS Linux release 7.2.1511 (Core)
-###試したこと
 社内にインフラのことが解る人が一人も居ないため、頼れるのはネットの情報のみです。
 調べてもなかなか解決法が見つからず困ったため、NetwokrManagerを入れ直しました。
@@ -80,6 +76,8 @@
 ###NetworkManagerの情報
@@ -122,112 +120,226 @@
-NetworkManagerのエラー以外にも、firewalldとiptablesのエラーが発生しています。
-以下エラー内容です。もしNetworkManagerと何らかの関係があるようでしたら
-ご教授いただければ幸いです。
-###firewalldのエラー
-```
-[root@localhost ~]# systemctl status firewalld -l
-● firewalld.service - firewalld - dynamic firewall daemon
-   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
-   Active: active (running) since 月 2020-10-12 14:45:00 JST; 1h 10min ago
- Main PID: 16344 (firewalld)
-   CGroup: /system.slice/firewalld.service
-           └─16344 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid
-10月 12 14:45:01 localhost.localdomain firewalld[16344]: 2020-10-12 14:45:01 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -w --table filter --delete FORWARD --destination 192.168.122.0/24 --out-interface virbr0 --match conntrack --ctstate ESTABLISHED,RELATED --jump ACCEPT' failed: iptables: Bad rule (does a matching rule exist in that chain?).
-10月 12 14:45:01 localhost.localdomain firewalld[16344]: 2020-10-12 14:45:01 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -w --table filter --delete FORWARD --source 192.168.122.0/24 --in-interface virbr0 --jump ACCEPT' failed: iptables: Bad rule (does a matching rule exist in that chain?).
-10月 12 14:45:01 localhost.localdomain firewalld[16344]: 2020-10-12 14:45:01 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -w --table filter --delete FORWARD --in-interface virbr0 --out-interface virbr0 --jump ACCEPT' failed: iptables: Bad rule (does a matching rule exist in that chain?).
-10月 12 14:45:01 localhost.localdomain firewalld[16344]: 2020-10-12 14:45:01 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -w --table filter --delete FORWARD --out-interface virbr0 --jump REJECT' failed: iptables: No chain/target/match by that name.
-10月 12 14:45:01 localhost.localdomain firewalld[16344]: 2020-10-12 14:45:01 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -w --table filter --delete FORWARD --in-interface virbr0 --jump REJECT' failed: iptables: No chain/target/match by that name.
-10月 12 14:45:01 localhost.localdomain firewalld[16344]: 2020-10-12 14:45:01 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -w --table filter --delete INPUT --in-interface virbr0 --protocol udp --destination-port 53 --jump ACCEPT' failed: iptables: Bad rule (does a matching rule exist in that chain?).
-10月 12 14:45:01 localhost.localdomain firewalld[16344]: 2020-10-12 14:45:01 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -w --table filter --delete INPUT --in-interface virbr0 --protocol tcp --destination-port 53 --jump ACCEPT' failed: iptables: Bad rule (does a matching rule exist in that chain?).
-10月 12 14:45:01 localhost.localdomain firewalld[16344]: 2020-10-12 14:45:01 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -w --table filter --delete OUTPUT --out-interface virbr0 --protocol udp --destination-port 68 --jump ACCEPT' failed: iptables: Bad rule (does a matching rule exist in that chain?).
-10月 12 14:45:01 localhost.localdomain firewalld[16344]: 2020-10-12 14:45:01 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -w --table filter --delete INPUT --in-interface virbr0 --protocol udp --destination-port 67 --jump ACCEPT' failed: iptables: Bad rule (does a matching rule exist in that chain?).
-10月 12 14:45:01 localhost.localdomain firewalld[16344]: 2020-10-12 14:45:01 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -w --table filter --delete INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT' failed: iptables: Bad rule (does a matching rule exist in that chain?).
-```
-###iptablesのエラー
-```
-[root@localhost ~]# systemctl status iptables
-● iptables.service - IPv4 firewall with iptables
-   Loaded: loaded (/usr/lib/systemd/system/iptables.service; disabled; vendor preset: disabled)
-   Active: failed (Result: exit-code) since 金 2020-10-09 15:15:26 JST; 3 days ago
- Main PID: 31799 (code=exited, status=1/FAILURE)
-10月 09 15:15:26 localhost.localdomain systemd[1]: Starting IPv4 firewall with iptables...
-10月 09 15:15:26 localhost.localdomain iptables.init[31799]: iptables: Applying firewall rules: iptables-restore v1.4.21: unknown arguments found on commandline
-10月 09 15:15:26 localhost.localdomain iptables.init[31799]: Error occurred at line: 12
-10月 09 15:15:26 localhost.localdomain iptables.init[31799]: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
-10月 09 15:15:26 localhost.localdomain systemd[1]: iptables.service: main process exited, code=exited, status=1/FAILURE
-10月 09 15:15:26 localhost.localdomain systemd[1]: Failed to start IPv4 firewall with iptables.
-10月 09 15:15:26 localhost.localdomain systemd[1]: Unit iptables.service entered failed state.
-10月 09 15:15:26 localhost.localdomain systemd[1]: iptables.service failed.
-10月 09 15:15:26 localhost.localdomain iptables.init[31799]: [失敗]
-```
-firewalldのエラーに関しては何を言っているのかさえさっぱり解らないため、
-エラーの意味だけでも教えていただけると大変助かります。
-よろしくお願い致します。
+###10月13日　追記
+以下のコマンドを実行してNetworkManagerについての情報を確認しました。
+###cat /var/log/messages
+```
+Oct 12 15:31:00 localhost systemd: Starting Network Manager...
+Oct 12 15:31:00 localhost NetworkManager[17643]: <info>  [1602484260.8844] NetworkManager (version 1.18.4-3.el7) is starting... (after a restart)
+Oct 12 15:31:00 localhost NetworkManager[17643]: <info>  [1602484260.8845] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-slaves-order.conf)
+Oct 12 15:31:00 localhost NetworkManager[17643]: <info>  [1602484260.8881] exiting (error)
+Oct 12 15:31:00 localhost systemd: NetworkManager.service: main process exited, code=exited, status=1/FAILURE
+Oct 12 15:31:00 localhost systemd: Failed to start Network Manager.
+Oct 12 15:31:00 localhost systemd: Unit NetworkManager.service entered failed state.
+Oct 12 15:31:00 localhost systemd: NetworkManager.service failed.
+Oct 12 15:31:01 localhost systemd: NetworkManager.service holdoff time over, scheduling restart.
+Oct 12 15:31:01 localhost systemd: start request repeated too quickly for NetworkManager.service
+Oct 12 15:31:01 localhost systemd: Failed to start Network Manager.
+Oct 12 15:31:01 localhost systemd: Unit NetworkManager.service entered failed state.
+Oct 12 15:31:01 localhost systemd: NetworkManager.service failed.
+```
+###journalctl -u NetworkManager.service --no-pager
+```
+10月 12 15:31:00 localhost.localdomain systemd[1]: Starting Network Manager...
+10月 12 15:31:00 localhost.localdomain NetworkManager[17643]: <info>  [1602484260.8844] NetworkManager (version 1.18.4-3.el7) is starting... (after a restart)
+10月 12 15:31:00 localhost.localdomain NetworkManager[17643]: <info>  [1602484260.8845] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-slaves-order.conf)
+10月 12 15:31:00 localhost.localdomain NetworkManager[17643]: <info>  [1602484260.8881] exiting (error)
+10月 12 15:31:00 localhost.localdomain systemd[1]: NetworkManager.service: main process exited, code=exited, status=1/FAILURE
+10月 12 15:31:00 localhost.localdomain systemd[1]: Failed to start Network Manager.
+10月 12 15:31:00 localhost.localdomain systemd[1]: Unit NetworkManager.service entered failed state.
+10月 12 15:31:00 localhost.localdomain systemd[1]: NetworkManager.service failed.
+10月 12 15:31:01 localhost.localdomain systemd[1]: NetworkManager.service holdoff time over, scheduling restart.
+10月 12 15:31:01 localhost.localdomain systemd[1]: start request repeated too quickly for NetworkManager.service
+10月 12 15:31:01 localhost.localdomain systemd[1]: Failed to start Network Manager.
+10月 12 15:31:01 localhost.localdomain systemd[1]: Unit NetworkManager.service entered failed state.
+10月 12 15:31:01 localhost.localdomain systemd[1]: NetworkManager.service failed.
+```
+###rpm -V NetworkManager
+```
+このコマンドでは何も表示されませんでした。
+```
+###systemctl list-unit-files | grep NetworkManager
+```
+NetworkManager-dispatcher.service          enabled
+NetworkManager-wait-online.service         masked
+NetworkManager.service                     enabled
+```
+###cat /etc/NetworkManager/NetworkManager.conf
+```
+# Configuration file for NetworkManager.
+#
+# See "man 5 NetworkManager.conf" for details.
+#
+# The directories /usr/lib/NetworkManager/conf.d/ and /var/run/NetworkManager/conf.d/
+# can contain additional configuration snippets installed by packages. These files are
+# read before NetworkManager.conf and have thus lowest priority.
+# The directory /etc/NetworkManager/conf.d/ can contain additional configuration
+# snippets. Those snippets are merged last and overwrite the settings from this main
+# file.
+#
+# The files within one conf.d/ directory are read in asciibetical order.
+#
+# If /etc/NetworkManager/conf.d/ contains a file with the same name as
+# /usr/lib/NetworkManager/conf.d/, the latter file is shadowed and thus ignored.
+# Hence, to disable loading a file from /usr/lib/NetworkManager/conf.d/ you can
+# put an empty file to /etc with the same name. The same applies with respect
+# to the directory /var/run/NetworkManager/conf.d where files in /var/run shadow
+# /usr/lib and are themselves shadowed by files under /etc.
+#
+# If two files define the same key, the one that is read afterwards will overwrite
+# the previous one.
+[main]
+#plugins=ifcfg-rh,ibft
+[logging]
+# When debugging NetworkManager, enabling debug logging is of great help.
+#
+# Logfiles contain no passwords and little sensitive information. But please
+# check before posting the file online. You can also personally hand over the
+# logfile to a NM developer to treat it confidential. Meet us on #nm on freenode.
+# Please post full logfiles except minimal modifications of private data.
+#
+# You can also change the log-level at runtime via
+#   $ nmcli general logging level TRACE domains ALL
+# However, usually it's cleaner to enable debug logging
+# in the configuration and restart NetworkManager so that
+# debug logging is enabled from the start.
+#
+# You will find the logfiles in syslog, for example via
+#   $ journalctl -u NetworkManager
+#
+# Note that debug logging of NetworkManager can be quite verbose. Some messages
+# might be rate-limited by the logging daemon (see RateLimitIntervalSec, RateLimitBurst
+# in man journald.conf).
+#
+#level=TRACE
+#domains=ALL
+```
+###journalctl -u NetworkManager
+NetworkManagerが起動しなくなったのが10月6日の17時以降なので、以下の内容が関係しているのかな？と思いましたが良く分からず…取り合えず載せておきます。すみません。
+```
+10月 06 17:00:16 localhost.localdomain NetworkManager[793]: <info>  VPN: unloaded org.freedesktop.NetworkManager.libreswan
+```
+文字数の関係でfirewalldとiptablesのエラー内容は削除いたしました。