I am getting following error while installing.
$ sudo yum install rabbitmq-server
Loaded plugins: aliases, changelog, fastestmirror, kabi, presto, refresh-packagekit, security, tmprepo, ulninfo, verify, versionlock
Loading support for kernel ABI
Setting up Install Process
Loading mirror speeds from cached hostfile
* epel: archive.linux.duke.edu
* ol6_UEKR3: slcac475.us.oracle.com
* ol6_latest: slcac475.us.oracle.com
Resolving Dependencies
--> Running transaction check
---> Package rabbitmq-server.noarch 0:3.1.5-1.el6 will be installed
--> Finished Dependency Resolution`
...
...
...
groupadd: Can't get unique system GID (no more available GIDs)
useradd: group 'rabbitmq' does not exist
error: %pre(rabbitmq-server-3.1.5-1.el6.noarch) scriptlet failed, exit status 6
Error in PREIN scriptlet in rpm package rabbitmq-server-3.1.5-1.el6.noarch
error: install: %pre scriptlet failed (2), skipping rabbitmq-server-3.1.5-1.el6
Verifying :
rabbitmq-server-3.1.5-1.el6.noarch
Failed
rabbitmq-server.noarch 0:3.1.5-1.el6
Complete!
Note: I have already installed the erlang
I have refereed few posts already there
Installing rabbitmq-server on RHEL
RabbitMQ install issue on Centos 5.5
Go to /etc/login.defs and check if you have something like this, if not add it into it.
SYS_GID_MIN 2000
SYS_GID_MAX 9000
Related
I want to install my #vue/cli 4.0.5 app under docker and using https://medium.com/#jwdobken/vue-with-docker-initialize-develop-and-build-51fad21ad5e6 link :
I modified the command line : modified node source from 11-alpine and renamed project name and installed the project, but running command
yarn serve
I got error that serve was not found :
me#athoe:/mnt/_work_sdb8/wwwroot/lar/VApps/DOCKER_TEST$ mkdir vtaskproject && cd "$_" && docker run --rm -v "${PWD}:/$(basename `pwd`)" -w "/$(basename `pwd`)" -it node:11-alpine sh -c "yarn global add #vue/cli && vue create ."
Unable to find image 'node:11-alpine' locally
11-alpine: Pulling from library/node
e7c96db7181b: Already exists
0119aca44649: Pull complete
40df19605a18: Pull complete
82194b8b4a64: Pull complete
Digest: sha256:8bb56bab197299c8ff820f1a55462890caf08f57ffe3b91f5fa6945a4d505932
Status: Downloaded newer image for node:11-alpine
yarn global v1.15.2
[1/4] Resolving packages...
warning #vue/cli > #vue/cli-ui > vue-cli-plugin-apollo > apollo > git-parse > babel-polyfill > core-js#2.6.11: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
warning #vue/cli > #vue/cli-ui > vue-cli-plugin-apollo > apollo > git-parse > babel-polyfill > babel-runtime > core-js#2.6.11: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
[2/4] Fetching packages...
info fsevents#1.2.11: The platform "linux" is incompatible with this module.
info "fsevents#1.2.11" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
warning Your current version of Yarn is out of date. The latest version is "1.21.1", while you're on "1.15.2".
info To upgrade, run the following command:
$ curl --compressed -o- -L https://yarnpkg.com/install.sh | bash
success Installed "#vue/cli#4.1.1" with binaries:
- vue
Done in 32.17s.
? Your connection to the default yarn registry seems to be slow.
Use https://registry.npm.taobao.org for faster installation? Yes
Vue CLI v4.1.1
? Generate project in current directory? Yes
Vue CLI v4.1.1
? Please pick a preset: default (babel, eslint)
? Pick the package manager to use when installing dependencies: Yarn
Vue CLI v4.1.1
��� Creating project in /vtaskproject.
��� Installing CLI plugins. This might take a while...
yarn install v1.15.2
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents#1.2.11: The platform "linux" is incompatible with this module.
info "fsevents#1.2.11" is an optional dependency and failed compatibility check. Excluding it from installation.
success Saved lockfile.
Done in 77.43s.
���� Invoking generators...
���� Installing additional dependencies...
yarn install v1.15.2
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents#1.2.11: The platform "linux" is incompatible with this module.
info "fsevents#1.2.11" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
Done in 24.82s.
��� Running completion hooks...
���� Generating README.md...
���� Successfully created project vtaskproject.
���� Get started with the following commands:
$ yarn serve
me#athoe:/mnt/_work_sdb8/wwwroot/lar/VApps/DOCKER_TEST/vtaskproject$ yarn serve
00h00m00s 0/0: : ERROR: [Errno 2] No such file or directory: 'serve'
serge#athoe:/mnt/_work_sdb8/wwwroot/lar/VApps/DOCKER_TEST/vtaskproject$ yarn --version
0.32
I see that on successfull installation newly created project dir was selected.
Also in the provided article next was :
Dockerfile The Dockerfile is identical to the given example in the
documentation. Only the build-stage is split up into an install-stage
and a build-stage, since we don’t need to build when we are
developing!
But the thin is I do not see any Dockerfile file in the created project : https://imgur.com/a/mKrdFgi as I expected.
Had Dockerfile be there and how move next ?
$ lsb_release -d; uname -r; uname -i
Description: Ubuntu 18.04.3 LTS
4.15.0-72-generic
x86_64
$ docker --version
Docker version 19.03.5, build 633a0ea838
We have some older servers with the legacy Docker package installed from the distribution package repository. Either from manual installs
$ yum install docker
Or older manifests
package { 'docker':
ensure => present,
}
We want to migrate to the official Docker repository and packages via the "supported" puppetlabs-docker module.
include docker
However, the legacy Docker packages are not removed or otherwise managed by this new module!
[vagrant#localhost ~]$ sudo -i puppet apply -e 'include docker'
Notice: Compiled catalog for localhost.localdomain in environment production in 0.42 seconds
Notice: /Stage[main]/Docker::Repos/Yumrepo[docker]/ensure: created
Error: Execution of '/bin/yum -d 0 -e 0 -y install docker-ce' returned 1: Error: docker-ce conflicts with 2:docker-1.13.1-75.git8633870.el7.centos.x86_64
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Error: /Stage[main]/Docker::Install/Package[docker]/ensure: change from 'purged' to 'present' failed: Execution of '/bin/yum -d 0 -e 0 -y install docker-ce' returned 1: Error: docker-ce conflicts with 2:docker-1.13.1-75.git8633870.el7.centos.x86_64
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
How do we make sure the legacy package is removed before installing the new package?
You want to start by ensuring the legacy package is absent.
package { 'docker':
ensure => absent,
}
But, you can't use Package['docker'], because the new puppetlabs-docker module already declares it. You have to do something like this:
package { 'legacy-docker':
ensure => absent,
name => 'docker',
}
There are a number of legacy prerequisite packages that also need to be removed, too.
package { [
'docker-client',
'docker-client-latest',
'docker-common',
'docker-latest',
'docker-latest-logrotate',
'docker-logrotate',
'docker-selinux',
'docker-engine-selinux',
'docker-engine',
]:
ensure => absent,
}
So, all together, this ordering seems to work implicitly.
package { 'legacy-docker':
ensure => absent,
name => 'docker',
}
package { [
'docker-client',
'docker-client-latest',
'docker-common',
'docker-latest',
'docker-latest-logrotate',
'docker-logrotate',
'docker-selinux',
'docker-engine-selinux',
'docker-engine',
]:
ensure => absent,
}
include docker
Actually, this seems to cause problems on subsequent runs of the manifest... common second-level dependencies are removed!
Error: Execution of '/bin/rpm -e container-selinux-2.68-1.el7.noarch' returned 1: error: Failed dependencies:
container-selinux >= 2.9 is needed by (installed) docker-ce-18.06.1.ce-3.el7.x86_64
Error: /Stage[main]/Profile::Docker/Package[docker-selinux]/ensure: change from '2:2.68-1.el7' to 'absent' failed: Execution of '/bin/rpm -e container-selinux-2.68-1.el7.noarch' returned 1: error: Failed dependencies:
container-selinux >= 2.9 is needed by (installed) docker-ce-18.06.1.ce-3.el7.x86_64
Error: Execution of '/bin/rpm -e container-selinux-2.68-1.el7.noarch' returned 1: error: Failed dependencies:
container-selinux >= 2.9 is needed by (installed) docker-ce-18.06.1.ce-3.el7.x86_64
Error: /Stage[main]/Profile::Docker/Package[docker-engine-selinux]/ensure: change from '2:2.68-1.el7' to 'absent' failed: Execution of '/bin/rpm -e container-selinux-2.68-1.el7.noarch' returned 1: error: Failed dependencies:
container-selinux >= 2.9 is needed by (installed) docker-ce-18.06.1.ce-3.el7.x86_64
Well, the package resource doesn't have a refreshonly kind of property, so we need to resort to an exec resource. Ugh.
package { 'legacy-docker':
ensure => absent,
name => 'docker',
notify => Exec['autoremove'],
}
exec { 'autoremove':
command => '/usr/bin/yum -y autoremove',
refreshonly => true,
}
include docker
This is... reasonable? The only thing might be ordering, you might explore explicit resource ordering using ->.
I am trying to configure DSE on newly configured centos 7 VM but I am getting error Attempting to configure dse-full 5.1.0, but found a different version installed. Upgrades and downgrades aren't supported." (opscd-pool-4) I am not able to understand why getting this error when the machine is completely new, even I haven't run any DSE command.
ERROR: Received error from node event-subtype="MeldError" job-id="a38724e1-2139-45f5-9266-079638c2ca2e" name="cassandra-5" ssh-management-address="192.168.159.175" node-id="dafe635a-6e98-4ae6-b0ea-6afa0da51731" event-type="error" message="Attempting to configure dse-full 5.1.0, but found a different version installed. Upgrades and downgrades aren't supported." (opscd-pool-4)
I am using Opscentre to configure Node.
Here you go detailed log of LCM
2017-11-29 05:38:37,753 [opscenterd] INFO: configure job started for node name="cassandra-5" ssh-management-address="192.168.138.237" node-id="dafe635a-6e98-4ae6-b0ea-6afa0da51731" (async-thread-macro-32)
2017-11-29 05:38:37,776 [opscenterd] INFO: Trying to establish ssh connection name="cassandra-5" ssh-management-address="192.168.138.237" node-id="dafe635a-6e98-4ae6-b0ea-6afa0da51731" node-name="cassandra-5" job-id="4fae4fe1-ca3c-4924-abdb-62c4cf4ad878" (async-thread-macro-32)
2017-11-29 05:38:38,515 [opscenterd] INFO: Received milestone from node name="cassandra-5" ssh-management-address="192.168.138.237" node-id="dafe635a-6e98-4ae6-b0ea-6afa0da51731" message="Uploaded facts to OpsCenter server" job-id="4fae4fe1-ca3c-4924-abdb-62c4cf4ad878" (opscd-pool-0)
2017-11-29 05:38:40,135 [opscenterd] ERROR: Received error from node event-subtype="MeldError" job-id="4fae4fe1-ca3c-4924-abdb-62c4cf4ad878" name="cassandra-5" ssh-management-address="192.168.138.237" node-id="dafe635a-6e98-4ae6-b0ea-6afa0da51731" event-type="error" message="Attempting to configure dse-full 5.1.0, but found a different version installed. Upgrades and downgrades aren't supported." (opscd-pool-7)
2017-11-29 05:38:40,161 [opscenterd] ERROR: Configure job 4fae4fe1-ca3c-4924-abdb-62c4cf4ad878 failed! (async-thread-macro-33)
2017-11-29 05:38:41,102 [opscenterd] INFO: configure job finished for node name="cassandra-5" ssh-management-address="192.168.138.237" node-id="dafe635a-6e98-4ae6-b0ea-6afa0da51731" (async-thread-macro-32)
Here you go node info:
[root#li1639-135 ~]# dpkg -l dse-full
-bash: dpkg: command not found
[root#li1639-135 ~]# yum info dse-full
Loaded plugins: fastestmirror
base | 3.6 kB 00:00
extras | 3.4 kB 00:00
updates | 3.4 kB 00:00
(1/4): base/7/x86_64/group_gz | 156 kB 00:00
(2/4): extras/7/x86_64/primary_db | 130 kB 00:00
(3/4): base/7/x86_64/primary_db | 5.7 MB 00:00
(4/4): updates/7/x86_64/primary_db | 3.6 MB 00:00
Determining fastest mirrors
* base: mirrors.linode.com
* extras: mirrors.linode.com
* updates: mirrors.linode.com
Error: No matching Packages to list
Job ID4fae4fe1-ca3c-4924-abdb-62c4cf4ad878
11/29/2017, 5:38:40AM UTC ERROR - MELDERROR Attempting to configure dse-full 5.1.0, but found a different version installed. Upgrades and downgrades aren't supported.
11/29/2017, 5:38:40AM UTC SHELL-COMMAND - RESULT Finished executing command: rpm -qa | grep -E ^dse-full-[[:digit:]] | grep 5.1.0
11/29/2017, 5:38:39AM UTC SHELL-COMMAND - INVOCATION Invoked command: rpm -qa | grep -E ^dse-full-[[:digit:]] | grep 5.1.0
11/29/2017, 5:38:39AM UTC CHECK - IS-PACKAGE-INSTALLED Checking if package dse-full is installed with version 5.1.0
11/29/2017, 5:38:39AM UTC CHANGE - PACKAGE-PROXY Not using proxy
11/29/2017, 5:38:38AM UTC MILESTONE - UPLOADED-FACTS Uploaded facts to OpsCenter server
11/29/2017, 5:38:38AM UTC SHELL-COMMAND - INVOCATION Invoked command: if [ -x "$(which yum)" ] && [ -f "/etc/redhat-release" -o -f "/etc/SuSE-release" -o -f "/etc/system-release" ]; then echo -n "yum"; elif [ -x "$(which...
Updated Answer
I was able to sync up with Ranjeet offline and found that the logs posted above were the result of configure jobs, which require that DSE is already installed. When running install jobs, things proceeded as expected.
There were also some issues with newly supported platforms and platform checks working in confusing ways, but none of that is reflected in the logs for the original post in this question.
Original Answer
OpsCenter/LCM engineer here, I work on the provisioning features.
"Attempting to configure dse-full 5.1.0, but found a different version installed. Upgrades and downgrades aren't supported." The meaning of the error message seems pretty clear. You're asking OpsCenter/LCM to install/configure DSE 5.1.0. Are you positive that you don't have a different version already installed?
On apt-based target machines, you can check what version of DSE is install with 'dpkg -l dse-full'
On yum-based target machines, you can check what version of DSE is installed with 'yum info dse-full'
If you're really trying to install DSE 5.1.0, but a different version is already present on your nodes, you'll have to upgrade/downgrade outside OpsCenter LCM and can the resume managing configs with LCM after the desired version is installed. See http://docs.datastax.com/en/upgrade/doc/upgrade/datastax_enterprise/upgrdDSE.html
If you're attempting to install some other version (which matches what's already installed), then you'll have to clone your config profile and set the correct DSE version when you create the new CP. See: https://support.datastax.com/hc/en-us/articles/212267063-Lifecycle-Manager-Cloning-Configuration-Profiles
If you believe the error from OpsCenter/LCM is mistaken, and that you don't really have a different version of DSE installed on the target nodes, then we'll need more log snippets from LCM with the events leading up to the error, and information about how you confirmed the DSE version on all nodes.
installed neo4j 2.2.1 after first removing the previous version.
service neo4j-service start
produces the error:
Failed to start neo4j-service.service: Unit neo4j-service.service failed to load: No such file or directory.
System is:
system: os => {"name"=>"Ubuntu", "family"=>"Debian", "release"=>{"major"=>"15.04", "full"=>"15.04"}, "lsb"=>{"distcodename"=>"vivid", "distid"=>"Ubuntu", "distdescription"=>"Ubuntu 15.04", "distrelease"=>"15.04", "majdistrelease"=>"15.04"}}
Output of the install script:
root#cb-8:~# aptitude install neo4j -y # Install Neo4j, community edition
The following NEW packages will be installed:
daemon{a} neo4j
0 packages upgraded, 2 newly installed, 0 to remove and 0 not to upgrade.
Need to get 0 B/53.2 MB of archives. After unpacking 62.4 MB will be used.
Selecting previously unselected package daemon.
(Reading database ... 183856 files and directories currently installed.)
Preparing to unpack .../daemon_0.6.4-1_amd64.deb ...
Unpacking daemon (0.6.4-1) ...
Selecting previously unselected package neo4j.
Preparing to unpack .../archives/neo4j_2.2.1_all.deb ...
Unpacking neo4j (2.2.1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (219-7ubuntu3) ...
Setting up daemon (0.6.4-1) ...
Setting up neo4j (2.2.1) ...
update-rc.d: error: initscript does not exist: /etc/init.d/neo4j-service
dpkg: error processing package neo4j (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
neo4j
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package. Trying to recover:
Setting up neo4j (2.2.1) ...
update-rc.d: error: initscript does not exist: /etc/init.d/neo4j-service
dpkg: error processing package neo4j (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
neo4j
root#cb-8:~# service neo4j-service status
● neo4j-service.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
/etc/init.d/neo4j-service does in fact exist.
lrwxrwxrwx 1 root root 36 Mar 5 17:28 /etc/init.d/neo4j-service -> /opt/neo4j-community-2.1.7/bin/neo4j
I'm out of ideas and hoping someone might be able to point me in the right direction.
~ Ross
I had the same exact error. However, if installing newer version (3.3.0 in my case) of neo4j the syntax is different. It should be:
service neo4j start
not
service neo4j-service start
To double check you can do:
ls /etc/init.d | grep neo4j
In my case it finds neo4j
Problem solved.
2.2.1 was still linking to 2.1.7 somehow.
removed the spurious link and it all worked.
Just setting up rails and RVM on a new laptop and i'm getting this error when running
Error running 'requirements_osx_port_update_system ruby-2.0.0-p247',
please read /Users/#####/.rvm/log/1380821805_ruby-2.0.0-p247/update_system.log
Requirements installation failed with status: 1.
When running this
sudo rvm install ruby
Which produces this code.
[2013-10-03 13:36:45] requirements_osx_port_update_system
requirements_osx_port_update_system ()
{
__rvm_try_sudo port -dv selfupdate || return $?
}
current path: /Users/matthewpetitt
command(2): requirements_osx_port_update_system ruby-2.0.0-p247
DEBUG: Copying /Users/matthewpetitt/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences
DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
---> Updating MacPorts base sources using rsync
rsync: failed to connect to rsync.macports.org: Operation timed out (60)
rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync- 42/rsync/clientserver.c(105) [receiver=2.6.9]
Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
Exit code: 10
DEBUG: Error synchronizing MacPorts sources: command execution failed
while executing
"macports::selfupdate [array get global_options] base_updated"
Error: Error synchronizing MacPorts sources: command execution failed
To report a bug, follow the instructions in the guide:
http://guide.macports.org/#project.tickets
Error: /Users/matthewpetitt/.rvm/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed
I already have Xcode and Xcode command line tools installed. Anyone fixed something like this before.
Realized that it was just some network configuration at work that must have been blocking the ports. Check your network permissions or try a different network.
You need to make sure this command can be run first:
sudo port -dv selfupdate
This can be temporary network problem - if it is not follow the displayed instructions.