Re: [las_users] problem/gotcha/workaround for a 6_5_1_2 install

[Jonathan Callahan <Jonathan.S.Callahan@xxxxxxxx>]

Rob,

Thanks for the report.  We'll try to get a patched release out with 
these and a few other minor patches in the near future.


-- Jon

Rob Cermak wrote:

> Fresh install on Mandrake 10.2
>
> Problem #1 : -------------------------
>
> Saw the URI version message and found another bug in configure.pl... the
> module name in the test also needs to be updated to trigger...
>
>                    } elsif ($module eq 'URI') {
>
> needs to be updated to URI:URL to match the module listing:
>  URI::URL => 'URI-1.19',
>
>
>                    } elsif ($module eq 'URI::URL') {
>
> # More recent versions of URI leave an extra slash when resolving 
> '//las.xml'.
>
>                     require('DBI.pm');
>                     if ($DBI::VERSION <= 1.19) {
>
>
> Once I had the local copy installed in las, I had to change it back to
>
>                    } elsif ($module eq 'URI') {
>
> to get the LAS through the configure process.  
> Might suggest?
>
>                    } elsif ($module eq 'URI' || $module eq 'URI:URL') {
>
>
> Problem/heads up #2 : -------- not really a problem, more of a gotcha
>
> Password mismatch from configure -> Java
>
> The password we enter during configure is not passed through to
> $LAS_HOME/las_servlet/src/las.properties
>
> I recall now that during the configure you have to use a 'root'-like 
> privileged user so it creates the las user and password in the mysql
> database.   What I did was created a las user with enough privileges
> to allow drops and index creation.  So, the step where the it serializes 
> the .xml to the database worked, fired up LAS and got a connection error
> in reported by java.  IE: the passwords didn't match...  lots of head 
> banging here.
>
> Rob
>
>