search for: xdr_u_int

...cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora -------------- next part -------------- >From 100fc211d672da2ef0adc81f65ec9903346c6d8c Mon Sep 17 00:00:00 2001 From: Richard Jones <rjones at redhat.com> Date: Wed, 25 Nov 2009 14:45:20 +0000 Subject: [PATCH 3/7] daemon/Win32: Use xdr_u_int for PortableXDR compatibility. PortableXDR didn't support xdr_uint32_t. xdr_u_int is the same type. --- daemon/guestfsd.c | 2 +- daemon/proto.c | 14 +++++++------- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/daemon/guestfsd.c b/daemon/guestfsd.c index 67206d0..f3...

...e. >> >> Here is the debug log of libvirtd when I try to connect with virsh: >> > >> 2020-07-14 16:29:58.220+0000: 5352: error : >> virNetMessageDecodeLength:131 : Unable to decode message length > > This is interesting. The error message is reported when xdr_u_int() > fails. It is trying to decode first 4 bytes of incoming message to > see how long it is. I can think of two possible reasons for this: > > 1) the client did not send 4 bytes > 2) the rpcgen generated some wrong code that libtirpc is unable to > decode. > > I suggest...

Hello all, I have been trying to get libvirtd to work but when I connect to it with virsh, I get "error : virNetMessageDecodeLength:131 : Unable to decode message length" This happens with libvirt 6.1.0, libtirpc 1.2.6, rpcsvc-proto 1.4.1. I have tried with other versions, but I still get the same error. If anybody has any tip on what to try next, that would be helpful. Thank you

...sr/include/rpc/xdr.h:293: error: previous declaration of ?xdr_u_long? was here /usr/include/rx/xdr_prototypes.h:46: error: conflicting types for ?xdr_int? /usr/include/rpc/xdr.h:290: error: previous declaration of ?xdr_int? was here /usr/include/rx/xdr_prototypes.h:47: error: conflicting types for ?xdr_u_int? /usr/include/rpc/xdr.h:291: error: previous declaration of ?xdr_u_int? was here /usr/include/rx/xdr_prototypes.h:48: error: conflicting types for ?xdr_char? /usr/include/rpc/xdr.h:320: error: previous declaration of ?xdr_char? was here /usr/include/rx/xdr_prototypes.h:49: error: conflicting types...

...helpful. Thank > you in advance. > > Here is the debug log of libvirtd when I try to connect with virsh: > > 2020-07-14 16:29:58.220+0000: 5352: error : > virNetMessageDecodeLength:131 : Unable to decode message length This is interesting. The error message is reported when xdr_u_int() fails. It is trying to decode first 4 bytes of incoming message to see how long it is. I can think of two possible reasons for this: 1) the client did not send 4 bytes 2) the rpcgen generated some wrong code that libtirpc is unable to decode. I suggest using wireshark to check what data is se...

If you spend your time looking at libguestfs debugging output you'll see many messages from the daemon main loop like this: guestfsd: main_loop: new request, len 0x54 guestfsd: main_loop: proc 278 (mkfs) took 0.02 seconds I don't think these messages really bring much value. This commit removes them entirely. An alternative might be to change them to make them shorter and/or less

...stfsd: leave: touch (0x3) took 0.00 secs --- daemon/proto.c | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/daemon/proto.c b/daemon/proto.c index 14f7efe94..9abc46962 100644 --- a/daemon/proto.c +++ b/daemon/proto.c @@ -96,11 +96,6 @@ main_loop (int _sock) xdr_u_int (&xdr, &len); xdr_destroy (&xdr); - if (verbose) - fprintf (stderr, - "guestfsd: main_loop: new request, len 0x%" PRIx32 "\n", - len); - /* Cancellation sent from the library and received after the * previous request has finish...

...dy\n"); - exit (EXIT_FAILURE); - } + if (!xdr_guestfs_message_error (&xdr, &err)) + error (EXIT_FAILURE, 0, "failed to encode error message body"); len = xdr_getpos (&xdr); xdr_destroy (&xdr); @@ -320,14 +311,10 @@ send_error (int errnum, char *msg) xdr_u_int (&xdr, &len); xdr_destroy (&xdr); - if (xwrite (sock, lenbuf, 4) == -1) { - fprintf (stderr, "guestfsd: xwrite failed\n"); - exit (EXIT_FAILURE); - } - if (xwrite (sock, buf, len) == -1) { - fprintf (stderr, "guestfsd: xwrite failed\n"); - exit (E...

..."\n"); - perror (channel); - exit (EXIT_FAILURE); + error (EXIT_FAILURE, errno, "open: %s", channel); } } } @@ -353,10 +353,8 @@ main (int argc, char *argv[]) xdrmem_create (&xdr, lenbuf, sizeof lenbuf, XDR_ENCODE); xdr_u_int (&xdr, &len); - if (xwrite (sock, lenbuf, sizeof lenbuf) == -1) { - perror ("xwrite"); - exit (EXIT_FAILURE); - } + if (xwrite (sock, lenbuf, sizeof lenbuf) == -1) + error (EXIT_FAILURE, errno, "xwrite"); xdr_destroy (&xdr); diff --git a/daemon/n...

This is an updated and extended version of the original patch: https://www.redhat.com/archives/libguestfs/2010-August/msg00163.html This adds OCaml and Perl bindings (both tested), support for progress bars in virt-resize, and adds progress notifications to a number of the simpler commands. Still to do is to add progress messages to more commands. There are still a few commands which would be