[one-users] Getting an "HTTP-Error: 500" when executing oneacct -g group

Javier Fontan jfontan at opennebula.org
Thu Feb 19 09:48:29 PST 2015


I've found that the the change comes in release 1.36.0. I'll update the
static xmlrpc library that we use to generate packages for the next release
with 1.40.0, that is the latest stable release.

Right now the only distribution packages that use the stock xmlrpc-c
library are CentOS 7. It comes with version 1.32.5 so I suppose I'll have
to link them statically.

Concerning manual compilation. While the new release is not ready you can
compile OpenNebula linking statically with the new library and only
substitute oned binary. That should be in src/Nebula directory after
compiling. You should be able to upgrade normally with this method. These
are the steps we use to compile OpenNebula:


--8<------
svn checkout http://svn.code.sf.net/p/xmlrpc-c/code/release_number/01.40.00
cd 01.40.00

export CXXFLAGS="-fPIC"
export CFLAGS="-Wno-error=format-security"
./configure --prefix=$PWD/install --enable-libxml2-backend
make install

# Delete dynamic libraries
rm -f install/{lib,lib64}/*.so install/{lib,lib64}/*.so.*

# Add xmlrpc-c libraries bin dir to the path
export PATH=$PWD/install/bin:$PATH
export XMLRPC=$PWD/install

cd <opennebula source code>
scons -j2 mysql=yes xmlrpc=$XMLRPC new_xmlrpc=yes syslog=yes
------>8--

Cheers







On Tue, Feb 17, 2015 at 12:06 PM, RubEn DIez LAzaro <rdiez at cesga.es> wrote:

>  Compile our own OpenNebula will break the package system maintenance. You
> can forget use yum or any other package management system. You can forget
> about the updating scripts associate to the package for automatically
> migrate and adapt the database schemes to updated versions....
>
> Compile our own OpenNebula in a production infrastructure means return to
> the Dark Ages from a sysadmin point of view... for EVERY site with this
> issue...
>
> In the easy way, OpenNebula staff should use a fixed version of
> libxmlrpc-c and so distribute a fixed package of OpenNebula.
>
> Other possibility is that libxmlrpc-c become a dynamically linked library
> instead statically linked one. In this way each site could use a fixed
> version of libxmlrpc-c....
>
> Regards.
>
>
>
> On 17/02/15 11:15, Esteban Freire wrote:
>
> Hi Carlos,
>
> Thank you very much for letting us know, we need to think it deeply :)
>
> Just one question, which are the pros and cons of compiling oned? It is a
> serious thing for us since the infrastructure is on production and I am not
> sure if it will break future updates trough yum/rpm and also, if we could
> break something in current ON installation at CESGA. Personally, I don't
> like this decision but it is my humble opinion and in any case, we need to
> discuss about it.
>
> Thanks in advance,
> Esteban
>
> On 02/17/2015 11:05 AM, Carlos Martín Sánchez wrote:
>
> Hi,
>
>  I forgot to add that if you want to test the new libxmlrpc version
> yourself, it's not that difficult to compile oned with the 'xmlrpc' scons
> option:
> http://docs.opennebula.org/4.10/integration/references/compile.html
>
>  Regards.
>
>  --
> Carlos Martín, MSc
> Project Engineer
> OpenNebula - Flexible Enterprise Cloud Made Simple
> www.OpenNebula.org | cmartin at opennebula.org | @OpenNebula
> <http://twitter.com/opennebula>
>
> On Fri, Feb 13, 2015 at 10:39 AM, RubEn DIez LAzaro <rdiez at cesga.es>
> wrote:
>
>> Hi:
>>
>> I Does not know really if some recent version of libxmlrpc-c fix this
>> bug... bug the patch seems to be into some branch....
>>
>> http://sourceforge.net/p/xmlrpc-c/code/2520/
>>
>> I don't pretend to confuse you with how we discover this bug, but in
>> short it appears when executing some accounting software by Boris Parak for
>> the Federate cloud of the EGI project....
>>
>> I hope the patch i link help to clarify the situation.
>>
>> Best regards.
>>
>>
>>
>> On 12/02/15 22:53, Alejandro Feijóo wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA512
>>>
>>> Hi to all.
>>>
>>> As Esteban say,  we have a planned updated to last stable opennebula
>>> release the Wednesday 18th, but i think we can wait if the libxmlrpc-c
>>> is updated in the next days or maybe weeks.
>>>
>>> I think we can wait because the new ON not have critical changes (we
>>> have pached one-flow yet) and make 2 updates in the same month can be a
>>> problem for our costumers... (we use oneflow in a lot of critical
>>> services and is a problem make 2 scheduled stops)
>>>
>>>
>>> But if the change is programated to 4.12 we going to update and patch it
>>> (I think Ruben have a special love story paching software hehe)
>>>
>>>
>>> Again, a lot of thanks.
>>>
>>>
>>> El 12/02/15 a las 19:32, Esteban Freire escribió:
>>>
>>>> Hi Carlos,
>>>>
>>>> Thank you very much for checking it :)
>>>>
>>>> About if it should be fixed in 1.33.14, I hope Rubén answer to this
>>>> tomorrow since it is the one looking at this issue.
>>>>
>>>> When do you think we could test this? Sorry for the question/hurry but
>>>> we are failing accounting due to this issue in FedCloud (EGI). In
>>>> principle, we are going to update to last ON version next Wednesday
>>>> 18th.
>>>>
>>>> Thanks in advance,
>>>> Esteban
>>>>
>>>> On 02/12/2015 07:23 PM, Carlos Martín Sánchez wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I'm not directly involved in the packaging, but as far as I can tell,
>>>>> OpenNebula 4.8 comes with libxmlrpc-c version 1.33.6.
>>>>> If I understand correctly, the problem you report should be fixed in
>>>>> 1.33.14?
>>>>>
>>>>> I've checked and the current super stable version is 1.33.16 [1]. We
>>>>> will see if the static library can be updated without breaking
>>>>> anything [2].
>>>>>
>>>>> Regards.
>>>>>
>>>>> [1] http://xmlrpc-c.sourceforge.net/change_super_stable.html
>>>>> [2] http://dev.opennebula.org/issues/3594
>>>>>
>>>>> --
>>>>> Carlos Martín, MSc
>>>>> Project Engineer
>>>>> OpenNebula - Flexible Enterprise Cloud Made Simple
>>>>> www.OpenNebula.org <http://www.OpenNebula.org> |
>>>>> cmartin at opennebula.org <mailto:cmartin at opennebula.org> | @OpenNebula
>>>>> <http://twitter.com/opennebula>
>>>>>
>>>>> On Thu, Feb 12, 2015 at 12:08 PM, RubEn DIez LAzaro <rdiez at cesga.es
>>>>> <mailto:rdiez at cesga.es>> wrote:
>>>>>
>>>>>      HI:
>>>>>
>>>>>      The distro is Scientific Linux release 6.4 (Carbon) and ONE is
>>>>>      installed from repo (it seems be the repo for CentOS 6)
>>>>>
>>>>>      [root at cloud yum.repos.d]# cat opennebula.repo
>>>>>      [opennebula]
>>>>>      name=opennebula
>>>>>      baseurl=http://downloads.opennebula.org/repo/4.8/CentOS/6/x86_64
>>>>>      enabled=1
>>>>>      gpgcheck=0
>>>>>
>>>>>
>>>>>      The installed (from standard repos) version of libxmlrpc-c is
>>>>> 1.16.24:
>>>>>
>>>>>      # yum info xmlrpc-c
>>>>>      [.....]
>>>>>      Installed Packages
>>>>>      Name        : xmlrpc-c
>>>>>      Arch        : x86_64
>>>>>      Version     : 1.16.24
>>>>>      Release     : 1209.1840.el6
>>>>>      Size        : 263 k
>>>>>      Repo        : installed
>>>>>      From repo   : sl
>>>>>      Summary     : A lightweight RPC library based on XML and HTTP
>>>>>      URL         : http://xmlrpc-c.sourceforge.net/
>>>>>      License     : BSD and MIT
>>>>>      Description : XML-RPC is a quick-and-easy way to make procedure
>>>>>      calls over the
>>>>>                  : Internet. It converts the procedure call into XML
>>>>>      document, sends
>>>>>                  : it to a remote server using HTTP, and gets back the
>>>>>      response as
>>>>>                  : XML.
>>>>>                  :
>>>>>                  : This library provides a modular implementation of
>>>>>      XML-RPC for C.
>>>>>
>>>>>      but this is no matter since you claims that ONE is statically
>>>>>      linked.... What version of xmlrpc-c is linked to the ONE from the
>>>>>      showed repo??
>>>>>
>>>>>      We get a source path for 1.33.14 and we build a possible (yet
>>>>>      untested, done by hand using patch we have for 1.33.14) patch for
>>>>>      1.16.24.... Perhaps we can send you these patches for fix the
>>>>>      issue in your statically linked xmlrpc-c???
>>>>>
>>>>>      Regards.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>      On 12/02/15 11:48, Carlos Martín Sánchez wrote:
>>>>>
>>>>>>      Hi,
>>>>>>
>>>>>>      We already use a statically linked libxmlrpc-c version to use a
>>>>>>      newer one for some distros.
>>>>>>      How did you install ONE, what packages are you using? Which
>>>>>> version?
>>>>>>
>>>>>>      Also, can you please share more about the libxmlrpc-c versions
>>>>>>      that cause problems, and when it was fixed?
>>>>>>
>>>>>>      Regards
>>>>>>      --
>>>>>>      Carlos Martín, MSc
>>>>>>      Project Engineer
>>>>>>      OpenNebula - Flexible Enterprise Cloud Made Simple
>>>>>>      www.OpenNebula.org <http://www.OpenNebula.org> |
>>>>>>      cmartin at opennebula.org <mailto:cmartin at opennebula.org> |
>>>>>>      @OpenNebula <http://twitter.com/opennebula>
>>>>>>
>>>>>>      On Wed, Feb 11, 2015 at 12:53 PM, Esteban Freire
>>>>>>      <esfreire at cesga.es <mailto:esfreire at cesga.es>> wrote:
>>>>>>
>>>>>>          Hello,
>>>>>>
>>>>>>          We are having an issue with oneacct command when we try to
>>>>>>          get the accounting for a group, for example:
>>>>>>
>>>>>>          [oneadmin at cloud ~]$ oneacct -g ops
>>>>>>          ops
>>>>>>          HTTP-Error: 500 Internal Server Error
>>>>>>
>>>>>>          [oneadmin at cloud ~]$  oneacct -g fedcloud.egi.eu
>>>>>>          <http://fedcloud.egi.eu>
>>>>>>          fedcloud.egi.eu <http://fedcloud.egi.eu>
>>>>>>          HTTP-Error: 500 Internal Server Error
>>>>>>
>>>>>>          As far as we have been told, it seems the issue it is hidden
>>>>>>          deep in libxmlrpc and has almost nothing to do with
>>>>>>          OpenNebula or its version. The problem is this (briefly):
>>>>>>
>>>>>>          Once the VM history goes over approx. 40k of VMs, libxmlrpc
>>>>>>          will refuse to allocate enough memory for some OpenNebula
>>>>>>          responses to RPC commands.
>>>>>>
>>>>>>          Also, the solution proposed is to compile OpenNebula against
>>>>>>          a newer and patched version of libxmlrpc but to be honest, I
>>>>>>          would prefer avoid this solution.
>>>>>>
>>>>>>          I understand this is not an OpenNebula issue but I wonder if
>>>>>>          as OpenNebula developers you have seen this issue before and
>>>>>>          it there is any other better solution. Also, if some other
>>>>>>          site has experiment this issue, I would like to know which
>>>>>>          was the solution applied.
>>>>>>
>>>>>>          Any help is welcome on this since we need to solve this issue
>>>>>>          asap :)
>>>>>>
>>>>>>          Thanks in advance,
>>>>>>          Esteban
>>>>>>
>>>>>>          --         ++-------------------------++
>>>>>>          Esteban Freire García
>>>>>>          Centro de supercomputación de Galicia
>>>>>>          Avda. de Vigo s/n. Campus Vida
>>>>>>          15705 - Santiago de Compostela. Spain
>>>>>>          Tlfn.: 981 56 98 10 Extension:274
>>>>>>          Fax: 981 59 46 16
>>>>>>
>>>>>>          _______________________________________________
>>>>>>          Users mailing list
>>>>>>          Users at lists.opennebula.org <mailto:
>>>>>> Users at lists.opennebula.org>
>>>>>>
>>>>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>      _______________________________________________
>>>>>>      Users mailing list
>>>>>>      Users at lists.opennebula.org  <mailto:Users at lists.opennebula.org>
>>>>>>      http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>>>>
>>>>>
>>>>>      _______________________________________________
>>>>>      Users mailing list
>>>>>      Users at lists.opennebula.org <mailto:Users at lists.opennebula.org>
>>>>>      http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users at lists.opennebula.org
>>>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at lists.opennebula.org
>>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>>
>>>>  - -- Alejandro Feijóo Fraga
>>> Systems Technician
>>> CESGA
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
>>> Comment: GPGTools - https://gpgtools.org
>>>
>>> iQEcBAEBCgAGBQJU3SDrAAoJEKshAoM6XWq54GwIAKY4yp/4+REWqjSKBCZoHInj
>>> RGmKvUFuGbo7pfV7Ttreztxu3wF1KidIAR0uMG0/zoJ3DR/q/c4hdWaIIhw3PAv8
>>> x/rBBWNYRgCOX520AmOA7AYaKMnvsRWsf4yQST2Q9Biij3dkaBvU7+IKpCcw6oeR
>>> L3Athpe15Jnl+k5oLw926ntrN0Ol+A3SBoWM4Ndn8+XCdEbEpi2BqrgcX0Ex5L0z
>>> L9e9Cl+pzl9wRVBNxiy3Fd/zPcFQI3MXvfyYmcceRbwEfgxO+o79e2ZcXmmLeXfc
>>> 9zhzHiSgjf1TlqrdHvDv7TT0cFIYXyiJRE3RDGhAwbBq8MwAmbAUc0mbQ7Bamg4=
>>> =WENu
>>> -----END PGP SIGNATURE-----
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opennebula.org
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>
>
>
> _______________________________________________
> Users mailing listUsers at lists.opennebula.orghttp://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
>
> --
> ++-------------------------++
> Esteban Freire García
> Centro de supercomputación de Galicia
> Avda. de Vigo s/n. Campus Vida
> 15705 - Santiago de Compostela. Spain
> Tlfn.: 981 56 98 10 Extension:274
> Fax: 981 59 46 16
>
>
>
> _______________________________________________
> Users mailing listUsers at lists.opennebula.orghttp://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>


-- 
Javier Fontán Muiños
Developer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | @OpenNebula | github.com/jfontan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20150219/9ff1a68a/attachment-0001.htm>


More information about the Users mailing list