Error running puppet - rvm

I've just installed puppet 3.8.4 on OSX 10.5.5. When running puppet --version from the command line to check the installation I get the following error:
macbook-MBP:~ richard$ puppet --version
dyld: lazy symbol binding failed: Symbol not found: _rb_ary_new_from_values
Referenced from: /Users/richard/.rvm/gems/ruby-2.2.2#global/gems/psych-2.0.15/lib/psych.bundle
Expected in: flat namespace
dyld: Symbol not found: _rb_ary_new_from_values
Referenced from: /Users/richard/.rvm/gems/ruby-2.2.2#global/gems/psych-2.0.15/lib/psych.bundle
Expected in: flat namespace
Any ideas why this is happening?

Puppet 3.x has no support for Ruby 2.2.
You will have to either
try and install Ruby 2.1
try and install Puppet 4
Puppet 4 has limited compatibility with 3, so going for an alternate Ruby will likely be easier, depending on your existing infrastructure.

Related

Can't install lua package using luarocks due to conflicting architecture

I'm getting the following error when trying to install the lpeg library using luarocks:
lptree.obj : error LNK2019: unresolved external symbol luaL_checkudata referenced in function lp_gc
C:\Program Files (x86)\Lua\5.1\lib\lua5.1.lib : warning LNK4272: library machine type 'x86' conflicts with target machine type 'x64'
lpeg.dll : fatal error LNK1120: 55 unresolved externals
Error: Build error: Failed installing lpeg.dll in C:\Program Files (x86)\Lua\5.1\rocks/lpeg/1.0.2-1/lib
I'm using the following version of lua:
Lua 5.1.5 Copyright (C) 1994-2012 Lua.org, PUC-Rio
And the following version of luarocks:
luarocks 2.0.2
LuaRocks main command-line interface
I installed lpeg using the command provided here namely:
luarocks install lpeg
I'm not sure what I'm doing wrong. Any ideas?

Could not find adapter type bigquery

Having trouble running dbt today... encountered this error message and cannot debug the issue. I did not have this issue yesterday and have not changed anything since.
Installed dbt with Homebrew
Running with dbt=0.18.0
dbt version: 0.18.0
...
Configuration:
profiles.yml file [ERROR invalid]
dbt_project.yml file [OK found and valid]
Profile loading failed for the following reason:
Runtime Error
Credentials in profile "dandelion-bq", target "dev" invalid: Runtime Error
Could not find adapter type bigquery!
Probably you installed a plugin or another version of dbt-core, try:
dbt --version
It should list the plugins installed, guess in your case there is no bigquery there:
dbt --version
installed version: 0.19.0
latest version: 1.0.0
Your version of dbt is out of date! You can find instructions for upgrading here:
https://docs.getdbt.com/docs/installation
Plugins:
- postgres: 0.19.0
- bigquery: 0.19.0
Install it, with pip or pip3
pip install dbt-bigquery
Same applies for any other plugin/adapter when you get the error Credentials in profile <profile>, target <target> invalid: Runtime Error Could not find adapter type <plugin>!

libtiff check failed when trying to build a library that depends on it

I am using ubuntu 18.04. I have libtiff5 installed (using sudo apt install libtiff5). When trying to build a library that depends on libtiff I get the following error:
checking for TIFFOpen in -ltiff... no
configure: error: libtiff check failed
Any suggestions on how to fix this? My guess is I have to modify LD_LIBRARY_PATH, but I don't know where apt installed libtiff

error in bazel/ tensorflow installation 'external:io_bazel_rules_closure: no such attribute 'urls' in 'http_archive' rule.'

Hi all I am trying to install tensor flow with GPU compatibility using this guide "guide 1" and guide 2 on ubuntu pc (cuda 8). I am stuck at installing tensorflow,
when I use ./configure, I getting this error
ERROR: /home/krishna/tensorflow/WORKSPACE:3:1: //external:io_bazel_rules_closure: no such attribute 'urls' in 'http_archive' rule.
ERROR: /home/krishna/tensorflow/WORKSPACE:3:1: //external:io_bazel_rules_closure: missing value for mandatory attribute 'url' in 'http_archive' rule.
ERROR: com.google.devtools.build.lib.packages.BuildFileContainsErrorsException: error loading package '': Encountered error while reading extension file 'closure/defs.bzl': no such package '#io_bazel_rules_closure//closure': error loading package 'external': Could not load //external package.
I am new to ubuntu, after reading a lot I understood that, the error has something to do with "version of bazel" (for version above 0.3.1 it does not apper).
When I use the command
$bazel version
Build label: 0.3.0
Build target: bazel-out/local-fastbuild/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Fri Jun 10 11:38:23 2016 (1465558703)
Build timestamp: 1465558703
Build timestamp as int: 1465558703
when i use
$ sudo apt-get install bazel
Reading package lists... Done
Building dependency tree
Reading state information... Done
bazel is already the newest version (0.4.5).
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
and
upgraded it using $ sudo apt-get upgrade bazel. Finally I tried
$ bazel version
Build label: 0.3.0
Build target: bazel-out/local-fastbuild/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Fri Jun 10 11:38:23 2016 (1465558703)
Build timestamp: 1465558703
Build timestamp as int: 1465558703
which shows me that I am at version 0.3.0. I even tried compiling tensorflow again,which gave me the same above error.
It looks like you have two versions of Bazel on your system (0.3.0 and 0.4.5). You can see what the current binary is by running which bazel. You can find all of the bazels on your system by running:
$ updatedb # This will take a while.
$ slocate bazel
Assuming this returns something like:
/etc/bazel/bin/bazel
/usr/bin/bazel
you can figure out which bazel is the "right" one (0.4.5) by running /usr/bin/bazel version etc. for each bazel slocate finds.
Once you find the right bazel, you want that to be the default, so you have to make sure Linux searches for Bazel in that directory first. If the right bazel is /usr/local/bin/bazel, you'd run:
$ export PATH="/usr/local/bin:$PATH"
Then you should be able to call "bazel" normally and your system will find the "right" one (you can also delete any old ones you find).
Alternatively, you can install Bazel using the installer which will tell you what directory it got installed in.

Phalcon 3 - Centos 7 Cpanel EasyApache 4 - php5.6

I am trying to install Phalcon with:
curl -s https://packagecloud.io/install/repositories/phalcon/stable/script.rpm.sh | sudo bash
yum install php56u-phalcon
but I get dependency errors:
Error: Package: php56u-phalcon-3.0.1-14.ius.el7.centos.x86_64 (phalcon_stable)
Requires: php56u-pdo(x86-64)
Error: Package: php56u-phalcon-3.0.1-14.ius.el7.centos.x86_64 (phalcon_stable)
Requires: php56u-common(x86-64)
Error: Package: php56u-phalcon-3.0.1-14.ius.el7.centos.x86_64 (phalcon_stable)
Requires: php56u(api) = 20131106
Error: Package: php56u-phalcon-3.0.1-14.ius.el7.centos.x86_64 (phalcon_stable)
Requires: php56u(zend-abi) = 20131226
These libraries are installed but with the modifier "ea-" of easy apache.
How I can install Phalcon 3 in Centos 7 cpanel easyapache 4?
Thanks in advance.
Seems like phalcon expecting you to have php56 from ius repository.
I've had same error, but because my php56 came from remi repo instead I had no modifier on php* packages, for example php-pdo package instead of php56u-pdo.
I've solved it this way:
yum install php-phalcon3
(can be php-phalcon2, php7-php-palcon3 and so on - see yum search phalcon)
In your case this probably won't help, because you have ea- modifier on php*.
Possibly somebody more experienced with yum could suggest how to solve this conflict. But you still have two more options:
compile phalcon.so from source code (described here: https://github.com/phalcon/cphalcon).
install php from ius Centos 7 repository.
UPD: I must add that I was unable to make phalcon (php-phalcon* from remi dedicated repos for php5.6 and php7) to work - I've got "child pid exit signal Segmentation fault".
As a general rule: your phalcon package should be from the same repo from which you've installed php and php-* packages(e.g. php-mysqlnd, php-pdo).
In my opinion, if you wnat to be sure that your library will work on particular machine the best way is to compile it on this or similar machine.