Discuss December 2014

discuss@lists.centos.org

164 participants
168 discussions

CentOS-6 Another email related AVC
by James B. Byrne 11 Dec '14

11 Dec '14

CentOS-6.6 Postfix-2.11.1 (local) ClamAV-0.98.5 (epel) Amavisd-new-2.9.1 (epel) opendkim-2.9.0 (centos) pypolicyd-spf-1.3.1 (epel) /var/log/maillog Dec 11 16:52:09 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl from read access on the file online. For complete SELinux messages. run sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a Dec 11 16:52:10 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl from read access on the file online. For complete SELinux messages. run sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a Dec 11 16:52:10 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl from read access on the file online. For complete SELinux messages. run sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a Dec 11 16:52:10 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl from read access on the file online. For complete SELinux messages. run sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a Dec 11 16:52:11 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl from read access on the file online. For complete SELinux messages. run sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a Dec 11 16:53:28 inet18 setroubleshoot: SELinux is preventing /usr/bin/clamscan from write access on the directory tmp. For complete SELinux messages. run sealert -l 1f0d210d-b4e1-4635-8765-f7e913e2bf28 Dec 11 16:53:29 inet18 setroubleshoot: SELinux is preventing /usr/bin/clamscan from write access on the directory tmp. For complete SELinux messages. run sealert -l 1f0d210d-b4e1-4635-8765-f7e913e2bf28 Dec 11 16:53:29 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl from read access on the file online. For complete SELinux messages. run sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a Dec 11 16:58:36 inet18 setroubleshoot: SELinux is preventing /usr/bin/clamscan from write access on the directory tmp. For complete SELinux messages. run sealert -l 1f0d210d-b4e1-4635-8765-f7e913e2bf28 Dec 11 16:58:36 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl from read access on the file online. For complete SELinux messages. run sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a Dec 11 16:58:37 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl from read access on the file online. For complete SELinux messages. run sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a SELinux is preventing /usr/bin/perl from read access on the file online. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that perl should be allowed read access on the online file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep amavisd /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp [root@inet18 ~ (master #)]# grep amavisd /var/log/audit/audit.log | audit2allow #============= amavis_t ============== allow amavis_t shell_exec_t:file { read open }; allow amavis_t sysfs_t:file read; -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

CentOS 5- mount shows a cifs share mounted 4 times!
by Niamh Holding 11 Dec '14

11 Dec '14

Hello, How can this happen? mount -l /dev/sda3/ on type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sda1 on /boot type ext4 (rw) /dev/sdb1 on /music type ext3 (rw) /dev/mapper/VolGroup00-LogVol00 on /fedora type ext3 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) 10.0.0.3:/backup on /backup type nfs (rw,addr=10.0.0.3) /etc/named on /var/named/chroot/etc/named type none (rw,bind) /etc/named.rfc1912.zones on /var/named/chroot/etc/named.rfc1912.zones type none (rw,bind) /etc/rndc.key on /var/named/chroot/etc/rndc.key type none (rw,bind) /usr/lib64/bind on /var/named/chroot/usr/lib64/bind type none (rw,bind) /etc/named.iscdlv.key on /var/named/chroot/etc/named.iscdlv.key type none (rw,bind) /etc/named.root.key on /var/named/chroot/etc/named.root.key type none (rw,bind) 10.0.0.253:/i-data/48e5a222/nfs/music on /thecus-music type nfs (rw,addr=10.0.0.253) 10.0.0.253:/i-data/48e5a222/nfs/fedora on /thecus-backup type nfs (rw,addr=10.0.0.253) \\\\10.0.0.253\\niamh on /NSA320-music type cifs (rw) \\\\10.0.0.253\\niamh on /NSA320-music type cifs (rw) \\\\10.0.0.253\\niamh on /NSA320-music type cifs (rw) \\\\10.0.0.253\\niamh on /NSA320-music type cifs (rw) \\\\10.0.0.253\\fedora on /NSA320-fedora type cifs (rw) -- Best regards, Niamh mailto:niamh@fullbore.co.uk

2 4

CentOS 7 grub.cfg missing on new install
by Jeff Boyce 11 Dec '14

11 Dec '14

Greetings - The short story is that got my new install completed with the partitioning I wanted and using software raid, but after a reboot I ended up with a grub prompt, and do not appear to have a grub.cfg file. So here is a little history of how I got here, because I know in order for anyone to help me they would subsequently ask for this information. So this post is a little long, but consider it complete. Brand new Dell system with two 3GB drives in this system with RAID1 LVM taking all the space outside the boot partitions. I initially created the sda[1,2] and sdb[1,2] partitions via GParted leaving the remaining space unpartitioned. A gpt partition table was put on both drives. During installation Anaconda recognized everything properly which resulted in the following partition summary: sda1 /boot/efi 500 MB EFI System Partition sda2 /boot 500 MB xfs vg_jab-hostroot / 8 GB LVM xfs RAID1 vg_jab-hostvar /var 4 GB LVM xfs RAID1 vg_jab-hostswap /swap 2 GB LVM swap RAID1 The installer also recognized and listed these unknown partitions that were untouched during installation. sdb1 vfat 500 MB standard partition sdb2 vfat 500 MB standard partition Installation proceeded successfully, and after the initial reboot of the system I used mdadm commands to watch the raid complete building before doing anything else (I know, not necessary but I am doing other things and had the time to let it complete). I rebooted the system and got a terminal prompt as expected (no GUI installed). At this point I needed to copy my /boot/efi and /boot partitions from sda[1,2] to sdb[1,2] so that the system would boot from either drive, so I issued the following sgdisk commands: root# sgdisk -R /dev/sdb1 /dev/sda1 root# sgdisk -R /dev/sdb2 /dev/sda2 root# sgdisk -G /dev/sdb1 root# sgdisk -G /dev/sdb2 Results of the first command above: Found invalid GPT and valid MBR; converting MBR to GPT format. Warning the kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. The same note (from the Warning on) was repeated for the other three commands. I then installed GRUB2 on /dev/sdb1 using the following command: root# grub2-install /dev/sdb1 Results: Installing for x86_64-efi platform. Installation finished. No error reported. I rebooted the system now, only to be confronted with a GRUB prompt. Thinking that this is a good opportunity to for me to learn to rescue a system since I am going to need to understand how to recover from a disk or raid failure, I started researching and reading. It takes a little bit of work to understand what information is valuable when a lot of it refers to GRUB (not GRUB2) and doesn't make reference to UEFI booting and partitions. I found this Ubuntu wiki as a pretty good source https://help.ubuntu.com/community/Grub2/Troubleshooting#Search_.26_Set Below is the current information of my system as seen by grub; grub# set (the important grub2 variables are:) prefix = (hd1, gpt2)/grub2 root = hd1, gpt2 grub# ls -lha Device proc: filesystem type procfs Device hd0: no known filesystem detected Device hd1: no known filesystem detected Partition hd1, gpt3: no known filesystem detected Partition hd1, gpt2: filesystem xfs Partition hd1, gpt1: filesystem fat Device hd2: no known filesystem detected Partition hd2, gpt3: no known filesystem detected Partition hd2, gpt2: no known filesystem detected Partition hd2, gpt1: no known filesystem detected grub# ls (hd1, gpt2) -l / /efi /grub /grub2 vmlinuz -3.10.0-123.el7.x86_64 initramfs-3.10.0-123.el7.x86_64.img ... plus some other files Looking through the directories, I see that there is no grub.cfg file. Other than grub not recognizing the filesystem on hd2, the directories on hd2, gpt[1,2] seem to be identical to hd1, gpt[1,2] as I would assume based on the sgdisk commands I gave to copy them. My initial thinking is that I need to re-run grub2-install on hd1 (sda), but I need a running system to do that. So following the guidance I had I issued the following commands in grub to boot the system. grub# linux /vmlinuz -3.10.0-123.el7.x86_64 root=/dev/sda2 ro grub# initrd /initramfs-3.10.0-123.el7.x86_64.img grub# boot Unfortunately the system hung on booting, with the following information in the "journalctl" file: # journalctl Not switching root: /sysroot does not seem to be an OS tree. /etc/os-release is missing. Initrd-switch-root.service: main process exited, code=exited, status=1/FAILURE Failed to start Switch Root. . . . . . Triggering OnFailure= dependencies of initrd-switch-root.service. Starting Emergency Shell. . . Failed to issue method call: Invalid argument Now I am not sure that I want to get misdirected to what the problem is with this boot, if I can boot from a CD in linux rescue mode and do the grub install, then be back to a booting system. So lets ignore the boot error if we can. So I boot from a CD in rescue mode, and it is only able to automatically mount sd3 under /mnt/sysimage (the LVM RAID1 containing mounts for / and /var). I am able to manually mount sda1 and sda2, but am not sure at what level in the filesystem to mount them (i.e., at /mnt/sda1 or at mnt/sysimage/sda1) in order to properly run grub2-install. So that is where I am at now. I would like to know how to repair the system, rather than starting over on a new install. Can someone enlighten me on what I need to do from here. Also if someone can speculate on why my grub.cfg is missing in the first place I would be interested. Also, please cc me directly on any responses, as I am only subscribed to the daily digest. Thanks. Jeff Boyce Meridian Environmental www.meridianenv.com

3 4

CentOS-announce Digest, Vol 118, Issue 7
by centos-announce-request＠centos.org 11 Dec '14

11 Dec '14

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://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. CESA-2014:1971 Important CentOS 7 kernel Security Update (Johnny Hughes) 2. CESA-2014:1976 Important CentOS 7 rpm Security Update (Johnny Hughes) 3. CEEA-2014:1980 CentOS 7 systemd Enhancement Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 10 Dec 2014 12:48:13 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2014:1971 Important CentOS 7 kernel Security Update Message-ID: <20141210124813.GA47995(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:1971 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1971.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 0ba4633c95c00c8c0e680e4ba25a7d86b814997e770ec969b13786e7dc293edb kernel-3.10.0-123.13.1.el7.x86_64.rpm 9394409a1a2198f722c5413405cab3a02ff9f3e84a4b7ebbc79bfd4d33a9c1bf kernel-abi-whitelists-3.10.0-123.13.1.el7.noarch.rpm c1fccd2c7a95dae3ccd3b4d3970c96fcda48c7fe21c8a7e8580dd19171c51278 kernel-debug-3.10.0-123.13.1.el7.x86_64.rpm b694c8adb48d481617db3056c34dd455962bf48994ebd5ac7339d5169842766d kernel-debug-devel-3.10.0-123.13.1.el7.x86_64.rpm fa1622aaa604897b79cd7e468b9d99c81c4e9b2c94c24ebacb6f94070907f579 kernel-devel-3.10.0-123.13.1.el7.x86_64.rpm 5db912400deea9b97dcbfb113d5dc67e47c6f04f763cdc28615f9eb7cf74c59d kernel-doc-3.10.0-123.13.1.el7.noarch.rpm 198ad46ad016f25e59c0d96daf207feaaf214c90e41c33e03324141f4d485c7e kernel-headers-3.10.0-123.13.1.el7.x86_64.rpm ddb99325960b064fb283c5a2dbc505b8a452663d00bbd6e6247150c53a834e18 kernel-tools-3.10.0-123.13.1.el7.x86_64.rpm bc0c7bde959031b02fe76e4ff4016d61bb0db6bc6cb15fe5bf7b858814539eaa kernel-tools-libs-3.10.0-123.13.1.el7.x86_64.rpm ac5b1b0066d71d38f2a5e2a231b6b81603dfd4f16c314d8eb94738550f4b2af1 kernel-tools-libs-devel-3.10.0-123.13.1.el7.x86_64.rpm 1221821e953c8c6122b87ca9878ef3fe69dac93243061e13fb6f8756a313fc0d perf-3.10.0-123.13.1.el7.x86_64.rpm 2ad0cf510727c006412e2ca1c944e0e47fb6cfb6c24a2bb86d3e6cbf61cc51b4 python-perf-3.10.0-123.13.1.el7.x86_64.rpm Source: 264dd245a168050e3c8cf54adf892827786fd07a03f55cc45e6b9fdb46486354 kernel-3.10.0-123.13.1.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Wed, 10 Dec 2014 12:49:42 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2014:1976 Important CentOS 7 rpm Security Update Message-ID: <20141210124942.GA48114(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:1976 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1976.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 42d0d9d8c43646be6bb73af2645e7e7d00613ffbd7281a167e938e13254d838d rpm-4.11.1-18.el7_0.x86_64.rpm 3718d08372462fb7670e87dd49c55ccd3ba241c9c99b849478fcba4783f78102 rpm-apidocs-4.11.1-18.el7_0.noarch.rpm 4cb5f67b92322653529f9c2c4f21756e4500c4c009c8d7e76a9ef29fa92e8d52 rpm-build-4.11.1-18.el7_0.x86_64.rpm 6d0cd4d0e424f21e6f51b89a9eb81b42c6d36824e16d8ff839f442c5504e081b rpm-build-libs-4.11.1-18.el7_0.i686.rpm 5414fe17e10dc2032fb7dd007f983acdee938c21c9352351e9c8a1529e990275 rpm-build-libs-4.11.1-18.el7_0.x86_64.rpm e9e3de0f85d9f06931ea379c9c0b9da041468986f4c6e96029c8ae918ab44db5 rpm-cron-4.11.1-18.el7_0.noarch.rpm e8f8a8be3445672da00e8c2a687b902981c6ea453bc3e87b6d0e83b9a93b6b94 rpm-devel-4.11.1-18.el7_0.i686.rpm 5e9ad78b8bbb20470671e3575657468c7db209156600b5502d06e3055e9a9808 rpm-devel-4.11.1-18.el7_0.x86_64.rpm b1cad417e97633e8989ffbc62512f9b51323d3adfe3f87455dd40df0cfc43ffd rpm-libs-4.11.1-18.el7_0.i686.rpm 44fe1c44040cd329c58ae73a02c778715f8bf1528bfc7fd6a18eac2c0bc0dfd2 rpm-libs-4.11.1-18.el7_0.x86_64.rpm 16fd2ef83d8b529c171275273dfb52a68605557ad8aad56e6f56ca2481bfd0d6 rpm-python-4.11.1-18.el7_0.x86_64.rpm 03ddda6f66ed8a65c43f2fddc6f3d9475d5891dd264cb6bff83a3707e953b36a rpm-sign-4.11.1-18.el7_0.x86_64.rpm Source: 7d5bbcb466c84459731a4830945d454ffbcf14b773fd318594d29e73fdde5052 rpm-4.11.1-18.el7_0.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Wed, 10 Dec 2014 18:01:42 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2014:1980 CentOS 7 systemd Enhancement Update Message-ID: <20141210180142.GA63031(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2014:1980 Upstream details at : https://rhn.redhat.com/errata/RHEA-2014-1980.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 76462e4363ce5797ab56121f8aa97d0d9f287a9aef553169acdac60335c4e18e libgudev1-208-11.el7_0.5.i686.rpm 58fbf71029f394dd4c479a485dbb6ae58dd53fb136c2f9f3f56a4b4ad7a5a037 libgudev1-208-11.el7_0.5.x86_64.rpm 72647abaf90ccfa43876fd0658274cb192321309ddffcfabf62e776c2eaf1b81 libgudev1-devel-208-11.el7_0.5.i686.rpm bb619bc91212161f1023c7d3a19f3621da0deb90ea9c423133e6808ac8081796 libgudev1-devel-208-11.el7_0.5.x86_64.rpm f92c934c7e33eecfa6d61e381c802b545bae7e4a7aea8c22c9620db36b60ce8c systemd-208-11.el7_0.5.x86_64.rpm 71c683a6e25be078a289a869ef19c99e4b551e227b7b235086e698a2c4634f65 systemd-devel-208-11.el7_0.5.i686.rpm ad81732daae202d6c2a8402b1cdafba71cabd3c32e07b929311be51f297d3670 systemd-devel-208-11.el7_0.5.x86_64.rpm 5340d9172ef47c5aa50da21e14a99a6e137c5e2bb46df50a820730838aea42a7 systemd-journal-gateway-208-11.el7_0.5.x86_64.rpm 21af9be039d62b5a5ff704091fe781af1c0a3cb385fc76114f3d82d37cc30027 systemd-libs-208-11.el7_0.5.i686.rpm 51b8848464514511f760b53df315ce47b16acc22dddd90893fbe16c603337dca systemd-libs-208-11.el7_0.5.x86_64.rpm c846665baf2c8db0ee7430e0cfef1a9b9bbe31bfe346e13ec6d2cfb0f11ae742 systemd-python-208-11.el7_0.5.x86_64.rpm 5c3772a7328bb90083d232a38daaa664ccba48dca13ceb0d8af6e8e3fa110401 systemd-sysv-208-11.el7_0.5.x86_64.rpm Source: 95d1c9bd799953ed083add14f9fec9acd3e2be2136457d8707278ff23afba2f2 systemd-208-11.el7_0.5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 118, Issue 7 ***********************************************

1 0

get /full/path/filename.ext from filename.ext
by ken 11 Dec '14

11 Dec '14

This should be simple, but it's not, unless I'm forgetting something. Writing a script, an arg is a filename. So fname=$1 But I want that expanded to include the full path and filename, not just what is given as the arg on the command line. E.g., if the user's cwd is /home/joe/a/b/c/ and he specifies ../x/file-a.ext then the function/utility should transform that into the absolute path with filename: /home/joe/a/b/x/file-a.ext In the simplest scenario, the answer would be $PWD/file-a.ext, but that would by no means cover a portion of the possible scenarios. You'd think this functionality would be included already in one or another linux utility. It's kinda like the complement to the 'basename' utility. I've looked into the dark corners of ls, stat, file, bash, type, find, and a few other linux standards, but nothing seems to do this. Any gurus out there know the utility which does this?

4 5

print something on console after boot
by Florin Andrei 10 Dec '14

10 Dec '14

CentOS 7 How do I print something on the text-mode console right after the OS has finished booting? I've a virtual instance and I need to know its IP address after it has finished booting up, to know where to ssh into it. I've tried adding "ip -4 addr > /dev/tty0" to rc.local, but that obviously doesn't work, because the login prompt overwrites everything I do. -- Florin Andrei http://florin.myip.org/

5 4

No package group "X Window System" in CentOS 7.0?
by Niki Kovacs 10 Dec '14

10 Dec '14

Hi, I'm currently experimenting with CentOS 7.0 in a few virtual guests, trying to install a reduced GNOME desktop as well as a minimal KDE desktop. I'm following this documentation: http://www.dokuwiki.tachtler.net/doku.php?id=tachtler:centos_7_-_minimal_de… I'm stuck at this point: # yum groupinstall "X Window System" Now I remember this from CentOS 5.x, when I began desktop installations with a minimal base system, then I added X11, configured it (using the minimal TWM), then added GNOME, then applications as needed. Now there seems to be no more "X Window System" group. At least 'yum grouplist' knows nothing about it. Any suggestions? Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

1 0

Re: [CentOS] CentOS-6.6 - Selinux and Postfix-2.11.1
by James B. Byrne 10 Dec '14

10 Dec '14

On Tue, December 9, 2014 18:45, Alexander Dalloz wrote: > Am 09.12.2014 um 23:04 schrieb James B. Byrne: >> Applied policy update. Now I see these occasionally. But by the time I try >> and >> see what the matter is the file is gone: > > Why do you start a new thread instead of continuing the old one about > the very same topic? > If you have a way to thread digest messages then I am open to suggestions. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

NSS update issues.
by Lamar Owen 10 Dec '14

10 Dec '14

Ran into a bit of a sticky wicket today. And for reasons that should be obvious it was a bit difficult to google for a solution, so I backed out the upgrade. So I'm hoping someone here has seen and fixed this already. System: CentOS 7, fully updated. After the nss updates in the past day or so, visiting https://www.google.com with Firefox results in the following error screen: Secure Connection Failed An error occurred during a connection to www.google.com. The server rejected the handshake because the client downgraded to a lower TLS version than the server supports. (Error code: ssl_error_inappropriate_fallback_alert) The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site. Ok, so how do I fix this (other than 'yum downgrade nss firefox nss-sysinit nss-devel nss-tools' which does 'fix' the issue)?

4 4

CentOS 7 install software Raid on large drives error
by Jeff Boyce 10 Dec '14

10 Dec '14

Greetings - I am trying to install CentOS 7 into a new Dell Precision 3610. I have two 3 TB drives that I want to setup in software RAID1. I followed the guide here for my install as it looked fairly detailed and complete (http://www.ictdude.com/howto/install-centos-7-software-raid-lvm/) I only changed the size of the partitions from what is described, but ended up with the disk configuration error that won't allow the installation to complete. The error is: You have not created a bootloader stage 1 target device. You have not created a bootable partition. So I am clearly missing a step in setting up the drives; likely before running the installer. My disks are blank raw disks right now with nothing on them. Reading the RHEL Storage Admin Guide (Sec. 18.6, Raid Support in the Installer) this should be supported, but I am assuming I may need to do something different because the drives are greater than 2 TB. I have a SystemRescueCD that I can use GParted to do some setup in advance of the installer, but am not sure of what exactly I need to do. My objective is to RAID1 the two drives, use LVM on top of the RAID, install CentOS7 as a KVM host system, with two KVM guests (Linux Mint and Windows 7). Can anyone tell me the steps I am missing, or point me to a better tutorial than what I have found in my extensive Google searches. Thanks. Please cc me directly on replies as I am only subscribed to the daily digest. Thanks. Jeff Boyce www.meridianenv.com

3 2

← Newer
1
...
8
9
10
11
12
13
14
...
17
Older →

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 December 2014