I'm seeing a few messages like this on my OSD logfiles: 2013-04-25 00:00:08.174869 e3ca2b70 0 bad crc in data 1652929673 != exp 2156854821 2013-04-25 00:00:08.179749 e3ca2b70 0 -- 192.168.200.191:6882/30908 >> 192.168.200.197:0/3338580093 pipe(0xc70e1c0 sd=24 :6882 s=0 pgs=0 cs=0 l=0).accept peer addr is really 192.168.200.197:0/3338580093 (socket is 192.168.200.197:37804/0)
And also occasionally: 2013-04-25 01:40:08.006246 e3da8b70 0 auth: could not find secret_id=0 2013-04-25 01:40:08.006275 e3da8b70 0 cephx: verify_authorizer could not get service secret for service osd secret_id=0 2013-04-25 01:40:08.006286 e3da8b70 0 -- 192.168.200.190:6872/9757 >> 192.168.200.197:0/3338580093 pipe(0xb2be540 sd=24 :6872 s=0 pgs=0 cs=0 l=1).accept: got bad authorizer 2013-04-25 01:40:08.006467 e3da8b70 0 auth: could not find secret_id=0 2013-04-25 01:40:08.006482 e3da8b70 0 cephx: verify_authorizer could not get service secret for service osd secret_id=0 2013-04-25 01:40:08.006491 e3da8b70 0 -- 192.168.200.190:6872/9757 >> 192.168.200.197:0/3338580093 pipe(0xb2be540 sd=24 :6872 s=0 pgs=0 cs=0 l=1).accept: got bad authorizer 2013-04-25 01:40:08.803858 e3da8b70 0 -- 192.168.200.190:6872/9757 >> 192.168.200.197:0/3338580093 pipe(0xb2be8c0 sd=24 :6872 s=0 pgs=0 cs=0 l=0).accept peer addr is really 192.168.200.197:0/3338580093 (socket is 192.168.200.197:43170/0) This happens in both my OSD's. When the above is logged the client logs errors in the kernel logs like: Apr 25 07:00:30 bitvs4 kernel: [415607.228653] libceph: osd72 192.168.200.190:6872 socket closed (con state OPEN) Apr 25 08:40:06 bitvs4 kernel: [421582.919271] libceph: osd82 192.168.200.191:6882 socket closed (con state OPEN) Apr 25 08:40:06 bitvs4 kernel: [421582.920608] libceph: osd82 192.168.200.191:6882 socket error on read Apr 25 09:01:07 bitvs4 kernel: [422843.611197] libceph: osd82 192.168.200.191:6882 socket closed (con state OPEN) Apr 25 10:00:36 bitvs4 kernel: [426412.718574] libceph: osd82 192.168.200.191:6882 socket closed (con state OPEN) Apr 25 10:00:36 bitvs4 kernel: [426412.719766] libceph: osd82 192.168.200.191:6882 socket error on read This seems to happen on a 20 minute boundary (eg 1:00, 1:20, or 1:40) but mostly the logging is independent in the OSD's - both OSD's tend not to log errors at the same time, but always on a 20 minute boundary. I'm using ceph provided 0.60 packages for Debian. Is this actually a problem? The client seems to perform just fine although I'm still tracking down some performance issues. 'ceph health' says everything is okay. The only evidence of a problem is in the logs. I can't tell if 'bad crc' refers to data received from the network or data read from disk. Thanks James _______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
