[rt-users] Error with Upgrade RT4.4.1 from RT4.2.10

[Carlos Alonso Lozano]

Hi everyone.
First sorry for my english i'm spanish.

I try upgrate to RT 4.4.1 and RTIR 4.0 from RT 4.2.10 with RTIR 3.2.
To Upgrade RT, after the "make upgrade" and the "make upgrade-database" withow 
problems, i have error 500.

The only error log is the file:  ../logs/error_log:
Socket object version 2.010 does not match bootstrap parameter 2.024 at 
/usr/lib64/perl5/DynaLoader.pm line 213.
Compilation failed in require at /usr/local/lib64/perl5/Sys/Syslog.pm line 9.
BEGIN failed--compilation aborted at /usr/local/lib64/perl5/Sys/Syslog.pm line 
9.
Compilation failed in require at /usr/local/share/perl5/Log/Dispatch/Syslog.pm 
line 14.
BEGIN failed--compilation aborted at 
/usr/local/share/perl5/Log/Dispatch/Syslog.pm line 14.
Compilation failed in require at /opt/rt4/sbin/../lib/RT.pm line 355.

With: cpan -a | fgrep "Socket", the result is:
IO::Socket::IP 0.38  0.38  PEVANS/IO-Socket-IP-0.38.tar.gz
IO::Socket::SSL   2.039 2.039  SULLR/IO-Socket-SSL-2.039.tar.gz
Socket2.024 2.024  PEVANS/Socket-2.024.tar.gz
IO::Socket 1.34  1.31  GBARR/IO-1.25.tar.gz
IO::Socket::INET   1.33  1.31  GBARR/IO-1.25.tar.gz
IO::Socket::SSL::Intercept 2.014 2.014  SULLR/IO-Socket-SSL-2.039.tar.gz
IO::Socket::SSL::PublicSuffix undef undef  
SULLR/IO-Socket-SSL-2.039.tar.gz
IO::Socket::SSL::Utils2.014 2.014  SULLR/IO-Socket-SSL-2.039.tar.gz
IO::Socket::UNIX   1.24  1.23  GBARR/IO-1.25.tar.gz


Thank you for your help.



Un saludo

Carlos Alonso Lozano
carlos.alo...@csa.es



En cumplimiento de la Ley Org?nica 15/1999, de 13 de diciembre, de Protecci?n 
de Datos de Car?cter Personal, los datos personales reflejados en este 
documento se incluir?n en una base de datos informatizada de titularidad de 
Centro Regional de Servicios Avanzados, S.A. Dicha base de datos se encuentra 
inscrita en el Registro General de Protecci?n de Datos conforme a lo dispuesto 
en la legislaci?n vigente y cumpliendo todas las medidas de seguridad del Real 
Decreto 994/1999, de 11 de junio, de medidas de seguridad de los ficheros 
automatizados que contengan datos de car?cter personal. Asimismo, el cliente 
dispone en todo momento de los derechos de informaci?n, acceso, rectificaci?n, 
cancelaci?n y oposici?n, que podr? ejercitar por escrito mediante carta 
dirigida al Responsable de Seguridad, en la siguiente direcci?n: C/ L?pez 
Bravo, 1. 09001 Burgos (Espa?a).
-
RT 4.4 and RTIR training sessions, and a new workshop day! 
https://bestpractical.com/training
* Los Angeles - January 9-11 2017

Re: [rt-users] supplying database credentials to rt-fulltext-indexer

[Alex Hall]

Hi all,
I think I can say definitely that this is a bug. I added the DB credentials
to RT_SiteConfig.pm and, suddenly, the indexer started working perfectly.
Yet RT itself pulls the exact same credentials from
RT_SiteConfig.d/03-DBInfo.pm with no trouble. I have all my settings in
multiple files under RT_SiteConfig.d, and they all work. It's just
rt-fulltext-indexer that seems to have trouble accessing them. This
explains a lot, and hopefully gets fixed in the next release. Thanks for
everyone's suggestions and help.

On Sat, Dec 10, 2016 at 5:56 AM, Alex Hall  wrote:

> I thought it would, but it doesn't seem to be. My db credentials must be
> correct, because RT isn't complaining of any db problems, and is working
> fine. Is it possible that there's a bug in 4.4.1 that causes this indexer
> to get confused by the use of the RT_SiteConfig.d/* files? I use those
> instead of a single .pm file. I'll have to try putting my database
> credentials in the actual PM file later today, once I'm awake, to see if
> that helps.
>
> Sent from my iPhone
>
> > On Dec 10, 2016, at 03:47, Alex Vandiver  wrote:
> >
> > On Fri, 9 Dec 2016 17:30:31 -0500
> > Alex Hall  wrote:
> >> What this file never says is how to tell the indexer tool how to
> connect to
> >> the database. It clearly isn't pulling from the RT configuration, nor
> from
> >> /home/www-data/rtrc.
> >
> > The indexer reads and uses the database configuration from
> > your /opt/rt4/etc/RT_Config.pm and /opt/rt4/tec/RT_SiteConfig.pm
> > files.  rtrc files are _only_ used by the "bin/rt" tool, which is meant
> > to be run from other machines than your RT host.
> >
> > The rt-setup-fulltext-indexer wants to know your DBA username and
> > password because it needs to create new tables and indexes, which the
> > standard RT database user does not have permissions to do.  Once the
> > index is set up, updates to the index are done as RT's standard
> > database user.
> >
> > - Alex
>



-- 
Alex Hall
Automatic Distributors, IT department
ah...@autodist.com
-
RT 4.4 and RTIR training sessions, and a new workshop day! 
https://bestpractical.com/training
* Los Angeles - January 9-11 2017

Re: [rt-users] supplying database credentials to rt-fulltext-indexer

[Jeff Voskamp]

On 12/12/16 10:42 AM, Alex Hall wrote:

Hi all,
I think I can say definitely that this is a bug. I added the DB 
credentials to RT_SiteConfig.pm and, suddenly, the indexer started 
working perfectly. Yet RT itself pulls the exact same credentials from 
RT_SiteConfig.d/03-DBInfo.pm with no trouble. I have all my settings 
in multiple files under RT_SiteConfig.d, and they all work. It's just 
rt-fulltext-indexer that seems to have trouble accessing them. This 
explains a lot, and hopefully gets fixed in the next release. Thanks 
for everyone's suggestions and help.
Permissions on RT_SiteConfig.d/03-DBInfo.pm are such that the user 
running rt-fulltext-indexer can read them? Alternately you're not 
running rt-fulltext-indexer from an earlier release (4.2.x) that didn't 
support RT_SiteConfig.d?


Jeff
-
RT 4.4 and RTIR training sessions, and a new workshop day! 
https://bestpractical.com/training
* Los Angeles - January 9-11 2017

Re: [rt-users] supplying database credentials to rt-fulltext-indexer

[Alex Hall]

Neither. For the moment, root runs everything (yes, I know that's enough to
get me slapped). 4.4.1 is the only version ever installed from source, thus
/opt/rt4/sbin/rt-fulltext-indexer has to be new. The only other version on
the server is indeed from 4.2, but is from a Debian package and thus lives
in some other sbin folder on the system and not this one.

On Mon, Dec 12, 2016 at 1:12 PM, Jeff Voskamp 
wrote:

> On 12/12/16 10:42 AM, Alex Hall wrote:
>
>> Hi all,
>> I think I can say definitely that this is a bug. I added the DB
>> credentials to RT_SiteConfig.pm and, suddenly, the indexer started working
>> perfectly. Yet RT itself pulls the exact same credentials from
>> RT_SiteConfig.d/03-DBInfo.pm with no trouble. I have all my settings in
>> multiple files under RT_SiteConfig.d, and they all work. It's just
>> rt-fulltext-indexer that seems to have trouble accessing them. This
>> explains a lot, and hopefully gets fixed in the next release. Thanks for
>> everyone's suggestions and help.
>>
> Permissions on RT_SiteConfig.d/03-DBInfo.pm are such that the user running
> rt-fulltext-indexer can read them? Alternately you're not running
> rt-fulltext-indexer from an earlier release (4.2.x) that didn't support
> RT_SiteConfig.d?
>
> Jeff
>



-- 
Alex Hall
Automatic Distributors, IT department
ah...@autodist.com
-
RT 4.4 and RTIR training sessions, and a new workshop day! 
https://bestpractical.com/training
* Los Angeles - January 9-11 2017