Hello – I decided to try the OMD route. The packaging does seem improved and much easier to navigate but I still find that I’m going down a rabbit’s hole of random
dependency errors. Specifically I get the following on my newly built RHEL 7.3 machine with OMD version 1.2.8p20.cre:
Starting rrdcached…/omd/sites/test/bin/rrdcached: error while loading shared libraries: libpcre.so.0: cannot open shared object file: No such file or directory
I can verify that this host doesn’t have libpcre.so.0 (I did a find from /) but it does have later versions:
Symbolic links are your friend. Simply create a symbolic link for the major version number you need to the major version reference, or the fully qualified name of the library you have.
libraries major version number, but they often do not create links for the .so file; so when you build executables the executable is dependent upon the more specific reference of the library. In this case, the .so.1 reference. Had both RHEL6 and RHEL7 had
.so references, there wouldn’t be this issue.
Hello – I decided to try the OMD route. The packaging does seem improved and much easier to navigate but I still find that I’m going down a rabbit’s hole of random
dependency errors. Specifically I get the following on my newly built RHEL 7.3 machine with OMD version 1.2.8p20.cre:
Starting rrdcached…/omd/sites/test/bin/rrdcached: error while loading shared libraries: libpcre.so.0: cannot open shared object file: No such file or directory
I can verify that this host doesn’t have libpcre.so.0 (I did a find from /) but it does have later versions: