How can I check the version of aerospike tools installed on the server? My server version is Linux CentOS 7.
Aerospike version is 3.7.1
AMC version is 3.6.11
I can get server version by running asinfo -v version but i'm struggling to find the version of the Tools installed. The link for the Tools is below.
http://www.aerospike.com/download/tools
For the package version use:
rpm -qi aerospike-tools
Some of the tools also have an --version option. These versions track the individual tools release and are independent of the package version.
rpm -qi aerospike-tools
Name : aerospike-tools
Version : 3.9.0
...
For instance, asadm supports --version and its release notes can be found at https://github.com/aerospike/aerospike-admin/releases.
$ asadm --version
0.1.4
Related
I couldn't install guest addition on virtual box version 5.2.12 error caused-
This system is currently not set up to build kernel modules.
Please install the gcc make perl packages from your distribution.
You can use the below command to install the packages in RHEL 7.
yum install gcc perl make
Virtual box is base for the RHEL, all packes should be installed in RHEL OS only.
Hope you set the repository and your VM have access to internet
Installing ruby version with rbenv rbenv install -lreturns the proper list. However
$ rbenv install 2.3.4 -v
fails on the download, even though it can be downloaded via a browser. My hunch about an improper version of openssl (due to some distant memory of having such issues - tls version? - in the past) is supported in verbose mode:
ruby-build: use openssl from homebrew
/var/folders/kV/kVDOSPkcEuqSVnTjenAVRE+++TI/-Tmp-/ruby-build.20170601122915.1010 ~ Downloading ruby-2.3.4.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.3/ruby-2.3.4.tar.bz2
curl: (35) error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
error: failed to download ruby-2.3.4.tar.bz2
how to overcome? can I point rbenv to use the downloaded tarball?
The reason is because rbenv use old system curl and old system openssl with it, which knows nothing about protocols TLS v 1.1-1.3. For me, installing new version of curl and openssl with brew did the work:
brew install openssl#1.1
brew install curl
Then add installed curl to your PATH (before default path, which is /usr/bin), and ensure that openssl of actual brew's version is also there (add this to your ./bash_profile or ./zshrc or etc):
export PATH="/usr/local/opt/openssl#1.1/bin:$PATH"
export PATH="/usr/local/opt/curl/bin:$PATH"
You can make sure after relaunch of terminal that latest versions of this programs will be used by trying
which -a openssl
which -a curl
openssl version -a
curl -V
First two commands should output all paths with the programs, but top ones should be brew versions. Last two commands should show latest versions of programs (1.1.0f and 7.55 for me now).
Now try
rbenv install [version]
Works on MacOS Sierra with enabled SIP.
I created a shared library with Visual Studio Enterprise 2015 Update 1 :
File > New Project > Templates > Visual C++ > Cross Platform > Shared Library (Android, iOS)
I got the following project structure by default :
The android project builds successfully. But the issue appears when I try to compile the iOS project (the highlighted one on the screenshot).
Since a build agent is needed, I installed it on a Mac using npm and vcremote (as explained here : https://msdn.microsoft.com/library/mt147405.aspx).
I successfully paired Visual Studio with the Mac by going into Tools > Options > Cross Platform > C++ > iOS > Pairing.
But I still get the following error :
"Build agent request has failed, this client is not compatible with the paired build agent. Client version "1.3.0", build agent version "2.3.0". Supported build agent versions are: "2.0.0 - 2.2.0". Please update vcremote with "npm update vcremote", on the Mac."
On the Mac Terminal I get a similar error message :
"Visual Studio is incompatible with the current version of this build agent. Please update vcremote using npm."
I did run the npm update vcremote command, it is now up to date, but the error still shows up. Moreover it seems that the build agent version is too high regarding the client version.
What do you guys suggest ?
The problem was the version of vcremote-lib which was too high (2.3.0). I tried to downgrade only this package but it didn't work, so I downgraded the entire vcremote and it finally worked. Here are the steps I followed to resolve my problem :
Uninstall vcremote :
(documentation about the npm "uninstall" command : https://docs.npmjs.com/cli/uninstall)
sudo npm -g uninstall vcremote --save
sudo npm -g uninstall vcremote-lib --save
Check which versions are available :
(documentation about the npm "version" command : https://docs.npmjs.com/cli/version)
If you don't specify a version number while installing a package the latest version is chosen by default. To check the available versions for a specific package (here we're talking about vcremote package) run the following command :
npm view vcremote versions
Reinstall a specific version of vcremote :
(documentation about the npm "install" command : https://docs.npmjs.com/cli/install)
I didn't want the last one (1.0.8), so I specified a prior version (1.0.6) while running the following command :
sudo npm install -g --unsafe-perm vcremote#1.0.6
...instead of using the following command provided in the documentation :
sudo npm install -g --unsafe-perm vcremote
And finally :
Now it's working fine because vcremote 1.0.6 uses vcremote-lib 2.0.0 (while vcremote 1.0.8 used vcremote-lib 2.3.0).
(i can't post comments yet...)
With visual studio 2015 update 2 released yesterday you get this error:
Build agent request has failed, this client is not compatible with the paired build agent. Client version "1.4.0", build agent version "2.0.0". Supported build agent versions are: "2.3.0 - 2.4.0". Please update vcremote with "npm update vcremote", on the Mac.
now need to update to vcremote 1.0.8 (in order to get vcremote-lib 2.0.3):
sudo npm install -g --unsafe-perm vcremote#1.0.8
which brought in vcremote-lib 2.0.3, version 2.0.4 doesn't seem to be available yet
How do I package a python2.7 project for installation on CentOS 6.7?
I plan on deploying a python2.7 package onto CentOS 6.7 systems that have had python2.7 installed from SCL along side the python2.6 needed for the system (as per this question).
So far, I've tried
using distutils on a CentOS 6.7 machine to make an rpm (bdist_rpm) -- but that's tyring to use python 2.6.
using distutils to make an rpm on a different machine with python2.7 only installed -- the resulting rpm cannot be installed since rpm on the CentOS machine assumes python2.6
I am working on a Project, which uses classes from the C++11 standard, on a Fedora 18 machine and want to deploy it on a Centos 6.4 server.
I was able to resolve all loader errors except for the libc and libc++ versions, which are GLIBC_2.11, GLIBCXX_3.4.15 and on my Fedora machine GLIBC_2.14 and at least GLIBCXX_3.4.17 respectively.
Is it possible to tell the compiler to compile/link for the server versions or older compatible versions of the libraries?
When i run ldd executable i get
./executable: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./executable)
./executable: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by ./executable)
Thanks in advance!
Instead of manually copying libraries to a separate directory you could set up a chroot contaiing the CentOS build env, using mock and the epel-6-x86_64 config.
Use yum in the mock chroot to install the packages you want (e.g. Qt) and build in there, that will ensure the code only uses the CentOS 6 libs that are installed in the chroot, not the rest of the packages on your Fedora OS.
Update:
When I'm using a mock chroot for building GCC I do this:
# only need these steps once to setup the chroot
mock -r fedora-19-x86_64 --init
mock -r fedora-19-x86_64 --install yum
mock -r fedora-19-x86_64 --shell 'mkdir -p /builddir/gcc/src /builddir/gcc/build'
su -c 'mount --bind $PATH_TO_GCC_SOURCES /var/lib/mock/fedora-19-x86_64/root/builddir/gcc/src'
# enter root password
mock -r fedora-19-x86_64 --shell
# now in chroot
yum install gmp-devel mpfr-devel libmpc-devel flex autogen
su - mockbuild
cd gcc/build
../src/configure --prefix=/builddir/gcc/install ... etc. ...
For your purpose you'd replace fedora-19 with epel-6
The bind mount means I don't need to have the GCC sources in the chroot, I can use the existing copy in my normal filesystem. See http://gcc.gnu.org/wiki/InstallingGCC for info on building GCC
Once you install GCC in the chroot you can use it to build your own programs then package them up for CentOS.
To go back into the chroot again later:
mock -r fedora-19-x86_64 --shell
su - mockbuild