Hi, Thank you for the hint. I found out that it also works by defining the no_proxy variable.
Best regards, Florian 2011/8/4 Carlos Martín Sánchez <cmar...@opennebula.org> > Hi, > > This problem has been described before; looks like it can be fixed > unsetting the http_proxy [1]. > > Regards. > > [1] > http://lists.opennebula.org/pipermail/users-opennebula.org/2010-August/002470.html > -- > Carlos Martín, MSc > Project Major Contributor > OpenNebula - The Open Source Toolkit for Cloud Computing > www.OpenNebula.org <http://www.opennebula.org/> | cmar...@opennebula.org > > > On Thu, Aug 4, 2011 at 8:42 AM, Florin Antonescu < > florinantone...@gmail.com> wrote: > >> Hello, >> >> I noticed that the scheduler of OpenNebula 3.0 is not able to connect to >> the XML-RPC server, however the XML-RPC API seems to be working just fine >> when invoked from an external application. >> The sched.log is full of entries similar to these ones: >> >> Thu Jul 28 09:51:03 2011 [HOST][E]: Exception raised: Unable to transport >> XML to server and get XML response back. HTTP response code is 404, not 200 >> Thu Jul 28 09:51:03 2011 [POOL][E]: Could not retrieve pool info from ONE >> >> but one_xmlrpc.log does not log any corresponding activity (the 404s do >> not appear in the log). >> Can anyone give me a suggestion on how to proceed? >> >> Best regards, >> Florian >> >> _______________________________________________ >> Users mailing list >> Users@lists.opennebula.org >> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >> >> >
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
