On 01/30/2014 10:17 AM, David Boreham wrote:
On 1/30/2014 10:18 AM, Paul Whitney wrote:
rpm -q 389-ds-base
389-ds-base-1.2.11.15-30.el6_5.x86_64
No errors, just a status:
reindex userRoot: Processed 315000 entries (pass 11) -- avg rate
15283456.5/sec, recent rate 0.0/sec. hit ration 0%
Then errors log states threshold has dropped belo 50%, ending pass
11, sweeps files for merging later, then restarts with pass 12.
First thing to determine is : is it "stuck" for some reason, or
actually performing work ?
Could you note and post here the machine load in the sulking period --
CPU, I/O stats, e.g the output from "iostat -x 1" ?
Also, if you could grab some process thread stack captures (use
"pstack" , or gdb) from the indexing process and post the highlights
here, that might give some insight into what's going on.
Yes, using the Debugging_Hangs instructions:
http://port389.org/wiki/FAQ#Debugging_Hangs
The output from "strace -p xxx" run on the indexing process could also
be useful, but probably less useful than the information mentioned above.
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
