Re: New password required.

[Chris Travers <..hidden..>]

Ok, few points here.

On Wed, Oct 19, 2011 at 11:13 PM, Dave Coventry <..hidden..> wrote:
> Hi Chris
>
> On 20 October 2011 07:52, Chris Travers <..hidden..> wrote:
>> I would have expected more here.  What about the PostgreSQL error logs?
> Nothing much there:


Ok, This is odd.  I would expect a failed connection to the db to
raise errors in both logs.

Maybe it is connecting but hitting the old db and not finding the
proper user credentials?
>
> ~~~~~~~~~~~~~~~~~~~ 8X ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ..hidden..:/opt# tail -f /var/log/postgresql/postgresql-8.4-main.log
> 2011-10-20 06:51:52 SAST WARNING:  nonstandard use of \\ in a string
> literal at character 76

Do you know if these are from LedgerSMB?  I doubt we are doing
anything that would raise those warnings.


>> How did you upgrade?
>
> Extracted the tarball to /opt/ledgersmb.1.3.1 and changed the
> /opt/ledgersmb symlink to point to it instead of my ledgersmb.1.2.22
> link.

Ok, you need to set a password for the postgres user or create a new
db superuser.

CREATE USER 'foo' WITH SUPERUSER PASSWORD 'bar';

Then you can log into the setup.pl with username foo and password bar.
>
> Also installed the dependencies through CPAN.
>
> I WAS going to run setup.pl, but the username/password requirement won't let me.
>
>>  How were things broken before the upgrade?
>
> ~~~~~~~~~~~~~~~~~~~ 8X ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Using a hash as a reference is deprecated at LedgerSMB/IS.pm line 820.
> defined(%hash) is deprecated at bin/io.pl line 1683.
> (Maybe you should just omit the defined()?)

That can't be the whole of it.  Those are warnings, probably thrown by
a new version of Perl, shouldn't be causing the software to
malfunction in this way.

If you set the symlink back and try to log in, what happens?  I'd
suggest getting 1.2 working again before upgrading to 1.3 so we aren't
troubleshooting two things at once.  1.2 is still supported.

Best Wishes,
Chris Travers