Discuss April 2022

discuss@lists.centos.org

22 participants
18 discussions

SSD for Centos SWAP /tmp & /var/ partition
by Keith Roberts 03 Sep '25

03 Sep '25

Has anyone actually used a SSD in a Centos setup? My little experiment with a s/h WD drive for /tmp and SWAP partitions kicked the bucket on Wednesday, when the poor WD drive caught the click-of-death. It was a s/h drive to start with and lasted about 4 months. But that was without the /var/log/ partition being written to it, as I mounted that back onto /var/log from the original drive. So I had to install another (WD) drive, and repartion it and rebuild my RPM package database, from the backed-up Packages file. That seems to be all OK now. I'm wondering if it would be a good idea to use a new SSD for moving all the disk i/o to, that Linux likes to do so often. Plus putting SWAP onto a decent SSD should speed things up somewhat. Here's a short video of a laptop fitted with a SSD drive booting macOS, compared to a similar laptop booting from the standard HDD. The laptop with the SSD boots and loads some apps in 28 seconds. The other one takes twice as long. http://eshop.macsales.com/shop/SSD/OWC/Mercury_Extreme_Pro_6G/?utm_source=t… Kind Regards, Keith Roberts ----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------

33 96

Problems with CentOS 8 kickstart
by Hooton, Gerard 23 Jun '25

23 Jun '25

Hi All, I am having problems with a kickstart install of CentOS 8 When I try to do a completely automated install using PXE/UEFI it get to the point where it reads the kickstart config file. Then I see the following message "kickstart install Started cancel waiting for multipath siblings for nvme0n1" This is what I have in the kickstart file # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel autopart --nohome --type=lvm --fstype=xfs ================ When I install from a USB drive it works OK and I have the following in /dev/disk/by-id lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810 -> ../../nvme0n1 lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-eui.002538b11102f46d -> ../../nvme0n1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 lvm-pv-uuid-5Dg4mg-saHa-hJJ6-n5a8-MxBS-gdFi-5jPoNn -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part2 UNG_MZVL2512HCJQ-0-> ../../nvme0n1p2 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part2 -> ../../nvme0n1p2 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part2 -> ../../nvme0n1p2 drwxr-xr-x. 2 root root 400 Jul 5 10:28 . lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKtEdtLjwJQyIdxJcSvPv8TEAjwYGMv6yU -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKAooqrczySYJyiHvUAUji9oScPN2cVi7J -> ../../dm-1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-swap -> ../../dm-1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-root -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkK5HZXbR2ow5xKGuD7jVe4UPzZm2qRLLXI -> ../../dm-2 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-home -> ../../dm-2 It's looks like that I am not doing the disk drive stuff in the config file correctly. -- Gerard Hooton. Senior Technical Officer School of Engineering. University College Cork. College Road. Cork. Ireland. Loc8: WDR-04-60G Tel: +353 21 4902296 Mobile: +353 852813491

3 7

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

01 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

Installing mdadm and C7 on new computer
by H 19 Oct '22

19 Oct '22

I have a new computer with 2 x 2TB SSDs where I wanted to install C7 and use mdadm for RAID1 configuration and encrypting the /home partition. On the net I found https://tuxfixer.com/centos-7-installation-with-lvm-raid-1-mirroring/ which I adopted slightly with respect to partition sizes, using RAID1 for /boot and /root as well and added the /home partition with RAID1 and chose to have /home encrypted. Is there an "official/recommended/suggested" page for installing C7 and using mdadm for RAID1 in combination with LUKS encryption? As far as I can tell things seem right but would like to check before proceeding to install lots of other software. Thanks.

3 7

OT:: Multiple PHP versions
by TE Dukes 22 Aug '22

22 Aug '22

Hello, Been trying to get multiple versions of PHP on a CentOS 7 machine, off and on for the past couple months. I have followed 5 or 6 different howtos but none work. They are very similar and they seems to be done on a fresh install as most do an apache install is the steps. I setup two virtualhosts one for PHP5.6 and one for PHP 7.4. When I create a file with phpinfo, it reports back 5.6.xxx on both sites. So, I'm wondering if I need to remove the existing PHP version that is included with CentOS? Any suggestions or a better way to do this? TIA

6 13

Raspberry Pi 4 and C++ 17
by Will 30 Apr '22

30 Apr '22

Hi, I have a program I want to run on a Raspberry PI 4 that was written on an x86_64 architecture. So I downloaded the Raspberry PI image of CentOS 7 and now I'm on armv7hl. Unfortunately, there doesn't appear to be any devtools for arm at all. Is there an easy(ish) way to get c++ 17 this architecture? Thank you! --- Will

7 12

Where can I find more information on the recent update to the 4.18.0-373 kernel
by Kay Schenk 29 Apr '22

29 Apr '22

Hello folks -- Is there any write up for the most recent update to kernel 4.18.0-373 specifically with respect to sound setup or anything really? I had been using an "alpha" driver for my Intel sound that was appended to my boot line up until this latest. This not only did not work but caused continual hangs. Edited the 4.18.0-373 kernel line and things got somewhat better...but....this version is loading A LOT of modules and do I really need them, etc. I am going through a lot of grief with this recent upgrade. Thanks for any help... -- Kay

4 10

Testing
by Turritopsis Dohrnii Teo En Ming 27 Apr '22

27 Apr '22

Testing

1 0

CentOS Linux Notifications for any changes in files or folders
by Kaushal Shriyan 26 Apr '22

26 Apr '22

Hi, I am running CentOS Linux release 7.9.2009 (Core). Is there a way to notify via email if any files or folders have been accessed, modified, or changed? Also, if somebody deletes or adds any files in a specific folder /opt. Sysadmin should be notified via email or Slack channel using an alerting mechanism. Please guide and suggest. Thanks in advance. Best Regards, Kaushal

5 6

arcconf Linux utility for Adaptec AAC-RAID (Rocket) (rev 02) (IBM ServeRAID 8k/8k-l8) unable to query RAID controller
by Turritopsis Dohrnii Teo En Ming 25 Apr '22

25 Apr '22

Subject: arcconf Linux utility for Adaptec AAC-RAID (Rocket) (rev 02) (IBM ServeRAID 8k/8k-l8) unable to query RAID controller Good day from Singapore, Our client has IBM System x3650 server (machine type: 7979). Operating system is CentOS Linux 6.10 (32-bit). Recently we keep getting the following error messages (output generated by dmesg). <CODE> sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 09 2a d1 50 00 02 00 00 end_request: critical target error, dev sda, sector 153801040 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 09 2a cf 50 00 02 00 00 end_request: critical target error, dev sda, sector 153800528 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 09 2a d3 50 00 02 00 00 end_request: critical target error, dev sda, sector 153801552 JBD2: Detected IO errors while flushing file data on dm-0-8 JBD2: Detected IO errors while flushing file data on dm-0-8 JBD2: Detected IO errors while flushing file data on dm-0-8 JBD2: Detected IO errors while flushing file data on dm-0-8 JBD2: Detected IO errors while flushing file data on dm-0-8 JBD2: Detected IO errors while flushing file data on dm-0-8 JBD2: Detected IO errors while flushing file data on dm-0-8 JBD2: Detected IO errors while flushing file data on dm-0-8 JBD2: Detected IO errors while flushing file data on dm-0-8 JBD2: Detected IO errors while flushing file data on dm-0-8 JBD2: Detected IO errors while flushing file data on dm-0-8 JBD2: Detected IO errors while flushing file data on dm-0-8 JBD2: Detected IO errors while flushing file data on dm-0-8 JBD2: Detected IO errors while flushing file data on dm-0-8 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a cf 38 00 01 00 00 end_request: critical target error, dev sda, sector 153800504 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d0 38 00 01 00 00 end_request: critical target error, dev sda, sector 153800760 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d0 00 00 00 08 00 end_request: critical target error, dev sda, sector 153800704 </CODE> /dev/sda is a RAID 5 array with 3 harddisks of 136.6 GB capacity each. <CODE> [root@teo-en-ming-server ~]# fdisk /dev/sda WARNING: DOS-compatible mode is deprecated. It's strongly recommended to switch off the mode (command 'c') and change display units to sectors (command 'u'). Command (m for help): p Disk /dev/sda: 293.4 GB, 293378981888 bytes 255 heads, 63 sectors/track, 35667 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x8b047782 Device Boot Start End Blocks Id System /dev/sda1 * 1 64 512000 83 Linux Partition 1 does not end on cylinder boundary. /dev/sda2 64 35668 285989888 8e Linux LVM Command (m for help): </CODE> We rebooted the server several times. The next morning we still get the same error messages. <CODE> sd 0:0:0:0: [sda] 573005824 512-byte logical blocks: (293 GB/273 GiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 06 00 10 00 sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, supports DPO and FUA sda: sda1 sda2 sd 0:0:0:0: [sda] Attached SCSI removable disk dracut: Scanning devices sda2 for LVM logical volumes vg_teo-en-ming-server/lv_swap vg_teo-en-ming-server/lv_root EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: SELinux: initialized (dev sda1, type ext4), uses xattr sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d0 00 00 00 80 00 end_request: critical target error, dev sda, sector 153800704 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d0 00 00 00 08 00 end_request: critical target error, dev sda, sector 153800704 Buffer I/O error on device sda, logical block 19225088 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d0 00 00 00 08 00 end_request: critical target error, dev sda, sector 153800704 Buffer I/O error on device sda, logical block 19225088 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d0 00 00 00 08 00 end_request: critical target error, dev sda, sector 153800704 Buffer I/O error on device sda, logical block 19225088 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d0 00 00 00 08 00 end_request: critical target error, dev sda, sector 153800704 Buffer I/O error on device sda, logical block 19225088 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d0 08 00 00 08 00 end_request: critical target error, dev sda, sector 153800712 Buffer I/O error on device sda, logical block 19225089 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d0 08 00 00 08 00 end_request: critical target error, dev sda, sector 153800712 Buffer I/O error on device sda, logical block 19225089 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d0 08 00 00 08 00 end_request: critical target error, dev sda, sector 153800712 Buffer I/O error on device sda, logical block 19225089 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d0 08 00 00 08 00 end_request: critical target error, dev sda, sector 153800712 Buffer I/O error on device sda, logical block 19225089 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d0 10 00 00 08 00 end_request: critical target error, dev sda, sector 153800720 Buffer I/O error on device sda, logical block 19225090 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d1 10 00 00 08 00 end_request: critical target error, dev sda, sector 153800976 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d1 10 00 00 08 00 end_request: critical target error, dev sda, sector 153800976 Buffer I/O error on device sda, logical block 19225122 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d1 10 00 00 08 00 end_request: critical target error, dev sda, sector 153800976 Buffer I/O error on device sda, logical block 19225122 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d1 18 00 00 08 00 end_request: critical target error, dev sda, sector 153800984 Buffer I/O error on device sda, logical block 19225123 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d1 18 00 00 08 00 end_request: critical target error, dev sda, sector 153800984 Buffer I/O error on device sda, logical block 19225123 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d1 18 00 00 08 00 end_request: critical target error, dev sda, sector 153800984 Buffer I/O error on device sda, logical block 19225123 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d1 18 00 00 08 00 end_request: critical target error, dev sda, sector 153800984 Buffer I/O error on device sda, logical block 19225123 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d1 20 00 00 08 00 end_request: critical target error, dev sda, sector 153800992 Buffer I/O error on device sda, logical block 19225124 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d1 20 00 00 08 00 end_request: critical target error, dev sda, sector 153800992 Buffer I/O error on device sda, logical block 19225124 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d1 20 00 00 08 00 end_request: critical target error, dev sda, sector 153800992 Buffer I/O error on device sda, logical block 19225124 Buffer I/O error on device sda, logical block 19225124 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d2 28 00 00 08 00 end_request: critical target error, dev sda, sector 153801256 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d2 28 00 00 08 00 end_request: critical target error, dev sda, sector 153801256 Buffer I/O error on device sda, logical block 19225157 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d2 28 00 00 08 00 end_request: critical target error, dev sda, sector 153801256 Buffer I/O error on device sda, logical block 19225157 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d2 28 00 00 08 00 end_request: critical target error, dev sda, sector 153801256 Buffer I/O error on device sda, logical block 19225157 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d2 30 00 00 08 00 end_request: critical target error, dev sda, sector 153801264 Buffer I/O error on device sda, logical block 19225158 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d2 30 00 00 08 00 end_request: critical target error, dev sda, sector 153801264 Buffer I/O error on device sda, logical block 19225158 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d2 30 00 00 08 00 end_request: critical target error, dev sda, sector 153801264 Buffer I/O error on device sda, logical block 19225158 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d2 30 00 00 08 00 end_request: critical target error, dev sda, sector 153801264 Buffer I/O error on device sda, logical block 19225158 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d2 38 00 00 08 00 end_request: critical target error, dev sda, sector 153801272 Buffer I/O error on device sda, logical block 19225159 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d2 38 00 00 08 00 end_request: critical target error, dev sda, sector 153801272 Buffer I/O error on device sda, logical block 19225159 Buffer I/O error on device sda, logical block 19225159 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d3 30 00 00 08 00 end_request: critical target error, dev sda, sector 153801520 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d3 38 00 00 08 00 end_request: critical target error, dev sda, sector 153801528 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d3 38 00 00 08 00 end_request: critical target error, dev sda, sector 153801528 Buffer I/O error on device sda, logical block 19225191 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d3 38 00 00 08 00 end_request: critical target error, dev sda, sector 153801528 Buffer I/O error on device sda, logical block 19225191 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d3 38 00 00 08 00 end_request: critical target error, dev sda, sector 153801528 Buffer I/O error on device sda, logical block 19225191 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d3 40 00 00 08 00 end_request: critical target error, dev sda, sector 153801536 Buffer I/O error on device sda, logical block 19225192 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d3 40 00 00 08 00 end_request: critical target error, dev sda, sector 153801536 Buffer I/O error on device sda, logical block 19225192 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d3 40 00 00 08 00 end_request: critical target error, dev sda, sector 153801536 Buffer I/O error on device sda, logical block 19225192 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d3 40 00 00 08 00 end_request: critical target error, dev sda, sector 153801536 Buffer I/O error on device sda, logical block 19225192 sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] sd 0:0:0:0: [sda] Add. Sense: Internal target failure sd 0:0:0:0: [sda] CDB: Read(10): 28 00 09 2a d3 48 00 00 08 00 end_request: critical target error, dev sda, sector 153801544 Buffer I/O error on device sda, logical block 19225193 Buffer I/O error on device sda, logical block 19225193 Buffer I/O error on device sda, logical block 19225193 </CODE> Based on the following discussion thread, we think that the RAID controller may be failing. Discussion thread: Which disk is bad in raid6 array Link: https://serverfault.com/questions/384935/which-disk-is-bad-in-raid6-array I had downloaded 32-bit arcconf Linux utility from the following link. Link: https://hwraid.le-vert.net/wiki/Adaptec <CODE> [root@teo-en-ming-server log]# lspci -vvv | grep RAID 04:00.0 RAID bus controller: Adaptec AAC-RAID (Rocket) (rev 02) Subsystem: IBM ServeRAID 8k/8k-l8 </CODE> However, we keep getting segmentation fault running arcconf utility. <CODE> [root@teo-en-ming-server log]# /usr/local/sbin/arcconf getconfig 1 Segmentation fault (core dumped) </CODE> These are the Linux Kernel messages. <CODE> Apr 22 11:11:33 teo-en-ming-server kernel: aacraid: Host adapter abort request (0,0,0,0) Apr 22 11:11:33 teo-en-ming-server kernel: aacraid: Host adapter reset request. SCSI hang ? Apr 22 11:11:33 teo-en-ming-server kernel: AAC: Host adapter BLINK LED 0x4 Apr 22 11:11:33 teo-en-ming-server kernel: AAC0: adapter kernel panic'd 4. Apr 22 11:12:23 teo-en-ming-server kernel: IRQ 17/aacraid: IRQF_DISABLED is not guaranteed on shared IRQs Apr 22 11:14:37 teo-en-ming-server kernel: aacraid: Host adapter abort request (0,0,0,0) Apr 22 11:14:37 teo-en-ming-server kernel: aacraid: Host adapter reset request. SCSI hang ? Apr 22 11:14:37 teo-en-ming-server kernel: AAC: Host adapter BLINK LED 0x4 Apr 22 11:14:37 teo-en-ming-server kernel: AAC0: adapter kernel panic'd 4. Apr 22 11:15:28 teo-en-ming-server kernel: IRQ 17/aacraid: IRQF_DISABLED is not guaranteed on shared IRQs Apr 22 11:16:34 teo-en-ming-server kernel: aacraid: Host adapter abort request (0,0,0,0) Apr 22 11:16:34 teo-en-ming-server kernel: aacraid: Host adapter reset request. SCSI hang ? Apr 22 11:16:34 teo-en-ming-server kernel: AAC: Host adapter BLINK LED 0x4 Apr 22 11:16:34 teo-en-ming-server kernel: AAC0: adapter kernel panic'd 4. </CODE> It seems that I could not query the RAID controller. It keeps saying that the RAID controller adapter has kernel panics. arcconf is a Linux utility to query the RAID controller. <CODE> [root@teo-en-ming-server cmdline]# lspci -nn | grep RAID 04:00.0 RAID bus controller [0104]: Adaptec AAC-RAID (Rocket) [9005:0286] (rev 02) </CODE> Do you know why I keep getting segmentation fault running arcconf Linux utility? Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore 24 April 2022 Sunday

2 1

Kernel rebuild failling on Centos 7: missing libbpf-devel and dwarves rpm too old
by Passerini Marco 20 Apr '22

20 Apr '22

Hi, I'm trying to rebuild the kernel specifically on Centos7 from src.rpm but some packages are missing or too old. I managed to get them and compile on Centos8 though. Any advice? # yumdownloader --source kernel.src # rpm -ivh ./kernel-4.18.0-348.20.1.el7.src.rpm # rpmbuild -bb --target=`uname -m` ~/rpmbuild/SPECS/kernel.spec Building target platforms: x86_64 Building for target x86_64 error: Failed build dependencies: libbpf-devel is needed by kernel-4.18.0-348.20.1.el7.x86_64 rpm < 4.13.0.1-19 conflicts with kernel-4.18.0-348.20.1.el7.x86_64 dwarves < 1.13 conflicts with kernel-4.18.0-348.20.1.el7.x86_64 # rpm -q dwarves dwarves-1.10-1.el7.x86_64 # rpm -q rpm rpm-4.11.3-48.el7_9.x86_64 # yum search libbpf-devel Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: de.mirrors.clouvider.net * centos-sclo-rh: ftp.tu-chemnitz.de * centos-sclo-sclo: centos.mirrors.psw.services * epel: ftp.uni-kl.de * extras: mirror.imt-systems.com * updates: centos.mirror.iphh.net Warning: No matches found for: libbpf-devel No matches found # yum info rpm Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: de.mirrors.clouvider.net * centos-sclo-rh: ftp.tu-chemnitz.de * centos-sclo-sclo: mirror.softaculous.com * epel: mirror.nextlayer.at * extras: mirror.imt-systems.com * updates: centos.mirror.iphh.net Installed Packages Name : rpm Arch : x86_64 Version : 4.11.3 Release : 48.el7_9 Size : 2.5 M Repo : installed >From repo : updates Summary : The RPM package management system URL : http://www.rpm.org/ License : GPLv2+ Description : The RPM Package Manager (RPM) is a powerful command line driven : package management system capable of installing, uninstalling, : verifying, querying, and updating software packages. Each software : package consists of an archive of files along with information about : the package like its version, a description, etc. # yum info dwarves Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: de.mirrors.clouvider.net * centos-sclo-rh: ftp.tu-chemnitz.de * centos-sclo-sclo: ftp.antilo.de * epel: mirror.de.leaseweb.net * extras: mirror.imt-systems.com * updates: centos.mirror.iphh.net Installed Packages Name : dwarves Arch : x86_64 Version : 1.10 Release : 1.el7 Size : 199 k Repo : installed >From repo : epel Summary : Debugging Information Manipulation Tools URL : http://oops.ghostprotocols.net:81/blog License : GPLv2 Description : dwarves is a set of tools that use the debugging information inserted in : ELF binaries by compilers such as GCC, used by well known debuggers such as : GDB, and more recent ones such as systemtap. : : Utilities in the dwarves suite include pahole, that can be used to find : alignment holes in structs and classes in languages such as C, C++, but not : limited to these. : : It also extracts other information such as CPU cacheline alignment, helping : pack those structures to achieve more cache hits. : : A diff like tool, codiff can be used to compare the effects changes in source : code generate on the resulting binaries. : : Another tool is pfunct, that can be used to find all sorts of information about : functions, inlines, decisions made by the compiler about inlining, etc. Regards, Marco Passerini

2 3

Apache APISIX on CentOS Linux release 7.9.2009 (Core)
by Kaushal Shriyan 14 Apr '22

14 Apr '22

Hi, I installing Apache APISIX https://apisix.apache.org/ on CentOS Linux release 7.9.2009 (Core) by referring to https://apisix.apache.org/docs/apisix/how-to-build [root@]#systemctl cat apisix.service # /usr/lib/systemd/system/apisix.service # apisix systemd service # https://github.com/api7/apisix-build-tools/blob/master/usr/lib/systemd/syst… [Unit] Description=apisix #Conflicts=apisix.service After=network-online.target Wants=network-online.target [Service] Type=forking Restart=on-failure WorkingDirectory=/usr/local/apisix ExecStart=/usr/bin/apisix start ExecStop=/usr/bin/apisix stop ExecReload=/usr/bin/apisix reload LimitNOFILE=65536 [Install] WantedBy=multi-user.target [root@]# systemctl restart apisix Job for apisix.service failed because the control process exited with error code. See "systemctl status apisix.service" and "journalctl -xe" for details. [root@apacheapisixapigateway ~]# systemctl status apisix ● apisix.service - apisix Loaded: loaded (/usr/lib/systemd/system/apisix.service; disabled; vendor preset: disabled) Active: failed (Result: start-limit) since Thu 2022-04-14 20:29:36 IST; 2ms ago Process: 1597 ExecStart=/usr/bin/apisix start (code=exited, status=1/FAILURE) Apr 14 20:29:35 apacheapisixapigateway systemd[1]: Failed to start apisix. Apr 14 20:29:35 apacheapisixapigateway systemd[1]: Unit apisix.service entered failed state. Apr 14 20:29:35 apacheapisixapigateway systemd[1]: apisix.service failed. Apr 14 20:29:36 apacheapisixapigateway systemd[1]: apisix.service holdoff time over, scheduling restart. Apr 14 20:29:36 apacheapisixapigateway systemd[1]: Stopped apisix. Apr 14 20:29:36 apacheapisixapigateway systemd[1]: start request repeated too quickly for apisix.service Apr 14 20:29:36 apacheapisixapigateway systemd[1]: Failed to start apisix. Apr 14 20:29:36 apacheapisixapigateway systemd[1]: Unit apisix.service entered failed state. Apr 14 20:29:36 apacheapisixapigateway systemd[1]: apisix.service failed. [root@]#journalctl -u apisix.service Apr 14 23:29:42 apacheapisixapigateway apisix[1798]: /usr/local/openresty/luajit/bin/luajit ./apisix/cli/apisix.lua start Apr 14 23:29:42 apacheapisixapigateway apisix[1798]: etcd cluster version 3.3.0 is less than the required version 3.4.0, please upgrade your etcd cluster Apr 14 23:29:42 apacheapisixapigateway systemd[1]: apisix.service: control process exited, code=exited status=1 Apr 14 23:29:42 apacheapisixapigateway systemd[1]: Failed to start apisix. Apr 14 23:29:42 apacheapisixapigateway systemd[1]: Unit apisix.service entered failed state. Apr 14 23:29:42 apacheapisixapigateway systemd[1]: apisix.service failed. Apr 14 23:29:42 apacheapisixapigateway systemd[1]: apisix.service holdoff time over, scheduling restart. Apr 14 23:29:42 apacheapisixapigateway systemd[1]: Stopped apisix. Apr 14 23:29:42 apacheapisixapigateway systemd[1]: Starting apisix... Apr 14 23:29:42 apacheapisixapigateway apisix[1822]: /usr/local/openresty/luajit/bin/luajit ./apisix/cli/apisix.lua start Apr 14 23:29:42 apacheapisixapigateway apisix[1822]: etcd cluster version 3.3.0 is less than the required version 3.4.0, please upgrade your etcd cluster Apr 14 23:29:42 apacheapisixapigateway systemd[1]: apisix.service: control process exited, code=exited status=1 Apr 14 23:29:42 apacheapisixapigateway systemd[1]: Failed to start apisix. Apr 14 23:29:42 apacheapisixapigateway systemd[1]: Unit apisix.service entered failed state. Apr 14 23:29:42 apacheapisixapigateway systemd[1]: apisix.service failed. Apr 14 23:29:42 apacheapisixapigateway systemd[1]: apisix.service holdoff time over, scheduling restart. Apr 14 23:29:42 apacheapisixapigateway systemd[1]: Stopped apisix. Apr 14 23:29:42 apacheapisixapigateway systemd[1]: Starting apisix... Apr 14 23:29:42 apacheapisixapigateway apisix[1845]: /usr/local/openresty/luajit/bin/luajit ./apisix/cli/apisix.lua start Apr 14 23:29:43 apacheapisixapigateway apisix[1845]: etcd cluster version 3.3.0 is less than the required version 3.4.0, please upgrade your etcd cluster Apr 14 23:29:43 apacheapisixapigateway systemd[1]: apisix.service: control process exited, code=exited status=1 Apr 14 23:29:43 apacheapisixapigateway systemd[1]: Failed to start apisix. Apr 14 23:29:43 apacheapisixapigateway systemd[1]: Unit apisix.service entered failed state. Apr 14 23:29:43 apacheapisixapigateway systemd[1]: apisix.service failed. Apr 14 23:29:43 apacheapisixapigateway systemd[1]: apisix.service holdoff time over, scheduling restart. Apr 14 23:29:43 apacheapisixapigateway systemd[1]: Stopped apisix. Apr 14 23:29:43 apacheapisixapigateway systemd[1]: Starting apisix... Apr 14 23:29:43 apacheapisixapigateway apisix[1869]: /usr/local/openresty/luajit/bin/luajit ./apisix/cli/apisix.lua start Apr 14 23:29:43 apacheapisixapigateway apisix[1869]: etcd cluster version 3.3.0 is less than the required version 3.4.0, please upgrade your etcd cluster Apr 14 23:29:43 apacheapisixapigateway systemd[1]: apisix.service: control process exited, code=exited status=1 Apr 14 23:29:43 apacheapisixapigateway systemd[1]: Failed to start apisix. Apr 14 23:29:43 apacheapisixapigateway systemd[1]: Unit apisix.service entered failed state. Apr 14 23:29:43 apacheapisixapigateway systemd[1]: apisix.service failed. Apr 14 23:29:43 apacheapisixapigateway systemd[1]: apisix.service holdoff time over, scheduling restart. Apr 14 23:29:43 apacheapisixapigateway systemd[1]: Stopped apisix. Apr 14 23:29:43 apacheapisixapigateway systemd[1]: start request repeated too quickly for apisix.service Apr 14 23:29:43 apacheapisixapigateway systemd[1]: Failed to start apisix. Apr 14 23:29:43 apacheapisixapigateway systemd[1]: Unit apisix.service entered failed state. Apr 14 23:29:43 apacheapisixapigateway systemd[1]: apisix.service failed. Please guide me. Thanks in Advance. Best Regards, Kaushal

2 1

server gave bad signature for RSA key 0 - ?
by lejeczek 12 Apr '22

12 Apr '22

Hi guys. Anybody has seen something like this from 'ssh' and care to comment? -> $ ssh 10.0.1.6 (root(a)10.0.1.6) Password: client_global_hostkeys_private_confirm: server gave bad signature for RSA key 0: error in libcrypto I have virtually identical c8 Stream boxes and only one gives out this message. I regen keys but that changed nothing. many thanks, L.

2 1

[Openssl]incorrect CVE mentioned in openssl changelog
by Akshar Kanak 08 Apr '22

08 Apr '22

Dear team in latest openssl openssl-1.0.2k-25.el7_9.x86_64 , looks like there is an issue with change logs . rpm -qi --changelog openssl-1.0.2k-25.el7_9.x86_64 shows me " * Wed Mar 23 2022 Dmitry Belyavskiy <dbelyavs(a)redhat.com> - 1:1.0.2k-25 - Fixes CVE-2022-2078 Infinite loop in BN_mod_sqrt() reachable when parsing certificates - Related: rhbz#2067160 " The CVE number should be CVE-2022-0778 . Right ? reference : https://bugzilla.redhat.com/show_bug.cgi?id=2062202 Thanks and regards Akshar

1 0

kickstart storage configuration hangs
by Leon Fauster 06 Apr '22

06 Apr '22

While playing with some CS9 kickstart installation attempts (manually/graphical works) I noticed following: What ever I provide as ks file "anaconda" outputs (text mode): <snip> Saving storage configuration ... Checking storage configuration ... . . .......................................................... <filling multiple lines> The ks file has nothing special, the storage related lines are: ignoredisk --only-use=nvme0n1 zerombr clearpart --all --initlabel --drives=nvme0n1 and then the part/volgroup/logvol lines. Does someone have the same issue? I guess anaconda is not ready? Because even the ks file from the manually installed system does not work ... -- Leon

2 2

Introducing CentOS Stream 9
by Johnny Hughes 05 Apr '22

05 Apr '22

Rich Bowen has posted a blog entry "Introducing CentOS Stream 9" https://blog.centos.org/2021/12/introducing-centos-stream-9/ More details here: https://centos.org/stream9/ Thanks, Johnny Hughes

5 13

Two labels, one mount point
by Kenneth Porter 01 Apr '22

01 Apr '22

I have a systemd mount unit that mounts an external drive by label. What happens if I plug in two USB external drives formatted with the same label? Does the last one discovered mount on top? I'm rotating backup drives and the backup software assumes the drive to be at a particular directory. Normally I'd stop the service, umount the drive (via systemd stop), unplug, plug the other one in, then start the service. (An automount unit will mount the replacement drive when the service touches the mount point.) But I'm wondering what happens if someone isn't careful and plugs in the 2nd drive before shutting down the service and removing the first one.

1 0

SELinux relabeling for a diffeerernt mount point
by Kenneth Porter 01 Apr '22

01 Apr '22

I'm preparing a disk mounted at /mnt/tmp to later be mounted at /var/lib/BackupPC. Is there some magic invocation to get the selinux labels for the structure I create to assume the final mount point, so that I don't have to relabel it when it's finally mounted at its target location? Or is there an argument to restorecon that will do the equivalent of chroot so that restorecon assumes the final location?

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss April 2022