`GLIBCXX_3.4.20′ not found Centos7

while starting deepstream output show like this how can i resolve this issue. I installed the latest version which is not available in yum repo by using rpm file

deepstream: /lib64/libstdc++.so.6: version GLIBCXX_3.4.20' not found (required by deepstream) deepstream: /lib64/libstdc++.so.6: versionGLIBCXX_3.4.21′ not found (required by deepstream) deepstream: /lib64/libstdc++.so.6: version `CXXABI_1.3.9′ not found (required by deepstream)

Centos7 iptables nor persisting after reboot

I’ve been researching and found a lot of consistent information about how to do this.

However, it is still not working.

I set up a couple iptables rules. I save them with: sudo service iptables save

I check /etc/sysconfig/iptables and the rules are saved there.

I then reboot the system and when it comes back, the new rules are not present.

Looking at /etc/sysconfig/iptables, they are still there.

I then proceed to do sudo systemctl restart iptables and the rules show up again.

Every time I reboot, I need to run the restart command again.

Any pointers?

Thanks!

Cryptodevice on top of DRBD with CentOS7

I have created a replicated drbd device.

On top, I have create an encrypted volume with cryptsetup and finally formatted with ext4. Additionally, I am using a keyfile to be able to automount the crypted device. (Please do insist this being unsecure. The keyfile is stored on an encrypted device itself, accessible only after giving the passphrase)

I want the device being automounted on boot so I added the entries in /etc/crypttab as well as /etc/fstab:

backuppc /dev/drbd1 /root/luks_key/backuppc.key luks

/dev/mapper/backuppc /mnt ext4 defaults 1 2

Unfortunately the device does not open during boot. Once booted I can activate the device and mount it without giving a passphrase.

I assume this is because the crypto setup tries to access the underlying /dev/drbd1 during boot while drbd is not up at this stage.

Question is:

How can I either -postpone cryptsetup until drbd is up and running or -force drbd to start earlier so cryptsetup will find the device?

Any clues? And yes, if there is no other solution I will do with rc.local file…

Thanks!

/K

Trouble removing package using Yum on CentOS7

Problem: Removing python-boto from the system and Yum. It appears to be no longer installed, but still appears in Yum.

Tried: yum clean all; yum check; rpm -e –noscripts python-boto and rpm -e –noscripts python-boto.noarch but has not resolved. Use find to check if package appears to be there. See below for detailed results of each.

Question: What else can I try and what risks are there with trying it

# yum list | grep boto python-boto.noarch                      2.25.0-2.el7.centos             extras python-boto3.noarch                     1.4.6-5.el7                     base python2-XStatic-roboto-fontface.noarch  0.4.3.2-4.el7                   epel python2-boto.noarch                     2.45.0-3.el7                    epel python2-boto3.noarch                    1.4.6-1.el7                     epel python2-botocore.noarch                 1.6.0-1.el7                     epel   # yum remove python-boto Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-               : manager This system is not registered with an entitlement server. You can use subscription-manager to register. No Match for argument: python-boto No Packages marked for removal   # yum clean all --verbose Loading "fastestmirror" plugin Loading "product-id" plugin Loading "search-disabled-repos" plugin Loading "subscription-manager" plugin Updating Subscription Management repositories. Unable to read consumer identity This system is not registered with an entitlement server. You can use subscription-manager to register. Config time: 0.074 Yum version: 3.4.3 Cleaning repos: base epel extras mariadb nodesource openproject-ce remi               : remi-php56 remi-php73 remi-safe updates Operating on /var/cache/yum/x86_64/7 (see CLEAN OPTIONS in yum(8) for details) Disk usage of /var/cache/yum/*/* after cleanup: 0      enabled repos 16 M   disabled repos:   16 M   /var/cache/yum/x86_64/7/centosplus 0      untracked repos 628    other data:   628    /var/cache/yum/x86_64/7/timedhosts 16 M   total   # yum list | grep boto python-boto.noarch                      2.25.0-2.el7.centos             extras python-boto3.noarch                     1.4.6-5.el7                     base python2-XStatic-roboto-fontface.noarch  0.4.3.2-4.el7                   epel python2-boto.noarch                     2.45.0-3.el7                    epel python2-boto3.noarch                    1.4.6-1.el7                     epel python2-botocore.noarch                 1.6.0-1.el7                     epel   # yum check Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-               : manager This system is not registered with an entitlement server. You can use subscription-manager to register. check all   # yum list | grep boto python-boto.noarch                      2.25.0-2.el7.centos             extras python-boto3.noarch                     1.4.6-5.el7                     base python2-XStatic-roboto-fontface.noarch  0.4.3.2-4.el7                   epel python2-boto.noarch                     2.45.0-3.el7                    epel python2-boto3.noarch                    1.4.6-1.el7                     epel python2-botocore.noarch                 1.6.0-1.el7                     epel   # yum remove python-boto Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-               : manager This system is not registered with an entitlement server. You can use subscription-manager to register. No Match for argument: python-boto No Packages marked for removal   # find / -name *boto* -print /usr/lib/python2.7/site-packages/boto3 /usr/lib/python2.7/site-packages/botocore /usr/lib/python2.7/site-packages/botocore-1.12.134.dist-info /usr/lib/python2.7/site-packages/boto3-1.9.134.dist-info  # rpm -e python-boto error: package python-boto is not installed # rpm -e --noscrips python-boto rpm: --noscrips: unknown option # rpm -e --noscripts python-boto error: package python-boto is not installed # rpm -e --noscripts python-boto.noarch error: package python-boto.noarch is not installed 

Your help greatly appreciated.

Centos7, firewall-cmd –reload, “COMMAND_FAILED –state requires an argument” How to give state an argument?

I am using Centos7 and have just made some changes to the firewall. I am trying to configure my firewall to filter my ssh connection. I am following the How To documentation on Centos7 How Tos, Securing OpenSSh: Filter SSH at the Firewall. Essentially these fire wall settings are recording access to port 22, and limiting the number of times the ip can access the port to 4 times in 60 seconds. These are the commands I have just ran.

iptables -A INPUT -p tcp --dport 22 -m state --state NEW -m recent --set --name ssh --rsource iptables -A INPUT -p tcp --dport 22 -m state --state NEW -m recent ! --rcheck --seconds 60 --hitcount 4 --name ssh --rsource -j ACCEPT   firewall-cmd --permanent --direct --add-rule ipv4 filter INPUT_direct 0 -p tcp --dport 22 -m state --state NEW -m recent --set firewall-cmd --permanent --direct --add-rule ipv4 filter INPUT_direct 1 -p tcp --dport 22 -m state --state NEW -m recent --update --seconds 30 --hitcount 4 -j REJECT --reject-with tcp-reset firewall-cmd --reload  

On firewall-cmd –reload I recive an the error

Error: COMMAND_FAILED: Direct: '/usr/sbin/iptables-restore -w -n' failed: iptables-restore v1.4.21: option "--state" requires an argument Error occured at line: 2 Try 'iptables-restore -h' or 'iptables-restore --help' for more infomation. 

Not sure what to do next. How do i give state an argument?