I have puppetmaster and agents versions 3.8.7 installed.
When I do a Puppet run, I get the following error:
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Syntax error at 'Enum'; expected ')' at
/etc/puppet/environments/production/modules/concat/manifests/init.pp:46
on node wiki
Why is this happening?
The issue is that you're running Puppet 3, whereas you have installed a recent version of the Puppet Concat module, which only supports Puppet 4 and 5.
If upgrading to Puppet 4 or 5 is not an option for you, you would need to install an older version of the Concat module that supports Puppet 3.
(Note that it's likely that you'll have the same problem with other modules too, as increasingly, Puppet 3 is no longer supported in Puppet Forge modules.)
Related
Following 2 links to setup Hyperledger Fabric 1.0 in system.
First link Hyperledger-fabric setup
After following commands
cd $GOPATH/src/github.com/hyperledger/fabric/devenv
vagrant up
vagrant ssh
Followed hypeledger latest setup docs
After using
cd $GOPATH/src/github.com/hyperledger/fabric
make dist-clean all
An error occured...
github.com/hyperledger/fabric/vendor/github.com/mattn/go-sqlite3 /usr/bin/ld: cannot find -lrocksdb collect2: error: ld returned 1 exit
status Makefile:137: recipe for target 'build/bin/peer' failed make:
*** [build/bin/peer] Error 2
On Left side my vagrant is running and right side is my Hyperledger Fabric 1.0 Setup command make dist-clean all
To me this seems to be problem of rocksdb, how can I resolve this?
Hyperledger Fabric 1.0 can be installed without having to build from source. The project publishes stable Docker images and binaries for each release. This may be a better approach to installing Fabric and its dependencies.
However, if you want to build from source, note that Vagrant is no longer needed. The build should be capable of running natively on most platforms (Mac, Windows and Ubuntu).
You will need the same prerequisites as for the Getting Started approach above - Docker (preferably the latest release), Go (1.9.x), Python 2.7 and Node 6.9.x (note that we do not yet support Node 7.x).
Occasionally, it has been observed that a fresh build (make all) from scratch may occasionally fail. If so, try running (make all) again.
As for the rocksdb error, Fabric no longer has a dependency on rocksdb and uses leveldb instead. It is entirely likely that because the vagrant environment gets little use of late, that it is not current.
I fond solution in one git hub link.
One can try to resolve this issue by using following commands-
apt-get install librocksdb-dev
apt-get install libsnappy-dev
apt-get install libbz2-dev
After this rockdb error should not be there. Will post more if found any other error and there solutions too.
When I run puppet agent -t on my server I get an error:
The logs from the puppet-master look like this:
Unfortunately, this is an error caused by using Ruby 1.8.7, a long EOL version of Ruby. Puppet uses Ruby to compile catalogs, and CentOS 6's upstream uses 1.8.7 Ruby, which has been EOL for 3 years.
The easiest way to fix this problem is to use Puppet 4 onwards, which packages it's own Ruby as part of the all-in-one package (to avoid errors like this on systems that support older Ruby versions)
I have installed both Puppet master and agent on machines running CentOS 6
Everything went well, until the moment I have tried to deploy a simple sample module: I got an error, explained on the picture.
Trying to edit the file didn't help and the file was actually updated each time from repository
I tried running a different module which resulted in the same error
The error is because the formatting for Ruby code will not work with older Ruby. The CentOS 6 upstream Ruby package is 1.8.7, which is a super old Ruby version, and has been EOL for 3 years since 2014.
To fix this problem, Puppet started packaging Ruby and other dependancies as part of an all-in-one package since Puppet 4. This means there's no dependancy hell when it comes to EOL Ruby, OpenSSL and any other dependancies: they're all bundled and supported as a single RPM, without affecting the system packages.
It also means that you don't break any applications that require a different system Ruby, and generally makes using Puppet a lot easier.
Adding to this, the version of Puppet in CentOS is 3.X, which is also EOL. You should upgrade to Puppet 4. Here's a handy script that will install the Puppet 4 agent package on CentOS 6: https://github.com/petems/puppet-install-shell
If you are limited to using Puppet 3 for whatever reason, there are a few less preferable solutions:
Download a new Ruby RPM for CentOS 6, (such as from this Github repo) or a CloudPackage.io repo (such as this one I made for CentOS 6 Ruby packages https://packagecloud.io/petems/ruby2/install)
Disadvantage: Those RPMs are not supported officially and might have unintentional issues
Fork the module to change the Ruby code
Disadvantage: This is a big maintenance cost, and you'll have to do this every time an update happens to the module upstream.
I am trying to install WAS7 using command line via putty and I am getting the following error:
[root#TVMSLD tools]# ./imcl install com.ibm.rational.was.v70.extension_1.0.0.20080911_1339 -repositories /home/admin/Softwares/WAS7.0/WAS70 -installationDirectory /opt/IBM/WebSphere/AppServer/V70/BASE -sharedResourcesDirectory /opt/IBM/InstallationManager/IMShared -acceptLicense -showProgress
25% 50% 75% 100%
------------------|------------------|------------------|------------------|
............................................................................
ERROR: The installation package 'IBM® WebSphere® Application Server Version 7.0 Test Environment' requires components supplied by other packages.
The required components might be supplied by the specified features of the following installation packages:
Package: Rational Application Developer 7.5.0 -- Features: Tools for WebSphere® Application Server, version 7.0
I tried the command with repository path like /home/admin/Softwares/WAS7.0/WAS70/disk1 and also /home/admin/Softwares/WAS7.0/WAS70/disk1/diskTag.inf
But I am getting the same error. Can anyone help please?
This is not standalone server, but test environment provided with Rational Application Developer. It can only be installed via RAD installation together with RAD.
See more info about the standalone developers version here.
I have an rpm compiled in centos 5.x which requires libnetsnmp.so.10 and other shared objects. I want to create an rpm of it which is to be run on centos 6.x but it fails to install as on installation it says :
error: Failed dependencies:
libnetsnmp.so.10()(64bit) is needed and so on...
But Centos 6.x contains libnetsnmp.so.20
So I created symbolic links of libnetsnmp.so.10 of libnetsnmp.so.20.
But problem is still the same.
So can you please help me to resolve this problem?
If recompiling for Centos 6 isn't an option, you can try two things, first, install the correct libnetsnmp in the Centos 6 server. If that's not an option, you can add the following to your RPM spec file:
Autoreq: no
This will cause it not to scan your binary for dependencies (such as dynamically linked libraries), and automatically build that into the RPM.
Of course, if that version of libnetsnmp is ACTUALLY required, your just hosing yourself down the road, but likely newer versions will work just fine.