Discuss December 2011

discuss@lists.centos.org

207 participants
175 discussions

vsftpd log issues
by Timo Neuvonen 04 Jan '12

04 Jan '12

I have an up-to-date CentOS 6 with reasonable amount of ftp activity (a dozen of network cameras uploading images every second 24x7). The first issue was that the whole /var filesystem was about to get full, because of huge ftp daemon log. vsftpd.conf says: # You may override where the log file goes if you like. The default is shown # below. xferlog_file=/var/log/vsftpd.log Ok, the above works now. But while the setting was (by default) commented out, the default wasn't /var/log/vsftpd.log but /var/log/xferlog which was growing without limits (it was over 6 GB when I first time noticed the problem) since logrotate tried to rotate vsftpd.log -rw------- 1 root root 0 Dec 31 03:07 vsftpd.log -rw------- 1 root root 39134459 Dec 31 12:19 vsftpd.log.1 -rw------- 1 root root 433305200 Dec 30 22:03 xferlog Now, after uncommenting the log file setting line in the conf the next issue is, that logrotate does rotate the log files (the old one gets .1 postfix added to its name and a new file is created), but it still keeps writing to the original file (which is renamed now) In the ls -l listing above: - vsftpd started to write log vsftpd.log around 10pm last night (when I uncommented the log setting from the conf and restarted the daemon, until that it was logging to xferlog) - during the night logrotate has changed the name of the existing log file to ...log.1 but now, several hours later, this renamed old file is still used for logging, and the new ...log file remains empty! Is there some simple option in logrotate's conf that could change this behaviour? Or how to fix this. There must be many others who already have run into this issue. Regards, Timo

3 2

what percent of time are there unpatched exploits against default config?
by Bennett Haselton 02 Jan '12

02 Jan '12

Suppose I have a CentOS 5.7 machine running the default Apache with no extra modules enabled, and with the "yum-updatesd" service running to pull down and install updates as soon as they become available from the repository. (Assume further the password is strong, etc.) On the other hand, suppose that as the admin, I'm not subscribed to any security alert mailing lists which send out announcements like "Please disable this feature as a workaround until this hole is plugged", so the machine just hums along with all of its default settings. So the machine can still be broken into, if there is an unpatched exploit released in the wild, in the window of time before a patch is released for that update. On the other hand, at any point in time where there are no unpatched exploits in the wild, the machine should be much harder to break into. Roughly what percent of the time is there such an unpatched exploit in the wild, so that the machine can be hacked by someone keeping up with the exploits? 5%? 50%? 95%? Hopefully this is specific enough that the answer is not "it depends" :) , an actual numeric answer should exist -- although I don't know if anyone has ever tried to work it out. But if not, then what's a good guess, based on observing how frequently root exploits are released in the wild, and how long the patches usually take. Bennett

28 97

Checkinstall rpm for CentOS-6 x86_64?
by James B. Byrne 01 Jan '12

01 Jan '12

I cannot seem to find a checkinstall rpm package for CentOS-6 or one for x86_64 more recent than CentOS4. When I try to build it locally from the most recent source I can find, c.2006, I get build errors having to do with size constants either missing or improperly defined. Does anyone have a source for an rpm of this package that runs on CentOS-6_x86_64 or can recommend a replacement for it? -- *** 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

5 5

CentOS 6 x86_64 can't detect raid 10
by David 31 Dec '11

31 Dec '11

Dear All, I just got a new server with the following specifications: motherboard : Intel S5500BC CPU : Xeon Quad Core 2.6Ghz RAM : 8GB HDD : 4 x 2TB SATA with configured raid 10 using raid embedded server. The problem is the centos installer can't detect raid virtual disk. I can't find any log error with the following error messages during installation process: Disks sda, sdb, sdc, sdd contain BIOS RAID metadata but are not part of any recognized BIOS RAID sets. I'm already use search engine to find the information regarding to this issue, but I can't find the solutions for CentOS. Thanks in advance -- -- Best regards, David ------------------------ http://blog.pnyet.web.id

3 2

CentOS 6 x86_64 can't detect raid 10
by David 31 Dec '11

31 Dec '11

3 2

RHEV guest tools
by Johan Kooijman 29 Dec '11

29 Dec '11

Hi all, We're running RHEV as our main virtualization platform. Most of our guests are CentOS though. Do you guys know if there's a guest tools package for CentOS available like there is for Windows for example? Can't really find an answer here. -- Met vriendelijke groeten / With kind regards, Johan Kooijman T +31(0) 6 43 44 45 27 F +31(0) 162 82 00 01 E mail(a)johankooijman.com

6 11

Refresh all packages?
by Weplica 29 Dec '11

29 Dec '11

Hello, I have dedicated server on CentOS Linux 6.1 with webmin/virtualmin and it tell me: Package updates 145 updates to system packages are available. Use the Virtualmin Package Updates module to install them selectively. 4 updates to Virtualmin packages are available. Use the Virtualmin Package Updates module to install them selectively. Should I update all packages?

3 2

why not have yum-updatesd running by default?
by Bennett Haselton 29 Dec '11

29 Dec '11

Ever since someone told me that one of my servers might have been hacked (not the most recent instance) because I wasn't applying updates as soon as they became available, I've been logging in and running "yum update" religiously once a week until I found out how to set the yum-updatesd service to do the equivalent automatically (once per hour, I think). Since then, I've leased dedicated servers from several different companies, and on all of them, I had to set up yum-updatesd to run and check for updates -- by default it was off. Why isn't it on by default? Or is it being considered to make it the default in the future? Power users can always change it if they want; the question is what would be better for the vast majority of users who don't change defaults. In that case it would seem better to have updates on, so that they'll get patched if an exploit is released but a patch is available. If the risk is that a buggy update might crash the machine, then that has to be weighed against the possibility of *not* getting updates, and getting hacked as a result -- usually the latter being worse. After all, if users are exhorted to log in to their machines and check for updates and apply them, that implies that the risk of getting hosed by a buggy update is outweighed by the risk of getting hacked by not applying updates. If that's true for updates that are applied manually, it ought to be true for updates that are downloaded and applied automatically, shouldn't it? Bennett

7 9

NFS options in fstab
by Daniel Bird 29 Dec '11

29 Dec '11

Hi All, I've a quick question I'm hoping someone can help out on; One of our NFS servers has an intermittent hard lock problem under high load. This is a CentOS 5.7 box. It's due for replacement sometime next year. However... The issue is when this box dies the boxes that mount the NFS exports have trouble with the mount and some processes time out casing the system mounting the file system to become unresponsive also. Of course un-monuting the file system with -l fixes it. This is an example of our current mount options in fstab hostname:/share1/ /mountpoint nfs rw,intr,soft,bg 0 0 The question is, what (other) options should we be using to allow the mounting server to ignore/fail/timeout the mount, or at least continue normal processing, when the NFS server packs up? FYI we can't move to NFS4 since we've some old boxes running Solaris 8 mounting this filesystem also, which cannot be upgraded Solaris 10 to support v4. All the best Dan

2 3

asus-wmi.ko for Asus G73Sw running CentOS 6.2
by Rob Kampen 29 Dec '11

29 Dec '11

Hi List, Just loaded our favorite OS onto my new ASUS laptop. Practically everything worked out of the box - I used the live DVD to check things out and installed from there. I have followed http://forum.notebookreview.com/asus-gaming-notebook-forum/553474-g73-asus-… to get suspend working and also to get function keys working for LCD screen backlight controls working (Fn F5 and Fn F6). Upon further searches I find that there is a kernel module asus-wmi.ko available in some distros that also allows some of the other Asus functions to operate - of particular interest is the keyboard backlight (Fn F3 and Fn F4) as well as the master backlight on/off key to function. Question, does anyone know where and how to locate this (asus-wmi.ko) and get it functioning under CentOS 6.2? I am prepared to set up the required build environment - but need some assistance as this is really at the limits of my experience. I have rebuilt the kernel to remove patches with some success previously and will have to dust off this knowledge if required. TIA

3 2

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 2011