From owner-freebsd-questions@FreeBSD.ORG Tue Mar 31 19:16:37 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 744B54D7 for ; Tue, 31 Mar 2015 19:16:37 +0000 (UTC) Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::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 EC87A841 for ; Tue, 31 Mar 2015 19:16:36 +0000 (UTC) Received: by lajy8 with SMTP id y8so20360788laj.0 for ; Tue, 31 Mar 2015 12:16:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=UdLdZ02f3SYpIcxKtBXeepsaeoSDBt1OjJqL41LvZMM=; b=C1qxzvPiGCz/ryhebROlZcX7CD9HLyxhnFZWc8JGwWTGqXV/Gov2zvRhYw7wR4QRS1 35QEcbb3UL77rZ37FNEIIBAAErlawdsm99skJqFcQPkVBNi4n81Z03WEHRenrRxRdeH8 sQ1PZVRlyM5oXZ1mWPmZpzmCacXs5cMLdR99jIzetLVeOmsyGGW+gBry3OhDlShCaGhT hejlNUXNnGlEhslXCQOoxRRYFclSpsjVSzLAix74hZM8BwFDfo0FTxJXYBiyztNwAh9o 8MAQRo/tzuHxXVMlZfDBe8IxwwTxoXOAnTG4bujMxpw3gEHnG/Be6fc2c8ul9VM5KHzC 5n4A== MIME-Version: 1.0 X-Received: by 10.152.180.75 with SMTP id dm11mr5531417lac.39.1427829394596; Tue, 31 Mar 2015 12:16:34 -0700 (PDT) Received: by 10.114.24.72 with HTTP; Tue, 31 Mar 2015 12:16:34 -0700 (PDT) Date: Tue, 31 Mar 2015 12:16:34 -0700 Message-ID: Subject: What to do about RPC errors in an old 8.3 jail From: javocado To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 19:16:37 -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.