Issue 7801 - test033-glue-syncrepl with bdb/hdb gets stuck on ppc64
Summary: test033-glue-syncrepl with bdb/hdb gets stuck on ppc64
Status: VERIFIED SUSPENDED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: 2.4.39
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-18 07:53 UTC by jsynacek@redhat.com
Modified: 2020-03-20 18:38 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description jsynacek@redhat.com 2014-02-18 07:53:20 UTC
Full_Name: Jan Synacek
Version: 2.4.39
OS: GNU/Linux
URL: 
Submission from: (NULL) (209.132.186.34)


I configured openldap with --enable-bdb, --enable-hdb and --enable-mdb. No other
options were used.
Reproduced on a ppc64 system with kernel 3.10.0.

# ./run -b hdb test033-glue-syncrepl
Cleaning up test run directory leftover from previous run.
Running ./scripts/test033-glue-syncrepl for hdb...
running defines.sh
Running slapadd to build glued slapd databases...
Starting slapd 1 on TCP/IP port 9011...
Using ldapsearch to check that slapd 1 is running...
Starting slapd 2 on TCP/IP port 9012...
Using ldapsearch to check that slapd 2 is running...
Using ldapadd to populate subtree="ou=Information Technology
Division,ou=People,dc=example,dc=com" on port 9011...
Using ldapadd to populate subtree="ou=Groups,dc=example,dc=com" on port 9012...

After that, there is no output.

# ps afx
...
25204 pts/0    S+     0:00  |       \_ /bin/sh ./run -b hdb
test033-glue-syncrepl
25221 pts/0    S+     0:00  |           \_ /bin/sh
./scripts/test033-glue-syncrepl
25241 pts/0    Sl+    0:00  |               \_
/root/openldap-2.4.39/tests/../servers/slapd/slapd -s0 -f
/root/openldap-2.4.39/tests/testrun/slapd.1.conf -h ldap://localhost:9011/ -d
0x4105
25247 pts/0    Sl+    8:48  |               \_
/root/openldap-2.4.39/tests/../servers/slapd/slapd -s0 -f
/root/openldap-2.4.39/tests/testrun/slapd.2.conf -h ldap://localhost:9012/ -d
0x4105
25254 pts/0    S+     0:00  |               \_ ../clients/tools/ldapmodify -a -P
3 -x -D cn=Manager 2,dc=example,dc=com -w        -h localhost -p 9012 -f
./testdata/test-ordered.ldif -c
...
25131 pts/0    Sl     9:36 /root/openldap-2.4.39/tests/../servers/slapd/slapd
-s0 -f /root/openldap-2.4.39/tests/testrun/slapd.2.conf -h
ldap://localhost:9012/ -d 0x4105
...
Comment 1 Howard Chu 2014-02-28 20:57:10 UTC
jsynacek@redhat.com wrote:
> Full_Name: Jan Synacek
> Version: 2.4.39
> OS: GNU/Linux
> URL:
> Submission from: (NULL) (209.132.186.34)
>
>
> I configured openldap with --enable-bdb, --enable-hdb and --enable-mdb. No other
> options were used.
> Reproduced on a ppc64 system with kernel 3.10.0.
>
> # ./run -b hdb test033-glue-syncrepl
> Cleaning up test run directory leftover from previous run.
> Running ./scripts/test033-glue-syncrepl for hdb...
> running defines.sh
> Running slapadd to build glued slapd databases...
> Starting slapd 1 on TCP/IP port 9011...
> Using ldapsearch to check that slapd 1 is running...
> Starting slapd 2 on TCP/IP port 9012...
> Using ldapsearch to check that slapd 2 is running...
> Using ldapadd to populate subtree="ou=Information Technology
> Division,ou=People,dc=example,dc=com" on port 9011...
> Using ldapadd to populate subtree="ou=Groups,dc=example,dc=com" on port 9012...
>
> After that, there is no output.

First thing to look at is a gdb stack trace of both slapds, to see what 
threads are actually stuck and where. Also look at the log files in the 
testrun directory to see what was the last operation being performed.

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/

Comment 2 Quanah Gibson-Mount 2020-03-20 18:38:13 UTC
Needs data that was never provided to proceed any further.