[bug-notifications] [berkeleydb4 0003806]: CSWsendmail will not start with CSWbdb4 (v.4.1.25, REV=2009.06.26)

Mantis Bug Tracker noreply at opencsw.org
Fri Jul 31 22:30:17 CEST 2009


The following issue has been SUBMITTED. 
====================================================================== 
http://opencsw.org/bugtrack/view.php?id=3806 
====================================================================== 
Reported By:                ois_unix
Assigned To:                
====================================================================== 
Project:                    berkeleydb4
Issue ID:                   3806
Category:                   regular use
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2009-07-31 22:30 CEST
Last Modified:              2009-07-31 22:30 CEST
====================================================================== 
Summary:                    CSWsendmail will not start with CSWbdb4
(v.4.1.25,REV=2009.06.26)
Description: 
Platform is fresh install of Solaris 10 SPARC (May 2009 Release). Patched
with the latest available Solaris vendor updates. Installed CSWsendmail
(v.8.14.2,REV=2007.12.17), which considers CSWbdb4 a dependency and
installs it automatically. When CSWsendmail tried to start, it reported an
error "Berkeley DB version mismatch: compiled against 4.2.52, run-time
linked against 4.7.25". CSWsendmail then transitioned to maintenance mode.

Compared the version that worked, CSWbdb4
(v.4.2.52,REV=2008.02.23_rev=p5), to the latest version available: CSWbdb4
(v.4.1.25,REV=2009.06.26). There appears to be a disparity of total blocks
in the /opt/csw/bdb4/lib directory. Total for v.4.2.52 (the old package) in
that directory is 22,204. Total for v.4.1.25 is 30.

Uninstalling CSWbdb4 (v.4.1.25,REV=2009.06.26) and reinstalling CSWbdb4
(v.4.2.52,REV=2008.02.23_rev=p5) immediately brought CSWsendmail up as
expected.
======================================================================




More information about the bug-notifications mailing list