Discuss March 2013

discuss@lists.centos.org

206 participants
228 discussions

Start a nNew thread

Installing VNCSERVER on Linux machine
by Norah Jones 13 Mar '13

13 Mar '13

How can I install vncserver on my linux machine so that I can connect from windows client.

4 3

CentOS-announce Digest, Vol 97, Issue 7
by centos-announce-request＠centos.org 13 Mar '13

13 Mar '13

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-2013:0640 Important CentOS 5 tomcat5 Update (Johnny Hughes) 2. CESA-2013:0630 Important CentOS 6 kernel Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 12 Mar 2013 19:14:34 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2013:0640 Important CentOS 5 tomcat5 Update To: centos-announce(a)centos.org Message-ID: <20130312191434.GA5581(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2013:0640 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0640.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: a99d538d8d34954e4599dba669aed2eedb87cedbdec498f94cdfe45d1880dbc9 tomcat5-5.5.23-0jpp.38.el5_9.i386.rpm 728956e52beb891e0e1e362898ae18e2aeef4af5f62bb11939562f9b12dc3f90 tomcat5-admin-webapps-5.5.23-0jpp.38.el5_9.i386.rpm 303905aa312b267877028f5fa41cd695eeb494316c86231bc82c9820bdab5663 tomcat5-common-lib-5.5.23-0jpp.38.el5_9.i386.rpm a0eeb13bb5b1ac435d0eae454ab2eec60d02ec0e379f0875843144f017427dd4 tomcat5-jasper-5.5.23-0jpp.38.el5_9.i386.rpm 529f7c5db10f7c3872054edbd98f5f6ac354de1b195e88fc746430e085fca376 tomcat5-jasper-javadoc-5.5.23-0jpp.38.el5_9.i386.rpm d5373805e3d61f4e80f5b989b5859f8e516b95e2da52c45b07f35defc6cbe1a9 tomcat5-jsp-2.0-api-5.5.23-0jpp.38.el5_9.i386.rpm 15aadf6a094a8787fe78116d15c0c1710c7bc166b90dc2513d7cc00c7755ec2c tomcat5-jsp-2.0-api-javadoc-5.5.23-0jpp.38.el5_9.i386.rpm b35ee32376cac25d1b2788097ef36b91b11c0247e5a3c9f1fd1ce49a4625e7fe tomcat5-server-lib-5.5.23-0jpp.38.el5_9.i386.rpm 2f0d6a12d965b714049e20cb9fd1da72b1c68b2eb6f2f45e87a43b41947ec824 tomcat5-servlet-2.4-api-5.5.23-0jpp.38.el5_9.i386.rpm bdf2ac0a25a1a821e5bee5150a437fea164b273afedecf1097060a4a8f0acd3d tomcat5-servlet-2.4-api-javadoc-5.5.23-0jpp.38.el5_9.i386.rpm 872e80c3f2abbe5b28087a6dbc1f1d29a5b20f9087b8e08c79b726f5da9f2dbe tomcat5-webapps-5.5.23-0jpp.38.el5_9.i386.rpm x86_64: 1d172b21e13f0da40d4eb271e45c97811f12809f6e0d5e399a0b4c75de987cd0 tomcat5-5.5.23-0jpp.38.el5_9.x86_64.rpm d169c3589902ef9183c685ebd06aba3f68d666a7083657da0e7eba9444150222 tomcat5-admin-webapps-5.5.23-0jpp.38.el5_9.x86_64.rpm 12254bc0b9f78f5b68e216e1f6b61047fef7fd8704461f95ddc2e0222b5b7037 tomcat5-common-lib-5.5.23-0jpp.38.el5_9.x86_64.rpm f6ba0d06219a5a7a6910fb95e62459e60e2eb887967005e7e2e813c1d770fc8b tomcat5-jasper-5.5.23-0jpp.38.el5_9.x86_64.rpm 9f312fa384b099ef42d38888f51382538a7fe1d576b0deb906144c29f05536b5 tomcat5-jasper-javadoc-5.5.23-0jpp.38.el5_9.x86_64.rpm fac46bbd9ca41eb774f972681a8a546d24f2be62abf335bdf695522bdc0f8eb5 tomcat5-jsp-2.0-api-5.5.23-0jpp.38.el5_9.x86_64.rpm 6be6bb3317ec3f48762c747b0a3a453fd5b2bfb4fc3d1082248407ca25c59382 tomcat5-jsp-2.0-api-javadoc-5.5.23-0jpp.38.el5_9.x86_64.rpm 2581603cde634301a37ec92727f54735483ba312dbe910f46ccc02f4312671f4 tomcat5-server-lib-5.5.23-0jpp.38.el5_9.x86_64.rpm f922f17317fb14a790dab41c8520f10257395193b800be5d338b6ce6cdbd4495 tomcat5-servlet-2.4-api-5.5.23-0jpp.38.el5_9.x86_64.rpm 30c1883994f90fad35b190fcb77004882c259c547818871902f61f78e933980d tomcat5-servlet-2.4-api-javadoc-5.5.23-0jpp.38.el5_9.x86_64.rpm 45c9fe4028aafb2b8f3c098c933193c1948344a39ea27eed4e3f2548b46e387f tomcat5-webapps-5.5.23-0jpp.38.el5_9.x86_64.rpm Source: f9ed2f48e9a7ffa7a1bf00802562d4e12f995071910ab5a7cf8dcf3887cf5d6f tomcat5-5.5.23-0jpp.38.el5_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Wed, 13 Mar 2013 11:49:36 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2013:0630 Important CentOS 6 kernel Update To: centos-announce(a)centos.org Message-ID: <20130313114936.GA22026(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2013:0630 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0630.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 3e5061fc581c4254587fd3ae85787df1cae3b1917d0fc0eae93fc24dc13b8981 kernel-2.6.32-358.2.1.el6.i686.rpm 6e6028ada0b77285cd641bc98e5b1bf4aefcf0368353c6d94dbe105070bd9bb6 kernel-debug-2.6.32-358.2.1.el6.i686.rpm 9cc3ea93cdbd66bf5e4deb45174b235d974893780b285841b8c005ef53ef9339 kernel-debug-devel-2.6.32-358.2.1.el6.i686.rpm 330b05baeb0bcfa6cbbded4ba78625fd7facd75ffc4fc7e8cad5495d9ce39902 kernel-devel-2.6.32-358.2.1.el6.i686.rpm 9957a709567b938e8749d6a1d7f561bd86ce08368d0fe2c07aef8e4c63ff5ee9 kernel-doc-2.6.32-358.2.1.el6.noarch.rpm bf3302507e788e28b3d30ff489f851855243d45e3881c8918aec745ee2f85e84 kernel-firmware-2.6.32-358.2.1.el6.noarch.rpm bd96328fd726c5960fb29255daa9f96d3e6acffe607a42c576a26537464b6997 kernel-headers-2.6.32-358.2.1.el6.i686.rpm 8de21b883f68ce2021fffb62b7a1ea1241d4ff0054be05c40202cb1d65e6dba2 perf-2.6.32-358.2.1.el6.i686.rpm a3d13198337ccc5af802783a02b5ae7f6d8dea182ac11b1bec66d50a1257ce80 python-perf-2.6.32-358.2.1.el6.i686.rpm x86_64: eec54b853e8993a252760a6ea9f2af09d15d592e786a4094558c8c859c967f16 kernel-2.6.32-358.2.1.el6.x86_64.rpm 828145f2f4191a2c3621646127be394c7f721f61cf645131f9a37b3f8178ac12 kernel-debug-2.6.32-358.2.1.el6.x86_64.rpm dcf53aea8fcbcdfd28bbe219898cc88cf0af494d1845f81d40b08ce1d30bf370 kernel-debug-devel-2.6.32-358.2.1.el6.x86_64.rpm 7d83d8c1af42c304b54e6fe456aa3741ffff1299ddb1fcb8be37c83858c51e88 kernel-devel-2.6.32-358.2.1.el6.x86_64.rpm 9957a709567b938e8749d6a1d7f561bd86ce08368d0fe2c07aef8e4c63ff5ee9 kernel-doc-2.6.32-358.2.1.el6.noarch.rpm bf3302507e788e28b3d30ff489f851855243d45e3881c8918aec745ee2f85e84 kernel-firmware-2.6.32-358.2.1.el6.noarch.rpm 2f5411c1ad0396b4774cfb650b94f87e362728e6e334301c2065191ba19826b7 kernel-headers-2.6.32-358.2.1.el6.x86_64.rpm 02ff187053c2769a136125c81a00c6e15cdc800112118476449562aa8da2406e perf-2.6.32-358.2.1.el6.x86_64.rpm 7fe6b45a6a6abc2bed7dfae5d7fad98426bf6842fd5b03ed363b0598046f27f0 python-perf-2.6.32-358.2.1.el6.x86_64.rpm Source: 2fe98c1bcac7c5998e338cdaf46bbe732615aea52192f8df64552f75345b87e8 kernel-2.6.32-358.2.1.el6.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 97, Issue 7 **********************************************

1 0

Postfix setup
by Austin Einter 13 Mar '13

13 Mar '13

Dear All I am planning to setup mail server for my domain. Which one is preferred postfix or sendmail. I came across a link * http://ostechnix.wordpress.com/2013/02/08/setup-mail-server-using-postfixdo… * for postfix mail setup. It says, Prerequisites: - The mail server should contain a valid MX record in the DNS server. Navigate to this link how to setup DNS server<http://ostechnix.wordpress.com/2013/01/25/setup-dns-server-step-by-step-in-…> . - Firewall and SELinux should be disabled. I have disabled iptables as my m/c is behind the firewall. It says I need to disable firewall. Is it really required. Kindly let me know. Best Regards Austin

6 16

what is "single spanned virtual disk" on RAID10????
by mcclnx mcc 13 Mar '13

13 Mar '13

We have DELL R910 with H800 adapter in it. several MD1220 connect to H800. Since MD1220 have 24 hard disks in it. When I configured RAID10, there is a choice call 'single spanned virtual disk" (22 disks). Can anyone tell me how "single spanned virtual disk" work? Any document relate to it? Thanks.

2 2

Re: [CentOS] CentOS 6.3 - fail2ban not working properly + workaround
by Fabien Archambault 12 Mar '13

12 Mar '13

2013/3/12 Theo Band <theo.band(a)greenpeak.com>: > On 03/12/2013 05:35 PM, Timothy Murphy wrote: >> I'm running fail2ban on my server (under CentOS-6.4) >> and it seems to be running according to >> ------------------------- >> [tim@grover fail2ban]$ sudo service fail2ban status >> Fail2ban (pid 31794) is running... >> Status >> |- Number of jail: 1 >> `- Jail list: ssh-iptables >> ------------------------- >> I have absolutely no idea how fail2ban works, >> and I'm running it with the default /etc/fail2ban/fail2ban.conf , >> which seems to set the logfile to /var/log/fail2ban.log . >> Should I actually study how it is meant to be configured? >> >> I just yum-installed it (from Epel, I assume) >> and hope it does its job, whatever that is. > It sets up iptables rules for every jail that is configured (iptables > -L). You seem to have only the ssh-iptables configured. Check the date > of the logfile. I noticed that SYSLOG is now used for logging. It used > to be /var/log/fail2ban.log in the past. I removed the old log file. > If ssh is the only public service you want to protect against brute > force, then you don't need to setup anything. But have a look in > /etc/fail2ban/jail.conf and add at least your email address to get a > notification when it blocks access. There lots of other "jails" that can > be enabled. > Normally I receive several messages a day. So not receiving them means > that the service is no longer protecting. Simply because it watches a > renamed no longer updated version of /var/log/secure: > > ls -l /var/log/secure* > -rw------- 1 root root 2130892 Mar 12 18:25 /var/log/secure > -rw------- 1 root root 1374710 Feb 17 01:31 /var/log/secure-20130217 > -rw------- 1 root root 1482646 Feb 24 03:09 /var/log/secure-20130224 > -rw------- 1 root root 1732930 Mar 3 03:13 /var/log/secure-20130303 > -rw------- 1 root root 656454 Mar 10 03:12 /var/log/secure-20130310 > > Once a week fail2ban stops working as a new secure log file is created > (logrotate) and it seems to watch the only old name. You will not see > any error message and status show as running. > But I have no proof that it keeps working with the gamin fix. > > Theo > I too have the same problem but couldn't figure where is the issue. It stops working even if the service says all is right. I have to restart the service to let it work again... I will try to find through your idea. Thanks, Fabien

3 2

CentOS 6.3 - fail2ban not working properly + workaround
by SilverTip257 12 Mar '13

12 Mar '13

I recall others on this list are using fail2ban to block brute force login attempts. Packages are from the EPEL repo, so I'm just sharing some knowledge here. For about two months now I've had a CentOS 6.3 box (web host) in production that occasionally is ftp brute forced. Oddly enough fail2ban wasn't nabbing the perpetrators. I found that the iptables chain for VSFTP isn't created for one. I have finally come to find [0] that indicates there's a problem with the inotify backend. Setting backend=gamin in /etc/fail2ban/jail.conf gives me the iptables chain I expect to find and one blocked host. Hope this is helpful to somebody until a new version is commited to EPEL. <quote> yarikoptic: ok -- that point was not yet good ;) now (0.8.6-95-gc0c1232) that branch seems to work just perfect. If I hear no complaints or do not see problem with my instance -- I will merge it into master tomorrow, thus closing this issue </quote> [0] https://github.com/fail2ban/fail2ban/issues/44 ---~~.~~--- Mike // SilverTip257 //

3 5

6.x - USB key
by m.roth＠5-cent.us 12 Mar '13

12 Mar '13

I just had to rebuild my USB key for a generic install (got to do that for a drive to send with the system back to the OEM for repair, y'know). This time, I used unetbootin, which took a while to build the key, and worked *almost* well. The two annoying hangups: it took a *long* time to extract the packages and put them all on the USB key, looking like a repo... EXCEPT that during the install, anaconda *demands* the .iso. I went back, deleted /mnt/usb/Packages, since it's only an 8G key, and just copied DVD 1 onto it. anaconda stopped, asked me where, I told it, and it happily went on its way. Then, it doesn't give you any kind of default grub.conf Oh, well. Drive's built and boots. mark

1 0

CentOs 6.4 and video drivers
by Yves Bellefeuille 12 Mar '13

12 Mar '13

The release notes for CentOS 6.4 state as follows: > With this release the ABI for the X.org video drivers changes, > possibly resulting in a failing X-Session. If you are running 3rd > party drivers - i.e. vBox addons, nVidia, ATI or ELRepo - you need to > ensure a compatible driver is loaded. I use flgrx from ELRepo. Does this mean that fglrx is now incompatible with CentOS? Yves Bellefeuille

6 12

strange sporadic sssd problem on centos
by Gelen James 12 Mar '13

12 Mar '13

>From time to time on centos 6 sssd I got login problems like 'connection closed by *.*.*.*.', after a while then I login in again and the problem already disappeared. For the ssh login problem, I can see the following entries in /var/log/secure. 'Failed public key for ....' is the entry for the login problem. Any one has some ideas why this happens? Mar 12 04:30:12 master01 sshd[25185]: Set /proc/self/oom_score_adj to 0 Mar 12 04:30:12 master01 sshd[25185]: Connection from 192.168.1.80 port 48718 Mar 12 04:30:18 master01 sshd[25185]: Found matching RSA key: 55:52:5e:6c:fe:74:ab:cd:ef:94:96:f4:f7:44:fb:fc Mar 12 04:30:18 master01 sshd[25186]: Postponed publickey for gotcha from 192.168.1.80 port 48718 ssh2 Mar 12 04:30:18 master01 sshd[25185]: Found matching RSA key: 55:52:5e:6c:fe:74:ab:cd:ef:94:96:f4:f7:44:fb:fc Mar 12 04:31:51 master01 sshd[25185]: Failed publickey for gotcha from 192.168.1.80 port 48718 ssh2 Mar 12 04:31:51 master01 sshd[25186]: fatal: Access denied for user gotcha by PAM account configuration Thanks. --Gelen

1 0

Solr 4.1 - how to check replication staistics using wget?
by Rafał Radecki 12 Mar '13

12 Mar '13

Hi All. I am currently migrating from solr 3.6 to solr 4.1. In 3.6 to check the status of solr master/slave replication I've been using url: http://${SOLRMASTER}:${SOLRPORT}/solr/admin/replication/index.jsp from script. After migration to 4.1 this url is no longer available. Can you tell which url can be used from script to check replication status? Best regards, Rafal.

1 0

← Newer
1
...
10
11
12
13
14
15
16
...
23
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 March 2013