On Sat, Nov 5, 2011 at 4:35 AM, Chris Travers wrote:
> On Fri, Nov 4, 2011 at 10:24 PM, Steven Marshall
> wrote:
> > On Nov 4, 2011, at 5:20 PM, "David A. Bandel"
> wrote:
> >
> >> On Fri, Nov 4, 2011 at 11:11, Steven Marshall
> >> wrote:
> >>> I have brand new installation of 1.3.3 with I beli
On Fri, Nov 4, 2011 at 10:24 PM, Steven Marshall
wrote:
> On Nov 4, 2011, at 5:20 PM, "David A. Bandel" wrote:
>
>> On Fri, Nov 4, 2011 at 11:11, Steven Marshall
>> wrote:
>>> I have brand new installation of 1.3.3 with I believe all prereqs.
>>>
>>> 1. Created Postgresql superuser "ledgersmb"
>
On Nov 4, 2011, at 5:20 PM, "David A. Bandel" wrote:
> On Fri, Nov 4, 2011 at 11:11, Steven Marshall
> wrote:
>> I have brand new installation of 1.3.3 with I believe all prereqs.
>>
>> 1. Created Postgresql superuser "ledgersmb"
>> 2. From browser navigate to http://localhost/ledgersmb/setup.pl
On Fri, Nov 4, 2011 at 12:03 PM, David A. Bandel wrote:
> 2011/11/4 Philippe Schelté :
>> In fact your discussion about non unique records gave me the idea to
>> renumbered all my parts (they where all at 1) 1,2,3...etc
>> and you know what ? it passed
>> I had also some invoices with the same num
I have installed the package postgresql-contrib, I have given this path :
/usr/share/postgresql/9.1/extension
I have verrified it exists and have hundred sql scripts in.
I have always the same error as Steven.
Do I have to execute one of those script before upgrading ?
Best.
Philippe
Le 04
On Fri, Nov 4, 2011 at 11:11, Steven Marshall
wrote:
> I have brand new installation of 1.3.3 with I believe all prereqs.
>
> 1. Created Postgresql superuser "ledgersmb"
> 2. From browser navigate to http://localhost/ledgersmb/setup.pl
> 3. On setup.pl screen enter ledgersmb/password/foo for Super
2011/11/4 Philippe Schelté :
> In fact your discussion about non unique records gave me the idea to
> renumbered all my parts (they where all at 1) 1,2,3...etc
> and you know what ? it passed
> I had also some invoices with the same number so I have fixed this.
>
> Now I'm on screen asking me :
>
>
In fact your discussion about non unique records gave me the idea to
renumbered all my parts (they where all at 1) 1,2,3...etc
and you know what ? it passed
I had also some invoices with the same number so I have fixed this.
Now I'm on screen asking me :
the contrib dir (Hu! never heard of that)
I have brand new installation of 1.3.3 with I believe all prereqs.
1. Created Postgresql superuser "ledgersmb"
2. From browser navigate to http://localhost/ledgersmb/setup.pl
3. On setup.pl screen enter ledgersmb/password/foo for SuperUser
Credentials and click Login button
4. On the Confirm Opera
I have an old database also and I don't think there would have been an
automated fix.
I wonder if it would make sense to have 1.2.2x have a upgrade vailidity
check.
Where you could run the check then go fix the problems then re-run the
check.
When i was doing the fixes I was running the checks
>>
>> # Database administrative login by UNIX sockets
>> local all postgres ident
>
> change ident above to trust
>
>>
>> # TYPE DATABASE USER CIDR-ADDRESS METHOD
>>
>> # "local" is for Unix domain socket connections only
>> local all
On Fri, Nov 4, 2011 at 09:40, Alvin Starr wrote:
> I have seen this page.
> It is the result from the pre-upgrade tests failing.
Actually, the latest setup.pl (upgrade script) does bail with a more
descriptive error message if the pre-up tests fail. It doesn't
actually fix those errors. I hav
I have seen this page.
It is the result from the pre-upgrade tests failing.
I think an argument could be made that the failure could be a little
more descriptive and suggest where to look for how to fix things.
On 11/04/2011 09:50 AM, Philippe Schelté wrote:
> Hello Chris,
>
> thanks for you
2011/11/4 Philippe Schelté :
> Hello David,
>
>> Postgres is rejecting authentication. You must allow a connection to
>> 127.0.0.1 and/or ::1 if using IPv6 to the database on port 5432.
>> Check your /etc/postgresql/9.1/main/pg_hba.conf file. Reconfigure
>> and
>> restart postgresql. Once you've
Hello David,
> Postgres is rejecting authentication. You must allow a connection to
> 127.0.0.1 and/or ::1 if using IPv6 to the database on port 5432.
> Check your /etc/postgresql/9.1/main/pg_hba.conf file. Reconfigure
> and
> restart postgresql. Once you've upgraded the database, you can
> c
2011/11/4 Philippe Schelté :
> Hello,
>
> After having upgraded my server to Ubuntu oneiric, my LedgerSMB 1.2.21
> stopped working with perl errors in the apache2 error.log.
> So I decided to move to the 1.3.3 version. In the meantime, the oneiric
> upgrades also postgresql from 8.4 to 9.1 things l
Hello Chris,
thanks for your reply !
> Use the setup.pl.
>
> Enter the company and postgresql superuser/password authentication
> fields. The company is your database name.
>
> It should detect 1.2 and ask if you want to upgrade. Say yes and
> continue.
>
I have done the setup.pl as I expl
2011/11/4 Philippe Schelté :
> Hi Håvard,
>
> Of course you are right, I would have look to the INSTALL file.
> So when I fill the database owner credentials and the database name in
> "company" field, I haven't got anymore the additionnal apache2
> authentication prompt,
> but I have this error :
Hi Håvard,
Of course you are right, I would have look to the INSTALL file.
So when I fill the database owner credentials and the database name in
"company" field, I haven't got anymore the additionnal apache2
authentication prompt,
but I have this error :
Error!
Database is not the expected ve
On 04. nov. 2011 09:11, Philippe Schelté wrote:
> Third, if I go to login.pl, I fill my LedgerSMB user credentials, in
> the "Company" field what do I have to fill exactly ?
> again I have the additionnal apache2 authentication that I fill with my
> postgresql user owner of the LedgerSMB database.
Hello,
After having upgraded my server to Ubuntu oneiric, my LedgerSMB 1.2.21
stopped working with perl errors in the apache2 error.log.
So I decided to move to the 1.3.3 version. In the meantime, the oneiric
upgrades also postgresql from 8.4 to 9.1 things look like have been
well done about Pos
21 matches
Mail list logo
