I tried to install heartbeat on Centos 7 by yum install heartbeat but it's giving me package not found.Does heartbeat (linux-HA) supported in centos 7 or not? .
Loading mirror speeds from cached hostfile
* base: mirrors.praction.in
* epel: epel.dionipe.id
* extras: mirrors.praction.in
* updates: mirrors.praction.in
No package heartbeat available.
Heartbeat is considered deprecate since RHEL7 / CentOS7.
Related
I am trying, unsuccessfully, to run "minikube start" on my UBUNTU 18.04.
The characteristics of the system are:
Windows 10 PC with Virtual Box 6.1.16
In Virtual Box I have installed Ubuntu 18.04 (11GB of memory and 2 processors)
I've also enabled nested virtualization
In Ubuntu I also installed (searching with google):virtualbox-dkms and linux-headers-generic
Every time I run
minikube start
I get the following messages
minikube v1.15.1 on Ubuntu 18.04
Automaticaally selected the virtualbox driver
Downloading VM boot image ...
minikube-v1.15.0.iso.sha256: 65 B / 65 B [-------] 100.00%? p / s 0s
minikube-v1.15.0.iso: 181.00 MiB / 181.00 MiB [] 100.00% 6.45 MiB p / s 28s
Starting control plne node minikube in cluster minikube
Downloading Kubernetes v1.19.4 preload ...
preloaded-images-k8s-v6-v1.19.4-docker-overlay2-amd64.tar.lz4: 486.35 MiB
Creating virtualbox VM (CPU = 2, Memory = 2600MB, Disk = 20000MB) ...
and here it stops.
I also thought that the problem was related to the lz4 format and that the machine was unable to decompress the image.
I then installed
liblz4-tool
but without success.
Could you help me?
Thanks
so I am using Pycharm 2019.2 with Python 2.7
and I can't download any package.
I have tried:
hard copying packages to Python2.7 directory
pip install urllib3[secure]
pip install --trusted-host=pypi.python.org --trusted-host=pypi.org
--trusted-host=files.pythonhosted.org xlrd
all refused to connect with errors like this:
Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, '_ssl.c:499: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version'),)': /simple/xlrd/
C:\Python27\lib\site-packages\pip-19.0.3-py2.7.egg\pip\_vendor\urllib3\util\ssl_.py:150: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
InsecurePlatformWarning
in Pycharm, I am getting the following error when trying to install a package:
Could not fetch URL https://pypi.org/simple/geopy/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/geopy/ (Caused by SSLError(SSLError(1, '_ssl.c:499: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version'),)) - skipping
Proposed Solution:
Try to run this command from the system terminal. Make sure that you use the correct version of 'pip' installed for your Python interpreter located at 'C:\Python27\python.exe'.
Everything is working perfectly fine suing python 3.4 but only with 2.7 I'm getting SSL error.
I can't change to 3.4 due to technical reasons at my workplace.
It is an Interpreter Issue. The code was originally written using python 3.7
System:
EC2 Instance Type: m5.2xlarge
OS: Ubuntu 14.04.5 LTS
Kernel Version: 4.4.0-1022-aws
vCPU: 8 Cores
Memory: 32Gib
Java Version: 1.8.0_171
We are running KAFKA in cluster mode with two kafka brokers(10.0.51.1 & 10.0.51.2) and three zookeeper nodes. I wanted to upgrade my AWS EC2 instance, so I ran sudo apt-get update and sudo apt-get upgrade and installed linux-aws kernel. After changing instance type, I started getting following error in my 10.0.51.2 kafka borker:
18/06/08 07:03:50 52902420 [kafka-network-thread-9092-0] ERROR kafka.network.Processor - Closing socket for /10.0.51.1 because of error
kafka.common.KafkaException: Wrong request type 18
at kafka.api.RequestKeys$.deserializerForKey(RequestKeys.scala:64)
at kafka.network.RequestChannel$Request.<init>(RequestChannel.scala:50)
at kafka.network.Processor.read(SocketServer.scala:450)
at kafka.network.Processor.run(SocketServer.scala:340)
at java.lang.Thread.run(Thread.java:748)
18/06/08 07:03:50 52902571 [kafka-network-thread-9092-2] ERROR kafka.network.Processor - Closing socket for /10.0.51.1 because of error
kafka.common.KafkaException: Wrong request type 16
at kafka.api.RequestKeys$.deserializerForKey(RequestKeys.scala:64)
at kafka.network.RequestChannel$Request.<init>(RequestChannel.scala:50)
at kafka.network.Processor.read(SocketServer.scala:450)
at kafka.network.Processor.run(SocketServer.scala:340)
at java.lang.Thread.run(Thread.java:748)
Only 1 broker is giving this error. But my KAFKA cluster is up and running, I can consume and produce from all topics.
Any help would be appreciated.
Thanks.
The client sent an ApiVersionsRequest (request code 18) and a ListGroupsRequest (request code 16). see source code
Probably not all brokers/consumers/producers are using the same version after the upgrade. Can you please verify and in case align the versions? new clients should be able to communicate to older version so probably the library used in your code is older.
Going through the motions to get TLS up and running for my website. I read under the AWS documentation to
sudo yum install -y mod24_ssl
but was getting a conflict on some dependencies.
I ended up reading a blog where someone mentioned sudo yum install mod_ssl and I ended up running that without any issues. Can someone let me know if this safe? What's the difference between mod_ssl and mod24_ssl?
Thanks
If your AWS instance is using the Amazon Linux 2 AMI you will use mod_ssl for Apache 2.4 installs.
Note the mod_ssl version is "2.4.6" and the AWS Repository is "amzn2-core".
Available Packages
Name : mod_ssl
Arch : x86_64
Epoch : 1
Version : 2.4.6
Release : 67.amzn2.6.1
Size : 110 k
Repo : amzn2-core/2017.12/x86_64
Summary : SSL/TLS module for the Apache HTTP Server
URL : http://httpd.apache.org/
License : ASL 2.0
Description : The mod_ssl module provides strong cryptography for the Apache Web
: server via the Secure Sockets Layer (SSL) and Transport Layer
: Security (TLS) protocols.
As #stdunbar said mod_ssl works with Apache 2.2 and mod24_ssl works with Apache 2.4.
We can see that the package descriptions are similar except for the Version:
[ec2-user]$ yum info mod_ssl
Available Packages
Name : mod_ssl
Arch : x86_64
Epoch : 1
Version : 2.2.32
Release : 1.9.amzn1
Size : 107 k
Repo : amzn-updates/latest
Summary : SSL/TLS module for the Apache HTTP Server
URL : http://httpd.apache.org/
License : ASL 2.0
Description : The mod_ssl module provides strong cryptography for the Apache Web
: server via the Secure Sockets Layer (SSL) and Transport Layer
: Security (TLS) protocols.
[ec2-user]$ yum info mod24_ssl
Installed Packages
Name : mod24_ssl
Arch : x86_64
Epoch : 1
Version : 2.4.27
Release : 3.71.amzn1
Size : 224 k
Repo : installed
From repo : amzn-updates
Summary : SSL/TLS module for the Apache HTTP Server
URL : http://httpd.apache.org/
License : ASL 2.0
Description : The mod_ssl module provides strong cryptography for the Apache Web
: server via the Secure Sockets Layer (SSL) and Transport Layer
: Security (TLS) protocols.
We can see what each package depends on using yum deplist:
[ec2-user]$ yum deplist mod_ssl
Loaded plugins: priorities, update-motd, upgrade-helper
26 packages excluded due to repository priority protections
package: mod_ssl.x86_64 1:2.2.32-1.9.amzn1
... snip ...
dependency: httpd = 2.2.32-1.9.amzn1
provider: httpd.x86_64 2.2.32-1.9.amzn1
... snip ...
[ec2-user]$ yum deplist mod24_ssl
Loaded plugins: priorities, update-motd, upgrade-helper
26 packages excluded due to repository priority protections
package: mod24_ssl.x86_64 1:2.4.27-3.71.amzn1
... snip ...
dependency: httpd24 = 2.4.27-3.71.amzn1
provider: httpd24.x86_64 2.4.27-3.71.amzn1
... snip ...
httpd and httpd24 conflict--you can't have both installed at the same time.
I am trying to install the latest version of cPanel on a server running Centos 6.6 and it is failing here:
[20150129.112152] Testing if it's possible to install a simple RPM
[20150129.112152] Retrieving http://httpupdate.cpanel.net/RPM/rpm_is_working-1.0-0.noarch.rpm
[20150129.112152] Preparing... ##################################################
[20150129.112152] rpm_is_working ##################################################
[20150129.112152] Now removing the RPM
info [updatenow] upcp Notification => root#server.serveraddress.com via EMAIL [level => 1]
Cpanel::iContact: icontact /usr/sbin/sendmail is not executable by 0
[20150129.112152] W An attempt to up/downgrade to 11.46.2.4 was blocked. Please review blockers.
Can't exec "/usr/local/cpanel/scripts/cpanel_initial_install": No such file or directory at
/home/cPanelInstall/selfgz11290/install line 146.
2015-01-29 11:21:52 148 (FATAL): Failure to exec /usr/local/cpanel/scripts/cpanel_initial_install
Removing /root/installer.lock
Does anyone have any ideas? I am trying to install this on an AWS EC2 instance that is running Centos 6.6. I tried opening my security group so that all traffic is allowed and this did not help.
It may be resulted from the failure of downloading essential files. I solved this problem on my server simply by clear /etc/sysconfig/iptables and stop the iptables service by service iptables stop.
What's more, I also delete ~/.cpan/, ~/.cpanm/, ~/.cpcpan/ and ~/cPanelInstall.