Discuss March 2019

discuss@lists.centos.org

85 participants
68 discussions

Re: [CentOS] upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap
by Gordon Messmer 27 Jan '20

27 Jan '20

On 1/2/19 12:09 PM, Miroslav Geisselreiter wrote: > some parameters from smb.conf: > [global] > workgroup = NT4DOMAIN > netbios name = nt4member > security = domain > passdb backend = ldapsam:"ldap://ldap1server.intranet.xx > ldap://ldap2server.intranet.xx" I'm not sure it makes sense to use "security = domain" with an ldap passdb backend. If you're using a real NT4 domain, then you shouldn't need a passdb backend at all. If you're not in an NT4 domain, then you should set "security = USER". The man page for smb.conf notes "This mode will only work correctly if net(8) has been used to add this machine into a Windows NT Domain." Did you add this host to a Windows NT domain, using "net join ..."?

3 7

CentOS 7.6 1810 vs. VirtualBox : bug with keyboard layout selection
by Nicolas Kovacs 20 Jan '20

20 Jan '20

Hi, I'm currently working on my next Linux book, which will be an elementary course about CentOS administration. I'm using VirtualBox for all the installer screenshots. Since CentOS has recently been upgraded to version 7.6, I thought I might as well base all book references on this version. So I downloaded the 7.6 1810 minimal ISO and started a fresh installation in VirtualBox. I'm using a Swiss French keyboard layout (ch-fr or fr_CH-latin1), so one of the first things I do in the installer is replace the default French AZERTY keyboard (since I use the french language) by a swiss french QWERTZ layout. Now when I reach this dialog in the installer and try do define my new layout, the slider in the selection window doesn't appear, and clicking on any of the first layouts doesn't do anything, so I'm basically stuck there. I'm running OpenSUSE Leap 15.0 KDE on my workstation, so I tried the same thing with the previous CentOS 7.5 1804 minimal ISO, and the keyboard selection dialog works perfectly. So my intuition would tell me that there's a nasty bug in the CentOS 7.6 installer. Maybe it went unnoticed, since most folks stick to the default keyboard layout selected in their language. Any suggestions ? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

7 11

CentOS 7 as a Fibre Channel SAN Target
by Steffan A. Cline 02 Jan '20

02 Jan '20

For quite some time I’ve been using FreeNAS to provide services as a NAS over ethernet and SAN over Fibre Channel to CentOS 7 servers each using their own export, not sharing the same one. It’s time for me to replace my hardware and I have a new R720XD that I’d like to use in the same capacity but configure CentOS 7 as a Fibre Channel target rather than use FreeNAS any further. I’m doing virtualization and this will allow me to have failover from one node to the other since they’ll all be sharing the same export rather than me simply backing up to the FreeNAS server the way I am now. Does anyone know of any really good current articles that explain how to set up CentOS 7 as the target in such a configuration and also setting up CLVMd so they can all share an export over Fibre Channel from CentOS 7? Steffan A. Cline steffan(a)hldns.com 602-793-0014

2 1

Centos 7 on Dell Latitude E6500
by Rainer Fügenstein 09 Oct '19

09 Oct '19

Hi, I tried to install Centos7 x86_64 minimal 1503-01 from an USB flash drive on my old Dell Latitude E6500 laptop. boots up in text mode, switches text resolution, writes: Started Show Plymouth Boot Screen Reached Target Paths Reached Target Basic System. then hangs for some time, eventually starting dracut emergency shell. log says: multipathd: sdb: spurious uevent, path already in pathvec multipathd: sda: spurious uevent, path already in pathvec interesting: sdb is the internal 240GB kingston SSD drive (existing ntfs bitlocker partition recognized as sdb1) sda is the write protected USB stick, recognised as CDROM drive. 4GB rom intel 45 express chipset mobile intel GMA 4500MHD graphics intel 5100AGN wifi what to try next? any additional infos I can give you? thnx in advance. -- Best regards, Rainer mailto:rfu@oudeis.org

6 7

/boot partition too small
by KM 02 Oct '19

02 Oct '19

First off - let me say I am not an administrator. I need to know if there is an easy way to increase my /boot partition. When I installed CentOS 6 after running 5, it was my oversight not to increase the /boot size. it's too small and I can't do yum updates. if it's not easy to actually increase it, is it safe to take a chunk in my root filesystem (like /new.boot or something) and just mount it as /boot from now on so it uses the space or is that not a good idea? I am sure I could easily copy the rpms/kernel stuff over to it and then unmounts the real /boot and mount this new area as /boot. Can you administrators let me know what you think of all this? Thanks in advance. KM

27 44

NFSv4: Using fsid=0 but *not* exporting the root filesystem
by Frank Thommen 12 Jun '19

12 Jun '19

Hi, I would like to use the NFSv4 ability to create a "root" filesystem with fsid=0, so that I don't have to refer to the whole path of the exported filesystem when I mount it. However I do *not* want this root filesystem to be mountable by any host. Is that possible and how? E.g Filesystem: /exports/data1 /exports/data2 /exports/data3 /etc/exports: /exports *(ro,no_subtree_check,fsid=0) /exports/data1 host1(rw) /exports/data2 host1(rw) /exports/data3 host2(rw) host1 and host2 can mount fileserver:/ and access any of the dataN directories at least read-only. That is unwanted. I'd like /exports/data1 and /exports/data2 to be exclusively accessible by host1 and /exports/data3 by host2. But I'd still like to be able to mount e.f. as fileserver:/data1 instead of fileserver:/exports/data1. I've search around a lot and I have found the question several times, but no solution yet. Cheers frank

2 2

weird RPM dependency error; '/bin/sh' needed, but is provided
by Brian Reichert 14 May '19

14 May '19

First off, I have to admit that I'm uncertain if this is the appropriate forum; I'd be happy for suggestions about where else to look. I'm doing this work on a stock install of CentOS-7-x86_64-Minimal-1810.iso, with no updates. I'm trying to create an RPM database from a custom set of RPMs. One RPM ('openldap-ltb' from the LDAP Tool Box project (ltb-project.org) has a dependency on '/bin/sh'. The bash RPM is demonstratedly present, yet the the 'rpm' utility thinks this dependency is not met. I'm open to any advice as to how to progress. It pretty easy to demonstrate what's going wrong, rather than trying to describe it. Straightforward to reproduce: Here, I collect the misc bits from the net: $ wget --quiet http://mirrors.mit.edu/centos/7/isos/x86_64/CentOS-7-x86_64-Minimal-1810.iso $ wget --quiet http://mirrors.mit.edu/centos/7/os/x86_64/Packages/libtool-ltdl-2.4.2-22.el… $ wget --quiet https://ltb-project.org/archives/berkeleydb-ltb-4.6.21.NC-4.el7.patch4.x86_… $ wget --quiet https://ltb-project.org/archives/openldap-ltb-2.4.47-1.el7.x86_64.rpm Now, I try to make an RPM database of these packages. The last step fails with an unmet dependency: $ sudo mount ~/CentOS-7-x86_64-Minimal-1810.iso -r -t iso9660 -o loop /mnt $ mkdir -p ~/local_rpm_db $ rpm --initdb --dbpath ~/local_rpm_db $ rpm --justdb --ignoresize --dbpath ~/local_rpm_db -Uvh /mnt/Packages/*.rpm *.rpm warning: /mnt/cdrom/Packages/acl-2.2.51-14.el7.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY warning: berkeleydb-ltb-4.6.21.NC-4.el7.patch4.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 6d45bfc5: NOKEY error: Failed dependencies: /bin/sh is needed by openldap-ltb-2.4.47-1.el7.x86_64 Which is weird, as the 'bash' RPM is clearly part of the set, and 'provides' the needed feature: $ rpm -q -provides -p /mnt/Packages/bash-4.2.46-31.el7.x86_64.rpm | egrep 'sh$' /bin/bash /bin/sh Further, it's not among the list of files in the payload of the RPM: $ rpm -q -l -p /mnt/Packages/bash-4.2.46-31.el7.x86_64.rpm | egrep 'sh$' /usr/bin/bash /usr/bin/sh These tactics did work with the related bits for CentOS 6. Here are some details of my environment; I'm happy to provide more, if anyone has any questions: $ cat /etc/redhat-release CentOS Linux release 7.6.1810 (Core) $ rpm -qf /usr/bin/rpm rpm-4.11.3-35.el7.x86_64 -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large

2 3

Re: [CentOS] How to specify kernel version when restart kdump
by Benjamin Hauger 15 Apr '19

15 Apr '19

kdump operates by booting a fresh kernel to capture the context of a crashed kernel, and so the only way for kdump to dump a kernel is to crash it and cause kdump to invoke its post-crash kernel. You can manually force a running kernel to panic (and invoke a correctly-configured kdump) with the following command sequence: > echo 1 > /proc/sys/kernel/sysrq > echo c > /proc/sysrq-trigger Cheers, Ben On 3/25/19 7:19 PM, wuzhouhui wrote: > Hi, > > Is there a way to specify kernel version when (re)start kdump > service? Suppose I have install a new kernel and kdump will > generate kdump.img for new kernel in next boot. But I want kdump > to generate kdump.img for new kernel immediately, is it possible? > > Thanks. > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > -- Benjamin Hauger SysAdmin/CSDC-DMO Rm. 94 x8371

3 7

Centos 7.6 & ether-wake
by Gregory P. Ennis 15 Apr '19

15 Apr '19

Everyone, I have not been able to get ether-wake to work waking up other centos 7.6 machines after the upgrade to Centos 7.6. Has anyone else had this problem, and if so any luck with a fix? Greg Ennis

4 5

Getting slapd under CentOS 6 to log connections, etc.
by Robert Heller 31 Mar '19

31 Mar '19

I am running the stock OpenLDAP-servers on a CentOS 6 system. Everything is working just fine, but I am trying to debug connections from a Ubuntu (18.04) system and want to turn on logging in slapd, but although I can get slapd to create a log file, it never actually writes anything. I have these two lines in /etc/openldap/slapd.d/cn=config.ldif: olcLogFile: /var/log/slapd/log olcLogLevel: conns BER config ACL stats none And although /var/log/slapd/log gets created, nothing is ever written to it. What am I missing? -- Robert Heller -- 978-544-6933 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller(a)deepsoft.com -- Webhosting Services

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss March 2019