From owner-freebsd-jail@FreeBSD.ORG Thu Apr 2 22:39:31 2015 Return-Path: Delivered-To: freebsd-jail@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5FF2BFA1 for ; Thu, 2 Apr 2015 22:39:31 +0000 (UTC) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D5A8082 for ; Thu, 2 Apr 2015 22:39:30 +0000 (UTC) Received: by lboc7 with SMTP id c7so69098431lbo.1 for ; Thu, 02 Apr 2015 15:39:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=hYpPt/m2LQCKv0h2oOUCHNsx9UZtsORS/3Cf05mZ218=; b=ky0bzJUYRTIG43Q3ZtJWqLVh1OPtd7RkgWBIxeQNcGMwu+nFalNkf9RAPnsl8mjFMJ LOBOCxllzw2SDoMYflrpN/AuSMEsI2H/NUFAiC3s7Q7wNDkPkY4fN1rx5vGMUW3mk0Ai KdcNLM9Mq+0S7kHzz81FdFATntWY1tMXTDdiw/L5q2DuhhbwC7XNs9hJeIFljXQE2YIP y5KPJa19QuwsB5yli5KDAZENxUleZOXCh5LvO4wYctJREd2k2xpOBoT9vkvqGTn5July mt6DTFvbhcZaUyX/e/Q3u0bq2cxGE90zYyFdXQZv6si42T1QEFJjowUbPmxu/D8RuFXk 2Tvw== MIME-Version: 1.0 X-Received: by 10.152.170.199 with SMTP id ao7mr41957699lac.27.1428014368634; Thu, 02 Apr 2015 15:39:28 -0700 (PDT) Received: by 10.114.24.72 with HTTP; Thu, 2 Apr 2015 15:39:28 -0700 (PDT) In-Reply-To: References: Date: Thu, 2 Apr 2015 15:39:28 -0700 Message-ID: Subject: Fwd: What to do about RPC errors in an old 8.3 jail From: javocado To: freebsd-jail@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2015 22:39:31 -0000 We have an older jail running on 8.3-RELEASE, and when we attempt to run a certain linux binary, it successfully runs, but bombs out with RPC errors: [03.03.2015 21:03:56] < 49156> cli| Thread started. Thread id: 49156, parent id: 16384, role: VRPC server thread [03.03.2015 21:03:56] < 49156> net| Veeam RPC server started. [03.03.2015 21:03:56] < 49156> net| Selected vRPC port: '2500'. [03.03.2015 21:03:56] < 49156> net| Listening vRPC port '2500'. [03.03.2015 21:03:56] < 16384> cli| Client works in standalone mode.[03.03.2015 21:03:57] < 49156> net| ERR |Veeam RPC server broken. [03.03.2015 21:03:57] < 49156> net| >> |WIN: Unable to update socket keep-alive settings. Error code: [92]. [03.03.2015 21:03:57] < 49156> net| >> |An exception was thrown from thread [49156]. [03.03.2015 21:03:57] < 49156> cli| Thread finished. Role: 'VRPC server thread'. As you can see, an RPC server is started, and is immediately broken with the error: [03.03.2015 21:03:57] < 49156> net| ERR |Veeam RPC server broken. We think this is an RPC problem and wonder if it is possible to solve it, perhaps with entries in the jails /etc/rc.conf ? Currently we have no rpc or lockd/statd entries in the jails rc.conf. When you see rpc errors in a jail, what does it mean, and how can it be fixed ? Thank you.