What to do about RPC errors in an old 8.3 jail

[javocado]

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.