[rt-users] Emoji Implementation?

[Lush, Aaron]

Is this the latest Emoji package to implement into RT?
http://search.cpan.org/~kawasaki/Unicode-Emoji-E4U-0.03/lib/Unicode/Emoji/E4U.pm

The Faculty at the school I work do love their emoji, so if I implement
them into our ticketing system, I feel it will take a little of the rigid
edge off their new ticketing system.

Sincerely,

Aaron Lush
Network Administrator
South Central Community School Corporation
(219) 767-2266 ext. 

-- 
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. 
-
RT 4.4 and RTIR training sessions, and a new workshop day! 
https://bestpractical.com/training
* Boston - October 24-26
* Los Angeles - Q1 2017

Re: [rt-users] SSO (Single Sign-On) for RT

[Lush, Aaron]

Which version of RT are you running?

Sincerely,

Aaron Lush
Network Administrator
South Central Community School Corporation
(219) 767-2266 ext. 

On Tue, May 17, 2016 at 12:06 PM, t s  wrote:

> Anyone have any direction on how to set up SSO for RT for Windows Active
> Directory?
>
>
> I am currently in the middle of following this set of directions from a
> SafeSquid app (
> https://www.safesquid.com/content-filtering/integrating-linux-host-windows-ad-kerberos-sso-authentication)
>  that
> seems like it would mostly apply to set up the service principals, user
> accounts, etc.  This seems like the best set of directions I could find,
> unless anyone knows of any that are better?  Most sites seem to assume
> Kerberos is already set up and working with the appropriate permissions.
>
>
> 
> Integrating a Linux Host with a Windows AD for Kerberos ...
> 
> www.safesquid.com
> Validate that IP of all our systems are resolvable by our DNS provider.
> Add the Linux host safesquid1 as a New Host in the DNS server's
> configuration such that it's ...
>
>
> And I am using:
>
>
> Set($WebExternalAuth , 1);
> Set($WebFallbackToInternalAuth , undef);
> Set($WebExternalGecos , undef);
> Set($WebExternalAuto , undef);
>
> with the ExternalAuth extension.
>
>
> Also using nginx with mod_auth_kerb.
>
>
> Thanks,
>
> ts
>
> -
> RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
> * 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. 
-
RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
* Washington DC - May 23 & 24, 2016

Re: [rt-users] LDAP External Auth intermittent failure

[Lush, Aaron]

The only thing that jumps out to me is that under "External Settings" you
are domain\service name, whereas in Set$(  LDAPUser) you are using the
DistinguishedName. I had similar issues in my RT 4.4 deployment until I
made both of those settings follow the DistinguishedName.

Sincerely,

Aaron Lush
Network Administrator
South Central Community School Corporation
(219) 767-2266 ext. 

On Thu, May 5, 2016 at 10:05 AM, t s <zzz...@hotmail.com> wrote:

> Here you go:
>
> By the way, I just changed the line below from
> 'server'=>  'LDAPSERVER:389' to 'server'
> => 'LDAPSERVER.CORP.COMPANYNAME.NET:389' and restarted so I will see if
> that has any effect on the error not coming back up or not.
>
>
>
> Set($WebPath , "");
> Set($WebBaseURL, "http://rt.servername.companyname.com;);
>
> Set($RestrictReferrer, '0');
>
> Set($DatabaseAdmin, 'root');
>
> Set($LogoURL, 'https://bestpractical.com/images/logo.png');
> Set($WebDefaultStylesheet, 'rudder');
>
> Set($LogToFile, 'error');
>
> Set($SetOutgoingMailFrom, "rt_trac...@companyname.com");
> Set($SMTPFrom, "mail-out.smtp.companyname.com");
> Set($ParseNewMessageForTicketCcs, 1);
> Set($HomePageRefreshInterval, 120);
> Set($NotifyActor,1)
>
> Set($SendmailArguments, "-t");
> Set($MailCommand, "sendmail");
> Plugin( "RT::Authen::ExternalAuth" );
> Plugin('RT::Extension::LDAPImport');
>
>
> Set($LDAPHost,'LDAPSERVER.CORP.COMPANYNAME.NET:389');
> Set($LDAPUser,'cn=companyname\\svc.servicename,cn=Users,dc=Corp,DC=
> companyname,DC=net');
> Set($LDAPPassword,'password');
> Set($LDAPBase,
> 'OU=Corp,OU=Users,OU=companyname,DC=Corp,DC=companyname,DC=net');
> Set($LDAPFilter, '(&(objectClass=person))');
> Set($LDAPMapping, {Name => 'sAMAccountName', # required
>EmailAddress => 'mail',
>RealName => 'cn',
>WorkPhone=> 'telephoneNumber',
>Organization => 'departmentName'});
> Set($LDAPSizeLimit, 1000);
>
>
> Set($ExternalAuthPriority, ['companynameLDAP']);
> Set($ExternalInfoPriority, ['companynameLDAP']);
> Set($UserAutocreateDefaultsOnLogin, { Privileged => 0 } );
> Set($AutoCreateNonExternalUsers, 1);
>
>
>
> Set($ExternalSettings, {
>
> 'companynameLDAP'   =>  {
> 'type'  =>  'ldap',
> 'server'=>  'LDAPSERVER:389',
> 'user'  =>  'companyname
> \\svc.servicename',
> 'pass'  =>  'password',
> 'base'  =>
> 'OU=Corp,OU=Users,OU=companyname,DC=corp,DC=companyname,DC=net',
> 'filter'=>  '(objectClass=person)',
> 'd_filter'  =>  '(objectClass=asdf)',
> 'net_ldap_args' => [version =>  3   ],
> 'attr_match_list' => [
>  'Name',
>  'EmailAddress',
> ],
> 'attr_map' => {
> 'Name' => 'sAMAccountName',
> 'EmailAddress' => 'mail',
> 'Organization' => 'physicalDeliveryOfficeName',
> 'RealName' => 'cn',
> 'ExternalAuthId' => 'sAMAccountName',
> 'Gecos' => 'sAMAccountName',
> 'WorkPhone' => 'telephoneNumber',
> 'Address1' => 'streetAddress',
> 'City' => 'l',
> 'State' => 'st',
> 'Zip' => 'postalCode',
> 'Country' =>
> 'co'
> },
> },
> } );
>
>
>
> Set($WebRemoteuserAuth,1);
> Set($WebRemoteUserContinuous,1);
> Set($WebFallbackToRTLogin, undef);
> Set($WebRemoteUserGecos,1);
> Set($WebRemoteUserAutocreate,1);
>
> Set( $rtname, 'CompanyName RT' );
> Set( $CommentAddress, '' );
> Set( $CorrespondAddress, '' );
> Set( $DatabaseHost, 'localhost' );
> Set( $DatabaseName, 'rt_database' );
> Set( $DatabasePassword, 'password' );
> Set( $DatabasePort, '3306' );
> Set( $DatabaseType, 'mysql' );
> Set( $DatabaseUser, 'root' );
> Set( $Organization, 'companyname.com' );
> Set( $OwnerEmail, 'ow...@companyname.com' );
> Set( $SendmailPath, 'usr/lib/sendmail' );
> Set( $SendmailArguments, "-t");
> Set( $MailCommand, "sendmail");
> Set( $WebDomain, 'rt.servername.companyname.com' );
> Set( $WebPort, '443' );
>
> Set(%CustomFieldGroupings,
>'RT::Ticket' => [
>'Basics' => ['

Re: [rt-users] LDAP External Auth intermittent failure

[Lush, Aaron]

Would you please post your LDAP configuration in RT_SiteConfig.pm? Omitting
any sensitive information, of course.

Sincerely,

Aaron Lush
Network Administrator
South Central Community School Corporation
(219) 767-2266 ext. 

On Thu, May 5, 2016 at 8:15 AM, t s  wrote:

> Getting an intermittent "RT::Authen::ExternalAuth::LDAP::_GetBoundLdapObj
> Can't bind: LDAP_INVALID_CREDENTIALS 49" error very similar to:
> http://requesttracker.8502.n7.nabble.com/LDAP-External-Auth-intermittent-failure-td58611.html
> .
>
>
> 
> LDAP External Auth intermittent failure - RequestTracker
> 
> requesttracker.8502.n7.nabble.com
> LDAP External Auth intermittent failure. I'm using RT-4.2.7 installed from
> source, on ubuntu 14.04LTS. I've been trying to get the External Auth
> (0.23) extension ...
>
> Almost daily the External Auth will randomly start getting the binding
> error above and stop accepting LDAP logins, a simple restart of RT fixes
> the problem.  I'm using External Auth 0.25 and RT 4.2.12.  The only
> suggestion in the post above is to update RT but these are both recent
> stable versions.
>
>
> Anyone ran into this problem?  Is it an RT_SiteConfig problem?  I wouldn't
> think so since it works for around 24 hours and then stops.  Could it be
> some kind of network connectivity problem?
>
> -
> RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
> * 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. 
-
RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
* Washington DC - May 23 & 24, 2016

Re: [rt-users] LDAP Configuration

[Lush, Aaron]

Please post all of the recent RT entries in your SYSLOG, after running
rt-ldapimport. This should provide some insight into where your
ExternalAuth is failing.

Sincerely,

Aaron Lush
Network Administrator
South Central Community School Corporation
(219) 767-2266 ext. 

On Wed, Apr 20, 2016 at 10:18 AM, t s <zzz...@hotmail.com> wrote:

>
> Debug mode was successful.  What's my next step?
>
>
>
> ------
> *From:* Lush, Aaron <al...@scentral.k12.in.us>
> *Sent:* Wednesday, April 20, 2016 8:45 AM
> *To:* Travis Slusher
> *Cc:* rt-users@lists.bestpractical.com
> *Subject:* Re: [rt-users] LDAP Configuration
>
> Set your log to "debug" and then run rt-ldapimport. Please post what your
> syslog says concerning RT.
>
> Sincerely,
>
> Aaron Lush
> Network Administrator
> South Central Community School Corporation
> (219) 767-2266 ext. 
>
> On Wed, Apr 20, 2016 at 7:28 AM, Travis Slusher <zzz...@hotmail.com>
> wrote:
>
>> Having lots of trouble getting Request Tracker (4.2) hooked up with
>> ExternalAuth for LDAP.  I have nginx (1.8.0) working with LDAP so it
>> successfully authenticates to the login page using Active Directory, but it
>> is not passing the username and password to the login page, so the user
>> ends up having to login twice.
>>
>>
>> Please take a look, this is a huge headache!
>>
>>
>> Here is my nginx config and my RT_SiteConfig:
>>
>>
>> nginx config:
>>
>>
>> # For more information on configuration, see:
>> #   * Official English Documentation: http://nginx.org/en/docs/
>> #   * Official Russian Documentation: http://nginx.org/ru/docs/
>>
>> user nginx;
>> worker_processes auto;
>> error_log /var/log/nginx/error.log;
>> pid /run/nginx.pid;
>>
>> events {
>> worker_connections 1024;
>> }
>>
>>
>> http {
>> log_format  main  '$remote_addr - $remote_user [$time_local]
>> "$request" '
>>   '$status $body_bytes_sent "$http_referer" '
>>   '"$http_user_agent" "$http_x_forwarded_for"';
>>
>>   auth_ldap_cache_enabled on;
>>   auth_ldap_cache_expiration_time 1;
>>   auth_ldap_cache_size 1000;
>>
>>   ldap_server acmeLDAP {
>>
>> url
>> "ldap://ldapserver:389/OU=Corp,OU=Users,OU=acme,DC=corp,DC=acme,DC=net?sAMAccountName?sub?(objectClass=person)";
>> binddn "acme\\appaccount";
>> binddn_passwd "password";
>> group_attribute member;
>> group_attribute_is_dn on;
>> satisfy any;
>> require valid_user;
>> }
>>
>>
>>
>>
>>
>>
>> access_log  /var/log/nginx/access.log  main;
>>
>> sendfileon;
>> tcp_nopush  on;
>> tcp_nodelay on;
>> keepalive_timeout   65;
>> types_hash_max_size 2048;
>>
>> include /etc/nginx/mime.types;
>> default_typeapplication/octet-stream;
>>
>> # Load modular configuration files from the /etc/nginx/conf.d
>> directory.
>> # See http://nginx.org/en/docs/ngx_core_module.html#include
>> # for more information.
>> include /etc/nginx/conf.d/*.conf;
>>
>> server {
>> listen   80 default_server;
>> listen   [::]:80 default_server;
>> server_name  _;
>> root /usr/share/nginx/html;
>>
>> # Load configuration files for the default server block.
>> include /etc/nginx/default.d/*.conf;
>>
>> location / {
>> }
>>
>>  location  ^~ /phpmyadmin/ {
>>   alias /usr/share/phpmyadmin/;
>>
>>   location ~ \.php$ {
>>include fastcgi_params;
>>fastcgi_param SCRIPT_FILENAME $request_filename;
>>fastcgi_pass  localhost:9000;
>>   }
>>   index index.php;
>>  }
>>
>> error_page 404 /404.html;
>> location = /40x.html {
>> }
>>
>> error_page 500 502 503 504 /50x.html;
>> location = /50x.html {
>> }
>> error_page 403 = @login;
>> location @login {
>>   rewrite ^.* https://secure.example.com/login;
>> }
>> }
>>
>>
>>
>> server {
>> listen 80;
>> auth_ldap "Please enter your ldap user"

Re: [rt-users] LDAP Configuration

[Lush, Aaron]

Set your log to "debug" and then run rt-ldapimport. Please post what your
syslog says concerning RT.

Sincerely,

Aaron Lush
Network Administrator
South Central Community School Corporation
(219) 767-2266 ext. 

On Wed, Apr 20, 2016 at 7:28 AM, Travis Slusher  wrote:

> Having lots of trouble getting Request Tracker (4.2) hooked up with
> ExternalAuth for LDAP.  I have nginx (1.8.0) working with LDAP so it
> successfully authenticates to the login page using Active Directory, but it
> is not passing the username and password to the login page, so the user
> ends up having to login twice.
>
>
> Please take a look, this is a huge headache!
>
>
> Here is my nginx config and my RT_SiteConfig:
>
>
> nginx config:
>
>
> # For more information on configuration, see:
> #   * Official English Documentation: http://nginx.org/en/docs/
> #   * Official Russian Documentation: http://nginx.org/ru/docs/
>
> user nginx;
> worker_processes auto;
> error_log /var/log/nginx/error.log;
> pid /run/nginx.pid;
>
> events {
> worker_connections 1024;
> }
>
>
> http {
> log_format  main  '$remote_addr - $remote_user [$time_local]
> "$request" '
>   '$status $body_bytes_sent "$http_referer" '
>   '"$http_user_agent" "$http_x_forwarded_for"';
>
>   auth_ldap_cache_enabled on;
>   auth_ldap_cache_expiration_time 1;
>   auth_ldap_cache_size 1000;
>
>   ldap_server acmeLDAP {
>
> url
> "ldap://ldapserver:389/OU=Corp,OU=Users,OU=acme,DC=corp,DC=acme,DC=net?sAMAccountName?sub?(objectClass=person)";
> binddn "acme\\appaccount";
> binddn_passwd "password";
> group_attribute member;
> group_attribute_is_dn on;
> satisfy any;
> require valid_user;
> }
>
>
>
>
>
>
> access_log  /var/log/nginx/access.log  main;
>
> sendfileon;
> tcp_nopush  on;
> tcp_nodelay on;
> keepalive_timeout   65;
> types_hash_max_size 2048;
>
> include /etc/nginx/mime.types;
> default_typeapplication/octet-stream;
>
> # Load modular configuration files from the /etc/nginx/conf.d
> directory.
> # See http://nginx.org/en/docs/ngx_core_module.html#include
> # for more information.
> include /etc/nginx/conf.d/*.conf;
>
> server {
> listen   80 default_server;
> listen   [::]:80 default_server;
> server_name  _;
> root /usr/share/nginx/html;
>
> # Load configuration files for the default server block.
> include /etc/nginx/default.d/*.conf;
>
> location / {
> }
>
>  location  ^~ /phpmyadmin/ {
>   alias /usr/share/phpmyadmin/;
>
>   location ~ \.php$ {
>include fastcgi_params;
>fastcgi_param SCRIPT_FILENAME $request_filename;
>fastcgi_pass  localhost:9000;
>   }
>   index index.php;
>  }
>
> error_page 404 /404.html;
> location = /40x.html {
> }
>
> error_page 500 502 503 504 /50x.html;
> location = /50x.html {
> }
> error_page 403 = @login;
> location @login {
>   rewrite ^.* https://secure.example.com/login;
> }
> }
>
>
>
> server {
> listen 80;
> auth_ldap "Please enter your ldap user";
> auth_ldap_servers acmeLDAP;
>
> server_name rt.servername.acme.com;
> access_log  /var/log/nginx/access.log;
> error_log /var/log/nginx/rt debug;
>
>
> location / {
>
>   alias /opt/rt4/share/html/;
>
>   fastcgi_param  QUERY_STRING   $query_string;
>   fastcgi_param  REQUEST_METHOD $request_method;
>   fastcgi_param  CONTENT_TYPE   $content_type;
>   fastcgi_param  CONTENT_LENGTH $content_length;
>
>   fastcgi_param  SCRIPT_NAME'';
>   fastcgi_param  PATH_INFO  $uri;
>   fastcgi_param  REQUEST_URI$request_uri;
>   fastcgi_param  DOCUMENT_URI   $document_uri;
>   fastcgi_param  DOCUMENT_ROOT  $document_root;
>   fastcgi_param  SERVER_PROTOCOL$server_protocol;
>
>   fastcgi_param  GATEWAY_INTERFACE  CGI/1.1;
>   fastcgi_param  SERVER_SOFTWAREnginx/$nginx_version;
>
>   fastcgi_param  REMOTE_ADDR$remote_addr;
>   fastcgi_param  REMOTE_PORT$remote_port;
>   fastcgi_param  SERVER_ADDR$server_addr;
>   fastcgi_param  SERVER_PORT$server_port;
>   fastcgi_param  SERVER_NAME$server_name;
>
>   fastcgi_pass 127.0.0.1:8090;
>
>
>
>
> }
>
> location = /auth {
>proxy_pass http://servername/phpmyadmin/phpTest.php;
>proxy_pass_request_body off;
>proxy_set_header Host $host;
>proxy_set_header X-Real-IP $remote_addr;
>proxy_set_header X-Origin-URI $request_uri;
>proxy_set_header Content-Length '0';
>}
>
>
>
>
>
>
> }
>
>
>
> RT_SiteConfig.pm:
>
>
> # Any configuration directives you include  here will override
> # RT's default configuration file, RT_Config.pm
> #
> # 

Re: [rt-users] Upgrading from 4.2.0 > 4.4.0

[Lush, Aaron]

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 <jvdw...@xs4all.nl> 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
Se

Re: [rt-users] Upgrading from 4.2.0 > 4.4.0

[Lush, Aaron]

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*

Sincerely,

Aaron Lush
Network Administrator
South Central Community School Corporation
(219) 767-2266 ext. 

On Fri, Feb 26, 2016 at 3:12 PM, Lush, Aaron <al...@scentral.k12.in.us>
wrote:

> Thanks, Joop. I'll restore my 4.2 database backup and run the following
> SQL command on the database:
>
> UPDATE users SET ExternalAuthID=null WHERE ExternalAuthId IS NOT null;
>
> MySQL isn't my strongest set of skills, but that is how I am understanding
> your post. Thanks a lot for the quick response!
>
> Sincerely,
>
> Aaron Lush
> Network Administrator
> South Central Community School Corporation
> (219) 767-2266 ext. 
>
> On Fri, Feb 26, 2016 at 2:59 PM, Joop <jvdw...@xs4all.nl> wrote:
>
>> On 26-2-2016 18:47, Lush, Aaron wrote:
>>
>> I'm trying to upgrade from 4.2.0 > 4.4.0 on Ubuntu Server 15.10 and have
>> been running into some snags. The first was that I had "ExternalAuthId"
>> with values in my RT4 database, as I was using that plug-in. Once I dropped
>> that table I was able to continue upgrading. However, my upgrade has
>> stalled at the following:
>>
>>
>> Using something like : update users set externalauthid=null where
>> externalauthid is not null should do the trick. Don't drop the users table.
>> I just did a test upgrade from 4.0.23 to 4.4.0 and we're using
>> ExternalAuth too.
>> For those interested: we also use AssetTracker and I migrated all its
>> assets to the shine new RT::Assets :-)
>> Got a question about something related but will post that in a new thread.
>>
>> Regards,
>>
>> Joop
>>
>>
>> -
>> 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. 
-
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

Re: [rt-users] Upgrading from 4.2.0 > 4.4.0

[Lush, Aaron]

Thanks, Joop. I'll restore my 4.2 database backup and run the following SQL
command on the database:

UPDATE users SET ExternalAuthID=null WHERE ExternalAuthId IS NOT null;

MySQL isn't my strongest set of skills, but that is how I am understanding
your post. Thanks a lot for the quick response!

Sincerely,

Aaron Lush
Network Administrator
South Central Community School Corporation
(219) 767-2266 ext. 

On Fri, Feb 26, 2016 at 2:59 PM, Joop <jvdw...@xs4all.nl> wrote:

> On 26-2-2016 18:47, Lush, Aaron wrote:
>
> I'm trying to upgrade from 4.2.0 > 4.4.0 on Ubuntu Server 15.10 and have
> been running into some snags. The first was that I had "ExternalAuthId"
> with values in my RT4 database, as I was using that plug-in. Once I dropped
> that table I was able to continue upgrading. However, my upgrade has
> stalled at the following:
>
>
> Using something like : update users set externalauthid=null where
> externalauthid is not null should do the trick. Don't drop the users table.
> I just did a test upgrade from 4.0.23 to 4.4.0 and we're using
> ExternalAuth too.
> For those interested: we also use AssetTracker and I migrated all its
> assets to the shine new RT::Assets :-)
> Got a question about something related but will post that in a new thread.
>
> Regards,
>
> Joop
>
>
> -
> 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. 
-
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

[rt-users] Upgrading from 4.2.0 > 4.4.0

[Lush, Aaron]

I'm trying to upgrade from 4.2.0 > 4.4.0 on Ubuntu Server 15.10 and have
been running into some snags. The first was that I had "ExternalAuthId"
with values in my RT4 database, as I was using that plug-in. Once I dropped
that table I was able to continue upgrading. However, my upgrade has
stalled at the following:

*Upgrade from 4.3.12 to 4.3.13 (Incomplete) Fri Feb 26 08:31:50 2016 4.4.0*
*Schema updates from /tmp/rt-4.4.0/etc/upgrade/4.3.13 (Incomplete) Fri Feb
26 08:31:50 2016 4.4.0*

I get the following error when running "make upgrade-database:"

*Processing 4.3.13Now populating database schema.[16494] [Fri Feb 26
16:48:54 2016] [critical]: DBD::mysql::st execute failed: Can't DROP
'IssueStatement'; check that column/key 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: Can't
DROP 'IssueStatement'; check that column/key exists at
/tmp/rt-4.4.0/sbin/../lib/RT/Handle.pm line 552.Makefile:391: recipe for
target 'upgrade-database' failedmake: *** [upgrade-database] Error 9*

Listing the Tables in my RT4 database doesn't show any such table, nor does
listing all rows in each column. I assume the error is because
IssuerStatement doesn't exist, so it fails. However, I am completely
clueless to this reference. Any help on this issue would be greatly
appreciated, as I have another RT server at another School that will have
the same issue. Thanks!

Sincerely,

Aaron Lush
Network Administrator
South Central Community School Corporation
(219) 767-2266 ext. 

-- 
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. 
-
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