Discuss

discuss@lists.centos.org

2 participants
34758 discussions

Citrix receiver and certificates on CentOS 7
by Nicolas Kovacs 22 Apr '19

22 Apr '19

Hi, I'm currently migrating a client's workstation from OpenSUSE Leap 15.0 to my personal blend of CentOS 7 and KDE. The client has some extra software installed on his machine, and one of these applications is causing me some troubles: Citrix Receiver. Here's my old blog article on installing Citrix Receiver on OpenSUSE : * https://www.microlinux.fr/citrix-receiver-opensuse-leap-15-0/ The application's certificate store is incomplete, so here's how I resolved the problem under OpenSUSE : # cd /opt/Citrix/ICAClient/keystore/ # rm -rf cacerts/ # ln -s /etc/ssl/certs cacerts Once this is done, Citric Receiver works perfectly under OpenSUSE. Now I tried to do the same thing under CentOS 7. The certificates are stored in a different directory, so here's what I did. # cd /opt/Citrix/ICAClient/keystore/ # rm -rf cacerts/ # ln -s /etc/pki/tls/certs cacerts Unfortunately this doesn't seem to work. Which leaves me clueless. Any suggestions? Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

1 1

Measure network bandwidth per process
by Kaushal Shriyan 21 Apr '19

21 Apr '19

Hi, Is there a way to measure network bandwidth per process in CentOS Linux release 7.6.1810 (Core) using any utility? I was reading about nethogs but it does not have the option to run it in daemon mode so that we can take a look at historical data to figure out the process which was consuming high network bandwidth instead it is a good tool for Live monitoring. Please suggest. Thanks in Advance. Best Regards, Kaushal

2 2

Does devtmps and tmpfs use underlying hard disk storage or Physical Memory (RAM)
by Kaushal Shriyan 21 Apr '19

21 Apr '19

Hi, I am running the below command on CentOS Linux release 7.6.1810 (Core) # df -hT --total Filesystem Type Size Used Avail Use% Mounted on /dev/xvda1 xfs 150G 8.0G 143G 6% / devtmpfs devtmpfs 7.8G 0 7.8G 0% /dev tmpfs tmpfs 7.8G 0 7.8G 0% /dev/shm tmpfs tmpfs 7.8G 817M 7.0G 11% /run tmpfs tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/995 tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/1000 total - 185G 8.8G 176G 5% - # Does devtmpfs and tmpfs use underlying hard disk storage or does it uses Physical Memory (RAM). What is the purpose of devtmpfs which is mounted on /dev, tmpfs mounted on /dev/shm and so on and so forth. What is the difference between devtmpfs and tmpfs? I will appreciate if anyone can help me understand the above output. Thanks in Advance and i look forward to hearing from you. Best Regards, Kaushal

4 3

CentOS-announce Digest, Vol 170, Issue 5
by centos-announce-request＠centos.org 20 Apr '19

20 Apr '19

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2019:0778 Moderate CentOS 7 java-11-openjdk Security Update (Johnny Hughes) 2. CESA-2019:0775 Important CentOS 7 java-1.8.0-openjdk Security Update (Johnny Hughes) 3. CESA-2019:0774 Important CentOS 6 java-1.8.0-openjdk Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 19 Apr 2019 18:39:15 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:0778 Moderate CentOS 7 java-11-openjdk Security Update Message-ID: <20190419183915.GA30308(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:0778 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2019:0778 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: b6a9b7941571bb174ce804b64d2ad94cc24f6af4e201196494c097de4a4ffaa8 java-11-openjdk-11.0.3.7-0.el7_6.i686.rpm b9b48cb489ef67b11e6cec5a4dfc55fd1cb89c046401543e671fea324cb99813 java-11-openjdk-11.0.3.7-0.el7_6.x86_64.rpm d1dad21be37df857e6a933c63ebee1a270991a8da22f3720055ecd7abda5900c java-11-openjdk-debug-11.0.3.7-0.el7_6.i686.rpm ef81f3232faf0f1d10b5ef447458ad9ea7cc532935cafa94c3e10e408ce2bd37 java-11-openjdk-debug-11.0.3.7-0.el7_6.x86_64.rpm 777e5539a1e0b16f8a823cb2db98c5f430b601c186a3e572aff1e0e43c48fcaa java-11-openjdk-demo-11.0.3.7-0.el7_6.i686.rpm 4a48999506ff914e54b9860c3082a2585d0969cdb4fa496c02bede5db4d52ee7 java-11-openjdk-demo-11.0.3.7-0.el7_6.x86_64.rpm a4f9b7863c331ac98b4d319fc1517af72144525831cf88ff5c8aefc39deb5648 java-11-openjdk-demo-debug-11.0.3.7-0.el7_6.i686.rpm 40030f978ab8451fb532dbcb4b407da17d5004ca88ef338911efdadb78c88b3b java-11-openjdk-demo-debug-11.0.3.7-0.el7_6.x86_64.rpm 03bcebe31f9891b540ef7274187192ac8d2b678fe2447370cba497d5890ff826 java-11-openjdk-devel-11.0.3.7-0.el7_6.i686.rpm 0e8eba5d04de047404e67f07318b74eb188c771141404576a969ce5e03ca3d86 java-11-openjdk-devel-11.0.3.7-0.el7_6.x86_64.rpm 3680df303d48ca74cae964d46e8f73b2a3b4f48f540c4d836c8ac459809e1f92 java-11-openjdk-devel-debug-11.0.3.7-0.el7_6.i686.rpm 09fded1933bb6c86075496f5896df626a63eaeee353a549e89ff7bb797f84d21 java-11-openjdk-devel-debug-11.0.3.7-0.el7_6.x86_64.rpm ff08e7ab4253c3ab7278ef6944926fb14b440b989b4d4304c759502217e931ff java-11-openjdk-headless-11.0.3.7-0.el7_6.i686.rpm 49fba40a09f2410abe59771ccd81fb65b6c16087e52f3555b10a51f52a7a0076 java-11-openjdk-headless-11.0.3.7-0.el7_6.x86_64.rpm 2ef67928c40a035d3c007aea2ef32c3dbaa8c17a78244e5ff15a0c0430126d37 java-11-openjdk-headless-debug-11.0.3.7-0.el7_6.i686.rpm c89a013731229814e930d6a9bec5c0ed21962acbca025d4730110648da402c5a java-11-openjdk-headless-debug-11.0.3.7-0.el7_6.x86_64.rpm d298c2948e78108b2a3b9de4d4ce7e0e6b3ba86a0b81f3ec0d057551c1020779 java-11-openjdk-javadoc-11.0.3.7-0.el7_6.i686.rpm 0dca6e3aa6af3b9015e9095dae148f92379a8d6b3d93d8de4044eba80c031e75 java-11-openjdk-javadoc-11.0.3.7-0.el7_6.x86_64.rpm b54b3bc176ba870cdea2ff46fe3c29dd3cc4d8e580ad87c7e3e43fa3f87bf0e3 java-11-openjdk-javadoc-debug-11.0.3.7-0.el7_6.i686.rpm 9b235a780b48395b9693669389a5f56dd531d2c59bc7ed94f26e17f597310d74 java-11-openjdk-javadoc-debug-11.0.3.7-0.el7_6.x86_64.rpm 796aa75e299bcda8abad4d95197767e6b97b94209f5a8b2fbd9dc77ba4f45ea6 java-11-openjdk-javadoc-zip-11.0.3.7-0.el7_6.i686.rpm 4da49197fd3b21c85ee232cc4be98b5bf9c8e8f0df074b9a35e09cdc4162b547 java-11-openjdk-javadoc-zip-11.0.3.7-0.el7_6.x86_64.rpm bc98c45b572e4decbea0b325fb7dadc4a63adb1d76f97c2f59b88f166d5a7302 java-11-openjdk-javadoc-zip-debug-11.0.3.7-0.el7_6.i686.rpm 86e3011db798495d044f6da0f80cdae0a343e81f9d0556cd721238a7c98be745 java-11-openjdk-javadoc-zip-debug-11.0.3.7-0.el7_6.x86_64.rpm 73879ef06cec69705ee5e7ac112faa64eef5861b74e66c6f47b9106bdba0aba1 java-11-openjdk-jmods-11.0.3.7-0.el7_6.i686.rpm 8b774cd47ed4d154fb2c7def5a08e1bc4d9b6ed7abe9e31bc2c2cc1501ac7c44 java-11-openjdk-jmods-11.0.3.7-0.el7_6.x86_64.rpm 0565f7b2853bacb2cb8e3e04bf6aa6da2ac9efc9fff36fe9a423e4727e3c9946 java-11-openjdk-jmods-debug-11.0.3.7-0.el7_6.i686.rpm 6be04d6605ab46e7822832cac298387a02d7128e0425a8cf196e924d5273d638 java-11-openjdk-jmods-debug-11.0.3.7-0.el7_6.x86_64.rpm 827a9288281a4f2c0ff2ed5a34ef512817e2b6f5e4c4abb8bc85181596e859fd java-11-openjdk-src-11.0.3.7-0.el7_6.i686.rpm 83f3b61b23f52ea8a71863f0f1c6f94707a107e387d85a560a498c79af3ee3b6 java-11-openjdk-src-11.0.3.7-0.el7_6.x86_64.rpm ed25c3c00bb2104cc3fc4b37c69dfb6f646e0f0d9d1b43f76d33f93a8a750cab java-11-openjdk-src-debug-11.0.3.7-0.el7_6.i686.rpm 465b443d20d398749d7b27848fa4b0be339a42f8f0d9f4d9998fe7fa24425afe java-11-openjdk-src-debug-11.0.3.7-0.el7_6.x86_64.rpm Source: 3e0c85c461aab5777e4b0e01a65350ed47dd35de428e30d6adb2fdf7d05fe651 java-11-openjdk-11.0.3.7-0.el7_6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Fri, 19 Apr 2019 18:51:58 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:0775 Important CentOS 7 java-1.8.0-openjdk Security Update Message-ID: <20190419185158.GA30895(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:0775 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:0775 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: e5f3f26b6ccacd414e4edd3a43b565301e03081315ce9a461d4c3b8615991047 java-1.8.0-openjdk-1.8.0.212.b04-0.el7_6.i686.rpm 476b75debe78e764b781aa994cfecf659926aa78a622b9c86542b4a0b6eede4e java-1.8.0-openjdk-1.8.0.212.b04-0.el7_6.x86_64.rpm 3ad77ed1e5de1f7a92ca210c62b53c532a6a4ea7943b65842b38a8f348374a34 java-1.8.0-openjdk-accessibility-1.8.0.212.b04-0.el7_6.i686.rpm 6417677031bea22f7c6789cf0a50cc3a52a27c3982eb3ec058fa935a969850d5 java-1.8.0-openjdk-accessibility-1.8.0.212.b04-0.el7_6.x86_64.rpm 45868b5a80e931bec334a3b4ef4b3d7b71728902b24fa5c729b2bbdd426428a0 java-1.8.0-openjdk-accessibility-debug-1.8.0.212.b04-0.el7_6.i686.rpm ca03e1115f8b44c046ee5121efa4dc39c42286737540d2597ef655a86c3d9172 java-1.8.0-openjdk-accessibility-debug-1.8.0.212.b04-0.el7_6.x86_64.rpm a8c97067f1db6f289af4acfe165df6a93f4305447ec29ed90b15a79d9f3daf5d java-1.8.0-openjdk-debug-1.8.0.212.b04-0.el7_6.i686.rpm 5d858ec0b40ecfc65d5a68ffe622a4b8528eefb428a2ad2adcee87714ad56e5a java-1.8.0-openjdk-debug-1.8.0.212.b04-0.el7_6.x86_64.rpm 126205b6851a064cba3c956fc250c507318c4ec781adbdc33d1a94fb974e1970 java-1.8.0-openjdk-demo-1.8.0.212.b04-0.el7_6.i686.rpm e1177924daa14398d678ec868cc96f5bc9986e2348c9d07501bd1843a3e3955d java-1.8.0-openjdk-demo-1.8.0.212.b04-0.el7_6.x86_64.rpm 31753810f7c2b547d3e669d9d216b70295d17fb392acf61619bbcf49b839c43b java-1.8.0-openjdk-demo-debug-1.8.0.212.b04-0.el7_6.i686.rpm c627aea9f3d2175b876044cb86cbb7b3b7239caa38534f5d443bf61dd8cd25eb java-1.8.0-openjdk-demo-debug-1.8.0.212.b04-0.el7_6.x86_64.rpm ed2876ad529c71571a95ebf89b7613ddf96522bb535113122024a130cb3902b3 java-1.8.0-openjdk-devel-1.8.0.212.b04-0.el7_6.i686.rpm def047c63f389c77ac83f8e8f318bc70ba3b3f05541668e90d960be8757fa669 java-1.8.0-openjdk-devel-1.8.0.212.b04-0.el7_6.x86_64.rpm 7cebb9e6d80de016330776384b7dd3d19fdab732dc0ac2d2be21cef318b245c5 java-1.8.0-openjdk-devel-debug-1.8.0.212.b04-0.el7_6.i686.rpm e14205a2686d4525a82f1f2697137b1a829408aac59d571907267c16ab51ffd8 java-1.8.0-openjdk-devel-debug-1.8.0.212.b04-0.el7_6.x86_64.rpm 25308351768720a6d5583e2021068d66a9642b64edcdb391cf2b25c671cd3a64 java-1.8.0-openjdk-headless-1.8.0.212.b04-0.el7_6.i686.rpm 0761db2f93558add610a1a90f5b521fa3c6bb8f85ef783b1f774de336b801024 java-1.8.0-openjdk-headless-1.8.0.212.b04-0.el7_6.x86_64.rpm 4e61bfa5c1e9879134a78d0d7d32453cbcc2c73947929f09ac29563db657bf3f java-1.8.0-openjdk-headless-debug-1.8.0.212.b04-0.el7_6.i686.rpm 9f38226977ed54dc80e7974068485f5474fb223064e1dc21618da1f83610f584 java-1.8.0-openjdk-headless-debug-1.8.0.212.b04-0.el7_6.x86_64.rpm 6d6a74f27e22928f67784c71a504db70b4f65cb3b4cc867c59e77e749048f81f java-1.8.0-openjdk-javadoc-1.8.0.212.b04-0.el7_6.noarch.rpm fecacb0703f7de4ae689c7721821f470ed4cc560b0ef87d08ac03cb3ee9bb6b1 java-1.8.0-openjdk-javadoc-debug-1.8.0.212.b04-0.el7_6.noarch.rpm e91ae235e6aba200f678c5e75e09fb37e15c7009b8ad25ec8d2475d3c604bc40 java-1.8.0-openjdk-javadoc-zip-1.8.0.212.b04-0.el7_6.noarch.rpm c1dfe7fb6bd94c0ac3f7249c9b4356f45172029652ab604d487c47aaf410dcc6 java-1.8.0-openjdk-javadoc-zip-debug-1.8.0.212.b04-0.el7_6.noarch.rpm ca21ee52f8f9ce4da3ac54486bcffe54bbbf3731affeba8558497f35a84b2aa0 java-1.8.0-openjdk-src-1.8.0.212.b04-0.el7_6.i686.rpm 51d21372261d7dacb7353091ec39bc847b2fc06915705c21ad7bd199ed79cf72 java-1.8.0-openjdk-src-1.8.0.212.b04-0.el7_6.x86_64.rpm 6c68b7145a57414d5a8e17d315a017c729596355e373d806e03e6e62fba9a2f1 java-1.8.0-openjdk-src-debug-1.8.0.212.b04-0.el7_6.i686.rpm 5aaab2b2bee92bbb63b387992c0b43eca8a35695f03907fc059d1ff24eff161b java-1.8.0-openjdk-src-debug-1.8.0.212.b04-0.el7_6.x86_64.rpm Source: cc2f5d26bd4c7302c1b29eec4b272ecf5b498575fbee43a3a36fcd5644c6361e java-1.8.0-openjdk-1.8.0.212.b04-0.el7_6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Fri, 19 Apr 2019 18:53:44 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:0774 Important CentOS 6 java-1.8.0-openjdk Security Update Message-ID: <20190419185344.GA31253(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:0774 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:0774 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0f8112dceb74d21296ee6d3ed003ae046b26d14041ebc81a39aa2a19180bc814 java-1.8.0-openjdk-1.8.0.212.b04-0.el6_10.i686.rpm 824c5a782d4b8bb5627efa495003f0c439d81a43d74b59cd009d8740cda6b0a1 java-1.8.0-openjdk-debug-1.8.0.212.b04-0.el6_10.i686.rpm d699358b7864c546e917f3010f1e9287db8d3fe5d766aade04d4084fa708b1d6 java-1.8.0-openjdk-demo-1.8.0.212.b04-0.el6_10.i686.rpm 9eb7b2f780cd6332eab31acb2fb540c2bd1cc3283f68b18875925e636843599b java-1.8.0-openjdk-demo-debug-1.8.0.212.b04-0.el6_10.i686.rpm 7e10a79fe240395478c0373e63af88cb0185f22b3ba2c1ad184c55bd8d23549c java-1.8.0-openjdk-devel-1.8.0.212.b04-0.el6_10.i686.rpm 039a5bbcb4640de935b3b38d6870add47a330350baec4714f6496cc27b38424f java-1.8.0-openjdk-devel-debug-1.8.0.212.b04-0.el6_10.i686.rpm 052ea026cd0423e6c16c1b02f19271caf562e40b34b6de189ce16fc8460a5b1b java-1.8.0-openjdk-headless-1.8.0.212.b04-0.el6_10.i686.rpm 2a556f7652b06a0c0b3dc447e8029129eb0f0900383218dd33e9adbe2154933a java-1.8.0-openjdk-headless-debug-1.8.0.212.b04-0.el6_10.i686.rpm 51061790215323c381fa60cb33008e90018a915e3f81788829ecca8b8f7253ed java-1.8.0-openjdk-javadoc-1.8.0.212.b04-0.el6_10.noarch.rpm d04e6c73123b6b07c2fbd35a0040007534fed609a5d15ccc040d149bdea7131c java-1.8.0-openjdk-javadoc-debug-1.8.0.212.b04-0.el6_10.noarch.rpm 7ae746fca08ca500e641ab11a3c7188e0e75aa021127d739a4de6b98a41ab879 java-1.8.0-openjdk-src-1.8.0.212.b04-0.el6_10.i686.rpm 048b352f99e79c0e2eb37014a7ddb7dc6feead646d8e851eae3788809b327dcf java-1.8.0-openjdk-src-debug-1.8.0.212.b04-0.el6_10.i686.rpm x86_64: f979ba26dc9cfd9f231f89e071f1256d97b7e40c70c75db726ca7d164cb51532 java-1.8.0-openjdk-1.8.0.212.b04-0.el6_10.x86_64.rpm e99b6978125cfd46be05a4d576f338a293d41e4bc750e795c132c4620d0d6dcf java-1.8.0-openjdk-debug-1.8.0.212.b04-0.el6_10.x86_64.rpm b81e81c7590fc53f3eeb8ce4ff93f327aebf1b706f3cc745b3fba7ca18ee85d6 java-1.8.0-openjdk-demo-1.8.0.212.b04-0.el6_10.x86_64.rpm b77224302704fe3977283d0170afbb11f2d80cb4a2f7573d070afcf5192d7fd9 java-1.8.0-openjdk-demo-debug-1.8.0.212.b04-0.el6_10.x86_64.rpm 2c445892f52366f97c7c160acf95f6ae38fa09693eb776c7def81d2c26b109fb java-1.8.0-openjdk-devel-1.8.0.212.b04-0.el6_10.x86_64.rpm a375168a809a242583116bf988f7701c33aea1ec5c6d38db753af5a19b53c12c java-1.8.0-openjdk-devel-debug-1.8.0.212.b04-0.el6_10.x86_64.rpm bb64c983932d1d89af13d0a364f007c7e67e7550bfca24530e6f7dcd2f9827b0 java-1.8.0-openjdk-headless-1.8.0.212.b04-0.el6_10.x86_64.rpm e20aa4cc26d74253fd0ac04336fa9677c0bc0a9f3647ec9cd9d94dccdd8fbe2e java-1.8.0-openjdk-headless-debug-1.8.0.212.b04-0.el6_10.x86_64.rpm 51061790215323c381fa60cb33008e90018a915e3f81788829ecca8b8f7253ed java-1.8.0-openjdk-javadoc-1.8.0.212.b04-0.el6_10.noarch.rpm d04e6c73123b6b07c2fbd35a0040007534fed609a5d15ccc040d149bdea7131c java-1.8.0-openjdk-javadoc-debug-1.8.0.212.b04-0.el6_10.noarch.rpm 18d96dcb44ef40f33d99e5a44343c24cab6af91469387ee5daf3e8acd50fc73c java-1.8.0-openjdk-src-1.8.0.212.b04-0.el6_10.x86_64.rpm 99b11a44f787d78b02bc7f634689552dc32fbd1d720f24072f2e6c7565065889 java-1.8.0-openjdk-src-debug-1.8.0.212.b04-0.el6_10.x86_64.rpm Source: 89a7301a8d9474f436e831377778827c599b4bba05e5267f0188fc9d082ef10b java-1.8.0-openjdk-1.8.0.212.b04-0.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 170, Issue 5 ***********************************************

1 0

Re: [CentOS] faI2ban detecting and banning but nothing happens
by Miguel Gonzalez 19 Apr '19

19 Apr '19

I find csf/lfd much easier to configure and can be used in combination with fail2ban. Gary Stainburn <gary.stainburn(a)ringways.co.uk> wrote: >I've followed one of the pages on line specifically for installing fail2ban on >Centos 7 and all looks fine. > >I've added a fail regex to /etc/fail2ban/filter.d/exim.conf as suggested on >another page: > > \[<HOST>\]: 535 Incorrect authentication data > >which appears to be successfully matchnig lines in /var/log/exim/mail.log such >as > >2019-04-19 13:06:10 dovecot_plain authenticator failed for ([185.222.209.71]) >[185.222.209.71]: 535 Incorrect authentication data > >/var/log/fail2ban.log, and the generarted emails all say that the regex is >working and the IP addresses are getting banned. > >2019-04-19 13:06:32,461 fail2ban.filter [21954]: INFO [dovecot] >Found 45.227.253.99 >2019-04-19 13:06:32,607 fail2ban.actions [21954]: NOTICE [dovecot] Ban >45.227.253.99 >2019-04-19 13:06:32,954 fail2ban.filter [21954]: INFO [dovecot] >Found 45.227.253.99 >2019-04-19 13:06:36,664 fail2ban.filter [21954]: INFO [dovecot] >Found 185.222.209.71 >2019-04-19 13:07:16,973 fail2ban.actions [21954]: NOTICE [dovecot] >Unban 185.211.245.198 >2019-04-19 13:07:42,108 fail2ban.actions [21954]: NOTICE [dovecot] >Unban 185.234.217.221 >2019-04-19 13:08:06,475 fail2ban.filter [21954]: INFO [dovecot] >Found 141.98.80.32 >2019-04-19 13:08:11,299 fail2ban.filter [21954]: INFO [dovecot] >Found 185.234.217.162 >2019-04-19 13:08:12,249 fail2ban.actions [21954]: NOTICE [dovecot] Ban >185.234.217.162 >2019-04-19 13:08:16,803 fail2ban.filter [21954]: INFO [dovecot] >Found 141.98.80.32 >2019-04-19 13:08:22,092 fail2ban.filter [21954]: INFO [dovecot] >Found 185.234.217.221 >2019-04-19 13:09:18,178 fail2ban.filter [21954]: INFO [dovecot] >Found 185.211.245.198 >2019-04-19 13:09:30,522 fail2ban.filter [21954]: INFO [dovecot] >Found 185.211.245.198 >2019-04-19 13:09:30,752 fail2ban.actions [21954]: NOTICE [dovecot] Ban >185.211.245.198 >2019-04-19 13:10:48,248 fail2ban.filter [21954]: INFO [dovecot] >Found 185.211.245.198 > > > >However, once an IP address is banned, it continues to appear >in /var/log/exim/main.log which would imply that the ban action is not >working. > >(Also, I don't understand why it's matching against dovecont ewhen the regex >is in exim.conf) > >I've found lots of pages relating to regex errors which this obviously isn't >but I can't seem to find pages about why the ban doesn't work. Does anyone >have any ideas? >_______________________________________________ >CentOS mailing list >CentOS(a)centos.org >https://lists.centos.org/mailman/listinfo/centos

1 0

epel-repository | repomd.xml.asc: [Errno 14] HTTP Error 404
by Stefanie Leisestreichler 18 Apr '19

18 Apr '19

Hi. I try to install openvpn at my centos 7 server (CentOS Linux release 7.6.1810 (Core)). According to many tutorials at the internet, I was using yum install epel-release -y to enable the repo. When (after installing epel-release) I try to install openvpn using yum install openvpn -y I get this error: Geladene Plugins: fastestmirror Loading mirror speeds from cached hostfile epel/x86_64/metalink | 30 kB 00:00:00 * base: mirror.fra10.de.leaseweb.net * epel: ftp-stud.hs-esslingen.de * extras: ftp.rz.uni-frankfurt.de * updates: centos.schlundtech.de base/7/x86_64/signature | 811 B 00:00:00 base/7/x86_64/signature | 3.6 kB 00:00:00 !!! https://mirror.imt-systems.com/epel/7/x86_64/repodata/repomd.xml.asc: [Errno 14] HTTPS Error 404 - Not Found Anderer Spiegelserver wird versucht. Ater that I get a lot of these errors, all with the same signature: https://ftp-stud.hs-esslingen.de/pub/epel/7/x86_64/repodata/repomd.xml.asc: [Errno 14] HTTPS Error 404 - Not Found Anderer Spiegelserver wird versucht. http://ftp.uni-stuttgart.de/epel/7/x86_64/repodata/repomd.xml.asc: [Errno 14] HTTP Error 404 - Not Found Anderer Spiegelserver wird versucht. https://mirror.infonline.de/epel/7/x86_64/repodata/repomd.xml.asc: [Errno 14] HTTPS Error 404 - Not Found .... What am I doing wrong? Thanks, Steffi

3 2

CentOS-announce Digest, Vol 170, Issue 4
by centos-announce-request＠centos.org 18 Apr '19

18 Apr '19

1 0

yum groupinstall "GNOME Desktop" fails
by Warren Young 17 Apr '19

17 Apr '19

I’ve got a CentOS 7 VM here that was installed with one of the CLI-only presets. To answer a question in another thread here, I wanted to install a GNOME desktop environment in it, so I went searching and found the standard instructions for doing that. The problem is that rebooting the VM gives me a black screen after it finishes the text booting parts. There’s an X cursor, and wiggling the mouse moves it, but I get no gray login screen. Pressing Ctrl-Alt-F2 and logging into a text console works. Saying “startx” brings X back up again — indicating that it does find the proper X drivers and such — but now I get just a few default icons on the desktop, but no top and bottom toolbars: https://imgur.com/IMI9Gh9 So, the GNOME shell is also broken. I’ve repeated the yum groupinstalls for “GNOME Desktop”, “Server with GUI” and “Graphical Administration Tools.” yum claims everything is fine. Short of installing another VM with a GUI enabled from the start, I’m stuck. For what it’s worth, the VM system is Parallels, and I do have the Parallels Tools installed. The same symptoms occur when booting into single-user mode and trying to startx from there.

3 3

FYI: C 7, broken cron, sort of SOLVED
by mark 17 Apr '19

17 Apr '19

I was fighting this a few weeks ago, and asking here. I *finally* solved it yesterday... and the answer isn't pleasant. Running the command authconfig --enablesssd --enablesssdauth --enablesmartcard --smartcardmodule=sssd --smartcardaction=0 --updateall breaks crond, as per bugzilla # Bug 1650314. The way that it breaks it is to insert into /etc/pam.d/password-auth-ac two lines reading auth required pam_deny.so one as the third line in the auth stanza, so: auth required pam_env.so auth required pam_faildelay.so delay=2000000 auth required pam_deny.so auth [default=1 ignore=ignore success=ok] pam_succeed_if.so uid >= 1000 quiet auth [default=1 ignore=ignore success=ok] pam_localuser.so auth sufficient pam_unix.so nullok try_first_pass auth requisite pam_succeed_if.so uid >= 1000 quiet_success <...> and the other where it belongs, as the last auth line. This is clearly a bug in the code, as pam_deny.so should ONLY be the *last* line in the auth stanza. We've replicated this on an RHEL workstation, and then put a ticket in. The... odd reply (so far) was that they weren't going to fix it in the 7.7 errata, and to use authselect in 8.0 (which is only a beta release). We're going to escalate this. In the meantime, if anyone has run into this, delete that auth required pam_deny.so that's in the middle of the auth stanza in /etc/pam.d/password-auth-ac, it should *only* be at the end of the auth stanza, and everything will work correctly. mark

1 0

A strange situation with MegaCli64 and smartctl
by mark 17 Apr '19

17 Apr '19

We have a system - it's C 7 - that a while back lost three drives of a large array. The other admin here replaced the failed drives, but never went through the MegaRAID replace series of commands. I've just brought it back up and put a new filesystem on it, but here's what's odd: if I do smartctl -a -d megaraid,x /dev/sda, where x=drive number, for all the other drives, I get smart info. For those three, I get Smartctl open device: /dev/sda [megaraid_disk_11] failed: INQUIRY failed However, if I run any commend with MegaCli64, it sees the drives fine. It's as though smartctl has cached some info, somewhere.... Any thoughts? NOTE: after a good bit of searching online, I found someone's cmts that on *some* cards, the drive number starts at 8. Oh, and when I tried that, I got "enclosure", and the actual drives show at 9.... mark

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss