Calendar
|
May '13 | |||||
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | 31 | ||
Archives
Tag Cloud
#asterisk #asterisk #voip #voip ACLs Active Directory AD ADAM Amanda Asterisk asterisk Benchmark Blog branding call centre callrecording Catalyst Clustering DBIC DBIx-Class Digium Directory Services Disaster Recovery Dojo eDirectory Enterprise Backups Enterprise Directory Fedora Fedora Directory Server Fedora DS Flexitime freeswitch FreeSWITCH IAM Identity Management IDM IP Telephony Isode Jabber Jabber/XMPP JavaScript Kamailio ldap LDAP LDAP Replication LDAP Schema linux Linux M-Vault Microsoft Microsoft FUD MirrorMode MySQL NBD ofcom OID on-hold OpenDS OpenLDAP openldap OpenLDAP Newsletter OpenLDAP Quick Tips OpenSIPS opensips open source Open Source Oracle Oracle Internet Directory PABX Perl pikatechnologies pikawarp PostgreSQL Quad-Core RDBMS Red Hat Replication RT Samba Sendmail SIP sip Squid SSO Sun Sun Microsystems SunOne suretec Suretec suretec telecom surevoip SureVoIP Symas Symas OpenLDAP UC UM Unified Communications VoIP voip X.500 XMPP
Tuesday, November 25. 2008
OpenLDAP Quick Tips: Regularly upgrade OpenLDAP!
Hi All,
Here's my 10th tip in the "OpenLDAP Quick Tips" series:
"You want to stay up to date with the latest version of OpenLDAP to benefit from bug fixes":
There's never been a better time to upgrade to the 2.4 series. It's actually very easy. If there haven't been any significant core changes between releases (excluding a 2.3.x to 2.4.x upgrade), then you can easily just install a new version on top of the existing one and restart.
If there has been a Berkeley DB change or any form data storage change (indexing etc.) then you should follow these steps:
1. Stop the current server when convenient
2. slapcat the current data out
3. Clear out the current data directory (/usr/local/var/openldap-data/) leaving DB_CONFIG in place
4. Perform the software upgrades
5. slapadd the exported data back into the directory
6. Start the server
It is recommended to do the above anyway, just to make sure as you can always start fresh with exported data.
Obviously this doesn't cater for any complicated deployments like MirrorMode or N-Way Multi-Master, but should you need advice or help, you can use either commercial support or community support to help you....or contact Suretec.
Thanks,
Gavin.
If you have an entry for our "OpenLDAP Quick Tips" series, why not e-mail your tip to us.
P.S. For direct access to this section, you can click OpenLDAP Quick Tips.
Here's my 10th tip in the "OpenLDAP Quick Tips" series:
"You want to stay up to date with the latest version of OpenLDAP to benefit from bug fixes":
There's never been a better time to upgrade to the 2.4 series. It's actually very easy. If there haven't been any significant core changes between releases (excluding a 2.3.x to 2.4.x upgrade), then you can easily just install a new version on top of the existing one and restart.
If there has been a Berkeley DB change or any form data storage change (indexing etc.) then you should follow these steps:
1. Stop the current server when convenient
2. slapcat the current data out
3. Clear out the current data directory (/usr/local/var/openldap-data/) leaving DB_CONFIG in place
4. Perform the software upgrades
5. slapadd the exported data back into the directory
6. Start the server
It is recommended to do the above anyway, just to make sure as you can always start fresh with exported data.
Obviously this doesn't cater for any complicated deployments like MirrorMode or N-Way Multi-Master, but should you need advice or help, you can use either commercial support or community support to help you....or contact Suretec.
Thanks,
Gavin.
If you have an entry for our "OpenLDAP Quick Tips" series, why not e-mail your tip to us.
P.S. For direct access to this section, you can click OpenLDAP Quick Tips.
Posted by Gavin Henry
in OpenLDAP, Open Source, Suretec
at
09:23
| Comments (2)
| Trackbacks (0)
Defined tags for this entry: Directory Services
, Enterprise Backups
, Enterprise Directory
, IAM
, Identity Management
, IDM
, ldap
, LDAP
, LDAP Replication
, LDAP Schema
, Linux
, openldap
, OpenLDAP
, OpenLDAP Newsletter
, OpenLDAP Quick Tips
, Open Source
, Replication
, Suretec
, Symas
, X.500
, Enterprise Backups, Enterprise Directory, IAM, Identity Management, IDM, ldap, LDAP, LDAP Replication, LDAP Schema, Linux, openldap, OpenLDAP, OpenLDAP Newsletter, OpenLDAP Quick Tips, Open Source, Replication, Suretec, Symas, X.500
Trackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
Upgrading from 2.3. to 2.4. with a bunch of schemas and a clean installation from debian/ubuntu does not work out of the box. plus 2.4 has a new scheme of "cn=config" elements you want to learn.
"cn=config" was in 2.3, so it's not new in 2.4.
That sounds like a debian packaging problem. You would also use the schemas that come with 2.4 as the core ones come with fixes etc. If you've done your own then 2.4 is more standards compliant so some things have changed.
If you have exact errors etc. I'd kindly ask you to file a bug report or post to the openldap-software mailing list so we can help.
Thanks,
Gavin.
Site Feeds
Quicksearch
Comments
Mon, 10.12.2012 09:35
Wed, 21.03.2012 11:47
Wed, 21.03.2012 10:50
Links
Categories
Powered by
