Re: [CentOS] ffmpeg
I work with ffmpeg a lot. I recommend that you don't try to build the rpms which are constantly out of date. ffmpeg is a moving target so I recommend compiling it from git. It's relatively easy and you can find most of the dependencies in either epel or rpmforge (lame, xvid, faac etc...). There are a few dependencies that you need to also compile yourself but only if you think you need those features (amr encoding, x264 etc..) x264 is also notoriously out of date in any repo. You'll want to compile that yourself as well. Brandon On Thu, Aug 11, 2011 at 6:20 AM, Lamar Owen lo...@pari.edu wrote: On Wednesday, August 10, 2011 05:11:12 PM m.r...@5-cent.us wrote: This is annoying. I've been trying to get motion working correctly on CentOS 6. I installed faad2-libs. It *still* will not install, telling me the same: Error: Package: ffmpeg-libs-0.4.9-0.52.20080908.el5.x86_64 (rpmfusion-free-updates5-testing) Requires: libfaad.so.0()(64bit) Available: 1:faad2-libs-2.6.1-5.el5.x86_64 (rpmfusion-free-updates5-testing) If you're doing this on C6, why are you using C5 repositories? It doesn't look like rpmfusion for EL6 has ffmpeg yet; you might be able to rebuild the fedora 12/13/14 RPM on C6. RPMfusion still has ffmpeg for F13; you might be able to grab the F13 source RPM for ffmpeg and rebuild it on EL6. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ffmpeg
On Thu, Aug 11, 2011 at 10:05 AM, Brandon Ooi brand...@gmail.com wrote: I work with ffmpeg a lot. I recommend that you don't try to build the rpms which are constantly out of date. ffmpeg is a moving target so I recommend compiling it from git. It's relatively easy and you can find most of the dependencies in either epel or rpmforge (lame, xvid, faac etc...). There are a few dependencies that you need to also compile yourself but only if you think you need those features (amr encoding, x264 etc..) x264 is also notoriously out of date in any repo. You'll want to compile that yourself as well. Brandon Oops, apologies for top-posting. Brandon ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] since CentOS 5.6 upgrade, squid crashes
On Tue, May 10, 2011 at 1:09 AM, Christopher Chan christopher.c...@bradbury.edu.hk wrote: On Monday, May 09, 2011 10:28 PM, Ljubomir Ljubojevic wrote: Laurent CREPET wrote: On Mon, 9 May 2011 05:20:48 -0700 (PDT) John Doejd...@yahoo.com wrote: From: Laurent CREPETl...@megrapet.fr Today, squid crashed again. Maybe ask on the squid mailing list, they might have more insight... JD No need, I have plugged my brain today. Check my latest e-mail (squid does not like temporary filesystem full in /var/log/squid) ;-) No link with 5.6 upgrade at all. Maybe /var/cache/yum was not cleaned of downloaded rpms after upgrade to 5.6? so /var partition run out of space or helped with out of space issue just enough to put it over the top. Or maybe it was stuffed with squid reports... a whole week of troubleshooting and you didn't check /var/log/messages? comon man. When I visit servers to make changes, I almost always check /var/log/messages and dmesg for latent errors or other issues that I can proactively solve. This should be sysadmin 101 :P Brandon ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOs 5.6 and Time Sync
On Mon, Apr 25, 2011 at 12:47 PM, Denniston, Todd A CIV NAVSURFWARCENDIV Crane todd.dennis...@navy.mil wrote: -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Mailing List Sent: Monday, April 25, 2011 13:57 To: CentOS mailing list Subject: Re: [CentOS] CentOs 5.6 and Time Sync List, I was not able to resolve my issue with the time on this machine. I went ahead and rolled the update back to 5.5 and disabled the update to 5.6. What I would like to know is if CentOS 6 might be ok when it rolls out, or am I just going to have to keep with 5.5 till EOL? Thanks to all with there help. 1) I hope you are only talking about having rolled back to the last working for you kernel from 5.5, not the whole distribution. 2) If I was in your position and had time, my method would be[1] a) get the srpm for the last known working kernel (2.6.18-194.32 ???) b) get the srpm for the first known not working kernel (2.6.18-238 ???) c) expand each of the above srpms into their own rpm build tree i.e., rpmdev-setuptree;rpm -i kern1; mv rpmbuild rpmbuild.kern1; rpmdev-setuptree;rpm -i kern2; mv rpmbuild rpmbuild.kern2 d) start looking at the differences in the patches applied in kern1 vs. those in kern2, i.e., read/diff the kernel.spec files see if there were any new ones that seemed likely to be causing the problem... RTFS if necessary to make better guesses. Rebuild kernel 2 with patches taken out/modified based on my investigations and test them and see if I guessed right. If no luck, think about opening an TUV bug with lots of the info you have sent here, they may be interested even if you don't have a subscription. [1] Been there, done that: http://www.gossamer-threads.com/lists/drbd/users/9616 At first I figured this was misconfigured NTP but I actually see this happening on one of my machines as well. Nothing interesting about it in particular but I verified that rolling back to the previous kernel (2.6.18-194.32.1.el5) solves the problem entirely. This happens when NTP is enabled or disabled. I get the following error messages in dmesg which are possibly related. time.c: can't update CMOS clock from 59 to 0 time.c: can't update CMOS clock from 59 to 0 time.c: can't update CMOS clock from 59 to 0 time.c: can't update CMOS clock from 59 to 0 The time drift is significantly higher than would be expected as normal. Because rolling back the kernel completely solves this issue, this must be a bug. [root@nexus4 ~]# date; ntpdate -u pool.ntp.org Mon May 9 16:51:03 PDT 2011 9 May 16:50:21 ntpdate[22117]: step time server 207.182.243.123 offset -42.418572 sec [root@nexus4 ~]# date; ntpdate -u pool.ntp.org Mon May 9 16:50:33 PDT 2011 9 May 16:50:35 ntpdate[22127]: step time server 207.182.243.123 offset -0.692146 sec Brandon ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SSH using Keys, no password and SFTP?
On Sun, May 8, 2011 at 12:29 PM, Ljubomir Ljubojevic off...@plnet.rswrote: Jason wrote: So is it possible to require some users to use Password only and some to use Key only authentication? -Jason I am not sure. First auth ssh will try is key pair. if that does not work, it will ask for username and password. So if you leave password auth runnig and you use key pair, it will work. Take a look at ssh man page for the specifics. Ljubomir Clients like filezilla can use SFTP keys held by ssh-agent. Filezilla on windows can use the ssh-agent provided by putty. Try just putting no password, the client may just work (with ssh-agent running) Brandon ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] list of supported hardware
On Tue, May 3, 2011 at 2:30 AM, John R Pierce pie...@hogranch.com wrote: On 05/03/11 2:16 AM, Michael Schumacher wrote: Hello CentOS list, I have been looking for a list of hardware that is supported by the Centos kernel and its modules. I couldn't find anything in the documentation at Centos nor at RH. Google didn't bring up anything either. Is there any list or will I need to browse the source code directories? Just for clarification, I am not looking for certified hardware. I just want to see if a certain piece of hardware is supported. the certified list at redhat.com is all you're likely to find. Honestly your best bet is to identify the hardware that may have issues (newer ethernet, raid cards, hba's etc..). Figure out what chipset they use and google for it or look at RH release notes and kernel source to see if the driver is included. The driver source code usually has a pretty good list of supported chipsets and pci ids. Brandon ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Convert Filesystem to Ext4
On Apr 19, 2011, at 11:55 AM, Ryan Wagoner rswago...@gmail.com wrote: On Tue, Apr 19, 2011 at 2:29 PM, Scott Silva ssi...@sgvwater.com wrote: on 4/19/2011 11:16 AM Scott Silva spake the following: on 4/19/2011 10:42 AM Matt spake the following: On a running 64 bit CentOS 5.6 box is it possible to convert from Ext3 to Ext4 to improve performance? Right now I can deal with a few hours of downtime on it. This is an email server with lots of I/O due to seek time. Software RAID1 as well. Will Ext4 offer much of an improvement? http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/96/html/Migration_Planning_Guide/ch03s02.html I know it is for RH 6, but probably sound advice. I converted my file server to ext4. The conversion went smoothly, but I highly recommend making a backup. You need to first turn on the ext4 features then run fsck to finish the process. The conversion takes as long as a fsck takes on ext3. tune4fs -O extents,uninit_bg,dir_index /dev/ e4fsck -yfDC0 /dev/ Ryan ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Mail servers with high I/O won't get much (if any) of a performance boost. It's an i/o issue not something that ext4 can help you with except possibly a faster fsck if things go down. Things like delayed allocation.. extents.. Don't help with millions of tiny files. Faster drives and hardware raid with write cache. Better if you can have multiple disk sets and spread i/o around. Brandon ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 40TB File System Recommendations
On Wed, Apr 13, 2011 at 6:04 PM, Ross Walker rswwal...@gmail.com wrote: One was a hardware raid over fibre channel, which silently corrupted itself. System checked out fine, raid array checked out fine, xfs was replaced with ext3, and the system ran without issue. Second was multiple hardware arrays over linux md raid0, also over fibre channel. This was not so silent corruption, as in xfs would detect it and lock the filesystem into read-only before it, pardon the pun, truly fscked itself. Happened two or three times, before we gave up, split up the raid, and went ext3, Again, no issues. Every now and then I hear these XFS horror stories. They seem too impossible to believe. Nothing breaks for absolutely no reason and failure to know where the breakage was shows that maybe there wasn't adequately skilled techinicians for the technology deployed. XFS if run in a properly configured environment will run flawlessly. That's not entirely true. Even in Centos 5.3(?), we ran into an issue of XFS running on an md array would lock up for seemingly no reason due to possible corruption. I've even bookmarked the relevant bug thread for posterity sake since it caused us so much grief. https://bugzilla.redhat.com/show_bug.cgi?id=512552 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 40TB File System Recommendations
On Tue, Apr 12, 2011 at 9:35 PM, Emmanuel Noobadmin centos.ad...@gmail.comwrote: Off-topic, but when you say add more disks, do you mean for the purpose of replacing failing disks or for expanding the array? I'm curious because on initial reading I read it to mean expanding the storage capacity of the array but thought it was currently not possible to expand a mdadm RAID 0 non-destructively. centos 5 can expand raid 0/1/5. just not 6. 10 is just layered 0/1 so you can expand it. centos 6 will be able to expand raid6 as it was a feature in 2.6.20 or something. Brandon ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ext4 support in anaconda?
On Sun, Apr 10, 2011 at 6:54 PM, Phil Schaffner philip.r.schaff...@nasa.gov wrote: S.Tindall wrote on 04/10/2011 01:46 PM: Just boot the installer with the ext4 option and anaconda will be able to format ext4, or at least that works in 5.5. Works just as well on 5.6. Sorry, this is the first time I've heard of this. How do you boot the installer with the ext4 option? Can this also be done via kickstart? Brandon ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 32-bit kernel+XFS+16.xTB filesystem = potential disaster (was:Re: ZFS @ centOS)
On Tue, Apr 5, 2011 at 10:21 AM, Lamar Owen lo...@pari.edu wrote: You really, really, really don't want to do this. Not on 32-bit. When you roll one byte over 16TB you will lose access to your filesystem, silently, and it will not remount on a 32-bit kernel. XFS works best on a 64-bit kernel for a number of reasons; the one you're likely to hit first is the 16TB hard limit for *occupied* file space; you can mkfs an XFS filesystem on a 17TB or even larger partition or volume, but the moment the occupied data rolls over the 16TB boundary you will be in disaster recovery mode, and a 64-bit kernel will be required for rescue. The reason I know this? I had it happen. On a CentOS 32-bit backup server with a 17TB LVM logical volume on EMC storage. Worked great, until it rolled 16TB. Then it quit working. Altogether. /var/log/messages told me that the filesystem was too large to be mounted. Had to re-image the VM as a 64-bit CentOS, and then re-attached the RDM's to the LUNs holding the PV's for the LV, and it mounted instantly, and we kept on trucking. There's a reason upstream doesn't do XFS on 32-bit. Afaik 32-bit binaries do run on the 64-bit build and compat libraries exist for most everything. You should evaluate if you really *really* need 32-bit. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] WD RE4-GP Dropped From Raid
On Fri, Apr 1, 2011 at 7:29 AM, compdoc comp...@hotrodpc.com wrote: I have a WD RE4-GP which dropped an Adaptec 51645 RAID controller. I ran a smartctl short test on the drive and it failed with a read error. What does smart say about reallocated sectors, pending sector count, drive temperature, etc? WD will send you a new one if it's an enterprise drive. No questions asked. I've done this many a time. Brandon ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
Hi Peter, I too was very undecided about using the LSI 1068e (on-board many supermicro boards) in production for this very reason. The problem is that chipset is basically unsupported by LSI and updates to it are sometimes necessary to maintain compatibility. The driver won't build sometimes on updated kernels forcing you to hold onto a particular version. Even if you could get away from that, the driver is black box and we found it to be somewhat unreliable (read: crashy). I believe even in IT mode that chipset requires a different driver (not megasr, mptsas?) and was also black box. We decided after a few update mistakes and trips to the datacenter, it wasn't worth it. I suggest instead buying a separate megaraid card (highly recommend the 92XX series) which are very well supported by the open source, in-kernel driver (megaraid_sas? megasas?). I don't believe the 1068e is a wise choice for new installations and the 4i variants run as low as $180 new. We currently run, in production, the X8DT3 with a 9240-8i card and skipped the onboard. Brandon On Wed, Mar 16, 2011 at 8:19 AM, Peter Peltonen peter.pelto...@gmail.comwrote: I have now partially solved my problem: On Wed, Mar 9, 2011 at 5:55 PM, Peter Peltonen peter.pelto...@gmail.com wrote: I need to do a new CentOS net install on a new server having the Supermicro X7DVL-3 motherboard: [...] So I assume the controller is not supported and I need a binary driver for it. For 1068e it should be: I received the driver image megasr-13.17.0421.2010-1-rhel50-u5-all.img from the hardware vendor and was able to use it as the driver disk for installation. Upgrading the kernel issue is still unresolved though: And what happens if I get the driver installed and then the server's kernel is updated? Do I need reinstall the driver somehow? After updates the system is unable to boot with the new kernel as it cannot find the megasr driver. What shoudl I do? Does the megasr module for the old kernel also work with the new kernel = do I need to copy it somewhere and create an initrd image including that module? Or do I need to find an updated megasr module from somewhere? Best regards, Peter ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
