similar to: ATA errors

I just took my first cent server into production and now saslauthd keep crashing after brute force attack. I found a bug report so this has already been reported but not fixed. http://bugs.centos.org/print_bug_page.php?bug_id=2860 I assume this has to be a large problem for many people and am surprised it hasn't been fixed yet. Has anyone found a work around for this bug? Is there a

Changing it to only apply to the MinGW-Makefiles generator is maybe the safest method. Though you would have to check if MINGW is only set in the Mingw-Makefiles generator and not In the MSYS-Makefiles or Cygwin generators (should be in the docs). -- Johannes S. Mueller-Roemer, MSc Wiss. Mitarbeiter - Interactive Engineering Technologies (IET) Fraunhofer-Institut für Graphische Datenverarbeitung

Hello, I was testing Fedora 16 (rc2) Xen host, with included Xen 4.1.1 rpms and Linux 3.1.0 dom0 kernel. Fedora 16 PV domUs seem to work nicely. I noticed a problem with Fedora 16 Xen HVM guests though. The F16 guest kernel (Linux 3.1.0) fails with the qemu-dm emulated DVD-ROM drive.. Full HVM guest kernel dmesg attached to this email. See the end of this email for Xen cfgfile for the

Can anyone update me on the status of http://bugs.centos.org/print_bug_page.php?bug_id=5897 I'd really like to know if there is a fix for this as we're trying to get AD/NFSv4 working on 6.3 and having one hell of a time. -- James A. Peltier Manager, IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fax : 778-782-3045 E-Mail :

I was rsync'ing data from one system to another, and the recipient suddenly started throwing DRDY errors. Now, it's a fairly new WD Red 3TB, and I'd think it was just a bad drive... but I'm really confused by this, from the logs: Jun 15 15:34:43 <servername> kernel: ata3: SError: { Dispar } Dispar? And googling, every reference I find to that word always has something else

Hi, I download the last svn and I also look around but I cannot find the source, I only found the patch http://bugs.digium.com/print_bug_page.php?bug_id=8919 any one can help me out. thx -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070209/6780fde6/attachment.htm

On 06/16/15 07:59, Ashish Yadav wrote: > Hi, > > On Tue, Jun 16, 2015 at 2:26 AM, <m.roth at 5-cent.us> wrote: > >> I was rsync'ing data from one system to another, and the recipient >> suddenly started throwing DRDY errors. Now, it's a fairly new WD Red 3TB, >> and I'd think it was just a bad drive... but I'm really confused by this, >>

This bug report http://bugs.digium.com/print_bug_page.php?bug_id=12038 apparently has been fixed. I dont see anything on the page saying what released version of asterisk this is in. How can I tell that? jerry

I have a Sangoma b600de analog card using dahdi 2.1.0.4 and I get the following results (same dialplan, config etc): Asterisk 1.6.0.1 => works fine Asterisk 1.6.0.9 => can't dial out unless I dial in once or apply patch >>>==> http://bugs.digium.com/print_bug_page.php?bug_id=14577 Asterisk 1.6.1.0 => can't dial out, regardless of patch or inbound call first.

Hi, this is my first post to this list, so please excuse if submitting a patch without previous discussion is considered bad form or anything similar. I encountered a bug in the CMake build while using MinGW (non-MSYS, non-CYGWIN) where the LTO_export fails with a "The syntax of the command is incorrect" error. This error was previously fixed for Windows in general using

Valeri Galtsev wrote: > > On Tue, June 16, 2015 7:11 am, mark wrote: >> On 06/16/15 07:59, Ashish Yadav wrote: >>> Hi, >>> >>> On Tue, Jun 16, 2015 at 2:26 AM, <m.roth at 5-cent.us> wrote: >>> >>>> I was rsync'ing data from one system to another, and the recipient >>>> suddenly started throwing DRDY errors. Now,

Hi All, I am fairly certain that this disk is failing in my server, and I am replacing it straight away anyway. However, I'd appreciate the views of the list just to be sure as I value your opinion(s). I got these errors, once only so far, in /var/log/messages. This disk has / on it. Oct 5 08:34:47 server1 kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Oct 5 08:34:47

Hello all, Probably a stupid question, but I'll ask the pros just to be sure. Time for a new hard drive? ---- Nov 16 17:35:42 weather3 kernel: ata1.01: exception Emask 0x40 SAct 0x0 SErr 0x80800 action 0x6 Nov 16 17:35:42 weather3 kernel: ata1: SError: { HostInt 10B8B } Nov 16 17:35:42 weather3 kernel: ata1.01: cmd a0/00:00:00:00:00/00:00:00:00:00/b0 tag 0 Nov 16 17:35:42 weather3

Hello, This morning I noticed the following output from "yum update": Installing: drbd82 x86_64 8.2.5-1.el5.centos extras 209 k replacing drbd.x86_64 8.0.11-1.el5.centos As far as I'm aware DRBD works fine for me. Is there a way I can find out about the new release and weather I should upgrade? I can't figure out the CentOS issue tracking system

Hi, I have some errors in dmesg: [ 542.255788] ata1.00: exception Emask 0x0 SAct 0xffffff SErr 0x0 action 0x0 [ 542.255797] ata1.00: irq_stat 0x40000008 [ 542.255805] ata1.00: failed command: READ FPDMA QUEUED [ 542.255821] ata1.00: cmd 60/00:00:1a:b7:7a/04:00:1d:00:00/40 tag 0 ncq 524288 in [ 542.255824] res 41/40:00:a0:b7:7a/00:00:1d:00:00/40 Emask 0x409 (media error) <F> [

I'm expanding our tiny asterisk setup with a couple of external SIP phones, and I've just noticed the issue of the callerid not being displayed on an attended transfer. This bug seems to deal with it: http://bugs.digium.com/print_bug_page.php?bug_id=8824 I'm surprised that this hasn't been dealt with a long time ago - is there perhaps a work-around that I'm not aware of?

Hello List, Does anyone know why this is not available in CentOS 6.6. I found it in a SL repo but not in CentOS. I found several CentOS Bugs one answered by JH http://bugs.centos.org/print_bug_page.php?bug_id=6822 saying it had been added to 6.5 2013-12-09 19:05 JohnnyHughes Resolution open => fixed But it is still not available. cat /etc/redhat-release CentOS release 6.6 (Final)

Got a bunch of servers from Penguin. Supermicro m/b's H8QG6. We put a 3tb drive in for additional workspace for the users, and some of them won't read, others will go for weeks, then spit out DRDY errors. lshw shows the controller as an ATI SB7x0/SB8x0/SB9x0 SATA. I did notice that it shows *-storage description: SATA controller product: SB7x0/SB8x0/SB9x0 SATA

Hi, On Tue, Jun 16, 2015 at 2:26 AM, <m.roth at 5-cent.us> wrote: > I was rsync'ing data from one system to another, and the recipient > suddenly started throwing DRDY errors. Now, it's a fairly new WD Red 3TB, > and I'd think it was just a bad drive... but I'm really confused by this, > from the logs: > Jun 15 15:34:43 <servername> kernel: ata3:

On Tue, June 16, 2015 7:11 am, mark wrote: > On 06/16/15 07:59, Ashish Yadav wrote: >> Hi, >> >> On Tue, Jun 16, 2015 at 2:26 AM, <m.roth at 5-cent.us> wrote: >> >>> I was rsync'ing data from one system to another, and the recipient >>> suddenly started throwing DRDY errors. Now, it's a fairly new WD Red >>> 3TB, >>> and