Hi Andrew,
Andrew Dumaresq said the following on 02/25/2005 01:26 AM:
> mcomm.MException: Mbus error: timeout while waiting on rpc return.
> RPC-ID: 3, hAlgO/5mr8WElLue
> mbus/1.0 3 1109289422 R (app:freevo type:home-theatre
> id:[EMAIL PROTECTED] module:tv_grab) (app:freevo type:home-theatre
> id:[EMAIL PROTECTED] module:recordserver) ()
> home-theatre.favorite.update ((("ID" "3" )("RPC-TYPE" "UNICAST" ))())
>
> I looked at the freevo code and it looks like it is sending the
> correct message back, but for some reason mbus is interpreting it as
> an error.
The answer to this RPC must be send by the recordserver with 3*100ms.
This error message should only be called when there is no answer within
this period of time or when the answer was a mal-formed RPC return. When
you say that there was an answer to this RPC command could you give me
the Mbus message? That would be helpful for debugging.
I suspect that the answer of the record-server was to late, which means
that the record-server was very busy doing something else that blocked
it from sending a message to the Mbus. Did you see any debug message
saying something like 'lost entity'?
crunchy
--
"Everything should be made as simple as possible, but not simpler."
(A.Einstein)
signature.asc
Description: OpenPGP digital signature
