I've attached my RT_SiteConfig to this email. I'm not using the Assets
extension, which is mind-boggling. All I'd used was the LDAP extension,
which you'll see is commented out. This is driving me crazy, as it's the
last hurdle before I can roll out my pilot program.
Any help would be greatly appreciated. Thanks!
Sincerely,
Aaron Lush
Network Administrator
South Central Community School Corporation
(219) 767-2266 ext.
On Fri, Feb 26, 2016 at 4:23 PM, Joop wrote:
> On 26-2-2016 22:39, Lush, Aaron wrote:
>
> No w I am getting the following error when upgrading, after using the
> UPDATE command listed below. This only occurs when upgrading from 4.3.9 to
> 4.3.10. Any further advice would be much appreciated!
>
> *Processing 4.3.10*
> *Now populating database schema.*
> *[19046] [Fri Feb 26 21:33:59 2016] [critical]: DBD::mysql::st execute
> failed: Table 'Assets' already exists at
> /tmp/rt-4.4.0/sbin/../lib/RT/Handle.pm line 552.
> (/tmp/rt-4.4.0/sbin/../lib/RT.pm:390)*
> *DBD::mysql::st execute failed: Table 'Assets' already exists at
> /tmp/rt-4.4.0/sbin/../lib/RT/Handle.pm line 552.*
> *Makefile:391: recipe for target 'upgrade-database' failed*
>
> That suggests that you have been using the Assets extension in 4.2.
> I didn't get that error when upgrading from 4.0.23 to 4.4, besides that ,
> I'm using postgres as a db backend but that shouldn't matter.
>
> Joop
>
> PS: its 23:20 for me so time to get some sleep :-)
>
>
> -
> RT 4.4 and RTIR Training Sessions (
> http://bestpractical.com/services/training.html)
> * Hamburg Germany - March 14 & 15, 2016
> * Washington DC - May 23 & 24, 2016
>
--
Email Confidentiality Notice: This email message, including all
attachments, is for the sole use of the intended recipient(s) and contains
confidential information. If you are not the intended recipient, you may
not use, disclose, print, copy or disseminate this information. Please
reply and notify the sender, delete the message and any attachments and
destroy all copies.
# Any configuration directives you include here will override
# RT's default configuration file, RT_Config.pm
#
# To include a directive here, just copy the equivalent statement
# from RT_Config.pm and change the value. We've included a single
# sample value below.
#
# This file is actually a perl module, so you can include valid
# perl code, as well.
#
# The converse is also true, if this file isn't valid perl, you're
# going to run into trouble. To check your SiteConfig file, use
# this command:
#
# perl -c /path/to/your/etc/RT_SiteConfig.pm
#
# You must restart your webserver after making changes to this file.
# Uncomment to set logging to DEBUG.
Set( $LogToSyslog, "warning");
# RT web configuration.
Set( $rtname, '');
Set( $RTAddressRegexp,'^rt(\+[a-z]+)?\@example\.com$');
Set( $CorrespondAddress, '');
Set( $CommentAddress, '');
Set( $Organization, '');
Set( $Timezone, 'US/Central');
Set( $WebDomain, '');
Set( $WebPort, 443);
Set( $WebPath, '');
Set( $DatabasePassword, '');
Set( $WebRemoteUserAuth , '1');
Set( $WebFallbackToRTLogin , '1');
Set( $WebRemoteUserGecos , undef);
Set( $WebRemoteUserAutocreate , '1');
Set( $PreferRichText, '0');
# You must install Plugins on your own, this is only an example
# of the correct syntax to use when activating them:
# Plugin( "RT::Extension::SLA" );
# Plugin( "RT::Authen::ExternalAuth" );
# Plugin( "RT::Extension::LDAPImport" );This has been
incorporated into 4.4
## LDAP Configurations
# LDAP Authentication
# Set( @Plugins, qw(RT::Authen::ExternalAuth RT::Extension::LDAPImport));
Incorporated into 4.4
## LDAP USER IMPORT
Set($ExternalAuth, 1);
Set($LDAPCreatePrivileged, 1);
Set($LDAPUpdateUsers, 1);
Set($LDAPHost,'');
Set($LDAPUser,'');
Set($LDAPPassword,'');
#my base OU for users, yours will probably differ
Set($LDAPBase,'');
Set($LDAPFilter, '(&(objectClass=person))');
Set($LDAPMapping, {
Name=> 'sAMAccountName',
EmailAddress=> 'mail',
Organization=> 'department',
RealName=> 'cn',
NickName=> 'givenName',
ExternalAuthId => 'sAMAccountName',
Gecos => 'sAMAccountName',
WorkPhone => 'telephoneNumber',
MobilePhone => 'mobile',
Address1=> 'streetAddress',
City=> 'l',
State => 'st',
Zip => 'postalCode',
Country => 'co'
});
## LDAP GROUP IMPORT AND MAPPINGS
Set($LDAPGroupMapping, {Name=> 'cn',
Member_Attr => 'member',
Member_Attr_Value => 'dn'});
#OU/basedn location of groups
Set($LDAPGroupBase, 'ou=SCGroups,dc=sc,dc=local');
# LDAP GROUP FILTERING, Below are 2 examples
#Set($LDAPGroupFilter, 'cn=Information Technology');
# 2 group import example
#Set($LDAPGroupFilter, '(|(cn=Information Technol
