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
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Any progress on the NFS mount problem?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Any%20progress%20on%20the%20NFS%20mount%20problem%3F&In-Reply-To=%3C505CB533.40400%40googlemail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="018814.html">
<LINK REL="Next" HREF="018824.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Any progress on the NFS mount problem?</H1>
<B>Anne Wilson</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Any%20progress%20on%20the%20NFS%20mount%20problem%3F&In-Reply-To=%3C505CB533.40400%40googlemail.com%3E"
TITLE="[Mageia-dev] Any progress on the NFS mount problem?">cannewilson at googlemail.com
</A><BR>
<I>Fri Sep 21 20:42:59 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="018814.html">[Mageia-dev] Any progress on the NFS mount problem?
</A></li>
<LI>Next message: <A HREF="018824.html">[Mageia-dev] Any progress on the NFS mount problem? - One step further
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18822">[ date ]</a>
<a href="thread.html#18822">[ thread ]</a>
<a href="subject.html#18822">[ subject ]</a>
<a href="author.html#18822">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 20/09/12 21:37, Guillaume Rousse wrote:
><i> Le 20/09/2012 20:17, Anne Wilson a écrit :
</I>>>>><i> Looks as though the problem relates to rpc on the server. I
</I>>>>><i> don't mind doing the digging, but can you point me to the
</I>>>>><i> right place to start the hole?
</I>>>><i> I'd try to understand why the nfs daemon (rpc.nfsd) is
</I>>>><i> listening on IPv6 only, whereas the mount daemon (rpc.mountd)
</I>>>><i> is listening both on IPv4 and IPv6.
</I>>>><i>
</I>>><i> Where is that configured?
</I>><i> There is no such 'use IPv6 only' configuration option AFAIK, this
</I>><i> seems rather like a problem. Maybe not specific to NFS, BTW.
</I>><i>
</I>><i> There is no --verbose flag for rpc.nfsd, but you may use rpcdebug
</I>><i> instead: rpcdebug -m nfsd -s all
</I>><i>
</I>><i> Then, restart the nfs-server service, and check your logs.
</I>><i>
</I>Sep 21 19:18:05 borg2 nfs-server[4320]: /etc/sysconfig/nfs-server:
line 11: -d: command not found
Sep 21 19:18:05 borg2 nfs-server[4320]: Stopping NFS kernel daemon
Sep 21 19:18:05 borg2 rpc.mountd[1765]: Caught signal 15,
un-registering and exiting.
Sep 21 19:18:05 borg2 nfs-server[4320]: Stopping rpc.mountd:[ OK ]
Sep 21 19:18:08 borg2 kernel: [110004.094558] nfsd: freeing readahead
buffers.
Sep 21 19:18:08 borg2 kernel: [110004.095309] nfsd: last server has
exited, flushing export cache
Sep 21 19:18:08 borg2 nfs-server[4320]: Stopping nfsd:[ OK ]
Sep 21 19:18:08 borg2 nfs-server[4320]: Unexporting directories for
NFS kernel daemon...
Sep 21 19:18:08 borg2 nfs-server[4359]: /etc/sysconfig/nfs-server:
line 11: -d: command not found
Sep 21 19:18:08 borg2 nfs-server[4359]: Exporting directories for NFS
kernel daemon...
Sep 21 19:18:08 borg2 nfs-server[4359]: Starting NFS kernel daemon
Sep 21 19:18:08 borg2 nfs-server[4359]: Starting nfsdrpc.nfsd: unable
to bind inet TCP socket: errno 98 (Address already in use)
Sep 21 19:18:08 borg2 kernel: [110004.460625] set_max_drc
nfsd_drc_max_mem 765952
Sep 21 19:18:08 borg2 kernel: [110004.461595] nfsd: creating service
Sep 21 19:18:08 borg2 kernel: [110004.461601] nfsd: allocating 32
readahead buffers.
Sep 21 19:18:08 borg2 kernel: [110004.461624] NFSD: Using
/var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Sep 21 19:18:08 borg2 kernel: [110004.461677] NFSD: starting 90-second
grace period
Sep 21 19:18:08 borg2 nfs-server[4359]: [ OK ]
Sep 21 19:18:09 borg2 nfs-server[4359]: Reloading rpc.idmapd[ OK ]
Sep 21 19:18:09 borg2 rpc.mountd[4403]: Version 1.2.5 starting
Sep 21 19:18:09 borg2 nfs-server[4359]: Starting rpc.mountd[ OK ]
Sep 21 19:19:39 borg2 kernel: [110094.560075] NFSD: laundromat service
- - starting
Sep 21 19:19:39 borg2 kernel: [110094.560086] NFSD: end of grace period
Sep 21 19:19:39 borg2 kernel: [110094.580278] NFSD: laundromat_main -
sleeping for 90 seconds
Sep 21 19:21:06 borg2 dovecot: imap-login: Disconnected (no auth
attempts): rip=192.168.0.40, lip=192.168.0.40, TLS handshaking:
Disconnected
Sep 21 19:21:09 borg2 kernel: [110184.800046] NFSD: laundromat service
- - starting
Sep 21 19:21:09 borg2 kernel: [110184.800060] NFSD: laundromat_main -
sleeping for 90 seconds
Sep 21 19:22:39 borg2 kernel: [110275.040069] NFSD: laundromat service
- - starting
Sep 21 19:22:39 borg2 kernel: [110275.040083] NFSD: laundromat_main -
sleeping for 90 seconds
Sep 21 19:24:09 borg2 kernel: [110365.280038] NFSD: laundromat service
- - starting
Sep 21 19:24:09 borg2 kernel: [110365.280047] NFSD: laundromat_main -
sleeping for 90 seconds
The Line 11 that it complains about says
RPCMOUNTD_OPTIONS="--port 4003" -d
I *don't think* I edited that, but after all the reading around I've
done it is just possible that I did. I do feel, though that I saw
that port mentioned and felt that I shouldn't edit it, since I haven't
a clue which of the many ports mentioned in the logs is the one it's
expecting. Sorry I can be more specific. I've removed the '-d' and
restarted.
Sep 21 19:30:06 borg2 nfs-server[5169]: Stopping NFS kernel daemon
Sep 21 19:30:06 borg2 rpc.mountd[4403]: Caught signal 15,
un-registering and exiting.
Sep 21 19:30:06 borg2 nfs-server[5169]: Stopping rpc.mountd:[ OK ]
Sep 21 19:30:09 borg2 kernel: [110725.276891] nfsd: freeing readahead
buffers.
Sep 21 19:30:09 borg2 kernel: [110725.277654] nfsd: last server has
exited, flushing export cache
Sep 21 19:30:09 borg2 nfs-server[5169]: Stopping nfsd:[ OK ]
Sep 21 19:30:09 borg2 nfs-server[5169]: Unexporting directories for
NFS kernel daemon...
Sep 21 19:30:10 borg2 nfs-server[5208]: Exporting directories for NFS
kernel daemon...
Sep 21 19:30:10 borg2 nfs-server[5208]: Starting NFS kernel daemon
Sep 21 19:30:10 borg2 nfs-server[5208]: Starting nfsdrpc.nfsd: unable
to bind inet TCP socket: errno 98 (Address already in use)
Sep 21 19:30:10 borg2 kernel: [110725.681229] set_max_drc
nfsd_drc_max_mem 765952
Sep 21 19:30:10 borg2 kernel: [110725.683544] nfsd: creating service
Sep 21 19:30:10 borg2 kernel: [110725.683551] nfsd: allocating 32
readahead buffers.
Sep 21 19:30:10 borg2 kernel: [110725.683569] NFSD: Using
/var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Sep 21 19:30:10 borg2 kernel: [110725.683610] NFSD: starting 90-second
grace period
Sep 21 19:30:10 borg2 nfs-server[5208]: [ OK ]
Sep 21 19:30:10 borg2 nfs-server[5208]: Reloading rpc.idmapd[ OK ]
Sep 21 19:30:10 borg2 rpc.mountd[5251]: Version 1.2.5 starting
Sep 21 19:30:10 borg2 nfs-server[5208]: Starting rpc.mountd[ OK ]
That looks better, I think? However, 'mount -a' on the client still
doesn't connect.
>>><i> BTW, you're also lacking rpc.idmapd, which is mandatory for
</I>>>><i> NFSv4 support, but that's a secondary issue.
</I>>>><i>
</I>>><i> I've done a lot of googling, and most of what I found was
</I>>><i> ubuntu-specific. However, I found a recent entry saying that it
</I>>><i> is provided by nfs-utils - that that is installed. nfs-common
</I>>><i> and nfs-server are both running, according to mcc.
</I>><i> nfs-common service, as 90% of similar services, use an
</I>><i> /etc/sysconfig/nfs-common congiguration file. Just set NEEDIDMAPD
</I>><i> to yes to ensure it runs.
</I>><i>
</I>><i> Also, you'd better forget GUIs when trying to debug issue, and
</I>><i> ressort to command line instead, you'll have much more control and
</I>><i> feedback.
</I>><i>
</I>That's fine. I prefer the command line where it is an area that I've
used before, but I'm nervous of it when I don't really know what I'm
doing, and assume that MCC will safeguard against my errors.
>><i> Following another lead, I tried to locate nfsmount.conf and
</I>>><i> found that I had a backup containing it, and a man page, but no
</I>>><i> actual file.
</I>><i> That's an interesting point, it means your actual setup differs
</I>><i> from the default package one. Try 'rpm --verify nfs-utils' and
</I>><i> 'rpm --verify nfs-utils-client' to check what has been modified
</I>><i> exactly.
</I>><i>
</I>>><i> This is incredibly difficult. Users shouldn't have to jump
</I>>><i> through this number of hoops to do something so basic to
</I>>><i> productivity :-(
</I>><i> I'm not sure what users should have to do or not, but I'm quite
</I>><i> sure this kind of imprecations won't help you solve the issue.
</I>><i>
</I>Of course :-) but you have to admit it was a pretty mild statement of
my frustration :-)
><i> If everything else fails, you may also inhibit IPv6 completly:
</I>
I doubt if that would cause any problems - at least not for some time yet.
><i> just add 'install ipv6 /bin/true' in any file under
</I>><i> /etc/modprobe.d, and reboot.
</I>><i>
</I>Really? That sounds counter-intuitive. Can you explain?
And if I inhibit IPv6 completely, will that automatically enable IPv4,
or am I still looking for the reason for that lack?
@AL13N -
><i> maybe those services were started when there was no ipv4 set up
</I>><i> yet, and thus was ignored?
</I>
I hesitate to say that anything is impossible, but this was a clean,
bog-standard Mageia2 install. I can't think why that should be so,
can you?
This is seriously impeding my work, but at least I'll have learned
from it :-)
Anne
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - <A HREF="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</A>
iEYEARECAAYFAlBctTMACgkQj93fyh4cnBf0sQCdGDjFZcuk7dlgJx4drpACNP3c
sfcAn3oe1iI5Ny0rNX1qGSX0rvS3qm7R
=0Bbq
-----END PGP SIGNATURE-----
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="018814.html">[Mageia-dev] Any progress on the NFS mount problem?
</A></li>
<LI>Next message: <A HREF="018824.html">[Mageia-dev] Any progress on the NFS mount problem? - One step further
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18822">[ date ]</a>
<a href="thread.html#18822">[ thread ]</a>
<a href="subject.html#18822">[ subject ]</a>
<a href="author.html#18822">[ 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>
|
