Discuss

discuss@lists.centos.org

1 participants
34753 discussions

CentOS 8 installation
by isdtor 08 May '20

08 May '20

Are there still a lot of rough edges in this area? There are some things I simply can't get to work. This is about kickstart installations. Finding the right stuff for the %packages sections is lucky dip at best. The RHEL manual points to the comps file, really? This file isn't meant to be parsed by humans. Specifying an environment - the example "Infrastructure Server" doesn't exist. Is this one of the areas where CentOS deviates from RHEL? I did find server-product-environment, custom-environment, minimal-environment. I followed the link in the documentation to the kickstart file generator. The generated file isn't usable as is, specifically the %packages section - anaconda says there is no group dns-server, for instance. Which dnf later confirms. The group list in dnf also seems to be a lot shorter than it used to be under 7? Specifying %packages --multilib, this is where it breaks down completely. For the chosen group/package mix, which works perfectly without multilib, anaconda complains about conflicts for files provided by both the i686 and the x86_64 version of, in this case, gdb-headless and sssd-common. Attempting to fix this with -gdb-headless.i686 -sssd-common.i686 fails, these lines are being ignored. Excluding gdb-headless altogether fails also because the main gdb package pulls it in. Honestly, I'm not sure where to go from here.

2 3

libQt5Core.so ver 5.12
by cristiantorres110＠hotmail.com 08 May '20

08 May '20

Hello, For the last few days, 'dnf upgrade' on my Centos 8 installation has been showing problems saying that it cannot install the best update candidates for packages (kf5-*) because nothing provides libQtCore.so.5(Qt_5.12). My system shows that it presently has libQtCore.so.5(Qt_5.11). I've been keeping the system up to date using the --nobest option in dnf. I could download 'libqt5-core-5.12.8-alt3.x86_64.rpm ' from here and install it but I haven't dared to try. Is there an expectation for when version Qt_5.12 will be in the official repos? BR --Cristian

2 2

Chrony
by Jerry Geis 08 May '20

08 May '20

I just happened to notice this morning in /var/log/messages: chronyd[1299]: Selected source 207.244.103.95 host 207.244.103.95 95.103.244.207.in-addr.arpa domain name pointer dns-e.wdc-us.hosts.301-moved.de. Just curious why my machine in Indiana (USA) is asking for time in Germany. Wouldn't it use something closer ? Thanks, jerry

2 1

video problems
by mark 07 May '20

07 May '20

I've got an ancient USB videocam (QuickCam Express, yes, 15 years old). I got it working under C7, after I removed the default loaded gspca_spca561, and replaced it with the previous driver, gspca_spca508. It also needed zc3xx. Then I updated and rebooted my system a couple of days ago, and now no /dev/video, no errors.... Any clues? mark "other than waiting for a camera to arrive from China somewhere in June or July?"

1 2

repomd.xml.asc BAD signature in CentOS-7-x86_64-Minimal-2003.iso
by Pany 07 May '20

07 May '20

Hi list, I downloaded the CentOS-7-x86_64-Minimal-2003.iso ( sha256sum 659691c28a0e672558b003d223f83938f254b39875ee7559d1a4a14c79173193 ) and mount it on /mnt Unfortunately, It returned "BAD signature" when I verified the repodata/repomd.xml.asc So should I continue to use this ISO? Below is my procedure: # gpg --import /mnt/RPM-GPG-KEY-CentOS-7 gpg: key F4A80EB5: public key "CentOS-7 Key (CentOS 7 Official Signing Key) <security(a)centos.org>" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) # gpg --fingerprint /root/.gnupg/pubring.gpg ------------------------ pub 4096R/F4A80EB5 2014-06-23 Key fingerprint = 6341 AB27 53D7 8A78 A7C2 7BB1 24C6 A8A7 F4A8 0EB5 uid CentOS-7 Key (CentOS 7 Official Signing Key) <security(a)centos.org> # gpg --verify /mnt/repodata/repomd.xml.asc gpg: Signature made Wed 22 Apr 2020 07:37:54 AM CST using RSA key ID F4A80EB5 gpg: BAD signature from "CentOS-7 Key (CentOS 7 Official Signing Key) <security(a)centos.org>"

1 0

du hung, wild display in ps
by Fred Smith 07 May '20

07 May '20

Hi! On Centos-7: $ cat /etc/centos-release CentOS Linux release 7.8.2003 (Core) Was running du to examine the sizes of my backups and found du hung, running "ps -eLf /mnt/backup/backups" shows this: # ps -eLf | grep du root 1185 1 1185 0 1 May01 ? 00:00:00 /usr/bin/abrt-watch-log -F Backtrace /var/log/Xorg.0.log -- /usr/bin/abrt-dump-xorg -xD root 1281 1 1281 0 1 May01 ? 00:00:01 /usr/bin/abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected ernel BUG at list_del corruption list_add corruption do_IRQ: stack overflow: ear stack overflow (cur: eneral protection fault nable to handle kernel ouble fault: RTNL: assertion failed eek! page_mapcount(page) went negative! adness at NETDEV WATCHDOG ysctl table check failed : nobody cared IRQ handler type mismatch Kernel panic - not syncing: Machine Check Exception: Machine check events logged divide error: bounds: coprocessor segment overrun: invalid TSS: segment not present: invalid opcode: alignment check: stack segment: fpu exception: simd exception: iret exception: /var/log/messages -- /usr/bin/abrt-dump-oops -xtD root 11090 1 11090 11 1 15:08 pts/1 00:01:10 du -s /mnt/backup/backups even after killing the du. there were two DUs shown, I killed the parent (presumably the one I started) but the one that remains seems to be un-killable. This is what the output looked like before I killed du: # ps -eLf | grep du root 1185 1 1185 0 1 May01 ? 00:00:00 /usr/bin/abrt-watch-log -F Backtrace /var/log/Xorg.0.log -- /usr/bin/abrt-dump-xorg -xD root 1281 1 1281 0 1 May01 ? 00:00:01 /usr/bin/abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected ernel BUG at list_del corruption list_add corruption do_IRQ: stack overflow: ear stack overflow (cur: eneral protection fault nable to handle kernel ouble fault: RTNL: assertion failed eek! page_mapcount(page) went negative! adness at NETDEV WATCHDOG ysctl table check failed : nobody cared IRQ handler type mismatch Kernel panic - not syncing: Machine Check Exception: Machine check events logged divide error: bounds: coprocessor segment overrun: invalid TSS: segment not present: invalid opcode: alignment check: stack segment: fpu exception: simd exception: iret exception: /var/log/messages -- /usr/bin/abrt-dump-oops -xtD root 11078 18627 11078 0 1 15:08 pts/1 00:00:00 sudo du -s /mnt/backup/backups root 11090 11078 11090 12 1 15:08 pts/1 00:01:10 du -s /mnt/backup/backups root 12125 19449 12125 0 1 15:17 pts/0 00:00:00 grep --color=auto du Oh, and I never did get the du out put I expected. Anyone got a clue? Thanks in advance! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- "For the word of God is living and active. Sharper than any double-edged sword, it penetrates even to dividing soul and spirit, joints and marrow; it judges the thoughts and attitudes of the heart." ---------------------------- Hebrews 4:12 (niv) ------------------------------

2 2

Odd permissions
by mark 07 May '20

07 May '20

I've posted a couple times in the last month, that for some reason, since I rebuilt to CentOS 7 from 6 (same home directory, another partition, of course), when I log out, it restarts with me logged in, and only the second time I log out does it actually log me out. Still debugging that. I have logged in as root, and don't have the problem, so I'm assuming that it's something incompatible, or somehow mis-set in ~/.<whatever>. Looking in ~/.cache, I found something weird: ~/.cache/gnome-control-center, which had permissions of d-w-rwxr-T Say *what*? Anyone got a clue as to why? And while I'm looking for clues, does anyone have any thoughts as to where my issue might lie? mark

2 1

rpm command option
by Chris Olson 06 May '20

06 May '20

We located an application recommended by one of customers for sharing certain data. It was available for installation using a few different methods. Using yum was also recommended for the installation. The install instructions began with what appeared to be a fairly typical command as indicated below (with the URL slightly altered). sudo rpm --import https://rpm.xxxxx.com/rpmrepo.key To our junior employee assigned to perform the install on a test system, it seemed like a good idea to do some checking on the rpm option --import indicated in those instructions. They did not find the --import in any of the 14 pages of the CentOS 7 man page for rpm. Some Google searches indicated that the --import option does exist. The repo setup and application installation all went well and took only about three minutes. The app is also working as intended. Is there some good reason for --import being left out of the manual page?

5 4

Custom ISO
by Jerry Geis 06 May '20

06 May '20

Hi All, I am trying to make a customer ISO. When I run this command: mkisofs -o $DESTINATION_FILE -b isolinux/isolinux.bin -c boot.cat \ -no-emul-boot -boot-info-table \ -V "$NAME" -boot-load-size 4 -boot-info-table -R -J -v -T \ -eltorito-alt-boot -e images/efiboot.img \ $DESTINATION_DIR it tells me: Size of boot image is 4 sectors -> No emulation Size of boot image is 17408 sectors -> genisoimage: Error - boot image 'images/efiboot.img' has not an allowable size. This is the exact same file that is on the Everything ISO image. What am I missing ? I also want to make the ISO boot with UEFI. I think I have the right parameters but getting this error. Thoughts? Thanks, Jerry

3 6

Samba update to 4.10 (with c7.8) - broken -?
by lejeczek 05 May '20

05 May '20

hi guys I've just let the system to get big update to 7.8 and with it came new Samba(4.10.4-10.el7.x86_64), a version with now fails on my boxes for no apparent reasons. My Samba uses LDAP backend but I can see no errors related to that neither. ... [2020/05/05 15:53:37.093041, 0] ../../lib/util/become_daemon.c:136(daemon_ready) daemon_ready: daemon 'smbd' finished starting up and ready to serve connections [2020/05/05 15:53:37.106797, 2] ../../source3/smbd/server.c:1415(smbd_parent_loop) waiting for connections [2020/05/05 15:53:37.108770, 3] ../../source3/smbd/server_exit.c:236(exit_server_common) Server exit (termination signal) Failed to start Samba SMB Daemon. Unit smb-ccnr-biotec.service entered failed state. smb-ccnr-biotec.service failed. Are you seeing anything weir with your Sambas? many thanks, L.

1 1

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