Jan Pokorný <jpoko...@redhat.com> schrieb am 24.03.2016 15:38:38: > Von: Jan Pokorný <jpoko...@redhat.com> > An: Cluster Labs - All topics related to open-source clustering > welcomed <users@clusterlabs.org> > Datum: 24.03.2016 15:50 > Betreff: Re: [ClusterLabs] Antwort: Re: Antwort: Re: pacemakerd: > undefined symbol: crm_procfs_process_info > > On 24/03/16 14:38 +0100, philipp.achmuel...@arz.at wrote: > > Jan Pokorný <jpoko...@redhat.com> schrieb am 24.03.2016 12:48:44: > > > >> Von: Jan Pokorný <jpoko...@redhat.com> > >> An: Cluster Labs - All topics related to open-source clustering > >> welcomed <users@clusterlabs.org> > >> Datum: 24.03.2016 12:50 > >> Betreff: Re: [ClusterLabs] Antwort: Re: pacemakerd: undefined > >> symbol: crm_procfs_process_info > >> > >> On 24/03/16 08:44 +0100, philipp.achmuel...@arz.at wrote: > >>> Jan Pokorný <jpoko...@redhat.com> schrieb am 23.03.2016 19:22:13: > >>> > >>>> Von: Jan Pokorný <jpoko...@redhat.com> > >>>> An: users@clusterlabs.org > >>>> Datum: 23.03.2016 19:23 > >>>> Betreff: Re: [ClusterLabs] pacemakerd: undefined symbol: > >>>> crm_procfs_process_info > >>>> > >>>> On 23/03/16 18:40 +0100, philipp.achmuel...@arz.at wrote: > >>>>> $ sudo pacemakerd -V > >>>>> pacemakerd: symbol lookup error: pacemakerd: undefined symbol: > >>>>> crm_procfs_process_info > >>>> > >>>> For a start, please provide output of: > >>>> > >>>> ls -l $(rpm -E %{_libdir})/libcrmcommon.so* > >>>> ldd $(rpm -E %{_sbindir})/pacemakerd > >>>> > >>>> Adjust the path per your actual installation, also depending > >>>> how you got the pacemaker installed: from RPMs (assumed), > >>>> by starting with the sources and compiling by hand, etc. > >>> > >>> i got sources from github and compiled by hand. > >>> > >>>> Note that if RPMs were indeed used, you should rather make sure > >>>> that the same version of the packages arising from single > >>>> SRPM is installed (pacemaker, pacemaker-libs, ...). > >>> > >>> on that hint - i removed all old source directories and startet new > >>> download/compilation today. > >>> after that everything works like expected - may i messed up some old
> > files > >>> in working directory. > >> > >> Do you use "make install" as part of your procedure? > >> Where I was headed is that either "ldconfig" invocation might be > >> missing once the libraries are at place, or that /usr/lib* remnants > >> take precedence over /usr/local/lib* files in run-time linking > >> (provided that use use default installation prefix). > > > > Yes, i use "make install" with default parameters to install to my > > environment. still not sure what happened yesterday - may some file > > permission issues during sync files in my environments. > > Additional syncing step might add this sort of fragility. > Anyway, please keep an eye on this should it ever be reproduced. > It's hard to claim native build/install arrangement is flawless > in any case. > I will have a look at that for future installations. Is there any documentation in which order i have to install all relevant cluster components when installing/compiling it with sources from ClusterLabs repository? > -- > Jan (Poki) > [Anhang "att7fk8o.dat" gelöscht von Philipp Achmüller/ARZ/AT] > _______________________________________________ > Users mailing list: Users@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org
_______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org