See <http://jenkins.cloud.fedoraproject.org/job/389-ds-base/122/>
------------------------------------------
Started by an SCM change
Building remotely on Fedora18 in workspace <http://jenkins.cloud.fedoraproject.org/job/389-ds-base/ws/>
Checkout:389-ds-base / <http://jenkins.cloud.fedoraproject.org/job/389-ds-base/ws/> - hudson.remoting.Channel@3394214b:Fedora18
Using strategy: Default
Last Built Revision: Revision 56441c31d8709fdd5c9e45a0cfcaa1e9ec88532a (origin/master)
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository http://git.fedorahosted.org/cgit/389/ds.git/
git --version
git version 1.8.1.4
ERROR: Error cloning remote repo 'origin' : Could not clone http://git.fedorahosted.org/cgit/389/ds.git/
hudson.plugins.git.GitException: Could not clone http://git.fedorahosted.org/cgit/389/ds.git/
at hudson.plugins.git.GitAPI.clone(GitAPI.java:273)
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1044)
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2387)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
Caused by: hudson.plugins.git.GitException: Command "git clone --progress -o origin http://git.fedorahosted.org/cgit/389/ds.git/ <http://jenkins.cloud.fedoraproject.org/job/389-ds-base/ws/"> returned status code 128:
stdout: Cloning into '<http://jenkins.cloud.fedoraproject.org/job/389-ds-base/ws/'...>
stderr: error: Failed connect to git.fedorahosted.org:443; Connection refused (curl_result = 7, http_code = 301, sha1 = 2b973befec06d8d60b34ec77c6e73ea3bdea110f)
error: Unable to find 767531d56226475e14aa4b9a0474fdfbd4a65b79 under http://git.fedorahosted.org/cgit/389/ds.git
Cannot obtain needed tree 767531d56226475e14aa4b9a0474fdfbd4a65b79
while processing commit 473fc77f98eafb1062683abee7b7b00c54ea4f13.
error: Fetch failed.
at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:897)
at hudson.plugins.git.GitAPI.access$000(GitAPI.java:42)
at hudson.plugins.git.GitAPI$1.invoke(GitAPI.java:269)
at hudson.plugins.git.GitAPI$1.invoke(GitAPI.java:248)
at hudson.FilePath.act(FilePath.java:904)
at hudson.FilePath.act(FilePath.java:877)
at hudson.plugins.git.GitAPI.clone(GitAPI.java:248)
... 12 more
Trying next repository
ERROR: Could not clone repository
FATAL: Could not clone
hudson.plugins.git.GitException: Could not clone
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1056)
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2387)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
https://fedorahosted.org/389/ticket/197https://fedorahosted.org/389/attachment/ticket/197/0001-Ticket-197-BDB-back…
Bug description: Even if entries in the database and changes in the
changelog database are deleted/trimmed, the unused pages of the data-
bases were not returned to the filesystem.
Fix description: This patch calls the compact API that Berkeley DB
provides, which compacts the database.
2 config parameters are introduced to specify the interval of the
compact calls.
Primary DBs (id2entry):
dn: cn=config,cn=ldbm database,cn=plugins,cn=config
nsslapd-db-compactdb-interval: <seconds>
Changelog DBs:
dn: cn=changelog5,cn=config
nsslapd-changelogcompactdb-interval: <seconds>
By default, 2592000 seconds (30 days)
https://fedorahosted.org/389/ticket/47488https://fedorahosted.org/389/attachment/ticket/47488/0001-Ticket-47488-User…
Bug description: When processing a DN from AD, the DN is passed to
a helper function is_subject_of_agreement_remote (windows_protocol_
util.c) to check if the DN is a subject of the sync service or not.
The helper function was checking if the AD DN is just one-level
child of the agreement subtree top (nsds7WindowsReplicaSubtree) but
not the subtree-level descendents. Note: the DN is an original one
in AD, which has not be flattened yet. Therefore, the AD entry was
determined not to be synchronized.
Fix description: This bug was fixed in the master tree with the
ticket #521 <https://fedorahosted.org/389/ticket/521> - modrdn +
NSMMReplicationPlugin - Consumer failed to
replay change.
3) is_subject_of_agreement_remote (windows_protocol_util.c):
When checking if the entry was in the subtree defined in the
agreement or not, it returned true only if the entry is a
direct child of the agreement subtree top. This patch returns
true if the entry is the further descendent of the subtree.
The fix is back ported to 389-ds-base-1.3.1 branch.