I'm running into the same issue with upgrading Ian's 10.0.6 (development build) to 10.0.8 now (Ubuntu 18.04). But I'm not sure what I'm supposed to see in terms of invalid attributes? This is my log:scantec,
I missed your post, no I only edited the ldap dump not the config.
Depending on when your develop branch was built, there could be 80+ new attributes.
However, check the zmsetup log for the line:
'Updating zimbraLDAPSchemaVersion to version'
below this will be a list of the current invalid attributes for your installation.
The installation I worked with had only 10 or so invalid attributes that needed to be removed from the ldap dump.
Code:
Thu May 9 01:02:08 2024 *** Running as zimbra user: /opt/zimbra/bin/ldap statusslapd running pid: 25162Thu May 9 01:02:09 2024 already running.Thu May 9 01:02:09 2024 Getting enabled services from ldapThu May 9 01:02:11 2024 Marking zimbra-core as installed. Services for zimbra-core will be enabled.Thu May 9 01:02:11 2024 Marking zimbra-ldap as installed. Services for zimbra-ldap will be enabled.Thu May 9 01:02:11 2024 Marking zimbra-logger as installed. Services for zimbra-logger will be enabled.Thu May 9 01:02:11 2024 Marking zimbra-mta as installed. Services for zimbra-mta will be enabled.Thu May 9 01:02:11 2024 Marking zimbra-dnscache as installed. Services for zimbra-dnscache will be enabled.Thu May 9 01:02:11 2024 Marking zimbra-snmp as installed. Services for zimbra-snmp will be enabled.Thu May 9 01:02:11 2024 Marking zimbra-store as installed. Services for zimbra-store will be enabled.Thu May 9 01:02:11 2024 Marking zimbra-apache as installed. Services for zimbra-apache will be enabled.Thu May 9 01:02:11 2024 Marking zimbra-spell as installed. Services for zimbra-spell will be enabled.Thu May 9 01:02:11 2024 Marking zimbra-memcached as installed. Services for zimbra-memcached will be enabled.Thu May 9 01:02:11 2024 Marking zimbra-proxy as installed. Services for zimbra-proxy will be enabled.Thu May 9 01:02:12 2024 Updating zimbraLDAPSchemaVersion to version '1673397105'Thu May 9 01:02:12 2024 entering function: gcf zimbraLDAPSchemaVersion=1673397105Thu May 9 01:02:12 2024 Updating cached global config attribute zimbraLDAPSchemaVersion=1673397105Thu May 9 01:02:12 2024 *** Running as zimbra user: /opt/zimbra/bin/zmprov -r -m -l mcf zimbraLDAPSchemaVersion '1673397105'ERROR: account.INVALID_ATTR_NAME (invalid attr name: invalid attr name - unable to modify attributes: ldap host=meel.halfgaar.net:389: entry update failed) (cause: com.zimbra.cs.ldap.LdapException$LdapInvalidAttrNameException invalid attr name - unable to modify attributes: ldap host=meel.halfgaar.net:389: entry update failed)Thu May 9 01:02:14 2024 Updating global config and COS's with attributes introduced after 10.0.6_GA...Thu May 9 01:02:14 2024 *** Running as zimbra user: zmjava com.zimbra.cs.account.ldap.upgrade.LdapUpgrade -b 27075 -v 10.0.6_GA--------------com.zimbra.cs.account.ldap.upgrade.LdapUpgrade -b 27075 -v 10.0.6_GA--------------------------------------------Upgrading global config:Checking global config attribute: zimbraHelpModernURL[11.0.0] skipping - does not have a default valueChecking global config attribute: zimbraMailSieveScriptMaxSize[11.0.0] skipping - already has value: 0 etcetcStatistics: Posted by halfgaar — Wed May 08, 2024 11:46 pm