Discuss December 2018

discuss@lists.centos.org

96 participants
97 discussions

Issues booting centos7 [dracut is failing to enable centos/root, centos/swap LVs]
by Yannis Milios 02 Feb '25

02 Feb '25

Hello, I'm having a strange problem booting a new centos7 installation. Below some background on this. [I have attached the tech details at the bottom of this message] I started a new CentOS7 installation on a VM, so far all good, o/s boots fine. Then I decided to increase VM disk size (initially was 10G) to 13G. Powered off the VM, increased the vhd via the hypervisor, booted from CentOS livecd, selected "recover my centos installation". Then I used the following sequence of commands to make the new vhd size "visible" to the o/s ... - ran fdisk /dev/sda and deleted partition 2. (This is the LVM partition where the o/s is stored. The first partition is /boot [xfs] partition *non lvm*.) - created a new partition with same starting sector as before deleting it, but a different ending sector (to reflect to the increased space). - set partition type to 8e (lvm), saved settings and exit. - ran pvresize and lvresize to make new space visible to the o/s.All good, I can see the space increase on 'lvdisplay centos/root'. - ran 'mount /dev/mapper/centos-root /mnt/root' to temporarily mount the o/s partition. - ran 'xfs_growfs /mnt/root' to resize the o/s fs to the new size. It was successful and I could actually chroot to the o/s and verify new disk size. - rebooted and tried to boot from hdd this time. Grub menu shows up and loads default kernel (3.10.0-862.9.1.el7.x86_64). - after initial kernel boot up process, booting continues to initrd and then it's where the problem starts... - looks like dracut has issues locating/enabling /dev/mapper/centos-root (lv) and as a result it cannot boot to the 'real' root fs (/). - while in dracut shell, I execute the following command sequence: 1. lvm lvchange -ay /dev/centos/root 2. lvm lvchange -ay /dev/centos/swap 3. ln -s /dev/mapper/centos-root /dev/root 4. exit ...and the o/s boots fine...so looks like the pv,vg,lv is detected properly while in initrd, but somehow dracut has difficulties enabling the root,swap LVs ? - While in o/s, I rebuild initrd by using: 'dracut -f -v -a lvm' Note, I have to use '-a lvm' as for some reason, if don't, the lvm utils (lvm,lvm_scan) are not being included to the initrd, not sure why this happens. After rebooting, same thing happens, I have to manually boot the system via dracut shell. I'm a bit stuck at this point, any clues what I'm doing wrong in here ? As I previously said, this is a new installation, so I could simply reinstall the whole thing, but I would rather try to find out some answer to why is this happening ... :-) [curiosity] Some additional details: ================== I've attached /run/initramfs/rdsosreport.txt file [generated while in inird] here: https://privatebin.net/?fdc4052c0c402884#gdB/QYR3IeR55SxUbjfrkZPQfJ7jMxiUxq… o/s ver=CentOS Linux release 7.5.1804 (Core) [root@localhost ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 13G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 8:2 0 12.5G 0 part ├─centos-root 253:0 0 11.5G 0 lvm / └─centos-swap 253:1 0 1G 0 lvm [SWAP] [root@localhost ~]# cat /etc/default/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rd.shell rhgb" GRUB_DISABLE_RECOVERY="true"

4 11

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

dmarc auth on incoming email
by Fred Smith 24 Jan '19

24 Jan '19

Just reading up on DMARC, toying with setting it up to auth against incoming emails. (but not configure my domain to use dmarc, or at least not yet) ran into an article about opendmarc, which is available on epel. but when I took a look at the opendmarc website and the git pages it doesn't appear to have been updated in several years. while I see that it is still available from epel, I wonder if anyone knows the project status? Is it still active? are there any other viable alternatives? thanks in advance! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- The eyes of the Lord are everywhere, keeping watch on the wicked and the good. ----------------------------- Proverbs 15:3 (niv) -----------------------------

2 1

upg. CentOS 7.5 to 7.6: unable to mount smb shares - samba NT domain member using ldap
by Miroslav Geisselreiter 03 Jan '19

03 Jan '19

Originally I posted this question at CentOS forum 20.12.2018. https://www.centos.org/forums/viewtopic.php?f=48&t=69193 Hi all, I am not able to mount samba shares after upgrading CentOS 7.5 to 7.6. I have been searching and trying to configure samba and winbind but no success. I find a lot of manuals and help pages about setting samba and winbind for machine acting as AD DC member but almost nothing about machine acting as NT4 style DC member and that is my case. Samba version before upgrade: samba-4.7.1-9.el7_5.x86_64, after upgrade: samba-4.8.3-4.el7.x86_64. I noticed that now it is necessary to use winbind which I did not use before upgrade. My network: Machine with CentOS 6.9 is PDC (NT4 style) configured with ldap and kerberos, providing domain logon services to Windows and Samba clients of an NT4-like domain. openldap-2.4.40-16.el6.x86_64, krb5-server-1.10.3-65.el6.x86_64, samba-3.6.23-51.el6.x86_64. Machine with CentOS 7.6 is domain member offering network shares to windows clients. Before upgrade my samba-4.7 run only smb and nmb services and everything were fine. After upgrade samba-4.8.3 runs smb nmb and winbind services. smb.conf: workgroup = NT4DOMAIN netbios name = NT4MEMBER |# wbinfo -m --verbose Domain Name DNS Domain Trust Type Transitive In Out BUILTIN Local NT4MEMBER Local NT4DOMAIN INTRANET.XX Workstation Yes No Yes # wbinfo --own-domain NT4DOMAIN | I discovered that winbind is not authenticating users with NT4DOMAIN but only with NT4MEMBER. In this case NT4MEMBER users ARE NT4DOMAIN users (there is only one user1 in ldap database). It can be seen in logs bellow. I set debug level 3 for smbd and winbindd. Windows machines have joined NT4DOMAIN but now cannot mount shares from NT4MEMBER. Windows mount command net use /user:NT4DOMAIN\user1 \\NT4MEMBER\share1 is equal to linux command smbclient //NT4MEMBER/share1 -U NT4DOMAIN\\user1. From linux machine I can mount share by this command: smbclient //NT4MEMBER/share1 -U NT4MEMBER\\user1 but from windows machine it is not possible. Normally (before upgrade) Windows users mapped shares from startup script with this command: net use \\NT4MEMBER\share1. What is going wrong can be seen from logs: |# smbclient //NT4MEMBER/share1 -U NT4DOMAIN\\user1 smbd log: check_ntlm_password: Checking password for unmapped user [NT4DOMAIN]\[user1]@[NT4MEMBER] with the new password interface check_ntlm_password: mapped user is: [NT4DOMAIN]\[user1]@[NT4MEMBER] check_ntlm_password: Authentication for user [user1] -> [user1] FAILED with error NT_STATUS_NO_MEMORY, authoritative=1 Auth: [SMB2,(null)] user [NT4DOMAIN]\[user1] at [Wed, 19 Dec 2018 13:56:08.989053 CET] with [NTLMv2] status [NT_STATUS_NO_MEMORY] workstation [NT4MEMBER] remote host [ipv4:X.X.X.X:40488] mapped to [NT4DOMAIN]\[user1]. local host [ipv4:X.X.X.X:445] log_no_json: JSON auth logs not available unless compiled with jansson gensec_spnego_server_negTokenTarg_step: SPNEGO(ntlmssp) login failed: NT_STATUS_NO_MEMORY smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_NO_MEMORY] || at ../source3/smbd/smb2_sesssetup.c:137 Server exit (NT_STATUS_END_OF_FILE) Terminated winbind log: [ 9232]: request interface version (version = 30) [ 9232]: request location of privileged pipe [ 9232]: pam auth crap domain: [NT4DOMAIN] user: user1 set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was a DC for domain NT4MEMBER, refusing to initialize [ 9228]: pam auth crap domain: NT4DOMAIN user: user1 set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was a DC for domain NT4MEMBER, refusing to initialize set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was a DC for domain NT4MEMBER, refusing to initialize ldb_wrap open of secrets.ldb rpccli_create_netlogon_creds failed for NT4DOMAIN, unable to create NETLOGON credentials: NT_STATUS_NO_MEMORY Could not open handle to NETLOGON pipe (error: NT_STATUS_NO_MEMORY, attempts: 0) The connection to netlogon failed, retrying set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was a DC for domain NT4MEMBER, refusing to initialize set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was a DC for domain NT4MEMBER, refusing to initialize ldb_wrap open of secrets.ldb rpccli_create_netlogon_creds failed for NT4DOMAIN, unable to create NETLOGON credentials: NT_STATUS_NO_MEMORY Could not open handle to NETLOGON pipe (error: NT_STATUS_NO_MEMORY, attempts: 1) This is again a problem for this particular call, forcing the close of this connection The connection to netlogon failed, retrying set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was a DC for domain NT4MEMBER, refusing to initialize set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was a DC for domain NT4MEMBER, refusing to initialize ldb_wrap open of secrets.ldb rpccli_create_netlogon_creds failed for NT4DOMAIN, unable to create NETLOGON credentials: NT_STATUS_NO_MEMORY Could not open handle to NETLOGON pipe (error: NT_STATUS_NO_MEMORY, attempts: 2) This is again a problem for this particular call, forcing the close of this connection This is the third problem for this particular call, adding DC to the negative cache list: NT4DOMAIN (null) The connection to netlogon failed, retrying set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was a DC for domain NT4MEMBER, refusing to initialize set_dc_type_and_flags_connect: DC for domain NT4DOMAIN claimed it was a DC for domain NT4MEMBER, refusing to initialize ldb_wrap open of secrets.ldb rpccli_create_netlogon_creds failed for NT4DOMAIN, unable to create NETLOGON credentials: NT_STATUS_NO_MEMORY Could not open handle to NETLOGON pipe (error: NT_STATUS_NO_MEMORY, attempts: 3) This is again a problem for this particular call, forcing the close of this connection This is the third problem for this particular call, adding DC to the negative cache list: NT4DOMAIN (null) NTLM CRAP authentication for user [NT4DOMAIN]\[user1] returned NT_STATUS_NO_MEMORY # smbclient //NT4MEMBER/share1 -U NT4MEMBER\\user1 smbd log: check_ntlm_password: Checking password for unmapped user [NT4MEMBER]\[user1]@[NT4MEMBER] with the new password interface check_ntlm_password: mapped user is: [NT4MEMBER]\[user1]@[NT4MEMBER] init_sam_from_ldap: Entry found for user: user1 auth_check_ntlm_password: sam authentication for user [user1] succeeded Auth: [SMB2,(null)] user [NT4MEMBER]\[user1] at [Wed, 19 Dec 2018 14:00:37.714900 CET] with [NTLMv2] status [NT_STATUS_OK] workstation [NT4MEMBER] remote host [ipv4:X.X.X.X:40494] became [NT4MEMBER]\[user1] [S-1-5-21-x-x-x-21020]. local host [ipv4:X.X.X.X:445] log_no_json: JSON auth logs not available unless compiled with jansson check_ntlm_password: authentication for user [user1] -> [user1] -> [user1] succeeded NTLMSSP Sign/Seal - Initialising with flags: Got NTLMSSP neg_flags=0x62088215 NTLMSSP Sign/Seal - Initialising with flags: Got NTLMSSP neg_flags=0x62088215 init_group_from_ldap: Entry found for group: 544 init_group_from_ldap: Entry found for group: 100000 Adding homes service for user 'user1' using home directory: '/posta/user1' adding home's share [user1] for user 'user1' at '/data/osobni/%S' Allowed connection from X.X.X.X (X.X.X.X) Connect path is '/tmp' for service [IPC$] Initialising default vfs hooks Initialising custom vfs hooks from [/[Default VFS]/] NT4MEMBER (ipv4:X.X.X.X:40494) connect to service IPC$ initially as user user1 (uid=10010, gid=513) (pid 7874) get_referred_path: |share1| in dfs path \NT4MEMBER\share1 is not a dfs root. smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_NOT_FOUND] || at ../source3/smbd/smb2_ioctl.c:312 NT4MEMBER (ipv4:X.X.X.X:40494) closed connection to service IPC$ Allowed connection from X.X.X.X (X.X.X.X) Connect path is '/samba1/664' for service [share1] Initialising default vfs hooks Initialising custom vfs hooks from [/[Default VFS]/] Initialising custom vfs hooks from [recycle] load_module_absolute_path: Module '/usr/lib64/samba/vfs/recycle.so' loaded NT4MEMBER (ipv4:X.X.X.X:40494) connect to service share1 initially as user user1 (uid=10010, gid=513) (pid 7874) winbind log: [ 9238]: request interface version (version = 30) [ 9238]: request location of privileged pipe sids_to_xids sam_sid_to_name sam_sid_to_name sam_sid_to_name StartTLS issued: using a TLS connection smbldap_open_connection: connection opened ldap_connect_system: successful connection to the LDAP server | I can provide more details (config parameters etc.) later if it is necessary. I played with all winbind parameters, idmap config parameters but no success. Can anyone please help me to solve this problem? Please find more logs. wbinfo -i user1 (without prepending domain) should show NT4DOMAIN\user1 not NT4MEMBER\user1. The same should be for wbinfo -i NT4DOMAIN\\user1. |# wbinfo -i user1 NT4MEMBER\user1:*:10010:513::/posta/user1:/bin/false winbindd log: [ 9747]: request interface version (version = 30) [ 9747]: request location of privileged pipe getpwnam user1 sam_name_to_sid name_to_sid: user1 for domain init_sam_from_ldap: Entry found for user: user1 name_to_sid: user1 for domain init_sam_from_ldap: Entry found for user: user1 sam_rids_to_names for NT4MEMBER sam_sid_to_name # wbinfo -i NT4MEMBER\\user1 NT4MEMBER\user1:*:10010:513::/posta/user1:/bin/false winbindd log: [ 9744]: request interface version (version = 30) [ 9744]: request location of privileged pipe getpwnam NT4MEMBER\user1 sam_name_to_sid name_to_sid: NT4MEMBER\user1 for domain NT4MEMBER init_sam_from_ldap: Entry found for user: user1 name_to_sid: NT4MEMBER\user1 for domain NT4MEMBER init_sam_from_ldap: Entry found for user: user1 sam_rids_to_names for NT4MEMBER sam_sid_to_name # wbinfo -i NT4DOMAIN\\user1 Could not get info for user NT4DOMAIN\user1 winbindd log: [ 9746]: request interface version (version = 30) [ 9746]: request location of privileged pipe getpwnam NT4DOMAIN\user1 sam_name_to_sid name_to_sid: NT4DOMAIN\user1 for domain NT4DOMAIN name_to_sid: failed to lookup name: NT_STATUS_NONE_MAPPED name_to_sid: NT4DOMAIN\user1 for domain NT4DOMAIN name_to_sid: failed to lookup name: NT_STATUS_NONE_MAPPED | wbinfo -u should list all users from NT4DOMAIN but list nothing. wbinfo -u --domain="NT4MEMBER" list all users which are from ldap - they are NT4DOMAIN users. |# wbinfo -u winbindd log: [ 9754]: request interface version (version = 30) [ 9754]: request location of privileged pipe [ 9754]: request interface version (version = 30) [ 9754]: request misc info [ 9754]: request netbios name [ 9754]: request domain name [ 9754]: domain_info [NT4DOMAIN] list_users NT4DOMAIN samr: sequence number # wbinfo -u --domain="NT4MEMBER" NT4MEMBER\dovecot NT4MEMBER\root NT4MEMBER\nobody NT4MEMBER\user1 winbindd log: [ 9756]: request interface version (version = 30) [ 9756]: request location of privileged pipe list_users NT4MEMBER samr_query_user_list smbldap_search_paged: base => [ou=Users,dc=intranet,dc=xx], filter => [(&(uid=*)(objectclass=sambaSamAccount))],scope => [2], pagesize => [1000] smbldap_search_paged: search was successful samr: sequence number sam_rids_to_names for NT4MEMBER | Mirek

3 10

Centos for Power7 no longer available ?
by christian.sonnemans＠xs4all.nl 01 Jan '19

01 Jan '19

Hello Centos fellows, I liked to run Centos on my IBM Power7 machine and therefore I used to download the images form: <http://isoredirect.centos.org/altarch/7/isos/ppc64/> http://isoredirect.centos.org/altarch/7/isos/ppc64/ But not it seems that this link is not working: The requested branch/release/arch/filename does not seem to be valid, please check your input Is Centos 7 no longer supporter for IBM Power 7 machines witch uses centos Big Endian 64 bits ? Any answer is appreciated Greetings Christian Sonnemans. --- Deze e-mail is gecontroleerd op virussen door AVG. http://www.avg.com

3 4

IPv6: ADDRCONF(NETDEV_UP): link is not ready after upgrading to 7.6
by Luigi Rosa 01 Jan '19

01 Jan '19

Hi, after upgrading to 7.6, kernel 3.10.0-957.1.3.el7.x86_64, at boot instead of the GUI login screen I got two lines like this: IPv6: ADDRCONF(NETDEV_UP): em1: link is not ready IPv6: ADDRCONF(NETDEV_UP): em1: link is not ready The server is accessible via ssh on IPv4 Server: DELL PowerEdge T 110 II NIC: Broadcom, driver tg3, lspci -v: 04:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5722 Gigabit Ethernet PCI Express Subsystem: Dell Device 04de Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at c4a00000 (64-bit, non-prefetchable) [size=64K] Expansion ROM at <ignored> [disabled] Capabilities: [48] Power Management version 3 Capabilities: [50] Vital Product Data Capabilities: [58] Vendor Specific Information: Len=78 <?> Capabilities: [e8] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [d0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Virtual Channel Capabilities: [160] Device Serial Number f8-db-88-ff-fe-fe-b4-57 Capabilities: [16c] Power Budgeting <?> Kernel driver in use: tg3 Kernel modules: tg3 dmesg says: [ 8.075141] tg3 0000:04:00.0 em1: Link is up at 1000 Mbps, full duplex [ 8.075153] tg3 0000:04:00.0 em1: Flow control is off for TX and off for RX [ 8.075174] IPv6: ADDRCONF(NETDEV_CHANGE): em1: link becomes ready IPv6 is configured as IGNORE in NetworkManager. I tried the following with the same result: net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.all.disable_ipv6 = 1 and reboot, no effect Setting an automatic IPv6 address: no effect. Suggestions? -- Ciao, luigi / +--[Luigi Rosa]-- \

2 2

daemon core dump
by Alice Wonder 31 Dec '18

31 Dec '18

I have a daemon I can conistently cause a crash on. https://iangilham.com/2016/12/08/core-dump-from-centos-7.html Is that the best way (obviously with debug packages installed) to get the core dump or is there a better way? It is NOT a CentOS/EPEL maintained daemon.

2 1

upgrading 7.5 ==> 7.6
by Fred Smith 31 Dec '18

31 Dec '18

hI ALL! There have been a large enough number of people posting here about difficulties when upgrading from 7. to 7.6 that I'm being somewhat paranoid about it. I have several machines to upgrade, but so far the only one I've dared to work on (least critical if it goes bad) is my new-to-me-but-used laptop. First I did a 'dd' backup of the whole drive onto an external USB drive then did the upgrade. Since I use the Mate desktop, I enabled the epel testing repo (per postings on Mate troubles at the time of the upgrade). Result: Boots to GDM just fine, but Mate is a black screen. Switching to Gnome, works fine, but I can't stand Gnome. Not knowing what else to try I restored the dd backup. Later I inserted a spare HD and did a new install from the DVD media. This installed without issue, but now no desktop works. Switching to a console (CTRL-ALT-F2) I did a full "yum update", which installed quite a few packages, but upon reboot nothing had improved. So I added the epel repo (and testing) and installed Mate. Ditto, nothing had changed. This laptop is fairly old, and according to lshw, has a RV635/M86 [Mobility Radeon HD 3650]I] video chipset, in case it matters. CPU is identified as: Intel(R) Core(TM)2 Duo CPU T9400 @ 2.53GHz Having previously installed 7.5 on it without trouble, on which Mate works just fine, I wonder what could have become so broken that neither an upgrade nor a fresh install works. I have, as I said, several other machines to upgrade, too, some of them have Nvidia grahics (esp. my main desktop box, which also uses Linux software RAID-1) and all run Mate. Then there is a netbook (low priority) a couple of VMs (in virtualbox) and at work several other VMS as well as bare-metal on a Lenovo deskside machine, and I'm afraid to do an update on all of them because I need them to be in usable condition. The Lenovo box in my office is somewhat urgent, as I am about to retire and turn it over to someone else who doesn't know much about Linux. I'd appreciate any advice I can get on how to get these systems upgraded without breaking them. thanks in advance for your help! Fred -- ------------------------------------------------------------------------------- Under no circumstances will I ever purchase anything offered to me as the result of an unsolicited e-mail message. Nor will I forward chain letters, petitions, mass mailings, or virus warnings to large numbers of others. This is my contribution to the survival of the online community. --Roger Ebert, December, 1996 ----------------------------- The Boulder Pledge -----------------------------

8 13

openiam or freeipa ?
by Ilyass Kaouam 31 Dec '18

31 Dec '18

Hi, What is the best OpenIAM or FreeIPA ? Thank's -- *Ilyass kaouam* *Ingénieur System OpenSource* *Mastère européen Manager de Projets Informatiques*

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss December 2018