So the 4 dependencies can be fixed like this: cd /usr/lib sudo ln -s libxmlrpc_server_abyss++.so.4 libxmlrpc_server_abyss++.so.3 sudo ln -s libxmlrpc_client++.so.4 libxmlrpc_client++.so.3 sudo ln -s libxmlrpc++.so.4 libxmlrpc++.so.3 sudo ln -s libxmlrpc_server++.so.4 libxmlrpc_server++.so.3
Now I'm stuck with a 'Database version mismatch." ... On Fri, Apr 20, 2012 at 2:17 PM, Valerio Schiavoni < [email protected]> wrote: > As a follow-up, oned is trying to link against these libs (note the not > found ones): > > > ldd /usr/bin/oned > linux-vdso.so.1 => (0x00007fff3278c000) > libcrypto.so.0.9.8 => /lib/libcrypto.so.0.9.8 (0x00007f6fbdcdc000) > libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 > (0x00007f6fbda43000) > libmysqlclient.so.16 => /usr/lib/libmysqlclient.so.16 > (0x00007f6fbd638000) > libxmlrpc_client.so.3 => /usr/lib/libxmlrpc_client.so.3 > (0x00007f6fbd42e000) > * libxmlrpc_client++.so.3 => not found* > libxml2.so.2 => /usr/lib/libxml2.so.2 (0x00007f6fbd0d9000) > * libxmlrpc_server_abyss++.so.3 => not found* > * libxmlrpc_server++.so.3 => not found* > libxmlrpc_server_abyss.so.3 => > /usr/lib/libxmlrpc_server_abyss.so.3 (0x00007f6fbced2000) > libxmlrpc_server.so.3 => /usr/lib/libxmlrpc_server.so.3 > (0x00007f6fbcccc000) > libxmlrpc_abyss.so.3 => /usr/lib/libxmlrpc_abyss.so.3 > (0x00007f6fbcab7000) > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x00007f6fbc898000) > * libxmlrpc++.so.3 => not found* > libxmlrpc.so.3 => /usr/lib/libxmlrpc.so.3 (0x00007f6fbc686000) > libxmlrpc_util.so.3 => /usr/lib/libxmlrpc_util.so.3 > (0x00007f6fbc480000) > libxmlrpc_xmlparse.so.3 => /usr/lib/libxmlrpc_xmlparse.so.3 > (0x00007f6fbc273000) > libxmlrpc_xmltok.so.3 => /usr/lib/libxmlrpc_xmltok.so.3 > (0x00007f6fbc057000) > libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 > (0x00007f6fbbd50000) > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f6fbbacb000) > libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 > (0x00007f6fbb8b5000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6fbb51f000) > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f6fbb31b000) > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f6fbb103000) > libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 > (0x00007f6fbaec9000) > libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 > (0x00007f6fbacaf000) > libcurl.so.4 => /usr/lib/libcurl.so.4 (0x00007f6fbaa56000) > /lib64/ld-linux-x86-64.so.2 (0x00007f6fbe075000) > libidn.so.11 => /usr/lib/libidn.so.11 (0x00007f6fba822000) > liblber-2.4.so.2 => /usr/lib/liblber-2.4.so.2 (0x00007f6fba614000) > libldap_r-2.4.so.2 => /usr/lib/libldap_r-2.4.so.2 > (0x00007f6fba3c8000) > librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f6fba1c0000) > libgssapi_krb5.so.2 => > /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x00007f6fb9f8b000) > libssl.so.0.9.8 => /lib/libssl.so.0.9.8 (0x00007f6fb9d37000) > libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 > (0x00007f6fb9b1c000) > libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x00007f6fb9902000) > libgnutls.so.26 => /usr/lib/x86_64-linux-gnu/libgnutls.so.26 > (0x00007f6fb9660000) > libgcrypt.so.11 => /lib/x86_64-linux-gnu/libgcrypt.so.11 > (0x00007f6fb93e6000) > libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 > (0x00007f6fb9122000) > libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 > (0x00007f6fb8efa000) > libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 > (0x00007f6fb8cf6000) > libkrb5support.so.0 => > /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x00007f6fb8aee000) > libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 > (0x00007f6fb88ea000) > libtasn1.so.3 => /usr/lib/x86_64-linux-gnu/libtasn1.so.3 > (0x00007f6fb86d9000) > libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 > (0x00007f6fb84d4000) > > > > On Fri, Apr 20, 2012 at 2:09 PM, Valerio Schiavoni < > [email protected]> wrote: > >> Hello Jaime, thanks for your suggestion. >> >> On Fri, Apr 20, 2012 at 12:41 PM, Jaime Melis <[email protected]>wrote: >> >>> >>> http://dev.opennebula.org/packages/opennebula-3.4.0/Ubuntu-10.04/ >>> >>> It looks like in your case you will only need to change the dependencies >>> in the debian/control file. >>> >> >> >> This almost works. After the modification in the list of dependencies, >> the installation process almost completes: >> >> sudo gdebi Ubuntu-11.04-opennebula_3.4.0-1_amd64.deb >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> Building data structures... Done >> Building data structures... Done >> >> >> OpenNebula >> OpenNebula is an open source virtual infrastructure engine that enables >> the >> dynamic deployment and re-placement of virtual machines on a pool of >> physical >> resources. >> . >> ONE (OpenNebula) extends the benefits of virtualization platforms from a >> single physical resource to a pool of resources, decoupling the server >> not >> only from the physical infrastructure but also from the physical >> location. >> Do you want to install the software package? [y/N]:y >> (Reading database ... 69942 files and directories currently installed.) >> Preparing to replace opennebula 3.4.0-1 (using >> Ubuntu-11.04-opennebula_3.4.0-1_amd64.deb) ... >> oned and scheduler stopped >> Unpacking replacement opennebula ... >> Setting up opennebula (3.4.0-1) ... >> chown: invalid group: `oneadmin:oneadmin' >> dpkg: error processing opennebula (--install): >> subprocess installed post-installation script returned error exit status >> 1 >> Processing triggers for ureadahead ... >> Processing triggers for man-db ... >> Errors were encountered while processing: >> opennebula >> >> Assuming that the problem with the user/group is due to the fact that >> oneadmin already exists, running "one start" spits this: >> >> one start >> /usr/bin/oned: error while loading shared libraries: >> libxmlrpc_client++.so.3: cannot open shared object file: No such file or >> directory >> /usr/bin/mm_sched: error while loading shared libraries: >> libxmlrpc_server_abyss++.so.3: cannot open shared object file: No such file >> or directory >> oned failed to start >> scheduler failed to start >> >> >> Is this the definitive sign that I should not continue down this path?... >> > >
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
