Discuss

discuss@lists.centos.org

8 participants
34745 discussions

CentOS7: Setting up ldap over TLS in kickstart file
by Patrick Begou 15 Jun '18

15 Jun '18

Hi, I'm facing a problem with setting up LDAP+TLS client authentication in a kickstart script on CentOS7 for several days. Setting up manualy the config with system-config-authentication works but I need to automate this in kickstart for deploying cluster nodes. This show that the server side is running fine. At this time the message is #systemctl status sssd |.... sssd[be[default]][2732]: Could not start TLS encryption. error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed (self signed certificate)| In my kickstart file I use: auth --useshadow --enableldaptls --enablecache --passalgo=sha512 --enableldap --enableldapauth --ldapserver="ldaps://my.ldap.server.fr" --ldapbasedn=dc=my,dc=base,dc=dn Then in a post install script I download the server and ca certificates and stops nslcd that I do not use: echo "TLS_REQCERT allow">>/etc/openldap/ldap.conf cd /etc/openldap/cacerts/ && wget http://xxx.xxx.xxx.xxx/Softwares7/LDAPCERTS/ca-bundle.crt && ln -s ca-bundle.crt $(openssl x509 -hash -in ca-bundle.crt -noout).0 cd /etc/openldap/certs/ && wget http://xxx.xxx.xxx.xxx/Softwares7/LDAPCERTS/server.crt cd / systemctl disable nslcd I'm unable to see what system-config-authentication is doing more in it's setup. Thanks for your help Patrick |||| || -- =================================================================== | Equipe M.O.S.T. | | | Patrick BEGOU | mailto:Patrick.Begou@grenoble-inp.fr | | LEGI | | | BP 53 X | Tel 04 76 82 51 35 | | 38041 GRENOBLE CEDEX | Fax 04 76 82 52 71 | ===================================================================

3 3

CentOS-announce Digest, Vol 160, Issue 3
by centos-announce-request＠centos.org 15 Jun '18

15 Jun '18

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. CEBA-2018:1838 CentOS 7 linux-firmware BugFix Update (Johnny Hughes) 2. CESA-2018:1836 Important CentOS 7 plexus-archiver Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 14 Jun 2018 15:09:26 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2018:1838 CentOS 7 linux-firmware BugFix Update Message-ID: <20180614150926.GA32842(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2018:1838 Upstream details at : https://access.redhat.com/errata/RHBA-2018:1838 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 940bc02535d7fd581dba6d53f939ed13dbf9a7cb78f23a22db0b94d6dbdbc980 iwl1000-firmware-39.31.5.1-62.2.el7_5.noarch.rpm 722a5873cbe15ee2c12aaac92f04ec012daca4b9d524037d358ebeeeb9e3f65b iwl100-firmware-39.31.5.1-62.2.el7_5.noarch.rpm 21a7b490b6736e116524cb3c6b676a8428323d6c90dee62694bb9b73cd86e1d9 iwl105-firmware-18.168.6.1-62.2.el7_5.noarch.rpm 0838322f12f12d545404810b33a006f7d9e981e1d9e758de14b7a8aadb143d4d iwl135-firmware-18.168.6.1-62.2.el7_5.noarch.rpm d0190f3079c3b729cefdb4fbdbfaea858778cce7d7214d636595657bdd4c43b4 iwl2000-firmware-18.168.6.1-62.2.el7_5.noarch.rpm c7a7cc8c5195e291ffc2ff8b647e642135f050611379e86c1d9c980439b80c67 iwl2030-firmware-18.168.6.1-62.2.el7_5.noarch.rpm a7f1d6426f6bd1440610f0b929971737c9fc24039bf88413cb43e21ad4ae1657 iwl3160-firmware-22.0.7.0-62.2.el7_5.noarch.rpm 12d43466da1c3c8055403ddcac8b4efba651ee35393fba897162cf86abcf0e0e iwl3945-firmware-15.32.2.9-62.2.el7_5.noarch.rpm 6fd48dfeef9416d6fa7636a89be2875c892335d89af6970b62aede43a8dc5e5c iwl4965-firmware-228.61.2.24-62.2.el7_5.noarch.rpm 5d5ff923fe6beb5904d43a5660b2f65d14a88fb5ae2f865ea10d2e17115a7360 iwl5000-firmware-8.83.5.1_1-62.2.el7_5.noarch.rpm 5ae3fa0eab138bb889e46725795724617047134f1c5c04113e6235c16761ee4c iwl5150-firmware-8.24.2.2-62.2.el7_5.noarch.rpm 8136f0d62b4419c840f101ca64c93e334ad6aa92e3e3d6fff37620069308f5b1 iwl6000-firmware-9.221.4.1-62.2.el7_5.noarch.rpm a0f96e3088e72ab8de9846ee75bc6460116b73b77db1bcdacde1a00dd1f7a076 iwl6000g2a-firmware-17.168.5.3-62.2.el7_5.noarch.rpm 5cbe19cd8a9be34c3ece1ea1ded527db0ccd5f8919c8a6b9ce29358b7dedc4ac iwl6000g2b-firmware-17.168.5.2-62.2.el7_5.noarch.rpm 8d7274ccd14611cb5214163c944b2834330984aa5906b68a49e28a8b82b8f7c1 iwl6050-firmware-41.28.5.1-62.2.el7_5.noarch.rpm 73ad0e98045b5da8a2600789197ec98c58ee605d83c3c24547bd8e498bdc9072 iwl7260-firmware-22.0.7.0-62.2.el7_5.noarch.rpm 03a7febf9a8380d07216ef53dd9d7ef78a684a61acc8006916d515d9cdb23583 iwl7265-firmware-22.0.7.0-62.2.el7_5.noarch.rpm b3eae0bc8cf3c427455ce5108efe07c3a76b7cdf8a3ad69342720b716b9ce864 linux-firmware-20180220-62.2.git6d51311.el7_5.noarch.rpm Source: b23b4d21947a38e5fb5353c3b49ee8d271cd779ad6ecb6509472c5bf345658e8 linux-firmware-20180220-62.2.git6d51311.el7_5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 14 Jun 2018 15:10:15 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:1836 Important CentOS 7 plexus-archiver Security Update Message-ID: <20180614151015.GA32924(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:1836 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:1836 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 9c26560f7b175d6e1455a7b9edf9c56be74c06a98f91074a36c3944a51ea110e plexus-archiver-2.4.2-5.el7_5.noarch.rpm 098c29d9f8e0b7703e1ded196eaa5ec3cbc68521fb4a46c9563cba2a9ceb7649 plexus-archiver-javadoc-2.4.2-5.el7_5.noarch.rpm Source: 3efde77b61ff8ce194ff060488b029ffbf3d465c8b9192b227ba8e3923d2d9ff plexus-archiver-2.4.2-5.el7_5.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 160, Issue 3 ***********************************************

1 0

rpmbuild --define | some rpm sorcerer around?
by lejeczek 15 Jun '18

15 Jun '18

hi how do you pass vars to rpmbuild for definition? eg rpmbuild --define \'"${_definition2}"\' I've been fiddling with ways to escape, but none is fricking working.. I mean, rpmbuild rushes to work(no errors nor failure) so if you try just the command line do not believe it, because later as it executes %if you will see process does not see these definitions. many thanks, L

4 7

Custom ISO With Post Installation Scripts
by Earl Ramirez 15 Jun '18

15 Jun '18

Dear All I have been working on a custom ISO with kickstart and a couple of post installation scripts and would like to have the script run before the login prompt. The custom ISO works; however, the scripts fails because some of the services, e.g. mariadb does not start before the server installation has been completed and rebooted; therefore, I have been putting the scripts in /etc/profile.d/ and after logging in the scripts will execute and upon completion of the script will be deleted from /etc/profile.d/. DuckDuckGo suggested that I copy the script to /etc/rc.d/rc.local and make it executable; however, I have tried that a few times and the script simply does not execute. Below is an excerpt from the ks.cfg. export SRCDIR="/run/install/repo" export DSTDIR="/mnt/sysimage" # copy scripts to the destintion of the server cp -v $SRCDIR/postinstall/script1.sh $DSTDIR/etc/rc.d/rc.local/script1.sh # Make scripts executable chmod +x $DSTDIR/etc/rc.d/rc.local.sh Since this is a ISO for a community project, don't think that tools such as Ansible, Chef, Puppet, etc. will work here. Also, it is a one time execution; therefore, I did not consider using systemd because the goal would be to have visibility while the script is running just as I see after I login; however, just need the script to be executed after the OS was installed and restarted and before the login prompt. All suggestions are welcome. Thanks in advance. -- Earl Ramirez <earlaramirez(a)gmail.com>

5 6

Difficulty configuring RDMA in CentOS
by Pat Haley 13 Jun '18

13 Jun '18

Hi We are trying to configure RDMA for an infiniband connection between our data server (running CentOS 6.8) and our compute nodes (running CentOS 6.6). We have been trying to follow the instructions in https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/ht… however we are getting conflicting information on whether the RDMA is correctly configured. Some of what we have done and some of the data are below. Can you suggest what other tests and what other data we should get to debug this problem? /etc/rdma/mlx4.conf to set the port types properly for RoCE/IBoE usage. Edit /etc/modprobe.d/mlx4.conf to instruct the driver on which packet priority is configured for the “no-drop” service on the Ethernet switches the cards are plugged into. vim /etc/rdma/mlx4.conf You can find the right pci device to use for any given card by loading # the mlx4_core module, then going to /sys/bus/pci/drivers/mlx4_core and # seeing what possible PCI devices are listed there.The possible values # for ports are: ib, eth, and auto.However, not all cards support all # types, so if you get messages from the kernel that your selected port # type isn't supported, there's nothing this script can do about it. [root@mseas-data2 mlx4_core]# ls /sys/bus/pci/drivers/mlx4_core 0000:81:00.0bindmodulenew_idremove_idueventunbind mstconfig -d 81:00.0 query Device #1: ---------- Device type:ConnectX3Pro PCI device:81:00.0 Configurations:Current SRIOV_EN1 NUM_OF_VFS8 LINK_TYPE_P13 LINK_TYPE_P23 LOG_BAR_SIZE3 BOOT_PKEY_P10 BOOT_PKEY_P20 BOOT_OPTION_ROM_EN_P11 BOOT_VLAN_EN_P10 BOOT_RETRY_CNT_P10 LEGACY_BOOT_PROTOCOL_P11 BOOT_VLAN_P11 BOOT_OPTION_ROM_EN_P21 BOOT_VLAN_EN_P20 BOOT_RETRY_CNT_P20 LEGACY_BOOT_PROTOCOL_P21 BOOT_VLAN_P21 Needed packages: Most if not all packages appear to be installed on server [root@mseas-data2 ~]# service rdma status Low level hardware support loaded: mlx4_ib Upper layer protocol modules: ib_ipoib User space access modules: rdma_ucm ib_ucm ib_uverbs ib_umad Connection management modules: rdma_cm ib_cm iw_cm Configured IPoIB interfaces: none Currently active IPoIB interfaces: ib0

1 0

C 7: smpboot: CPU 16 is now offline
by m.roth＠5-cent.us 13 Jun '18

13 Jun '18

Current kernel, and I just booted, and dmesg shows, of the 32 cores, 0, 2, 4 and 6 ok, and *all* other show "is now offline. What's happening here? mark

1 3

CentOS-announce Digest, Vol 160, Issue 2
by centos-announce-request＠centos.org 13 Jun '18

13 Jun '18

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. Announcing release of HAProxy 1.8 on CentOS 7 x86_64 (Jan Stan?k) 2. Announcing release of MongoDB 3.6 on CentOS 7 x86_64 (Jan Stan?k) 3. Announcing release of Perl 5.26 on CentOS 7 x86_64 (Jan Stan?k) 4. Announcing release of PostgreSQL 10.0 on CentOS 7 x86_64 (Jan Stan?k) 5. Announcing release of Ruby 2.5 on CentOS 7 x86_64 (Jan Stan?k) 6. Announcing release of Varnish Cache 5 on CentOS 7 x86_64 (Jan Stan?k) ---------------------------------------------------------------------- Message: 1 Date: Tue, 12 Jun 2018 15:20:13 +0200 From: Jan Stan?k <jstanek(a)redhat.com> To: centos-announce(a)centos.org Subject: [CentOS-announce] Announcing release of HAProxy 1.8 on CentOS 7 x86_64 Message-ID: <c2cb0e51-90f7-3c18-5dd1-884a545f2bdb(a)redhat.com> Content-Type: text/plain; charset="utf-8" I am pleased to announce the immediate availability of HAProxy in version 1.8 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo) QuickStart ---------- You can get started in three easy steps: # 1. Install a package with repository for your system: # On CentOS, install package centos-release-scl available in CentOS repository: $ sudo yum install centos-release-scl # On RHEL, enable RHSCL repository for you system: $ sudo yum-config-manager --enable rhel-server-rhscl-7-rpms # 2. Install the collection: $ sudo yum install rh-haproxy18 # 3. Start using software collections: $ scl enable rh-haproxy18 bash At this point you should be able to use varnish just as a normal application. Some usage examples follow: $ systemctl start rh-haproxy18-haproxy This collections is CentOS-based rebuild built by SCLo SIG community, and the packages have been available in Red Hat Software Collections 3.1 for RHEL: https://access.redhat.com/documentation/en-us/red_hat_software_collections/… So, for RHEL-based builds, follow the steps in the documentation above. About Software Collections -------------------------- Software Collections give you the power to build, install, and use multiple versions of software on the same system, without affecting system-wide installed packages. Each collection is delivered as a group of RPMs, with the grouping being done using the name of the collection as a prefix of all packages that are part of the software collection. The SCLo SIG in CentOS ---------------------- The Software Collections SIG group is an open community group co-ordinating the development of the SCL technology, and helping curate a reference set of collections. In addition to the collection NodeJS being released here, we also build and deliver databases, web servers, and language stacks including multiple versions of PostgreSQL, MariaDB, Apache HTTP Server, Python, Ruby, Ruby on Rails and others. You can learn more about Software Collections concepts at: http://softwarecollections.org You can find information on the SIG at https://wiki.centos.org/SpecialInterestGroup/SCLo ; this includes how to get involved and help with the effort. Enjoy! -- Jan Stan?k Associate Software Engineer, Brno Red Hat Czech jstanek(a)redhat.com IM: jstanek

1 0

centos+unsubscribe@centos.org
by Ahmed Hassan 13 Jun '18

13 Jun '18

1 0

Generic linux question: sysctl and swiotlb
by m.roth＠5-cent.us 12 Jun '18

12 Jun '18

Anyone know if I can increase the size of swiotlb using sysctl, rather than waiting to reboot? mark

1 0

Articles on OpenSSH and Personal Git
by Alice Wonder 11 Jun '18

11 Jun '18

Hi, Wrote a couple articles on OpenSSH and on running your Git server in a CentOS 7 environment https://notrackers.com/the-command-line/openssh-primer/ and https://notrackers.com/the-command-line/setting-up-your-own-git-server/ And the domain name is honest, there no trackers on that blog. None. (that blog is actually for a WordPress project not ready for general use but it seemed like a good place for the articles too) -=- I am sure they aren't perfect, but they may be of assistance to some. Any blatant mistakes, I am not above correction. Git article needs SELinux instructions added for web content served outside of /var/www/html and the public web git viewer I'm planning to fork to fix some issues I have it (I'll contribute patches back if they want them) I still need to find a CI solution (alternate to Travis-CI) that works just from standard Git - e.g. a git hook when pushing commits or tagging a release that pings the CI solution causing it to do a standard git pull to run the build and unit tests.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss