Re: [CentOS] Sound drop out with totem. mplayer Can't open audio device /dev/dsp[partially SOLVED]

2012-02-17 Thread Mark LaPierre 
On 02/17/2012 11:43 PM, Mark LaPierre wrote:
> On 02/13/2012 12:15 AM, John Stanley wrote:
>> On Sun, 2012-02-12 at 20:30 -0500, Mark LaPierre wrote:
>>
>>> No such audio driver 'pulse'
>>> Could not open/initialize audio device ->   no sound.
>>> Audio: no sound
>>> Video: no video
>>>
>>>
>>> Exiting... (End of file)
>> 
>> You should get this: `mplayer -ao pulse my.mp3`
>>
>> Opening audio decoder: [mpg123] MPEG 1.0/2.0/2.5 layers I, II, III
>> AUDIO: 44100 Hz, 2 ch, s16le, 128.0 kbit/9.07% (ratio: 16000->176400)
>> Selected audio codec: [mpg123] afm: mpg123 (MPEG 1.0/2.0/2.5 layers I,
>> II, III)
>> ==
>> AO: [pulse] 44100Hz 2ch s16le (2 bytes per sample)
>> Video: no video
>> Starting playback...
>> A:  41.3 (41.3) of 254.0 (04:14.0)  0.5%
>>
>>
>> MPlayer interrupted by signal 2 in module: play_audio
>> A:  41.3 (41.3) of 254.0 (04:14.0)  0.5%
>>
>> Exiting... (Quit)
>> -
>> With ALSA:
>> mplayer -ao alsa my.mp3
>>
>> ==
>> Opening audio decoder: [mpg123] MPEG 1.0/2.0/2.5 layers I, II, III
>> AUDIO: 44100 Hz, 2 ch, s16le, 128.0 kbit/9.07% (ratio: 16000->176400)
>> Selected audio codec: [mpg123] afm: mpg123 (MPEG 1.0/2.0/2.5 layers I,
>> II, III)
>> ==
>> AO: [alsa] 44100Hz 2ch s16le (2 bytes per sample)
>> Video: no video
>> Starting playback...
>> A:  12.7 (12.7) of 254.0 (04:14.0)  0.4%
>>
>>
>> MPlayer interrupted by signal 2 in module: play_audio
>> A:  12.8 (12.7) of 254.0 (04:14.0)  0.4%
>>
>> Exiting... (Quit)
>> 
>>
>> On a corectly configured DAW Machine with pulseaudio you should be able
>> to run:  `padsp mplayer my.mp3`
>>
>> AO: [oss] 44100Hz 2ch s16le (2 bytes per sample)
>> 
>> Video: no video
>> Starting playback...
>> A:  11.1 (11.1) of 254.0 (04:14.0)  0.4%
>>
>>
>> MPlayer interrupted by signal 2 in module: play_audio
>> A:  11.2 (11.1) of 254.0 (04:14.0)  0.4%
>> --
>>
>> On EL6 you should be using ALSA for mplayer as alsa targets pulse.
>>
>>> aplay file.mp3 says:
>>> Playing raw data 'file.mp3' : Unsigned 8 bit, Rate 8000 Hz, Mono
>>>
>>> Still just makes a nasty hiss.
>>
>> `aplay -f dat my.wav` is what you want. "little indianess" byte words.
>>
>>> Still no /dev/dsp.  Maybe there isn't supposed to be one for my sound
>>> hardware?
>>
>> I said previously there is NO ""/dev/dsp"" and there want be one for
>> EL6.  If perhaps you had one then you really have someing funny going
>> on.
>>
>>> lspci says:
>>> Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237
>>> AC97 Audio Controller (rev 60)
>>
>> Those cards can be nothing but problems.  Some say that there are common
>> in linux but I say nothing but common trouble.
>>
>> When did you update the the kernel last?  Something good is `alsa-info`
>> and read the instructions on the terminal and where to run it and get
>> the standard output of it.  You could try a diffeernt "codec" besides
>> "lame" like mpg123.  Does asound.conf point to the pulses conf file?
>>
>> It is a normal thing that pulseaudio will pop and skip and snap crackle
>> when it does not have enough of a Buffer or Priority and when a card is
>> going bad.
>>
>> Since in the above mplayer can not access pulse last thing you could do
>> is reinstall all the pulse packages.
>>
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> http://lists.centos.org/mailman/listinfo/centos
>>
>
> I downgraded lame back to the previous package and rebooted the machine.
>That fixed the skipping and dropouts from totem/gstreamer.
>
> Shortly after that I got a kernel upgrade notice on my auto update tool.
>I installed that but declined the upgrade to lame.  After reboot that
> still worked.  Last night I reinstalled the lame upgrade and did another
> cold start.  Still no skipping and dropouts from totem/gstreamer.
>
> mplayer still doesn't want to hear it.
> mplayer -ao pulse my.mp3 >  No Joy
> mplayer -ao alsa my.mp3 >  No Joy
>
> padsp mplayer my.mp3 works.
> It says:
> AO: [oss] 44100Hz 2ch s16le (2 bytes per sample)
> Sound it good.
>
> `aplay -f dat my.mp3` just makes a hissy noise, but it's a different
> hissy noise than `aplay my.mp3` does.
>
> My alsa information is at:
> http://www.alsa-project.org/db/?f=522b3664bd765b464440dabd18c7b2dda0a5e154
>

Oh hold the phone!  aplay doesn't support mp3.  It works fine with wav 
files.  Duhhh! I guess I should RTFM.

-- 
 _
°v°
   /(_)\
^ ^  Mark LaPierre
Registerd Linux user No #267004
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.or

Re: [CentOS] Sound drop out with totem. mplayer Can't open audio device /dev/dsp[partially SOLVED]

2012-02-17 Thread Mark LaPierre 
On 02/13/2012 12:15 AM, John Stanley wrote:
> On Sun, 2012-02-12 at 20:30 -0500, Mark LaPierre wrote:
>
>> No such audio driver 'pulse'
>> Could not open/initialize audio device ->  no sound.
>> Audio: no sound
>> Video: no video
>>
>>
>> Exiting... (End of file)
> 
> You should get this: `mplayer -ao pulse my.mp3`
>
> Opening audio decoder: [mpg123] MPEG 1.0/2.0/2.5 layers I, II, III
> AUDIO: 44100 Hz, 2 ch, s16le, 128.0 kbit/9.07% (ratio: 16000->176400)
> Selected audio codec: [mpg123] afm: mpg123 (MPEG 1.0/2.0/2.5 layers I,
> II, III)
> ==
> AO: [pulse] 44100Hz 2ch s16le (2 bytes per sample)
> Video: no video
> Starting playback...
> A:  41.3 (41.3) of 254.0 (04:14.0)  0.5%
>
>
> MPlayer interrupted by signal 2 in module: play_audio
> A:  41.3 (41.3) of 254.0 (04:14.0)  0.5%
>
> Exiting... (Quit)
> -
> With ALSA:
> mplayer -ao alsa my.mp3
>
> ==
> Opening audio decoder: [mpg123] MPEG 1.0/2.0/2.5 layers I, II, III
> AUDIO: 44100 Hz, 2 ch, s16le, 128.0 kbit/9.07% (ratio: 16000->176400)
> Selected audio codec: [mpg123] afm: mpg123 (MPEG 1.0/2.0/2.5 layers I,
> II, III)
> ==
> AO: [alsa] 44100Hz 2ch s16le (2 bytes per sample)
> Video: no video
> Starting playback...
> A:  12.7 (12.7) of 254.0 (04:14.0)  0.4%
>
>
> MPlayer interrupted by signal 2 in module: play_audio
> A:  12.8 (12.7) of 254.0 (04:14.0)  0.4%
>
> Exiting... (Quit)
> 
>
> On a corectly configured DAW Machine with pulseaudio you should be able
> to run:  `padsp mplayer my.mp3`
>
> AO: [oss] 44100Hz 2ch s16le (2 bytes per sample)
> 
> Video: no video
> Starting playback...
> A:  11.1 (11.1) of 254.0 (04:14.0)  0.4%
>
>
> MPlayer interrupted by signal 2 in module: play_audio
> A:  11.2 (11.1) of 254.0 (04:14.0)  0.4%
> --
>
> On EL6 you should be using ALSA for mplayer as alsa targets pulse.
>
>> aplay file.mp3 says:
>> Playing raw data 'file.mp3' : Unsigned 8 bit, Rate 8000 Hz, Mono
>>
>> Still just makes a nasty hiss.
>
> `aplay -f dat my.wav` is what you want. "little indianess" byte words.
>
>> Still no /dev/dsp.  Maybe there isn't supposed to be one for my sound
>> hardware?
>
> I said previously there is NO ""/dev/dsp"" and there want be one for
> EL6.  If perhaps you had one then you really have someing funny going
> on.
>
>> lspci says:
>> Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237
>> AC97 Audio Controller (rev 60)
>
> Those cards can be nothing but problems.  Some say that there are common
> in linux but I say nothing but common trouble.
>
> When did you update the the kernel last?  Something good is `alsa-info`
> and read the instructions on the terminal and where to run it and get
> the standard output of it.  You could try a diffeernt "codec" besides
> "lame" like mpg123.  Does asound.conf point to the pulses conf file?
>
> It is a normal thing that pulseaudio will pop and skip and snap crackle
> when it does not have enough of a Buffer or Priority and when a card is
> going bad.
>
> Since in the above mplayer can not access pulse last thing you could do
> is reinstall all the pulse packages.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>

I downgraded lame back to the previous package and rebooted the machine. 
  That fixed the skipping and dropouts from totem/gstreamer.

Shortly after that I got a kernel upgrade notice on my auto update tool. 
  I installed that but declined the upgrade to lame.  After reboot that 
still worked.  Last night I reinstalled the lame upgrade and did another 
cold start.  Still no skipping and dropouts from totem/gstreamer.

mplayer still doesn't want to hear it.
mplayer -ao pulse my.mp3 > No Joy
mplayer -ao alsa my.mp3 > No Joy

padsp mplayer my.mp3 works.
It says:
AO: [oss] 44100Hz 2ch s16le (2 bytes per sample)
Sound it good.

`aplay -f dat my.mp3` just makes a hissy noise, but it's a different 
hissy noise than `aplay my.mp3` does.

My alsa information is at:
http://www.alsa-project.org/db/?f=522b3664bd765b464440dabd18c7b2dda0a5e154

-- 
 _
°v°
   /(_)\
^ ^  Mark LaPierre
Registerd Linux user No #267004
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Fwd: CentOS4 desktop has stopped recognizing removable media - haldaemon problem?

2012-02-17 Thread Phil Schaffner 
Bart Schaefer wrote on 02/15/2012 05:00 PM:
> Didn't get any response to this last time, but it's still happening,
> so I'm trying again.  No clues?

Try it on a freshly created account. If it works, then it's something 
you did to your account.  If it does not then it is a system-level bug 
or setting - unlikely.

Phil


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Filing a bug for clamav

2012-02-17 Thread Phil Schaffner 
Jobst Schmalenbach wrote on 02/17/2012 07:40 PM:
>   "yum list installed | grep clamav"

# yum --showduplicates --noplugins --enablerepo atrpms,epel,rpmforge 
list clamav
...
Available Packages
clamav.x86_64  0.96.1-1.el5.rf  
rpmforge
clamav.x86_64  0.96.2-1.el5.rf  
rpmforge
clamav.x86_64  0.96.2-2.el5.rf  
rpmforge
clamav.x86_64  0.96.3-1.el5.rf  
rpmforge
clamav.x86_64  0.96.3-2.el5.rf  
rpmforge
clamav.x86_64  0.96.4-1.el5.rf  
rpmforge
clamav.x86_64  0.96.5-1.el5.rf  
rpmforge
clamav.x86_64  0.97-1.el5.rf
rpmforge
clamav.x86_64  0.97.1-1.el5.rf  
rpmforge
clamav.x86_64  0.97.2-1.el5.rf  
rpmforge
clamav.x86_64  0.97.3-1.el5.rf  
rpmforge
clamav.i3860.97.3-3.el5 
epel
clamav.x86_64  0.97.3-3.el5 
epel
clamav.x86_64  1:0.97.3-61.el5  
atrpms

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Filing a bug for clamav

2012-02-17 Thread Jobst Schmalenbach 
On Fri, Feb 17, 2012 at 09:38:02AM -0600, Johnny Hughes (joh...@centos.org) 
wrote:
> On 02/17/2012 07:06 AM, Jobst Schmalenbach wrote:
> > Hi.
> >
> > IMHO there is a bug in the latest updater for clamav:
> >
> CentOS does not distribute clamav ...
> 
> 
> 

OK, thanks ... I am a step further then.
Now if I do a 

 "yum list installed | grep clamav"

then this happens:

  [root ~] #>yum list installed | grep clam
  clamav.x86_64  0.97.3-3.el5
installed
  clamav-db.x86_64   0.97.3-3.el5
installed
  clamav-milter.x86_64   0.97.3-3.el5
installed
  clamd.x86_64   0.97.3-3.el5
installed

It only says "installed" but I cannot remember the repository ... sadly.

How can I find out the repository it came from?

There does not seem to be an option in YUM to list all available rpm's from a 
particular reposotory ...




-- 
"There are three kinds of lies: Lies, Damn lies, and statistics." - Disraeli

  | |0| |   Jobst Schmalenbach, jo...@barrett.com.au, General Manager
  | | |0|   Barrett Consulting Group P/L & The Meditation Room P/L
  |0|0|0|   +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] smartd and smartctl

2012-02-17 Thread Yves Bellefeuille 
On Friday 17 February 2012, m.r...@5-cent.us wrote:

> SMART Self-test log structure revision number 1
> Num  Test_DescriptionStatus  Remaining
> LifeTime(hours)  LBA
> _of_first_error
> # 1  Extended offlineCompleted without error   00%  2536
>   -
> # 2  Short offline   Completed without error   00%  2529
>   -
> 
> So I'm befuddled why it won't tell me anything about this pending
> error.

I've had a hard drive with *many* bad sectors, and still smartctl 
reported "Completed without error". I believe this means that there are 
still spare sectors available.

I suggest "badblocks -n", as I said in another message. This may also 
detect more bad sectors. What does "5 Reallocated_Sector_Ct" say?

-- 
Yves Bellefeuille 
"La Esperanta Civito ne rifuzas anticipe la kunlaboron de erarintoj, se
ili konscias pri sia eraro." -- Heroldo Komunikas, n-ro 473.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] smartd and smartctl

2012-02-17 Thread Yves Bellefeuille 
On Friday 17 February 2012, Andrzej Szymański  
wrote:

> As the location and contents of this sector are quite hard to find,
> the simplest, but the most troublesome way of solving the problem is
> moving all data away from this disk, writing the whole surface with
> zeros (dd) and moving the data back.

badblocks -n would also work, I imagine.

-- 
Yves Bellefeuille 
"La Esperanta Civito ne rifuzas anticipe la kunlaboron de erarintoj, se
ili konscias pri sia eraro." -- Heroldo Komunikas, n-ro 473.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] smartd and smartctl

2012-02-17 Thread m . roth 
Mike VanHorn wrote:
>
> FWIW, on some of my workstations, when I have gotten the "sector pending"
> messages, I have been able to take the drive out and run the
> manufacturer's diagnostics on it (in my case, Seatools), and that fixed
> some things and I haven't had any issues since.
>
Well, since the server has users on it, I can't really do that, or wipe
the disk I'm not really worried - it's stayed at 1 sector. If that
starts growing, then I'll worry, and get ready to replace the disk. Right
now, it's just an annoyance, as I said, that it shows up on email logs
from our loghost twice every hour. And I'm still waiting for anyone to
explain to me what I'm doing using smartctl that results in it *not*
telling me there's an error, or where the error is. In fact, the last long
test I started, early this afternoon, seems to be done, and with smartctl
-a, I see
SMART Self-test log structure revision number 1
Num  Test_DescriptionStatus  Remaining 
LifeTime(hours)  LBA
_of_first_error
# 1  Extended offlineCompleted without error   00%  2536  
  -
# 2  Short offline   Completed without error   00%  2529  
  -

So I'm befuddled why it won't tell me anything about this pending error.

mark

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Race Condition In PHP Session Handler

2012-02-17 Thread Adam Tauno Williams 
php-5.3.3-3.el6_2.6.x86_64
2.6.32-220.4.2.el6.x86_64

After some testing we moved our production PHP intranet site from an old
server to a new CentOS 6.2 instance running the mentioned versions.  At
first it worked well and then user's started to experience a hung site.
Upon some digging it appears that the PHP module is getting stuck in a
race condition regarding the sessions file -

[root@yannigan-orange fd]# strace -p  22607
Process 22607 attached - interrupt to quit
flock(53, LOCK_EX^C 

where file handle 53 is 

...
lr-x--. 1 root root 64 Feb 17 15:24 52
-> /opt/informix/msg/en_us/0333/cli.iem
lrwx--. 1 root root 64 Feb 17 15:24 53
-> /var/lib/php/session/sess_ulgsl9joplobb9o4fue3n2e1k0
l-wx--. 1 root root 64 Feb 17 15:24 6 -> pipe:[660246]


The PHP session file.  Originally I had a tmpfs mounted for the session
files.  I removed that and used the underlying filesystem.  Same issue.
I disabled APC.  Same issue.

Switching the the memcache session handler resolved the issue,  although
that may be less optimal.  But this seems like a PHP bug.

Tips, comments, pointers?

Backtrace of a hung httpd -
#0  0x7fa175af9be7 in flock () from /lib64/libc.so.6
#1  0x7fa16cb59dfc in ?? () from /etc/httpd/modules/libphp5.so
#2  0x7fa16cb5a047 in ?? () from /etc/httpd/modules/libphp5.so
#3  0x7fa16cb56e4c in php_session_start ()
from /etc/httpd/modules/libphp5.so
#4  0x7fa16cb57559 in ?? () from /etc/httpd/modules/libphp5.so
#5  0x7fa16cc9afe8 in ?? () from /etc/httpd/modules/libphp5.so
#6  0x7fa16cc72320 in execute () from /etc/httpd/modules/libphp5.so
#7  0x7fa16cc4ca5d in zend_execute_scripts ()
from /etc/httpd/modules/libphp5.so
#8  0x7fa16cbfacf8 in php_execute_script ()
from /etc/httpd/modules/libphp5.so
#9  0x7fa16ccd59a5 in ?? () from /etc/httpd/modules/libphp5.so
#10 0x7fa17751da60 in ap_run_handler ()
#11 0x7fa17752131e in ap_invoke_handler ()
#12 0x7fa17752c990 in ap_process_request ()
#13 0x7fa177529858 in ?? ()
#14 0x7fa177525568 in ap_run_process_connection ()
#15 0x7fa177531767 in ?? ()
#16 0x7fa177531a7a in ?? ()
#17 0x7fa177531dab in ap_mpm_run ()
#18 0x7fa177509900 in main ()



-- 
System & Network Administrator [ LPI & NCLA ]

OpenGroupware Developer 
Adam Tauno Williams


signature.asc
Description: This is a digitally signed message part
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] smartd and smartctl

2012-02-17 Thread Andrzej Szymański 
W dniu 2012-02-17 21:25, m.r...@5-cent.us pisze:
> Mike Burger wrote:
> Ok, but my thinking was, first, that after the fsck, the system wouldn't
> try to write to the bad sector, thus not provoking smart. The more
> annoying thing is that I don't understand why smartctl doesn't give the
> same info as smartd. When I do a -a, it does tell me that one sector's
> pending, but not that there's any error.
>

Actually smartd is reporting THIS pending sector, and it probably won't 
stop until this sector is reallocated, which will happen on a nearest 
write to this sector.

As the location and contents of this sector are quite hard to find, the 
simplest, but the most troublesome way of solving the problem is moving 
all data away from this disk, writing the whole surface with zeros (dd) 
and moving the data back.

However, I would carefully monitor number of reallocated sectors on this 
disk. If it grows steadily, then better move your valuable data elsewhere.

Andrzej
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] smartd and smartctl

2012-02-17 Thread Mike VanHorn 

FWIW, on some of my workstations, when I have gotten the "sector pending"
messages, I have been able to take the drive out and run the
manufacturer's diagnostics on it (in my case, Seatools), and that fixed
some things and I haven't had any issues since.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.engineering.wright.edu/~mvanhorn/





On 2/17/12 3:25 PM, "m.r...@5-cent.us"  wrote:

Mike Burger wrote:
>
>> A few weeks ago, one of my servers started complaining, via smartd, that
>> one drive had one unreadable sector. I umounted it, and ran an fsck -c,
>> then remounted it. Error didn't go away. Now, what's really annoying is
>> that I've gotten back to it today, and it's reporting the problem, as it
>> has for weeks now, every half an hour.
>>
>> However, when I run
>>> smartctl -q errorsonly -H -l selftest -l error /dev/sdb
>> it gives me *nothing*. Anyone understand why I get two different
>> results?
>>
>>  mark "and I am waiting for the smartctl -t long /dev/sdb to
>> complete"
>
> The smart system works at the hardware level, reading diagnostic
> information from the SMART circuitry on the hard drives, themselves. The
> hard drives will often, now, try to move the data from bad sectors on the
> platters to good sectors, and then mark them so that they won't be used,
> later.
>
> Running fsck only works at the logical filesystem layer. The fsck tool
>has
> no hooks to deal with the physical layer.

Ok, but my thinking was, first, that after the fsck, the system wouldn't
try to write to the bad sector, thus not provoking smart. The more
annoying thing is that I don't understand why smartctl doesn't give the
same info as smartd. When I do a -a, it does tell me that one sector's
pending, but not that there's any error.

mark

___
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] smartd and smartctl

2012-02-17 Thread m . roth 
Mike Burger wrote:
>
>> A few weeks ago, one of my servers started complaining, via smartd, that
>> one drive had one unreadable sector. I umounted it, and ran an fsck -c,
>> then remounted it. Error didn't go away. Now, what's really annoying is
>> that I've gotten back to it today, and it's reporting the problem, as it
>> has for weeks now, every half an hour.
>>
>> However, when I run
>>> smartctl -q errorsonly -H -l selftest -l error /dev/sdb
>> it gives me *nothing*. Anyone understand why I get two different
>> results?
>>
>>  mark "and I am waiting for the smartctl -t long /dev/sdb to
>> complete"
>
> The smart system works at the hardware level, reading diagnostic
> information from the SMART circuitry on the hard drives, themselves. The
> hard drives will often, now, try to move the data from bad sectors on the
> platters to good sectors, and then mark them so that they won't be used,
> later.
>
> Running fsck only works at the logical filesystem layer. The fsck tool has
> no hooks to deal with the physical layer.

Ok, but my thinking was, first, that after the fsck, the system wouldn't
try to write to the bad sector, thus not provoking smart. The more
annoying thing is that I don't understand why smartctl doesn't give the
same info as smartd. When I do a -a, it does tell me that one sector's
pending, but not that there's any error.

mark

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] smartd and smartctl

2012-02-17 Thread Mike Burger 

> A few weeks ago, one of my servers started complaining, via smartd, that
> one drive had one unreadable sector. I umounted it, and ran an fsck -c,
> then remounted it. Error didn't go away. Now, what's really annoying is
> that I've gotten back to it today, and it's reporting the problem, as it
> has for weeks now, every half an hour.
>
> However, when I run
>> smartctl -q errorsonly -H -l selftest -l error /dev/sdb
> it gives me *nothing*. Anyone understand why I get two different results?
>
>  mark "and I am waiting for the smartctl -t long /dev/sdb to complete"

The smart system works at the hardware level, reading diagnostic
information from the SMART circuitry on the hard drives, themselves. The
hard drives will often, now, try to move the data from bad sectors on the
platters to good sectors, and then mark them so that they won't be used,
later.

Running fsck only works at the logical filesystem layer. The fsck tool has
no hooks to deal with the physical layer.

-- 
Mike Burger
http://www.bubbanfriends.org

Visit the Dog Pound II BBS
telnet://dogpound2.citadel.org http://dogpound2.citadel.org
https://dogpound2.citadel.org

To be notified of updates to the web site, visit:

https://www.bubbanfriends.org/mailman/listinfo/site-update

or send a blank email to:

site-update-subscr...@bubbanfriends.org
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] smartd and smartctl

2012-02-17 Thread m . roth 
A few weeks ago, one of my servers started complaining, via smartd, that
one drive had one unreadable sector. I umounted it, and ran an fsck -c,
then remounted it. Error didn't go away. Now, what's really annoying is
that I've gotten back to it today, and it's reporting the problem, as it
has for weeks now, every half an hour.

However, when I run
> smartctl -q errorsonly -H -l selftest -l error /dev/sdb
it gives me *nothing*. Anyone understand why I get two different results?

 mark "and I am waiting for the smartctl -t long /dev/sdb to complete"

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum update stuck...

2012-02-17 Thread Mike Burger 
> On 10/02/12 10:50, John Doe wrote:
>> Hi,
>>
>> Running Transaction
>>Updating   : selinux-policy
>> 1/6
>>Updating   : kmod-r8168
>> 2/6
>> Working. This may take some time ...
>>
>>
>> An hour later, still working...
>>
>
> Wow. These kmods can take quite some time to update/install in yum,
> hence the informational message, but I've not yet seen one take an hour!
>
> How many kernels do you have installed as time is proportional to the
> number of kernels the module has to install against. Is it a
> particularly slow/old system, maybe short on memory?
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>

I don't recall, now, if I've replied to this thread or not, but...

I ran into a similar issue a few weeks ago...it turned out that I was
having an issue with my /tmp filesystem (at least)...I couldn't even
perform an orderly shutdown -r.

I wound up hard booting, during which /tmp was fsck'd, clearing a fair
number of orphaned inodes, and my yum update ran just fine after that.

Just a thought.

-- 
Mike Burger
http://www.bubbanfriends.org

Visit the Dog Pound II BBS
telnet://dogpound2.citadel.org http://dogpound2.citadel.org
https://dogpound2.citadel.org

To be notified of updates to the web site, visit:

https://www.bubbanfriends.org/mailman/listinfo/site-update

or send a blank email to:

site-update-subscr...@bubbanfriends.org
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Any experience with eSATA and port multiplier...?

2012-02-17 Thread Gary Greene 
On 2/17/12 3:47 AM, "John Doe"  wrote:


>Hey,
>
>just bought an eSATA/USB dual drive docking station and my CentOS 5 can
>only see one drive at a time...
>Any one knows if there are specific parameters to set somewhere?
>Or do I need a more recent kernel (like upgrading to CentOS 6?)
>
>The docking is a Sharkoon Quickport Duo v2 + 2 drives + 1 eSATA cable...
>http://www.sharkoon.com/?q=en/content/sata-quickport-duo-v2
>The eSATA controller is an HighPpoint PciE 2 ports combo eSATA/USB with
>(supposedly) port-multiplier support
>Apparently based on an Silicon image Sil 3132
>Seems like the port multiplier part does not work correctly...
>
>kernel: ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 10)
>kernel: ata7.15: Port Multiplier 1.1, 0x197b:0x2352 r0, 2 ports, feat
>0x0/0x0
>kernel: ata7.15: Asynchronous notification not supported, hotplug won't
>kernel:  work on fan-out ports. Use warm-plug instead.
>kernel: ata7.00: hard resetting link
>
>The logs are full of "hard resetting link", "softreset failed" and other
>"failed to reset PMP, giving up"
>
>
>I did not try to reboot yet...  Would be a pain to have to reboot every
>time I need to plug drives.  :/
>
>
>I am not the only one...
>http://linux.derkeiler.com/Mailing-Lists/SuSE/2011-10/msg00055.html
>He has a kernel 2.6.37.6-0.7 and it still fails so I am wondering if
>upgrading to CentOS 6.x would help at all...
>


To make this work, the module for the chipset for the SATA controller that
the device uses must support Port Multiplier options. Unfortunately, from
my experience, not many SATA drivers in the Linux kernel actually support
PMP properly or reliably. I've a server at home using this for storage of
video data which is using an SiS chipset which works well after going
through two manufacturers which did not.

--
Gary L. Greene, Jr.
Sr. Systems Administrator
IT Operations, Minerva Networks Inc.
Cell: (650) 704-6633
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS-announce Digest, Vol 84, Issue 10

2012-02-17 Thread centos-announce-request 
Send CentOS-announce mailing list submissions to
centos-annou...@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-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@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-2012:0143 Critical CentOS 5 xulrunner Update (Johnny Hughes)
   2. CESA-2012:0142 Critical CentOS 4 firefox Update (Johnny Hughes)
   3. CESA-2012:0141 Critical CentOS 4 seamonkey Update (Johnny Hughes)
   4. CESA-2012:0143 Critical CentOS 6 xulrunner Update (Johnny Hughes)
   5. CESA-2012:0140 Critical CentOS 6 thunderbird  Update
  (Johnny Hughes)


--

Message: 1
Date: Fri, 17 Feb 2012 01:35:23 +
From: Johnny Hughes 
Subject: [CentOS-announce] CESA-2012:0143 Critical CentOS 5 xulrunner
Update
To: centos-annou...@centos.org
Message-ID: <20120217013523.ga7...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2012:0143 Critical

Upstream details at : http://rhn.redhat.com/errata/RHSA-2012-0143.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
0dcf1983ec06f56f3009843c736af1cf93d5da0d3e02bdf6780e58401cd3cf82  
xulrunner-1.9.2.26-2.el5_7.i386.rpm
b8f757d7a49d40d7e54cb15bfb5015c558c7e546d3611dd3dbc0f918df1ad483  
xulrunner-devel-1.9.2.26-2.el5_7.i386.rpm

x86_64:
0dcf1983ec06f56f3009843c736af1cf93d5da0d3e02bdf6780e58401cd3cf82  
xulrunner-1.9.2.26-2.el5_7.i386.rpm
e2415c9b93d16a4bb508c35746bce17d311bd64900e97787c663da0b0a4eea8a  
xulrunner-1.9.2.26-2.el5_7.x86_64.rpm
b8f757d7a49d40d7e54cb15bfb5015c558c7e546d3611dd3dbc0f918df1ad483  
xulrunner-devel-1.9.2.26-2.el5_7.i386.rpm
d8608e99851ad34e27c0a176ba96e2afa2d65e4d6531e1ea214e7c9def71af73  
xulrunner-devel-1.9.2.26-2.el5_7.x86_64.rpm

Source:
07ade572362e70646b8aabca07f97e764cfd369c484f54b850cba4c08e45c322  
xulrunner-1.9.2.26-2.el5_7.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

Message: 2
Date: Fri, 17 Feb 2012 01:39:20 +
From: Johnny Hughes 
Subject: [CentOS-announce] CESA-2012:0142 Critical CentOS 4 firefox
Update
To: centos-annou...@centos.org
Message-ID: <20120217013920.ga7...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2012:0142 Critical

Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0142.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
26c5569bbec99ea80c80dc8da3146d0de4d2ad59b6bbbe1cd11517a1196bdbf3  
firefox-3.6.26-3.el4.centos.i386.rpm

x86_64:
badbcc0c95ece02255d5683412623395eefbf4bcec7412481508bd3cb0be67a4  
firefox-3.6.26-3.el4.centos.x86_64.rpm

Source:
b627e370bde234945efae706acb6a765a09edda1966eb0659d764e2774a2e591  
firefox-3.6.26-3.el4.centos.src.rpm



-- 
Tru Huynh
CentOS Project { http://www.centos.org/ }
irc: tru_tru, #cen...@irc.freenode.net



--

Message: 3
Date: Fri, 17 Feb 2012 01:42:07 +
From: Johnny Hughes 
Subject: [CentOS-announce] CESA-2012:0141 Critical CentOS 4 seamonkey
Update
To: centos-annou...@centos.org
Message-ID: <20120217014207.ga7...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2012:0141 Critical

Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0141.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
55b7e003ac20912ede26be03713073f83feee2e82fbe437cb4890bb3c827847a  
seamonkey-1.0.9-79.el4.centos.i386.rpm
1fe20d952c91fa25b20573972c6aae2202ed2a3066a82b0ffd717c1327a52da8  
seamonkey-1.0.9-79.el4.centos.i686.rpm
9a83f274cb7125b765ead6e13a24c5dabbae3c31d2583851a063c04dc8181b61  
seamonkey-chat-1.0.9-79.el4.centos.i386.rpm
545bdfe21b31306781ba6b237114d13783342b897767a2ba639b6e3531503183  
seamonkey-chat-1.0.9-79.el4.centos.i686.rpm
f7c90337c3b81fb24192b61e659e7e65acaf2893edac7ae7ecdd7cd9864388b8  
seamonkey-devel-1.0.9-79.el4.centos.i386.rpm
1b2b6704da8ca7898a9133f518525854d5a3edf17516fb98362f00f72cdf6b14  
seamonkey-devel-1.0.9-79.el4.centos.i686.rpm
b9fda45424605ab3fd8e5b39b6b575b4810790c7ee3f475fd96d34e8ab9c8433  
seamonkey-dom-inspector-1.0.9-79.el4.centos.i386.rpm
74f53bb0059bf3b3f46ea62b3d4636d0e9cfb88c2427954e39c55f10097e8cb7  
seamonkey-dom-inspector-1.0.9-79.el4.centos.i686.rpm
d0a4d8522b161e172cc23e50a1fd822519c170245df343023ea90a2f5c87a96b  
seamonkey-js-debugger-1.0.9-79.el4.centos.i386.rpm
5a04d651e3147d12beddb358cd37edbd65116d60

Re: [CentOS] Filing a bug for clamav

2012-02-17 Thread Morten Stevens 
On 17.02.2012 14:06, Jobst Schmalenbach wrote:
> Hi.
>
> IMHO there is a bug in the latest updater for clamav:
>
> Where do I file a bug report?

Repo? EPEL? If, Yes: https://bugzilla.redhat.com/

Select: Enter a new bug report > Fedora > Fedora EPEL

Best regards,

Morten
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Filing a bug for clamav

2012-02-17 Thread Johnny Hughes 
On 02/17/2012 07:06 AM, Jobst Schmalenbach wrote:
> Hi.
>
> IMHO there is a bug in the latest updater for clamav:
>
>  * it places a freshclam script into /etc/cron.daily that uses a hardcoded 
> datadir not defined in /etc/clamd.conf
>its never done that before in the last 5 years or so, and I have a script 
> running from cron.d
>
>  * its overwrites the permissions of existing directories (lib and log) to 
> another new clamav user, although one already exist
>(making the system unstable)
>
> Where do I file a bug report?
> Jobst

CentOS does not distribute clamav ...





signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] init/upstart issue? ypbind and autofs

2012-02-17 Thread Lars Hecking 

> |  Won't help in this case, I think, as this behaviour already makes my
> |  kickstart
> |  %post fail.
 
 Correcting myself ... what fails is an init script generated at %post time.

> Once you make the network interface no longer NM managed you can then perform
> a service network restart in your post and all network functionality should
> then become available.

 I don't see the need for NM on racked servers and stationary workstations.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Filing a bug for clamav

2012-02-17 Thread Jobst Schmalenbach 
Hi.

IMHO there is a bug in the latest updater for clamav:

 * it places a freshclam script into /etc/cron.daily that uses a hardcoded 
datadir not defined in /etc/clamd.conf
   its never done that before in the last 5 years or so, and I have a script 
running from cron.d

 * its overwrites the permissions of existing directories (lib and log) to 
another new clamav user, although one already exist
   (making the system unstable)

Where do I file a bug report?
Jobst



-- 
Sendmail administration is not black magic.  There are legitimate technical 
reasons why it requires the sacrificing of a live chicken.

  | |0| |   Jobst Schmalenbach, jo...@barrett.com.au, General Manager
  | | |0|   Barrett Consulting Group P/L & The Meditation Room P/L
  |0|0|0|   +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Any experience with eSATA and port multiplier...?

2012-02-17 Thread John Doe 
Hey,

just bought an eSATA/USB dual drive docking station and my CentOS 5 can only 
see one drive at a time...
Any one knows if there are specific parameters to set somewhere?
Or do I need a more recent kernel (like upgrading to CentOS 6?)

The docking is a Sharkoon Quickport Duo v2 + 2 drives + 1 eSATA cable...
http://www.sharkoon.com/?q=en/content/sata-quickport-duo-v2
The eSATA controller is an HighPpoint PciE 2 ports combo eSATA/USB with 
(supposedly) port-multiplier support
Apparently based on an Silicon image Sil 3132
Seems like the port multiplier part does not work correctly...

kernel: ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 10)
kernel: ata7.15: Port Multiplier 1.1, 0x197b:0x2352 r0, 2 ports, feat 0x0/0x0
kernel: ata7.15: Asynchronous notification not supported, hotplug won't
kernel:  work on fan-out ports. Use warm-plug instead.
kernel: ata7.00: hard resetting link

The logs are full of "hard resetting link", "softreset failed" and other 
"failed to reset PMP, giving up"


I did not try to reboot yet...  Would be a pain to have to reboot every time I 
need to plug drives.  :/


I am not the only one...
http://linux.derkeiler.com/Mailing-Lists/SuSE/2011-10/msg00055.html
He has a kernel 2.6.37.6-0.7 and it still fails so I am wondering if upgrading 
to CentOS 6.x would help at all...


Thx,
JD

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos