trying to install pgbouncer on amazon met this:
[root#somehost ~]# uname -a
Linux somehost 4.4.35-33.55.amzn1.x86_64 #1 SMP Tue Dec 6 20:30:04 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[root#somehost ~]# yum install pgbouncer
Loaded plugins: priorities, update-motd, upgrade-helper
No package pgbouncer available.
Error: Nothing to do
Went to github - found only compilable version. Googled and decided to post solution below
at The PostgreSQL Global Development Group repo copy link to your linux release (in my case Amazon Linux AMI 2015.03 - x86_64) and run:
rpm -Uvh https://download.postgresql.org/pub/repos/yum/9.3/redhat/rhel-6-x86_64/pgdg-ami201503-93-9.3-3.noarch.rpm
yum install pgbouncer
as result:
Installed:
pgbouncer.x86_64 0:1.7.2-6.rhel6
Related
All. I recently built a RHEL 8.5 (Ootpa) VM with all the bells and whistles in my home lab. II want to run yum update -y to see if there's a link between 8.6 and 8.5 not subscribing. Below is a copy of the output on my server:
[~]$ sudo subscription-manager attach --auto
Installed Product Current Status:
Product Name: Red Hat Enterprise Linux for x86_64
Status: Not Subscribed
Unable to find available subscriptions for all your installed products.
[erik#RHEL85-1 ~]$ sudo subscription-manager list
+-------------------------------------------+
Installed Product Status
+-------------------------------------------+
Product Name: Red Hat Enterprise Linux for x86_64
Product ID: 479
Version: 8.5
Arch: x86_64
Status: Not Subscribed
Status Details: Not supported by a valid subscription.
Starts:
Ends:
[~]$ sudo yum repolist
Updating Subscription Management repositories.
repo id repo name
packages-microsoft-com-prod packages-microsoft-com-prod
[~]$
We are using Nagios XI with Nagios Core 4.4.5. We have updated clients to nrpe 4.0.3 agent. We get "Remote does not support Version 3 Packets" messages in the server log. How to solve this, shouldn't nrpe 4.0.3 support version 3 packets by default. Is there something missing in the configuration? We know that requests can be configured to use version 2, only, but using the newest version is better, isn't it?
EDIT:
nagios-server:~$ /usr/local/nagios/bin/nagios -h
Nagios Core 4.4.5
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 2019-08-20
License: GPL
nagios-server:~$ cat /usr/local/nagiosxi/var/xiversion
full=5.6.7
major=5
minor=6.7
releasedate=2019-09-26
release=5607
Most likely you updated the NRPE client but did not update the plugins in the agent machine
Run these commands to check some plugins versions (nrpe, http, ping):
/usr/lib/nagios/plugins/check_nrpe --version
/usr/lib/nagios/plugins/check_http --version
/usr/lib/nagios/plugins/check_ping --version
Also run this command to check the nrpe daemon version:
/usr/sbin/nrpe-ng --version
Most likely you would get reported version below 3 so you will need to update the plugins.
solr-5.4.0 version
My Java version
java -version
java version "1.7.0_91"
OpenJDK Runtime Environment (IcedTea 2.6.3) (7u91-2.6.3-0ubuntu0.14.04.1)
OpenJDK 64-Bit Server VM (build 24.91-b01, mixed mode)
I did all steps finally am getting this error
sudo service solr status
Found 1 Solr nodes:
Solr process 6003 from /var/solr/solr-8983.pid not found.
How to fix this error?
That Digital Ocean tutorial recommends Java 8 with Solr 5 and provides installation instructions using a PPA. I also found another SO question where switching to Java 8 was the resolution.
I created a fresh Ubuntu 14.04 VM using Vagrant and VirtualBox with these commands...
vagrant init ubuntu/trusty64
vagrant up
Then I followed the tutorial with Solr 5.4.0, and got the same error you did. However, my Solr logs were not deleted, so I was able to find this...
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 402653184 bytes for committing reserved memory.
My Vagrant VM had 512 MB of RAM so I doubled that to 1 GB which is recommended in the tutorial, did a vagrant reload, and Solr started working. Here is my minimal Vagrantfile...
Vagrant.configure(2) do |config|
config.vm.box = "ubuntu/trusty64"
config.vm.network "private_network", ip: "192.168.33.10"
config.vm.provider "virtualbox" do |vb|
vb.memory = "1024"
end
end
I'm using VirtualBox 5.0.10 and Vagrant 1.8.1. I hope this works for you.
UPDATE: I just went through the tutorial again with a 32-bit Ubuntu 14.04 VM (ubuntu/trusty32 in Vagrantfile) and that also worked. So if you're on a 32-bit host or the 64-bit VM doesn't work for you, the 32-bit VM should work.
I will throw my answer in here just in case someone else spends another hour like I did.
Solr version 6.1.0 + Java 1.7 same error.
I had to upgrade to 1.8. How did I know that was the problem?
:/var/solr/logs# cat solr-8983-console.log
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/eclipse/jetty/start/Main : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:803)
at ....
The 52 version means you need Java 1.8.
Upgrade Ubuntu using
$ sudo add-apt-repository ppa:webupd8team/java
$ sudo apt-get update
$ sudo apt-get install oracle-java8-installer
Credit to this comment.
On a client's legacy Rails 2.1.1 app, I'm encountering an error where ruby crashes and emits 'Illegal instruction.' The crash is triggered by calls to methods on Digest::SHA2.
>> Digest::SHA2
=> Digest::SHA2
>> Digest::SHA2.new()
Illegal instruction
The Rails app is running on two servers behind a load balancer. The stacks on the two servers are very close to being identical and only one triggers the crash. They're both REE 1.8.7, Rails 2.1 and Debian 6. One is running the Linux kernel version 3.9.3 and one is running version 3.9.2—but I'm unsure how to determine if that's even relevant.
Digest::SHA2 seems to be mostly implemented in C. I know very little C and diagnosing this one is over my head. Any help / pointers in the right direction would be greatly appreciated!
Thanks a bunch!!
Environment Info
Here's the REE source for Digest::SHA2:
https://github.com/FooBarWidget/rubyenterpriseedition187-330/tree/master/ext/digest/sha2
On the server that's encountering the crash:
hostname#node1:~/appname$ cat /etc/issue
Debian GNU/Linux 6.0 \n \l
hostname#node1:~/appname$ uname -a
Linux node1.hostname.org 3.9.2-x86_64-[redacted] #1 SMP Tue May 14 17:16:34 EDT 2013 x86_64 GNU/Linux
hostname#node1:~/appname$ which ruby
/opt/ruby-enterprise-1.8.7-2012.02/bin/ruby
hostname#node1:~/appname$ irb
irb(main):001:0> require 'digest'
=> true
irb(main):002:0> Digest::SHA2.hexdigest('foo')
=> "2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae"
irb(main):003:0> exit
hostname#node1:~/appname$ ./script/console
Loading development environment (Rails 2.1.1)
>> Digest::SHA2.hexdigest('foo')
Illegal instruction
On the server that is not crashing:
hostname#node2:~/appname$ cat /etc/issue
Debian GNU/Linux 6.0 \n \l
hostname#node2:~/appname$ uname -a
Linux node2.hostname.org 3.9.3-x86_64-[redacted] #1 SMP Mon May 20 10:22:57 EDT 2013 x86_64 GNU/Linux
hostname#node2:~/appname$ which ruby
/opt/ruby-enterprise-1.8.7-2012.02/bin/ruby
hostname#node2:~/appname$ irb
irb(main):001:0> require 'digest'
=> true
irb(main):002:0> Digest::SHA2.hexdigest('foo')
=> "2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae"
irb(main):003:0> exit
hostname#node2:~/appname$ ./script/console
Loading development environment (Rails 2.1.1)
>> Digest::SHA2.hexdigest('foo')
=> "2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae"
The xdebug server doesn't connect to any of the clients on port 9000 ie:Netbeans IDE ,debugclient etc.xdebug is shown in phpinfo output.The above clients keep on waiting for the connection to be established.when ever I try to run a php script from the cli it gives the following warning message:
"PHP Warning: Module 'xdebug' already loaded in Unknown on line 0"
The 9000 port has been opened and shows up in the netstat --numeric-port -l command.
I have no idea what might have gone wrong.I have checked all the configuration files,everything seems ok. Any help will be appreciated.
Section of my configuration files
Linux abc.localdomain 3.1.1-2.fc16.x86_64 #1 SMP Mon Nov 14 15:46:10 UTC 2011 x86_64
This program makes use of the Zend Scripting Language Engine:
Zend Engine v2.3.0, Copyright (c) 1998-2011 Zend Technologies
with Xdebug v2.1.2, Copyright (c) 2002-2011, by Derick Rethans
[Zend]
zend_extension=/usr/lib64/php/modules/xdebug.so
[XDebug]
xdebug.remote_enable=On
xdebug.remote_autostart=On
xdebug.remote_handler=dbgp
xdebug.remote_host=localhost
xdebug.remote_port=9000
xdebug.remote_mode=req
xdebug.remote_log=/var/log/xdebug.log
php_api no. coincides
Xdebug Simple DBGp client (0.10.0)
Copyright 2002-2007 by Derick Rethans.
- libedit support: enabled
Waiting for debug server to connect.
Is it black magic!!
Thank You
It was actually Selinux not allowing Httpd to connect to other network resources.
Setting the boolean for httpd solved the problem:
setsebool -P httpd_can_network_connect on
OS Fedora 16-X_64
For me the solution was
sudo chcon -R -h -t /path/to/xdebug.so
meaning SELinux now allows httpd to execute this shared object.