The response could not be parsed......

[earthwormjim]

Hi All,

I'm new to r & ntorrent this is my first post, apologies if this is a
beginners error;

I've installed rtorrent and it appears to be working, but when I try
to connect to it I get "The response could not be parsed".
With the help of the forum I've located the log file, here's the
contents, please can anybody help?

03-Mar-2009 20:27:12 ntorrent.io.xmlrpc.XmlRpcConnection <init>
INFO: New http connection to url=http://192.168.0.8:8081/RPC2 using
proxy=DIRECT
03-Mar-2009 20:28:13
STDERR: [Fatal Error] :1:1: Premature end of file.

03-Mar-2009 20:28:13 ntorrent.Session run
WARNING: The response could not be parsed.
redstone.xmlrpc.XmlRpcException: The response could not be parsed.
at redstone.xmlrpc.XmlRpcHTTPClient.handleResponse
(XmlRpcHTTPClient.java:445)
at redstone.xmlrpc.XmlRpcHTTPClient.endCall(XmlRpcHTTPClient.java:
389)
at redstone.xmlrpc.XmlRpcHTTPClient.invoke(XmlRpcHTTPClient.java:221)
at redstone.xmlrpc.XmlRpcProxy.invoke(XmlRpcProxy.java:168)
at $Proxy0.xmlrpc_dialect(Unknown Source)
at ntorrent.io.xmlrpc.XmlRpcConnection.<init>(XmlRpcConnection.java:
156)
at ntorrent.Session.run(Session.java:75)
at java.lang.Thread.run(Unknown Source)
Caused by: redstone.xmlrpc.XmlRpcException: A problem occured during
parsing
at redstone.xmlrpc.XmlRpcParser.parse(XmlRpcParser.java:147)
at redstone.xmlrpc.XmlRpcHTTPClient.handleResponse
(XmlRpcHTTPClient.java:431)
... 7 more
Caused by: org.xml.sax.SAXParseException: Premature end of file.
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse
(Unknown Source)
at redstone.xmlrpc.XmlRpcParser.parse(XmlRpcParser.java:143)
... 8 more

[Kim Eik]

What version of rtorrent/libtorrent and xmlrpc-c are you using?

[earthwormjim]

Hi,

Thanks for replying.

rtorrent 0.8.4-1
xmlrpc-c 1.11.00-3

On Mar 4, 5:43 pm, Kim Eik <kei...@gmail.com> wrote:
> What version of rtorrent/libtorrent and xmlrpc-c are you using?
>
> On Tue, Mar 3, 2009 at 9:29 PM, earthwormjim

> <mailthecart...@tiscali.co.uk>wrote:

[Kim Eik]

Well, this could be any number of things. Make sure you have configured the socket correctly on the server side, that the connection info you are supplying nTorrent is correct and that the two machines can communicate with eachother.

The error you are having suggests that nTorrent is able to open a connection and is recieving a response from its request, however the response is not xml that is parsable by nTorrent.

use tools like the xmlrpc command line client to make sure that xmlrpc command can be executed on the server side, then try to make sure that the http socket is correctly configured.

Best of luck!

[earthwormjim]

Thanks Kim,

I'm confused, I don't seem to have an xmlrpc client....
The forums seem to suggest it comes with xmlrpc-c, but it's not there.
Is it part of another package or has something gone wrong?

[earthwormjim]

From the xml-rpc manual;
"Xmlrpc-c comes with a few utility programs that you can use to
diagnose problems or learn about XML-RPC or Xmlrpc-c. These programs
double as examples of how to use the Xmlrpc-c function libraries.

Because the utility programs are not essential to the package, the
default install tools don't install them at all. The builder does
build them, though, and if you build Xmlrpc-c from source, you will
find them all in the tools/ directory. "

I guess thats why I haven't got xmlrpc client then. Thats a shame.

[Kim Eik]

And you haven't compiled xmlrpc-c from source?

[earthwormjim]

No, afraid not. I'm installing on a Buffalo NAS device, and using the
optware repository for the software source.

(http://ipkg.nslu2-linux.org/feeds/optware/cs05q3armel/cross/stable/)

I read elsewhere that xmlrpc-c package version 1.11.00-3 is "broken"
in the repository, this may be causing my problem...?

Setting up the NAS box for compling from source - or setting up
another machine for cross compiling (?) would presumably be my next
option,
but as you may have guessed, this is a beyond my knowledge &
experience, to do unaided.

[Kim Eik]

Ok, as i see it, the issue could be the xmlrpc-c package. but the other
alternative is that you simply are typing the wrong connection info, or
have configured the http socket in either lighttpd, or apache
incorrectly, or maybe even the rtorrent socket.

So what you could do is to make sure is to double check that
configuration, and if you are 100% sure that it's setup correct. Read
the guides on both nTorrent site, and rTorrent site on setting up
xmlrpc-c but also third party "unofficial" sources. If this doesnt bare
fruits then i would advise you to install rtorrent, libtorrent, xmlrpc-c
on a virtual machine (or another pc laying around) just to create a
working system, and once you have that system up and running, and its
connectable through nTorrent. Then you can more easily debug the two
systems by comparing them to see where their config and setup differs.

But as you know, nTorrent is just the client software, and the this
setting up the server side, this really shouldn't be nTorrent's problem.
nTorrent only demands a socket that spews out correctly formatted xml.

But ofc, i try to help whenever i can.

Good luck.

[earthwormjim]

Ok, I use kubuntu on my laptop, I'll try and install and set it up on
that.
At least I can compile on that if I need to.

I'll report back later...

[earthwormjim]

I bet you thought I'd given up........

I nearly did to be honest, but I think I've just got it working! :-)

I'll write it all up and post it in the next few days. A small error
in the instructions I was following for lightppd config turned out
to be the root of all my problems (compounded by a lack of
understanding of how it ties up with rtorrent & ntorrent).

Thanks Kim for the moral support, I hope to start experimenting with
ntorrent now.

[Kim Eik]

Im glad you got it working!  Give yourself a clap on the back for a job well done.
-Kim