[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: syncrepl consumer locks up (ITS#3263)
On Monday 02 August 2004 19:41, Jong-Hyuk wrote:
> A stack trace when it is locked up and/or when a search to syncrepl<rid>
> entry is performed will help to identify the case. It'll also be of great
> help if you send me the syncrepl part of the slapd.conf file.
> - Jong-Hyuk
This is the syncrepl configuration on the consumer:
syncrepl rid=123
provider=ldap://puma.rentec.com
type=refreshAndPersist
searchbase="dc=rentec,dc=com"
filter="(objectclass=*)"
attrs="*,creatorsName,createTimestamp,modifiersName,modifyTimestamp"
scope=sub
updatedn="cn=update,dc=rentec,dc=com"
bindmethod=sasl
saslmech=GSSAPI
authcId="host/panther.rentec.com@RENTEC.COM"
It refreshes the kerberos ticket via cron. On the provider side I have the
sessionlog set to "123 500". I'll try to recreate the hang and get a
stacktrace next time I see it. It could be related to restarts of the
provider but I'm not sure. What I did yesterday was that I restarted the
provider a couple of times and then restarted the consumer. After the
provider restarts I always saw the consumer to reconnect and it apparently
didn't have a problem but after the consumer restart it hung on certain
accesses (but not all queries failed).
Karsten.
--
The biggest difference between time and space is that you can't reuse
time.
-- Merrick Furst