`<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix"><tt>Hi,<br>
<br>
It would be good to know how to work around this without having
to reboot the server.<br>
<br>
Anyway, after some time the network/nfs/server timed out:<br>
<br>
==> /var/svc/log/network-nfs-server:default.log <==<br>
[ Dec 11 12:05:08 Method or service exit timed out. Killing
contract 123. ]<br>
<br>
==> /var/svc/log/svc.startd.log <==<br>
Dec 11 12:05:08/3: svc:/network/nfs/server:default: Method or
service exit timed out. Killing contract 123.<br>
Dec 11 12:05:08/366: network/nfs/server:default timed out:
transitioned to maintenance (see 'svcs -xv' for details)<br>
<br>
==> /var/adm/messages <==<br>
Dec 11 12:05:08 monza.motec.com.au svc.startd[10]: [ID 122153
daemon.warning] svc:/network/nfs/server:default: Method or
service exit timed out. Killing contract 123.<br>
Dec 11 12:05:08 monza.motec.com.au svc.startd[10]: [ID 748625
daemon.error] network/nfs/server:default timed out: transitioned
to maintenance (see 'svcs -xv' for details)<br>
Dec 11 12:05:08 monza.motec.com.au fmd: [ID 377184 daemon.error]
SUNW-MSG-ID: SMF-8000-YX, TYPE: defect, VER: 1, SEVERITY: major<br>
Dec 11 12:05:08 monza.motec.com.au EVENT-TIME: Wed Dec 11
12:05:08 EST 2013<br>
Dec 11 12:05:08 monza.motec.com.au PLATFORM: X9DR3-F, CSN:
1234567890, HOSTNAME: monza.motec.com.au<br>
Dec 11 12:05:08 monza.motec.com.au SOURCE: software-diagnosis,
REV: 0.1<br>
Dec 11 12:05:08 monza.motec.com.au EVENT-ID:
ae3c39b1-7f6c-e39e-bef1-977913c867ce<br>
Dec 11 12:05:08 monza.motec.com.au DESC: A service failed - a
start, stop or refresh method failed.<br>
Dec 11 12:05:08 monza.motec.com.au Refer to
<a class="moz-txt-link-freetext" href="http://illumos.org/msg/SMF-8000-YX">http://illumos.org/msg/SMF-8000-YX</a> for more information.<br>
Dec 11 12:05:08 monza.motec.com.au AUTO-RESPONSE: The service
has been placed into the maintenance state.<br>
Dec 11 12:05:08 monza.motec.com.au IMPACT:
svc:/network/nfs/server:default is unavailable.<br>
Dec 11 12:05:08 monza.motec.com.au REC-ACTION: Run 'svcs -xv
svc:/network/nfs/server:default' to determine the generic reason
why the service failed, the location of any logfiles, and a list
of other services impacted.<br>
<br>
# svcs -xv svc:/network/nfs/server:default<br>
svc:/network/nfs/server:default (NFS server)<br>
State: maintenance since 11 December 2013 12:05:08 PM EST<br>
Reason: Start method died on Killed (9).<br>
See: <a class="moz-txt-link-freetext" href="http://illumos.org/msg/SMF-8000-KS">http://illumos.org/msg/SMF-8000-KS</a><br>
See: man -M /usr/share/man -s 1M nfsd<br>
See: /var/svc/log/network-nfs-server:default.log<br>
Impact: This service is not running.<br>
<br>
# svcs -vp svc:/network/nfs/server:default<br>
STATE NSTATE STIME CTID FMRI<br>
maintenance - 12:05:08 -
svc:/network/nfs/server:default<br>
<br>
ps -elf | grep share<br>
0 S root 1684 1055 0 50 20 ? 576 ?
12:36:52 pts/1 0:00 grep share<br>
0 S root 1134 1 0 40 20 ? 1607 ?
10:05:08 ? 0:00 /usr/sbin/sharemgr stop -P nfs -a<br>
0 S root 1485 1 0 40 20 ? 1623 ?
11:05:08 ? 0:00 /usr/sbin/sharemgr start -P nfs -a<br>
<br>
The network/nfs/server service couldn't be started so I tried
unsuccessfully to get rid of the sharemgr processes. Maybe my
assumption was bad? Are these processes only related to the nfs
server?<br>
<br>
No joy again, so I rebooted.<br>
<br>
What am I not understanding here?<br>
<br>
Also, before rebooting, I had set the nfs properties as:<br>
<br>
servers=512<br>
lockd_listen_backlog=256<br>
lockd_servers=128<br>
lockd_retransmit_timeout=5<br>
grace_period=90<br>
server_versmin=2<br>
server_versmax=3<br>
client_versmin=2<br>
client_versmax=3<br>
server_delegation=on<br>
nfsmapid_domain=<br>
max_connections=-1<br>
protocol=ALL<br>
listen_backlog=32<br>
device=<br>
<br>
I've moved backward to NFSv3 and both client and server seem a
lot happier. I've just about completed a full load test and it
all looks pretty stable.<br>
<br>
Kind regards,<br>
Tom<br>
</tt><br>
<pre class="moz-signature" cols="100">Tom Robinson
IT Manager/System Administrator
MoTeC Pty Ltd
121 Merrindale Drive
Croydon South
3136 Victoria
Australia
T: +61 3 9761 5050
F: +61 3 9761 5051
E: <a class="moz-txt-link-abbreviated" href="mailto:tom.robinson@motec.com.au">tom.robinson@motec.com.au</a>
</pre>
On 11/12/13 11:01, Tom Robinson wrote:<br>
</div>
<blockquote cite="mid:52A7AB75.6070804@motec.com.au" type="cite">
<pre wrap="">OmniOS v11 r151006
Hi,
I'm having many stability/performance issues with NFS. Server end is OmniOS; client end is CentOS 5.
When the server end is functioning, I can mount OK, but there are really long waits on simple things
like listing a directory. Often I will get an I/O error. I have been using NFS4 but I'm thinking I
should just configure the server/client maximum to NFS3.
Currently the NFS server is hosed. This happened yesterday as well. The only way I could bring it
back to life was to reboot the hardware; something I want to avoid. Is there a way to tidy up the
network/nfs/server without rebooting?
I had these settings:
# sharectl get nfs
servers=16
lockd_listen_backlog=32
lockd_servers=20
lockd_retransmit_timeout=5
grace_period=90
server_versmin=2
server_versmax=4
client_versmin=2
client_versmax=4
server_delegation=on
nfsmapid_domain=
max_connections=-1
protocol=ALL
listen_backlog=32
device=
But after reading this: <a class="moz-txt-link-freetext" href="http://virtuallyhyper.com/2013/04/installing-and-configuring-omnios/">http://virtuallyhyper.com/2013/04/installing-and-configuring-omnios/</a>
I have changed to these settings to try to improve responsiveness under load:
# sharectl get nfs
servers=512
lockd_listen_backlog=256
lockd_servers=128
lockd_retransmit_timeout=5
grace_period=90
server_versmin=2
server_versmax=3
client_versmin=2
client_versmax=3
server_delegation=on
nfsmapid_domain=
max_connections=-1
protocol=ALL
listen_backlog=32
device=
The problem is I can't re-enable the service and I don't want to reboot to have to fix this.
# svcs -a | grep -e nfs -e rpc
disabled 17:24:56 svc:/network/nfs/cbd:default
disabled 17:24:56 svc:/network/nfs/client:default
disabled 17:24:57 svc:/network/nfs/log:default
disabled 17:27:55 svc:/network/rpc/meta:default
disabled 17:27:55 svc:/network/rpc/metamh:default
disabled 17:27:55 svc:/network/rpc/rex:default
disabled 17:27:55 svc:/network/rpc/metamed:default
disabled 17:27:55 svc:/network/rpc/mdcomm:default
online 17:25:55 svc:/network/rpc/bind:default
online 17:25:56 svc:/network/rpc/keyserv:default
online 17:25:56 svc:/network/nfs/status:default
online 17:27:55 svc:/network/nfs/mapid:default
online 17:27:56 svc:/network/rpc/gss:default
online 17:27:56 svc:/network/rpc/smserver:default
online 17:27:56 svc:/network/nfs/rquota:default
online* 10:05:07 svc:/network/nfs/server:default
online 10:32:20 svc:/network/nfs/nlockmgr:default
# svcs -xv network/nfs/server
svc:/network/nfs/server:default (NFS server)
State: online since 11 December 2013 10:05:07 AM EST
See: man -M /usr/share/man -s 1M nfsd
See: /var/svc/log/network-nfs-server:default.log
Impact: None.
# svcs -vl network/nfs/server
fmri svc:/network/nfs/server:default
name NFS server
enabled true
state online
next_state offline
state_time 11 December 2013 10:05:07 AM EST
logfile /var/svc/log/network-nfs-server:default.log
restarter svc:/system/svc/restarter:default
contract_id 96
dependency require_any/error svc:/milestone/network (online)
dependency require_all/error svc:/network/nfs/nlockmgr (online)
dependency optional_all/error svc:/network/nfs/mapid (online)
dependency require_all/restart svc:/network/rpc/bind (online)
dependency optional_all/none svc:/network/rpc/keyserv (online)
dependency optional_all/none svc:/network/rpc/gss (online)
dependency optional_all/none svc:/network/shares/group (multiple)
dependency optional_all/none svc:/system/filesystem/reparse (online)
dependency require_all/error svc:/system/filesystem/local (online)
# svcs -vp network/nfs/server
STATE NSTATE STIME CTID FMRI
online offline 10:05:07 96 svc:/network/nfs/server:default
17:27:56 692 nfsd
10:05:07 1123 nfs-server
10:05:07 1134 sharemgr
# ps -elf | grep -e share -e nfs -e rpc
0 S daemon 465 1 0 40 20 ? 796 ? 17:25:56 ? 0:00
/usr/sbin/rpcbind
0 S daemon 582 1 0 40 20 ? 1554 ? 17:27:56 ? 0:00
/usr/lib/nfs/nfsmapid
0 S daemon 545 1 0 40 20 ? 758 ? 17:25:57 ? 0:00
/usr/lib/nfs/statd
0 S daemon 692 1 0 39 0 ? 732 ? 17:27:56 ? 5:27
/usr/lib/nfs/nfsd
0 S root 1123 10 0 40 20 ? 946 ? 10:05:08 ? 0:00 /sbin/sh
/lib/svc/method/nfs-server
0 S root 1134 1123 0 40 20 ? 1607 ? 10:05:08 ? 0:00
/usr/sbin/sharemgr stop -P nfs -a
0 S root 1462 1318 0 50 20 ? 578 ? 11:00:43 pts/4 0:00 grep -e
share -e nfs -e rpc
0 S daemon 1274 1 0 39 0 ? 713 ? 10:32:20 ? 0:00
/usr/lib/nfs/lockd
/var/svc/log/network-nfs-server:default.log
[ Dec 11 10:05:07 Stopping because service restarting. ]
[ Dec 11 10:05:07 Executing stop method ("/lib/svc/method/nfs-server stop 96"). ]
I'm really stuck. Any assistance is much appreciated.
Kind regards,
Tom
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OmniOS-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a>
<a class="moz-txt-link-freetext" href="http://lists.omniti.com/mailman/listinfo/omnios-discuss">http://lists.omniti.com/mailman/listinfo/omnios-discuss</a>
</pre>
</blockquote>
<br>
</body>
</html>
`