Discuss

discuss@lists.centos.org

2 participants
34758 discussions

mediacheck on kickstart
by Jerry Geis 21 Apr '15

21 Apr '15

I am using a kickstart centos 1503 file. For some reason I am getting a mediacheck even though I do not have mediacheck in my kickstart file. Any ideas why? Something change on that? Jerry

1 0

Laptop for CentOS
by Steve Clark 20 Apr '15

20 Apr '15

Hello, Has anyone used the Dell M3800 (ubuntu) laptop to run CentOS 6.x? If so how did it work out? Also does anyone have a fairly new laptop they are running CentOS 6.x on, that they are happy about? I am in the market for a new laptop and it must run CentOS 6.x. Thanks, -- Stephen Clark

10 15

CentOS6.6 installation failure
by lhecking＠users.sourceforge.net 20 Apr '15

20 Apr '15

I have been installing CentOS for years using PXE, kickstart and NFS, but the procedure fails with CentOS 6.6 for some reason. A PXE-initiated, manual install goes through all the setup steps, and once rpm installation has started, it dies after a few packages: anaconda 13.21.229 exception report Traceback (most recent call first): File "/usr/lib/anaconda/yuminstall.py", line 1006, in _handleFailure os.unlink(package.localPkg()) File "/usr/lib/anaconda/yuminstall.py", line 196, in callback self.ayum._handleFailure(po, trynumber) OSError: [Errno 30] Read-only file system: '/mnt/source/Packages/mailcap-2.1.31-2.el6.noarch.rpm' When a kickstart file is used instead, the installation dies at a different package. I have tried providing the OS installation files from different machines, checked package integrity etc., but cannot figure out what is happening here. The anaconda traceback file also has 12:19:59,354 WARNING : Failed to get file:///mnt/source/Packages/mailcap-2.1.31- 2.el6.noarch.rpm from mirror 1/1, or downloaded file is corrupt 12:19:59,354 WARNING : package download failure, retrying automatically That said, installing 6.4 off the same NFS server works just fine.

2 3

bash script fails conditional test
by Tim Dunphy 20 Apr '15

20 Apr '15

Hey all, I wrote a very basic script to determine if cassandra db is running. I'm setting a variable called 'pid' to the output of a ps | grep like to grab the pid of the cassandra process. #!/bin/bash pid=$(ps -ef | grep cassandra | grep -v grep | grep -i -v -e grep -e screen -e s3fs|awk '{print $2}') if [[ -e $pid ]] then echo "Cassandra is running with pid: $pid" else echo "Cassandra is DOWN!!!" fi But for some reason the script doesn't realize that the pid variable has been set, and fails the condition. It then reports that Cassnadra is DOWN!!!". [root@web1:~] #sh -x ./bin/check-cass.sh ++ ps -ef ++ grep -v grep ++ grep -i -v -e grep -e screen -e s3fs ++ awk '{print $2}' ++ grep cassandra + pid=26979 + [[ -e 26979 ]] + echo 'Cassandra is DOWN!!!' Cassandra is DOWN!!! Can anybody tell me where I'm going wrong here? Because from what I can see, clearly the pid variable is being set so the script should be reporting that cassandra is up! I'd appreciate any advice you may have. Thanks, Tim -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

5 11

Preferred partition type for raid 5
by Mark LaPierre 20 Apr '15

20 Apr '15

Hey All, I my research I came across a note that a specific partition type was preferable when creating a raid 5 array. I installed my HDs and used mdadm to assemble them into a raid 5 array. I then partitioned the array using gdisk. The default partition type is "8300 Linux filesystem" for the two partitions that I created. The article I read said that a specific partition type was preferred to avoid issues if the array was to be moved to another machine. Now I can't find where I read that. What is the preferred partition type that I should use for my partitions? -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

2 2

Re: [CentOS] ClamAV reports a trojan
by James B. Byrne 19 Apr '15

19 Apr '15

On Sat, April 18, 2015 11:16, Jake Shipton wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 16/04/15 16:01, James B. Byrne wrote: >> This morning I discovered this in my clamav report from one of our >> imap servers: >> >> /usr/share/nmap/scripts/irc-unrealircd-backdoor.nse: >> Unix.Trojan.MSShellcode-21 FOUND >> >> >> I have looked at this script and it appears to be part of the nmap >> distribution. It actually tests for irc backdoors. IRC is not >> used here and its ports are blocked by default both at the gateway >> and on all internal hosts. >> >> However, I none-the-less copied that file, removed namp, >> re-installed nmap from base, and diffed the file of the same name >> installed with nmap against the copy. They are identical. >> >> The question is: Do I have a problem here or a false positive? >> >> I am not sure why nmap is on that host but evidently I had some >> reason last October to use it from that server. In any case I am >> going to remove it for good, or at least until the reason I had it >> there reoccurs or is recalled to mind. >> > > Hi, > > I believe this is definitely a false positive. > > Our mail server (CentOS 6.6) is reporting the very same "Trojan" on > the very same file. I've already done our investigation and came to > the conclusion it is a false positive based on a verification of files > from RPMDB and also our intrusion detection system has not detected > any changed files in /usr/share/ since before and after said "trojan" > appeared. > > Top that with two people seeing the same thing at the same time in two > completely different machines/companies chances are high its a false > positive. > > Hope this helps set your mind at ease :-). > > Kind Regards, > Jake Shipton (JakeMS) > Twitter: @CrazyLinuxNerd > GPG Key: 0xE3C31D8F > GPG Fingerprint: 7515 CC63 19BD 06F9 400A DE8A 1D0B A5CF E3C3 1D8F > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > > iQEcBAEBAgAGBQJVMnVaAAoJEB0Lpc/jwx2P7s4H/2V++W499w2fAZPM8kjnKi9b > EBS0vl/oYAOVgzc3lo4y0CbY9GQtQ3258tISCeMGGOR/OjPYl3BqINsS1Qf0FGSw > FzNHWrlgas/bZO/HbTAzWbtxknRKIJiiYfBHqLL6s/r9WpOMsBvA2eVpkXsEZZoz > AWC0CFcrVsh7+Agqk46GyIsDn8ZpT+IymwMp+gKiqBv8e4uG5WjE8YRGBybscJgk > DAPZ9ZaSJpJNFkJ0tpAAgNkPO96lFv6l43nnm/IyTfKtd/1rWJ9ejb0ZjtZnP6Dr > xWdNyTjK39euHiVBP3pZ6ex8VKthph6b9FeferoQaGFxGvixk7epIihPbeEYqbg= > =lowP > -----END PGP SIGNATURE----- > > Thank you. We run aide on that box and it did not report any recent changes to that file. RPM and yum history corroborated the install date as being last October. We have concluded this is a false positive following a recent ClamAV update. We have none-the-less removed nmap from that host. -- *** 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

Re: [CentOS] yum install failiure - CentOS-7 - Base
by Richard 19 Apr '15

19 Apr '15

------------ Original Message ------------ > Date: Sunday, April 19, 2015 18:44:43 +0000 > From: Sarogahtyp <sarogahtyp(a)web.de> > To: centos(a)centos.org > Subject: [CentOS] yum install failiure - CentOS-7 - Base > > I have a running CentOS 6.5 64-bit system running and i like to > have a CentOS 7 chrooted system inside. > Ive done that chroot environment as described in > http://www.jefftk.com/p/32-bit-chroot-on-centos > > Now my problem ist that yum is not working as i suggested: > > bash-4.2# yum install sudo > Geladene Plugins: fastestmirror > http://mirror.centos.org/centos/7/os/i386/repodata/repomd.xml: > [Errno 14] HTTP Error 404 - Not Found > Anderer Spiegelserver wird versucht. > Yum is working fine, and gave the correct response "HTTP Error 404 - Not Found". If you look with a browser you'll see that there's no i386 directory under .../7/os/. I haven't been following this closely, but I don't believe that there was an RH 32-bit release of 7. A Centos group was looking into building one, but I'm not certain of its status.

2 2

yum install failiure - CentOS-7 - Base
by Sarogahtyp 19 Apr '15

19 Apr '15

I have a running CentOS 6.5 64-bit system running and i like to have a CentOS 7 chrooted system inside. Ive done that chroot environment as described in http://www.jefftk.com/p/32-bit-chroot-on-centos Now my problem ist that yum is not working as i suggested: bash-4.2# yum install sudo Geladene Plugins: fastestmirror http://mirror.centos.org/centos/7/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found Anderer Spiegelserver wird versucht. One of the configured repositories failed (CentOS-7 - Base), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Disable the repository, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable base 4. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=base.skip_if_unavailable=true failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. http://mirror.centos.org/centos/7/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found bash-4.2# any ideas ?

1 0

Custom named logwatch script
by Todor Petkov 19 Apr '15

19 Apr '15

Hello, I am using multiple files for logging activities for named daemon. The files are in /var/named/chroot/var/log/named/, for example /var/named/chroot/var/log/named/general.log. I am trying to make logwatch look into them. I have created /usr/share/logwatch/default.conf/logfiles/named.conf like this: LogFile = /var/named/chroot/var/log/named/general.log *ExpandRepeats *OnlyHost *ApplyStdDate Then I have changed /usr/share/logwatch/default.conf/services/named.conf like this: Title = "Named" LogFile = named $named_ip_lookup = No *RemoveHeaders When I run "logwatch --detail High --debug High --print --range All", I can see the log file is proceeded, but I don't see any reports. Can anyone point me to where my mistake is? Regards,

3 3

NFS4 automount and IPA (sssd) ?
by Günther J. Niederwimmer 19 Apr '15

19 Apr '15

hello, CentOS 7.1 IPA 4.1 sssd 1.2 om my system it is not possible to automount with a IPA config,, when I mount this on a command line it is working I have this Error in the logs automount[1718]: lookup_read_map: lookup(sss): getautomntent_r: No such file or directory. Is this from a broken sssd? have any a working configuration? The mount points are created but inside the mount points I have no files and Directories. thanks for a answer -- mit freundlichen Grüßen / best regards, Günther J. Niederwimmer

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss