aingaranweb

Well-Known Member
Mar 23, 2003
65
0
156
Toronto, Ontario
Nov 20 17:45:03 cp2 kernel: ata1: command 0xca timeout, stat 0x80 host_stat 0x21

According to my /var/log/messages.1 this is the last entry.

Can anyone help me identify the problem?
 

aingaranweb

Well-Known Member
Mar 23, 2003
65
0
156
Toronto, Ontario
I've contacted them 6 hours.. No response.. It's getting quite frustrating.. Luckily, it's a new server and I only have 1 account on it.. and I have backup of the account on a different server, but the account owner made some modifications this afternoon and he wants all of that back.


Here's some more /var/log/messages.1 from this morning...

Nov 20 01:30:17 cp2 kernel: audit(1164004217.434:28): avc: denied { search } for pid=15466 comm="rndc" name="/" dev=proc ino=1 scontext=root:system_r:ndc_t tcontext=system_u:eek:bject_r:proc_t tclass=dir
Nov 20 01:30:17 cp2 kernel: audit(1164004217.434:29): avc: denied { read } for pid=15466 comm="rndc" name="self" dev=proc ino=2 scontext=root:system_r:ndc_t tcontext=system_u:eek:bject_r:proc_t tclass=lnk_file
Nov 20 01:30:17 cp2 kernel: audit(1164004217.435:30): avc: denied { search } for pid=15466 comm="rndc" name="15466" dev=proc ino=1013579778 scontext=root:system_r:ndc_t tcontext=root:system_r:ndc_t tclass=dir
Nov 20 01:30:17 cp2 kernel: audit(1164004217.435:31): avc: denied { read } for pid=15466 comm="rndc" name="exe" dev=proc ino=1013579784 scontext=root:system_r:ndc_t tcontext=root:system_r:ndc_t tclass=lnk_file
 

AndyReed

Well-Known Member
PartnerNOC
May 29, 2004
2,221
4
193
Minneapolis, MN
Nov 20 17:45:03 cp2 kernel: ata1: command 0xca timeout, stat 0x80 host_stat 0x21
From this single line, this isn't enough information to say whether you have a hardware problem or not. Contact your Data Center and ask them to look into your HD.
 

AndyReed

Well-Known Member
PartnerNOC
May 29, 2004
2,221
4
193
Minneapolis, MN
Nov 20 01:30:17 cp2 kernel: audit(1164004217.434:28): avc: denied { search } for pid=15466 comm="rndc" name="/" dev=proc ino=1
I think this is SELinux related. That said, make sure it's disabled:
cat /etc/selinux/config