September 2011 - 389-users - Fedora Mailing-Lists

by Rich Megginson

The EPEL-6 repo has been fixed. You can now install 389-ds-base-1.2.9.9 via yum. See http://directory.fedoraproject.org/wiki/Download for more information.

12 years, 7 months

2
2
0 / 0

adding schema to 389ds

by Karoly Czovek

Hi guys, I'm just trying to extend 389ds schemes with this schema: http://proyectofedora.org/wiki/Fedora_Directory_Server_99zimbra.ldif but i get the following errors, any easy workaround/fix about? DS version is 1.2.8rc2 Starting dirsrv: ds-swz...[14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraAccountClientAttr] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraAccountExtraObjectClass] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraAllowFromAddress] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraArchiveAccount] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraArchiveMailFrom] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraAuthLdapURL] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the EQUALITY matching rule [octetStringMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.40] for the attribute [zimbraAuthTokenKey] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraAvailableSkin] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraCOSInheritedAttr] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraCalResContactEmail] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraCertAuthorityCertSelfSigned] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraCertAuthorityKeySelfSigned] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraComponentAvailable] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraDebugInfo] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraDomainAdminModifiableAttr] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraDomainInheritedAttr] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraForeignPrincipal] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraGalLdapAttrMap] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraGalLdapFilterDef] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraGalLdapURL] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraHttpProxyURL] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraImapBindAddress] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraImapDisabledCapability] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraImapSSLBindAddress] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraImapSSLDisabledCapability] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraInstalledSkin] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraLmtpBindAddress] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraLogHostname] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraMailAddress] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraMailAlias] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraMailCanonicalAddress] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraMailCatchAllAddress] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraMailDeliveryAddress] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraMailForwardingAddress] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraMailHost] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraMailHostPool] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraMailTransport] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraMailboxLocationBeforeMove] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraMemberOf] [14/Sep/2011:14:21:34 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraMimeFileExtension] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraMtaAuthHost] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraMtaAuthURL] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraMtaBlockedExtension] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraMtaCommonBlockedExtension] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraMtaMyNetworks] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraMtaRecipientDelimiter] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraMtaRelayHost] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraMtaRestriction] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraNewMailNotificationBody] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraNewMailNotificationFrom] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraNewMailNotificationSubject] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraNotifyBindAddress] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraNotifySSLBindAddress] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the EQUALITY matching rule [octetStringMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.40] for the attribute [zimbraPasswordHistory] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the EQUALITY matching rule [generalizedTimeMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.24] for the attribute [zimbraPasswordLockoutFailureTime] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraPop3BindAddress] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraPop3SSLBindAddress] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraPrefCalendarInitialCheckedCalendars] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraPrefForwardReplyPrefixChar] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraPrefHtmlEditorDefaultFontColor] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraPrefHtmlEditorDefaultFontFamily] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraPrefHtmlEditorDefaultFontSize] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraPrefMailForwardingAddress] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraPrefNewMailNotificationAddress] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraPrefOutOfOfficeDirectAddress] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraPrefTimeZoneId] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraPrefWhenInFolderIds] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraPrefWhenSentToAddresses] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraProxyAllowedDomains] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraProxyCacheableContentTypes] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraRedoLogProvider] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraRemoteManagementCommand] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraRemoteManagementPrivateKeyPath] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraRemoteManagementUser] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraServerInheritedAttr] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraServiceEnabled] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraServiceInstalled] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraShareInfo] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraSmtpHostname] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraSpamIsNotSpamAccount] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraSpamIsSpamAccount] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for[root@ds_sws]:/etc/dirsrv/slapd-ds-swz/schema#> the attribute [zimbraSpamSubjectTag] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraSpellCheckURL] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraSshPublicKey] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraSslCaCert] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.26] for the attribute [zimbraSslCaKey] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraTableMaintenanceOperation] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraTimeZoneDaylightDtStart] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraTimeZoneDaylightOffset] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraTimeZoneDaylightRRule] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraTimeZoneStandardDtStart] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraTimeZoneStandardOffset] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraTimeZoneStandardRRule] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraVirtualHostname] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraZimletAvailableZimlets] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraZimletHandlerConfig] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseExactSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraZimletScript] [14/Sep/2011:14:21:35 +0200] attr_syntax_create - Error: the SUBSTR matching rule [caseExactSubstringsMatch)] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [zimbraZimletUserProperties] [14/Sep/2011:14:21:35 +0200] dse - The entry cn=schema in file /etc/dirsrv/slapd-ds-swz/schema/99zimbra.ldif is invalid, error code 21 (Invalid syntax) - object class zimbraAccount: Unknown allowed attribute type "gn" [14/Sep/2011:14:21:35 +0200] dse - Please edit the file to correct the reported problems and then restart the server. -- Karoly CZOVEK Global Systems Administrator MoveOne IT Department Eastern Europe - Balkans - CIS& Central Asia - Middle East& Africa - Asia Pacific phone: +36 1 266 0181 - ext.6710 mobile: +36 70 708 9953 skype: mo_karoly.czovek email: karoly.czovek(a)moveoneinc.com web: http://www.moveoneinc.com

12 years, 7 months

3
4
0 / 0

Certificate based Authentication

by David Partridge

Attempting to configure Certificate based authentication with SASL External such that if TLS successfully completed the user is authenticated by certificate DN as an authenticated user without the requirement for the corresponding DN to be present in the Directory Server. nsslapd-sasl-force-external: on is part of the puzzle what other SASL mapping configurations are required to allow successful completion of authenticated access. We can complete OU, O, C RDN values can be mapped and certificate trust for clients properly configured, but cannot necessarily make any mappings on certificate CN RDN values. Example cert DN value: cn=[Lastname.Firstname.MI], OU=[Affiliation], O=[Company Name], C=[ISO 3166 Country Code] were OU could be multivalued in cert RDN. David M. Partridge dpartridge(a)tangible.net

12 years, 7 months

2
1
0 / 0

Certificate based Authentication

by David Partridge

Attempting to configure Certificate based authentication with SASL External such that if TLS successfully completed the user is authenticated by certificate DN as an authenticated user without the requirement for the corresponding DN to be present in the Directory Server. nsslapd-sasl-force-external: on is part of the puzzle what other SASL mapping configurations are required to allow successful completion of authenticated access. We can complete OU, O, C RDN values can be mapped and certificate trust for clients properly configured, but cannot necessarily make any mappings on certificate CN RDN values. Example cert DN value: cn=[Lastname.Firstname.MI], OU=[Affiliation], O=[Company Name], C=[ISO 3166 Country Code] were OU could be multivalued in cert RDN. David M. Partridge dpartridge(a)tangible.net

12 years, 7 months

1
0
0 / 0

RH5 upgrade Problem Directoryserver

by Neuhold Christian (TSA)

Hello, I tried an upgrade with "yum upgrade" on our Redhat 5 x86_64 machine. But I get following error: ->yum upgrade Loaded plugins: rhnplugin, security Skipping security plugin, no data Setting up Upgrade Process Resolving Dependencies Skipping security plugin, no data --> Running transaction check ---> Package 389-admin.x86_64 0:1.1.23-1.el5 set to be updated ---> Package 389-admin-console.noarch 0:1.1.8-1.el5 set to be updated ---> Package 389-admin-console-doc.noarch 0:1.1.8-1.el5 set to be updated --> Processing Dependency: libadminutil.so.1()(64bit) for package: 389-dsgw --> Processing Dependency: libadmsslutil.so.1()(64bit) for package: 389-dsgw ---> Package 389-adminutil.x86_64 0:1.1.14-1.el5 set to be updated ---> Package 389-console.noarch 0:1.1.7-1.el5 set to be updated ---> Package 389-ds-base.x86_64 0:1.2.9.9-1.el5 set to be updated ---> Package 389-ds-base-devel.x86_64 0:1.2.9.9-1.el5 set to be updated ---> Package 389-ds-base-libs.x86_64 0:1.2.9.9-1.el5 set to be updated ---> Package 389-ds-console.noarch 0:1.2.6-1.el5 set to be updated ---> Package 389-ds-console-doc.noarch 0:1.2.6-1.el5 set to be updated ---> Package 389-dsgw.x86_64 0:1.1.7-1.el5 set to be updated ---> Package ghostscript.i386 0:8.70-6.el5_7.3 set to be updated ---> Package ghostscript.x86_64 0:8.70-6.el5_7.3 set to be updated ---> Package idm-console-framework.noarch 0:1.1.7-5.el5 set to be updated --> Finished Dependency Resolution 389-dsgw-1.1.7-1.el5.x86_64 from epel has depsolving problems --> Missing Dependency: libadmsslutil.so.1()(64bit) is needed by package 389-dsgw-1.1.7-1.el5.x86_64 (epel) 389-dsgw-1.1.7-1.el5.x86_64 from epel has depsolving problems --> Missing Dependency: libadminutil.so.1()(64bit) is needed by package 389-dsgw-1.1.7-1.el5.x86_64 (epel) Error: Missing Dependency: libadminutil.so.1()(64bit) is needed by package 389-dsgw-1.1.7-1.el5.x86_64 (epel) Error: Missing Dependency: libadmsslutil.so.1()(64bit) is needed by package 389-dsgw-1.1.7-1.el5.x86_64 (epel) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest The program package-cleanup is found in the yum-utils package. yum provides */libadminutil.so.1 Loaded plugins: rhnplugin, security 389-adminutil-1.1.13-1.el5.x86_64 : Utility library for 389 administration Repo : installed Matched from: Filename : /usr/lib64/libadminutil.so.1 Is this failure known? br cnu80 -~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~ This message may contain confidential and/or privileged information intended only for the addressee. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Any views expressed in this message are those of the individual sender and may not necessarily reflect the opinions of austriamicrosystems AG. -~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~ Diese E-Mail enthaelt moeglicherweise vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Etwaige in dieser E-mail geaeusserte Ansichten und Meinungen stammen vom Versender dieser Nachricht und muessen nicht notwendigerweise mit den Meinungen und Ansichten von austriamicrosystems AG uebereinstimmen. ~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~

12 years, 7 months

4
10
0 / 0

Redhat5 Client not working "pam_ldap: ldap_initialize Bad parameter to an ldap routine"

by Neuhold Christian (TSA)

Hello, we migrate our NIS system to 389-directory server. To support our old systems, we use still "descrypt" and no md5. I configured our Redhat4 machines with the command: authconfig --disablemd5 --passalgo descrypt --enablelocauthorize \ --disablecache --kickstart --disablenis --disablekrb5 -disablewinbind \ --disablehesiod --enableldap --enableldapauth -ldapserver="XXX" \ --ldapbasedn="dc=XXX,dc=XXX" -enableshadow RH4 (x86_64) is working fine. (Change user, change password and so on). Now we try to update our workstations to RH5 update 7 (x86_64). I tried the same command, but I get following error message: /var/log/secure "su: pam_ldap: ldap_initialize Bad parameter to an ldap routine" Some ideas? thanks, br cnu80 -~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~ This message may contain confidential and/or privileged information intended only for the addressee. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Any views expressed in this message are those of the individual sender and may not necessarily reflect the opinions of austriamicrosystems AG. -~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~-~^~ Diese E-Mail enthaelt moeglicherweise vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Etwaige in dieser E-mail geaeusserte Ansichten und Meinungen stammen vom Versender dieser Nachricht und muessen nicht notwendigerweise mit den Meinungen und Ansichten von austriamicrosystems AG uebereinstimmen. ~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~.~-~

12 years, 7 months

1
0
0 / 0

java error on 389-console command

by Paul Robert Marino

a couple of days a ago I did a yum update on one of my boxes. one of the thing that updated was the 389-console rpm now every time i try to run it i get an error " The java class could not be loaded. java.lang.UnsupportedClassVersionError: (com/netscape/management/client/console/Console) bad major version at offset=6 " this is the version it updated to " rpm -qf /usr/bin/389-console 389-console-1.1.7-1.el6.noarch " I am currently running Red Hat Enterprise Linux Server release 6.1 (Santiago) x86_64 is there a know bug or issue that can be worked around that might cause this

12 years, 7 months

2
10
0 / 0

LDAP Secondary not returning the same as primary with getent passwd

by Dan H. Eicher

Synopsis: getent passwd {user} works on secondary and primary server, getent passwd fails (does not return all users) on secondary, works correctly on primary. getent passwd {username} - works when pointing to both primary and secondary. getent passwd | grep {username} only works if pointed to primary. On Primary: % getent passwd | wc 11482 29170 937571 On Secondary: % getent passwd | wc 2039 4994 165383 ldapsearch by uid works in both cases. The only change I make is changing ldap.conf from ldap01 (primary) to ldap02 (secondary). Any tips appreciated. Dan

12 years, 7 months

3
3
0 / 0

Announcing 389 Directory Server version 1.2.9.9

by Rich Megginson

The 389 Project team is pleased to announce the release of 389-ds-base-1.2.9.9. This release is primarily to fix bugs found in 1.2.9.x testing. NOTE: EL6.1 is fully supported. See http://port389.org/wiki/Download for information about how to set up your yum repositories. EL6.0 is not and will not be supported. Installation yum install 389-ds setup-ds-admin.pl Upgrade yum upgrade setup-ds-admin.pl -u How to Give Feedback * Go to https://admin.fedoraproject.org/updates * In the Search box in the upper right hand corner, type in the name of the package * In the list, find the version and release you are using (if you're not sure, use rpm -qi <package name> on your system) and click on the release * On the page for the update, scroll down to "Add a comment" and provide your input Or just send us an email to 389-users(a)lists.fedoraproject.org If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389 Reporting Bugs If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389 More Information * Release Notes - http://port389.org/wiki/Release_Notes * Install_Guide - http://port389.org/wiki/Install_Guide * Download - http://port389.org/wiki/Download

12 years, 7 months

1
0
0 / 0

webmin.schema

by SHAW-MILLER, JOHN (Synetrix)

All, Thanks in advance for any advice..... Has anyone any previous experience in converting webmin.schema to 99webmin.ldif? I have converted it - but my webmin system throws a wobbly whenever I try and configure it...... regards, John Shaw-Miller Senior Unix Consultant ISP Services ITNS Professional Services M: 07920 824938 F:01252 405605 E: john.shaw-miller(a)synetrix.co.uk <mailto:john.shaw-miller@synetrix.co.uk> E: john.shaw-miller(a)capita.co.uk <mailto:john.shaw-miller@capita.co.uk> Synetrix House, 49-51 Victoria Road Farnborough, Hampshire, GU14 7PA http://www.synetrix.co.uk.uk <http://www.synetrix.co.uk.uk/> Part of The Capita Group plc www.capita.co.uk <http://www.capita.co.uk> Synetrix (Holdings) Limited is a limited company registered in England and Wales. Registered number: 0349 1956. VAT number: GB618 1841 40. Registered office: Synetrix (Holdings) Ltd, 17-19 Rochester Row, London, SW1P 1QT. IMPORTANT NOTICE:This message is intended solely for the use of the Individual or organisation to whom it is addressed. It may contain privileged or confidential information. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you should not use, copy, alter, or disclose the contents of this message. All information or opinions expressed in this message and/or any attachments are those of the author and are not necessarily those of Synetrix Holdings Limited. Synetrix Holdings Limited accepts no responsibility for loss or damage arising from its use, including damage from virus.

12 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users September 2011