HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Unresolved symbol: __dbm_do_nextkey
Operating System - HP-UX
1832541
Members
6133
Online
110043
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2004 12:58 AM
06-29-2004 12:58 AM
Unresolved symbol: __dbm_do_nextkey
I've got hp-ux 11.11, gcc 3.3.3, openssl 0.9.7c, apache 1.3.29 and mod_ssl 2.8.16. Everything compiles up fine, but when trying to start apache in SSL mode, I get:
/usr/lib/dld.sl: Unresolved symbol: __dbm_do_nextkey (code) from /usr/lib/libdbm.1
Syntax error on line 207 of /home/kferry/apachessl/conf/httpd.conf:
Cannot load /home/kferry/apachessl/libexec/libssl.so into server: No such file or directory
./apachectl startssl: httpd could not be started
It runs fine without SSL, and it has no problem with other modules such as mod_proxy. Any ideas on how to fix this?
/usr/lib/dld.sl: Unresolved symbol: __dbm_do_nextkey (code) from /usr/lib/libdbm.1
Syntax error on line 207 of /home/kferry/apachessl/conf/httpd.conf:
Cannot load /home/kferry/apachessl/libexec/libssl.so into server: No such file or directory
./apachectl startssl: httpd could not be started
It runs fine without SSL, and it has no problem with other modules such as mod_proxy. Any ideas on how to fix this?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2004 01:34 PM
06-30-2004 01:34 PM
Re: Unresolved symbol: __dbm_do_nextkey
I'd probably start by working backwards from libssl.so, does it exist in the directory given? /home/kferry/apachessl/libexec
If it does, does it have read access for everyone? What are the contents of lines 206 and 207 of the httpd.conf file?
That's all I can think of at the moment.
Cheers
Steven
If it does, does it have read access for everyone? What are the contents of lines 206 and 207 of the httpd.conf file?
That's all I can think of at the moment.
Cheers
Steven
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2004 08:57 PM
06-30-2004 08:57 PM
Re: Unresolved symbol: __dbm_do_nextkey
It turns out that I needed --enable-rule=SSL_SDBM when configuring mod_ssl. Here's the text from the modssl install doc:
NOTE: The --enable-rule=SSL_SDBM option enabled the use of the built-in SDBM library instead of a custom defined or vendor supplied DBM library. This can be useful when the vendor DBM library is buggy or restricts the data size too dramatically (for SSL sessions to be cacheable the DBM library should allow more than 1KB of data to be stored under a particular key).
NOTE: The --enable-rule=SSL_SDBM option enabled the use of the built-in SDBM library instead of a custom defined or vendor supplied DBM library. This can be useful when the vendor DBM library is buggy or restricts the data size too dramatically (for SSL sessions to be cacheable the DBM library should allow more than 1KB of data to be stored under a particular key).
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP