1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] systemd network.service issues
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20systemd%20network.service%20issues&In-Reply-To=%3C4F6335EF.1080705%40colin.guthr.ie%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="013165.html">
<LINK REL="Next" HREF="013169.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] systemd network.service issues</H1>
<B>Colin Guthrie</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20systemd%20network.service%20issues&In-Reply-To=%3C4F6335EF.1080705%40colin.guthr.ie%3E"
TITLE="[Mageia-dev] systemd network.service issues">mageia at colin.guthr.ie
</A><BR>
<I>Fri Mar 16 13:45:35 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="013165.html">[Mageia-dev] systemd network.service issues
</A></li>
<LI>Next message: <A HREF="013169.html">[Mageia-dev] systemd network.service issues
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#13166">[ date ]</a>
<a href="thread.html#13166">[ thread ]</a>
<a href="subject.html#13166">[ subject ]</a>
<a href="author.html#13166">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>'Twas brillig, and Anssi Hannula at 16/03/12 03:45 did gyre and gimble:
><i> Hi all!
</I>><i>
</I>><i> So, I've just upgraded my home server to mga2/cauldron.
</I>><i>
</I>><i> Something seems fishy in the network.service handling, systemd thinks it
</I>><i> has failed:
</I>><i>
</I>><i> # systemctl status network.service
</I>><i> network.service - LSB: Bring up/down networking
</I>><i> Loaded: loaded (/etc/rc.d/init.d/network)
</I>><i> Active: failed (Result: exit-code) since Fri, 16 Mar 2012
</I>><i> 05:25:09 +0200; 11min ago
</I>><i> CGroup: name=systemd:/system/network.service
</I>><i> ├ 4679 /sbin/ifplugd -I -b -i eth0
</I>><i> ├ 4723 /sbin/ifplugd -I -b -i eth1
</I>><i> └ 5372 /sbin/dhclient -q -lf
</I>><i> /var/lib/dhcp/dhclient-eth0.leases -pf /var/run/dhclient-eth0.pid -cf
</I>><i> /etc/dhclient-eth0.conf...
</I>><i>
</I>><i> Mar 16 05:25:09 delta.onse.fi ifplugd(eth1)[4723]: Using detection mode:
</I>><i> SIOCETHTOOL
</I>><i> Mar 16 05:25:09 delta.onse.fi ifplugd(eth1)[4723]: Initialization
</I>><i> complete, link beat not detected.
</I>><i> Mar 16 05:25:09 delta.onse.fi network[4397]: [161B blob data]
</I>><i> Mar 16 05:25:09 delta.onse.fi network[4397]: [14B blob data]
</I>><i> Mar 16 05:25:13 delta.onse.fi ifplugd(eth0)[4679]: Link beat detected.
</I>><i> Mar 16 05:25:14 delta.onse.fi ifplugd(eth0)[4679]: Executing
</I>><i> '/etc/ifplugd/ifplugd.action eth0 up'.
</I>><i> Mar 16 05:25:15 delta.onse.fi dhclient[5312]: DHCPREQUEST on eth0 to
</I>><i> 255.255.255.255 port 67
</I>><i> Mar 16 05:25:15 delta.onse.fi dhclient[5312]: DHCPACK from 109.204.128.1
</I>><i> Mar 16 05:25:15 delta.onse.fi ifplugd(eth0)[4679]: client: Determining
</I>><i> IP information for eth0... done.
</I>><i> Mar 16 05:25:15 delta.onse.fi ifplugd(eth0)[4679]: Program executed
</I>><i> successfully.
</I>><i>
</I>><i>
</I>><i> Trying to restart it I seem to hit other issues:
</I>><i>
</I>><i> # systemctl restart network.service
</I>><i> Job failed. See system journal and 'systemctl status' for details.
</I>><i> # systemctl status network.service
</I>><i> network.service - LSB: Bring up/down networking
</I>><i> Loaded: loaded (/etc/rc.d/init.d/network)
</I>><i> Active: failed (Result: exit-code) since Fri, 16 Mar 2012
</I>><i> 05:36:39 +0200; 3s ago
</I>><i> Process: 8027 ExecStart=/etc/rc.d/init.d/network start
</I>><i> (code=exited, status=1/FAILURE)
</I>><i> CGroup: name=systemd:/system/network.service
</I>><i> ├ 8195 /sbin/ifplugd -I -b -i eth0
</I>><i> └ 8353 /sbin/dhclient -q -lf
</I>><i> /var/lib/dhcp/dhclient-eth0.leases -pf /var/run/dhclient-eth0.pid -cf
</I>><i> /etc/dhclient-eth0.conf...
</I>><i>
</I>><i> Mar 16 05:36:39 delta.onse.fi network[8027]: RTNETLINK answers: File exists
</I>><i> Mar 16 05:36:39 delta.onse.fi network[8027]: RTNETLINK answers: File exists
</I>><i> Mar 16 05:36:39 delta.onse.fi network[8027]: RTNETLINK answers: File exists
</I>><i> Mar 16 05:36:39 delta.onse.fi network[8027]: RTNETLINK answers: File exists
</I>><i> Mar 16 05:36:39 delta.onse.fi dhclient[8261]: DHCPREQUEST on eth0 to
</I>><i> 255.255.255.255 port 67
</I>><i> Mar 16 05:36:40 delta.onse.fi dhclient[8261]: DHCPACK from 109.204.128.1
</I>><i> Mar 16 05:36:40 delta.onse.fi ifplugd(eth0)[8195]: client: Determining
</I>><i> IP information for eth0...NETLINK: Error: File exists
</I>><i> Mar 16 05:36:40 delta.onse.fi ifplugd(eth0)[8195]: client: done.
</I>><i> Mar 16 05:36:40 delta.onse.fi ifplugd(eth0)[8195]: client: NETLINK:
</I>><i> Error: File exists
</I>><i> Mar 16 05:36:40 delta.onse.fi ifplugd(eth0)[8195]: Program executed
</I>><i> successfully.
</I>><i>
</I>><i> Any ideas? If not, I'll investigate this myself later.
</I>
network.service fails here too, but I've not been able to work out
exactly why. It doens't bother me too much tho' as all my devices are
using network manager!
THat said, it seems that network.service has still started an ifplugd
for my wlan, despite the ifcfg file clearly saying that NM should take
care of that interface... needs some investigating for sure.
><i> On a related note, I also got dropped to emergency console on first
</I>><i> boot, not sure why was that (it didn't tell me the reason... maybe the
</I>><i> reason was in another virtual console, but I didn't remember to check
</I>><i> there at the time). I just exited the console and it continued to boot...
</I>
Interesting. Was it a dracut shell or a systemd one? (sometimes hard to
tell which is which, but the text usually tells you.
Knowing which should help identify why. Does it happen on subsequent boots?
><i> I see the following in systemctl --failed:
</I>><i>
</I>><i> # systemctl --failed
</I>><i> UNIT LOAD ACTIVE SUB JOB DESCRIPTION
</I>><i> bootparamd.service loaded ESC[1;31mfailed failedESC[0m
</I>><i> SYSV: The bootparamd server allows older Sun workstations to net boot
</I>><i> from Linux boxes. It (along with rarp) is rarely used anymore; bootp and
</I>><i> dhcp have mostly replaced both of them.
</I>><i> fedora-loadmodules.service loaded ESC[1;31mfailed failedESC[0m
</I>><i> Load legacy module configuration
</I>
dmorgan reported this as well, but it's a really simple script and
really shouldn't fail.
I think it must be the /etc/rc.modules script that is likely failing
here. Perhaps trying to modprobe a module that no longer exists due to
old configuration? If possible can you debug the fedora-load-modules
service and comment out one half of the script such that only the
rc.modules bit is run and confirm that's where it's bust. Then maybe
work out what in rc.modules is broken. That woudl be useful as it works
fine here.
><i> network.service loaded ESC[1;31mfailed failedESC[0m
</I>><i> LSB: Bring up/down networking
</I>
Mentioned above. Needs to be debugged.
><i> systemd-modules-load.service loaded ESC[1;31mfailed failedESC[0m
</I>><i> Load Kernel Modules
</I>
Yeah this one fails for me too. Not sure why, but maybe because I've
done something stupid and symlinked stuff into /etc/modules-load.d when
I shouldn't. I'll look into it.
Incidentally, just answering your private tmp question from IRC...
This is what Lennart had to say about it:
<mezcalero> coling: the /tmp dir used by PrivateTmp lies beneath /tmp
<mezcalero> coling: hence, if /tmp is cleaned up those private tmps will
be cleaned up too
<mezcalero> coling: since the clean-up is recursive
--
Colin Guthrie
colin(at)mageia.org
<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
Day Job:
Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>
Open Source:
Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A>
PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>
Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="013165.html">[Mageia-dev] systemd network.service issues
</A></li>
<LI>Next message: <A HREF="013169.html">[Mageia-dev] systemd network.service issues
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#13166">[ date ]</a>
<a href="thread.html#13166">[ thread ]</a>
<a href="subject.html#13166">[ subject ]</a>
<a href="author.html#13166">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
