Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 Jul 2014 21:23:21 -0700
From:      Marc Fournier <scrappy@hub.org>
To:        freebsd-stable@freebsd.org
Subject:   FreeBSD 10.x + LiquidSoap + NFS == Server Hang
Message-ID:  <D12AB91B-78FC-47A7-84C5-8F69DCD5A5CD@hub.org>

next in thread | raw e-mail | index | archive | help

Hi all =85

	I have a jail running on FreeBSD 10-STABLE (svn update as of =
July 2nd @ ~05:30 UTC:

=3D=3D
Working Copy Root Path: /usr/src
URL: https://svn0.us-east.freebsd.org/base/stable/10
Relative URL: ^/stable/10
Repository Root: https://svn0.us-east.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 268135
Node Kind: directory
Schedule: normal
Last Changed Author: pfg
Last Changed Rev: 268132
Last Changed Date: 2014-07-02 01:28:38 +0000 (Wed, 02 Jul 2014)
=3D=3D

	Currently it has 3 jail=92d environments running off it, with =
the files for them NFS mounted from a NetApp filer =85 and right now, =
the NFS mount that these jails are running from is =93locked=94 =85 a =
=91df=92 hangs =85 trying to do a =91jexec # /bin/tcsh=92 into one of =
the jail=92s hangs =85 etc.

	The same NFS file system is mounted and running on a half dozen =
other servers, and they are all operating just fine, so the NetApp is =
operating properly.

	If I move the jail with liquidsoap running around to a different =
server, the hang will follow to the new server, and the old server will =
once more become rock solid =85=20

	I=92m not 100% certain it is liquidsoap, but the hang appears to =
always coincide with reloading a new playlist =85 and although it =
happens frequently (more with recent upgrades), it doesn=92t happen =
*every* night =85

	This is on a remote server =85 so doing things at the console =
isn=92t possible, and although I=92ve got a remote console on this, I=92ve=
 never figured out how to break to the debugger through it, although I=92m=
 going to work on it to see if I can=92t get it to work =85

	Baring breaking to the debugger (is there a way, from the =
command line, to force it to break to the debugger?), is there anything =
else I can use to provide some sort of useful information?

ps aux for the proces shows:

# ps aux | grep liq
1002     2957   0.0  0.7 226888 112792  -  TLJ   4:45AM   370:27.23 =
/usr/local/bin/liquidsoap -q -d /usr/local/etc/liquidsoap/liquidsoap.liq

and:

# ps auxxwl | grep 2957
1002     2957   0.0  0.7 226888 112792  -  TLJ   4:45AM   370:27.23 =
/usr/local/bin/l  1002     1   0  20  0 -
1002    96280   0.0  0.0  12316      0  -  IWJ  -           0:00.00 =
pwait 2957        1002 96274   0  52  0 kqread
root    96508   0.0  0.0  18788   1828  4  S+    4:19AM     0:00.00 grep =
2957            0 96505   0  20  0 piperd

	Other commands I can / should run next time it happens =85 ?    =
Which won=92t take long ...

Thanks =85





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D12AB91B-78FC-47A7-84C5-8F69DCD5A5CD>