teratail
回答率
85.30%
質問するログイン新規登録
トップに関する質問CentOS7　NetworkManager.serviceが起動しません。

編集履歴

質問編集履歴

1

情報の追加

2020/10/13 06:22

投稿

syosinnsya_
syosinnsya_

スコア5

title CHANGED
File without changes
body CHANGED
@@ -1,6 +1,8 @@
1
1
  社内でBINDインストール～DNSサーバー構築の学習をしています。
2
2
  WindowsからSSHクライアントソフトでサーバーに接続して操作しています。
3
3
 
4
+ OS:CentOS 7.2
5
+
4
6
  色々なサイトに載っている手順を参考にして構築を進めていたのですが、
5
7
  named.confを編集し、ゾーンファイルを作成してサービスを再起動した際に
6
8
  何らかのエラーが発生し、インターネットに繋がらなくなりました。
@@ -31,14 +33,11 @@
31
33
  ```
32
34
 
33
35
 
34
- ###CentOS version
35
- CentOS Linux release 7.2.1511 (Core)
36
-
37
- ###試したこと
38
36
  社内にインフラのことが解る人が一人も居ないため、頼れるのはネットの情報のみです。
39
37
  調べてもなかなか解決法が見つからず困ったため、NetwokrManagerを入れ直しました。
40
38
  （今思うとこれがいけなかったかもしれません...。）
41
39
 
40
+
42
41
  ###NetworkManagerの情報
43
42
 
44
43
  ```
@@ -60,58 +59,115 @@
60
59
 
61
60
  ```
62
61
 
63
- NetworkManagerのエラー以外にも、firewalldとiptablesのエラーが発生しています。
62
+ ###10月13日　追記
64
- 以下エラー内容です。もしNetworkManagerと何らかの関係があるようでしたら
63
+ 以下のコマンドを実行してNetworkManagerについての情報を確認しました。
65
- ご教授いただければ幸いです。
66
64
 
67
- ###firewalldのエラー
65
+ ###cat /var/log/messages
68
66
 
69
67
  ```
68
+ Oct 12 15:31:00 localhost systemd: Starting Network Manager...
69
+ Oct 12 15:31:00 localhost NetworkManager[17643]: <info> [1602484260.8844] NetworkManager (version 1.18.4-3.el7) is starting... (after a restart)
70
+ Oct 12 15:31:00 localhost NetworkManager[17643]: <info> [1602484260.8845] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-slaves-order.conf)
71
+ Oct 12 15:31:00 localhost NetworkManager[17643]: <info> [1602484260.8881] exiting (error)
72
+ Oct 12 15:31:00 localhost systemd: NetworkManager.service: main process exited, code=exited, status=1/FAILURE
73
+ Oct 12 15:31:00 localhost systemd: Failed to start Network Manager.
74
+ Oct 12 15:31:00 localhost systemd: Unit NetworkManager.service entered failed state.
75
+ Oct 12 15:31:00 localhost systemd: NetworkManager.service failed.
76
+ Oct 12 15:31:01 localhost systemd: NetworkManager.service holdoff time over, scheduling restart.
77
+ Oct 12 15:31:01 localhost systemd: start request repeated too quickly for NetworkManager.service
78
+ Oct 12 15:31:01 localhost systemd: Failed to start Network Manager.
79
+ Oct 12 15:31:01 localhost systemd: Unit NetworkManager.service entered failed state.
80
+ Oct 12 15:31:01 localhost systemd: NetworkManager.service failed.
70
81
 
71
- [root@localhost ~]# systemctl status firewalld -l
72
- ● firewalld.service - firewalld - dynamic firewall daemon
73
- Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
74
- Active: active (running) since 月 2020-10-12 14:45:00 JST; 1h 10min ago
75
- Main PID: 16344 (firewalld)
82
+ ```
76
- CGroup: /system.slice/firewalld.service
77
- └─16344 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid
78
83
 
79
- 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?).
80
- 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?).
81
- 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?).
82
- 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.
83
- 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.
84
- 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?).
85
- 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?).
86
- 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?).
87
- 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?).
88
- 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?).
84
+ ###journalctl -u NetworkManager.service --no-pager
85
+ ```
86
+ 10月 12 15:31:00 localhost.localdomain systemd[1]: Starting Network Manager...
87
+ 10月 12 15:31:00 localhost.localdomain NetworkManager[17643]: <info> [1602484260.8844] NetworkManager (version 1.18.4-3.el7) is starting... (after a restart)
88
+ 10月 12 15:31:00 localhost.localdomain NetworkManager[17643]: <info> [1602484260.8845] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-slaves-order.conf)
89
+ 10月 12 15:31:00 localhost.localdomain NetworkManager[17643]: <info> [1602484260.8881] exiting (error)
90
+ 10月 12 15:31:00 localhost.localdomain systemd[1]: NetworkManager.service: main process exited, code=exited, status=1/FAILURE
91
+ 10月 12 15:31:00 localhost.localdomain systemd[1]: Failed to start Network Manager.
92
+ 10月 12 15:31:00 localhost.localdomain systemd[1]: Unit NetworkManager.service entered failed state.
93
+ 10月 12 15:31:00 localhost.localdomain systemd[1]: NetworkManager.service failed.
94
+ 10月 12 15:31:01 localhost.localdomain systemd[1]: NetworkManager.service holdoff time over, scheduling restart.
95
+ 10月 12 15:31:01 localhost.localdomain systemd[1]: start request repeated too quickly for NetworkManager.service
96
+ 10月 12 15:31:01 localhost.localdomain systemd[1]: Failed to start Network Manager.
97
+ 10月 12 15:31:01 localhost.localdomain systemd[1]: Unit NetworkManager.service entered failed state.
98
+ 10月 12 15:31:01 localhost.localdomain systemd[1]: NetworkManager.service failed.
99
+ ```
100
+ ###rpm -V NetworkManager
101
+ ```
102
+ このコマンドでは何も表示されませんでした。
103
+ ```
89
104
 
105
+ ###systemctl list-unit-files | grep NetworkManager
90
106
  ```
107
+ NetworkManager-dispatcher.service enabled
108
+ NetworkManager-wait-online.service masked
109
+ NetworkManager.service enabled
110
+ ```
91
111
 
92
- ###iptablesのエラー
112
+ ###cat /etc/NetworkManager/NetworkManager.conf
93
-
94
113
  ```
114
+ # Configuration file for NetworkManager.
115
+ #
116
+ # See "man 5 NetworkManager.conf" for details.
117
+ #
118
+ # The directories /usr/lib/NetworkManager/conf.d/ and /var/run/NetworkManager/conf.d/
119
+ # can contain additional configuration snippets installed by packages. These files are
120
+ # read before NetworkManager.conf and have thus lowest priority.
121
+ # The directory /etc/NetworkManager/conf.d/ can contain additional configuration
122
+ # snippets. Those snippets are merged last and overwrite the settings from this main
123
+ # file.
124
+ #
125
+ # The files within one conf.d/ directory are read in asciibetical order.
126
+ #
127
+ # If /etc/NetworkManager/conf.d/ contains a file with the same name as
128
+ # /usr/lib/NetworkManager/conf.d/, the latter file is shadowed and thus ignored.
129
+ # Hence, to disable loading a file from /usr/lib/NetworkManager/conf.d/ you can
130
+ # put an empty file to /etc with the same name. The same applies with respect
131
+ # to the directory /var/run/NetworkManager/conf.d where files in /var/run shadow
132
+ # /usr/lib and are themselves shadowed by files under /etc.
133
+ #
134
+ # If two files define the same key, the one that is read afterwards will overwrite
135
+ # the previous one.
95
136
 
96
- [root@localhost ~]# systemctl status iptables
137
+ [main]
97
- ● iptables.service - IPv4 firewall with iptables
138
+ #plugins=ifcfg-rh,ibft
98
- Loaded: loaded (/usr/lib/systemd/system/iptables.service; disabled; vendor preset: disabled)
99
- Active: failed (Result: exit-code) since 金 2020-10-09 15:15:26 JST; 3 days ago
100
- Main PID: 31799 (code=exited, status=1/FAILURE)
101
139
 
102
- 10月 09 15:15:26 localhost.localdomain systemd[1]: Starting IPv4 firewall with iptables...
103
- 10月 09 15:15:26 localhost.localdomain iptables.init[31799]: iptables: Applying firewall rules: iptables-restore v1.4.21: unknown arguments found on commandline
104
- 10月 09 15:15:26 localhost.localdomain iptables.init[31799]: Error occurred at line: 12
105
- 10月 09 15:15:26 localhost.localdomain iptables.init[31799]: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
106
- 10月 09 15:15:26 localhost.localdomain systemd[1]: iptables.service: main process exited, code=exited, status=1/FAILURE
107
- 10月 09 15:15:26 localhost.localdomain systemd[1]: Failed to start IPv4 firewall with iptables.
108
- 10月 09 15:15:26 localhost.localdomain systemd[1]: Unit iptables.service entered failed state.
109
- 10月 09 15:15:26 localhost.localdomain systemd[1]: iptables.service failed.
110
- 10月 09 15:15:26 localhost.localdomain iptables.init[31799]: [失敗]
111
140
 
141
+ [logging]
142
+ # When debugging NetworkManager, enabling debug logging is of great help.
143
+ #
144
+ # Logfiles contain no passwords and little sensitive information. But please
145
+ # check before posting the file online. You can also personally hand over the
146
+ # logfile to a NM developer to treat it confidential. Meet us on #nm on freenode.
147
+ # Please post full logfiles except minimal modifications of private data.
148
+ #
149
+ # You can also change the log-level at runtime via
150
+ # $ nmcli general logging level TRACE domains ALL
151
+ # However, usually it's cleaner to enable debug logging
152
+ # in the configuration and restart NetworkManager so that
153
+ # debug logging is enabled from the start.
154
+ #
155
+ # You will find the logfiles in syslog, for example via
156
+ # $ journalctl -u NetworkManager
157
+ #
158
+ # Note that debug logging of NetworkManager can be quite verbose. Some messages
159
+ # might be rate-limited by the logging daemon (see RateLimitIntervalSec, RateLimitBurst
160
+ # in man journald.conf).
161
+ #
162
+ #level=TRACE
163
+ #domains=ALL
112
164
  ```
113
165
 
114
- firewalldのエラーに関しては何を言っているのかさえさっぱり解らないため、
115
- エラーの意味だけでも教えていただけると大変助かります。
166
+ ###journalctl -u NetworkManager
167
+ NetworkManagerが起動しなくなったのが10月6日の17時以降なので、以下の内容が関係しているのかな？と思いましたが良く分からず…取り合えず載せておきます。すみません。
168
+ ```
169
+ 10月 06 17:00:16 localhost.localdomain NetworkManager[793]: <info> VPN: unloaded org.freedesktop.NetworkManager.libreswan
116
170
 
171
+ ```
172
+
117
- よろしくお願い致します。
173
+ 文字数の関係でfirewalldとiptablesのエラー内容は削除いたしました。