On 01/30/2014 11:33 AM, Paul Whitney
wrote:
Guys I appreciate you help in this issue. I unfortunately am
hosting on a disconnected network and cannot post any of the
information you are requesting without in essence "re-typing" it
all in. In the interest of saving time, I am just
reinitializing the directory server. In the past this has
worked.
For the record, this db2index function does work fine on the
RHDS 8.2. But on both RHDS 9.0 and 9.1, it appears to get
stuck. Even after killing the process, the server attmepts to
resume the process but makes no progress.
If we cannot get large logs or debug traces, how do you suggest
going about solving this problem?
Can you give us your databases and index configuration?
I know for a fact that db2index works on RHDS 9.1, with very large
databases. So the problem them becomes - what is it about your data
and/or configuration that is causing problems?
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
--
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