sql-ledger-users

new to sql-ledger and postgresql.

[klavs k. <kl...@vs...>]

Hi guys,

I just installed rpm's of postgresql, and installed sql-ledger.

When I try to connect and "Create Dataset" from admin.pl, it keeps
giving me "Error. Could not connect to server: connection refused".

I tried adding a new postgres user (tnx. for the link to postgresql
guide I got earlier on the list). I still get the same error even though
I added the user, with the -P (to set password).
postgresql listens on udp 1045 according to lsof -i udp.

what am I missing?
--=20
Regards,
Klavs Klavsen

-------------| This mail has been sent to you by: |------------
              Klavs Klavsen - Open Source Consultant=20
                 kl...@vs... - http://www.vsen.dk

    Get PGP key from www.keyserver.net - Key ID: 0x586D5BCA=20
Fingerprint =3D A95E B57B 3CE0 9131 9D15 94DA E1CD 641E 586D 5BCA
--------------------[ I believe that... ]-----------------------
It is a myth that people resist change. People resist what other
people make them do, not what they themselves choose to do...
That's why companies that innovate successfully year after year
seek their peopl's ideas, let them initiate new projects and
encourage more experiments.            -- Rosabeth Moss Kanter

Re: new to sql-ledger and postgresql.

[Olaf F. <ofa...@at...>]

Klav,

See the snippet below from the Postgres manual.  Perhaps sql-ledger is
trying to connect via TCP, but Postgres is only accepting connections via
UDP (the Postgres default, at least at one time).

-Olaf

=======================

3.3.2. Client Connection Problems
Although the error conditions possible on the client side are quite varied
and application-dependent, a few of them might be directly related to how
the server was started up. Conditions other than those shown below should be
documented with the respective client application.


psql: could not connect to server: Connection refused
        Is the server running on host server.joe.com and accepting
        TCP/IP connections on port 5432?
This is the generic "I couldn't find a server to talk to" failure. It looks
like the above when TCP/IP communication is attempted. A common mistake is
to forget the -i option to allow the postmaster to accept TCP/IP
connections.

Alternatively, you'll get this when attempting Unix-socket communication to
a local postmaster:

psql: could not connect to server: Connection refused
        Is the server running locally and accepting
        connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

----- Original Message -----
From: "klavs klavsen" <kl...@vs...>
To: "SQL-Ledger mailinglist" <sql...@li...>
Sent: Thursday, March 21, 2002 5:53 AM
Subject: new to sql-ledger and postgresql.

Re: new to sql-ledger and postgresql.

[Gianluca C. <te...@li...>]

You can also modify the postgresql.conf file:

tcpip_socket = true

You have also to grant access to the clients, modifying the file
pg_hba.conf, that is in
$PGDATA directory (/usr/local/pgsql/data in my case).
It is self explanatory, for example I introduced this line in it

host all 192.168.0.0 255.255.0.0 trust

supposing that clients connections arrive from 192.168.0.0 network.

HIH.



Bye,

Gianluca

----- Original Message -----
From: "Olaf Faaland" <ofa...@at...>
To: "klavs klavsen" <kl...@vs...>; "SQL-Ledger mailinglist"
<sql...@li...>
Sent: Thursday, March 21, 2002 4:51 PM
Subject: Re: new to sql-ledger and postgresql.


> Klav,
>
> See the snippet below from the Postgres manual.  Perhaps sql-ledger is
> trying to connect via TCP, but Postgres is only accepting connections via
> UDP (the Postgres default, at least at one time).
>
> -Olaf
>
> =======================
>
> 3.3.2. Client Connection Problems
> Although the error conditions possible on the client side are quite varied
> and application-dependent, a few of them might be directly related to how
> the server was started up. Conditions other than those shown below should
be
> documented with the respective client application.
>
>
> psql: could not connect to server: Connection refused
>         Is the server running on host server.joe.com and accepting
>         TCP/IP connections on port 5432?
> This is the generic "I couldn't find a server to talk to" failure. It
looks
> like the above when TCP/IP communication is attempted. A common mistake is
> to forget the -i option to allow the postmaster to accept TCP/IP
> connections.
>
> Alternatively, you'll get this when attempting Unix-socket communication
to
> a local postmaster:
>
> psql: could not connect to server: Connection refused
>         Is the server running locally and accepting
>         connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
>
> ----- Original Message -----
> From: "klavs klavsen" <kl...@vs...>
> To: "SQL-Ledger mailinglist" <sql...@li...>
> Sent: Thursday, March 21, 2002 5:53 AM
> Subject: new to sql-ledger and postgresql.
>
>
>
>
>

Re: new to sql-ledger and postgresql.

[klavs k. <kl...@vs...>]

Hi Olaf (and the rest of the list),

I got it working with tips from Jesper, Alexander and Martin.
Thank you everybody.

perhaps a good add-on to the sql-ledger README would be:

If you just installed postgresql (as rpm only?) then do:

createuser sqlledger -W
> say yes to both questions and select a password.

edit /etc/rc.d/init.d/postgresql (RH/MDK specific)
so that the pg_ctl gets an extra option "-o -i" to tell postmaster
process to listen on standard tcp port 5432.

edit /var/lib/pgsql/data/pg_hba.conf and add line=20
> host       all         127.0.0.1     255.255.255.255     password
(this works if your httpd and postgresql are on the same server
otherwise put your webservers IP instead of 127.0.0.1)

follow rest of README and connect with the sqlledger user.


Thanks everybody for the tips you gave me.

I only need one more thing, to somehow enable the postmaster process to
only listen on localhost (right now it listens to 0.0.0.0 - which is bad
securitywise - even though there is access control and I do have an
iptables firewall in front - but better safe than sorry, has always been
my motto).

On Thu, 2002-03-21 at 16:51, Olaf Faaland wrote:
> Klav,
>=20
> See the snippet below from the Postgres manual.  Perhaps sql-ledger is
> trying to connect via TCP, but Postgres is only accepting connections via
> UDP (the Postgres default, at least at one time).
>=20
> -Olaf
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> 3.3.2. Client Connection Problems
> Although the error conditions possible on the client side are quite varie=
d
> and application-dependent, a few of them might be directly related to how
> the server was started up. Conditions other than those shown below should=
 be
> documented with the respective client application.
>=20
>=20
> psql: could not connect to server: Connection refused
>         Is the server running on host server.joe.com and accepting
>         TCP/IP connections on port 5432?
> This is the generic "I couldn't find a server to talk to" failure. It loo=
ks
> like the above when TCP/IP communication is attempted. A common mistake i=
s
> to forget the -i option to allow the postmaster to accept TCP/IP
> connections.
>=20
> Alternatively, you'll get this when attempting Unix-socket communication =
to
> a local postmaster:
>=20
> psql: could not connect to server: Connection refused
>         Is the server running locally and accepting
>         connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
>=20
> ----- Original Message -----
> From: "klavs klavsen" <kl...@vs...>
> To: "SQL-Ledger mailinglist" <sql...@li...>
> Sent: Thursday, March 21, 2002 5:53 AM
> Subject: new to sql-ledger and postgresql.
>=20
>=20
>=20
>=20
--=20
Regards,
Klavs Klavsen

-------------| This mail has been sent to you by: |------------
              Klavs Klavsen - Open Source Consultant=20
                 kl...@vs... - http://www.vsen.dk

    Get PGP key from www.keyserver.net - Key ID: 0x586D5BCA=20
Fingerprint =3D A95E B57B 3CE0 9131 9D15 94DA E1CD 641E 586D 5BCA
--------------------[ I believe that... ]-----------------------
It is a myth that people resist change. People resist what other
people make them do, not what they themselves choose to do...
That's why companies that innovate successfully year after year
seek their peopl's ideas, let them initiate new projects and
encourage more experiments.            -- Rosabeth Moss Kanter

Multiple companies and consolidated company reports

[Michael A. S. <msa...@se...>]

Does anyone know if sql-ledger handles multiple companies?

and

Can these multiple companies can be consolidated into one report?

Thanks,
Mike Salvucci

Re: Multiple companies and consolidated company reports

[Dieter S. <dsi...@sq...>]

Multiple companies, yes, consolidation, no.


Dieter Simader    http://www.sql-ledger.org   (780) 472-8161
DWS Systems Inc.     Accounting Software       Fax: 478-5281
=========== On a clear disk you can seek forever ===========

On Thu, 21 Mar 2002, Michael A. Salvucci wrote:

> Does anyone know if sql-ledger handles multiple companies?
> 
> and
> 
> Can these multiple companies can be consolidated into one report?
> 
> Thanks,
> Mike Salvucci
> 
> 

RE: Multiple companies and consolidated company reports

[Dr D. <drd...@ho...>]

If you can export balance sheet plus P/L to a text file you could then
import to a multiple page spreadsheet, 
one per company, and put a totals page at the end.. Bit of extra work,
but then in consolidation you might 
want to review some things anyway..

-----Original Message-----
From: sql...@li...
[mailto:sql...@li...] On Behalf Of
Dieter Simader
Sent: donderdag 21 maart 2002 20:44
To: Michael A. Salvucci
Cc: sql...@li...
Subject: Re: Multiple companies and consolidated company reports


Multiple companies, yes, consolidation, no.


Dieter Simader    http://www.sql-ledger.org   (780) 472-8161
DWS Systems Inc.     Accounting Software       Fax: 478-5281
=========== On a clear disk you can seek forever ===========

On Thu, 21 Mar 2002, Michael A. Salvucci wrote:

> Does anyone know if sql-ledger handles multiple companies?
> 
> and
> 
> Can these multiple companies can be consolidated into one report?
> 
> Thanks,
> Mike Salvucci
> 
> 

Re: Multiple companies and consolidated company reports

[Markus D. <mda...@sw...>]

Dr Default wrote:

>If you can export balance sheet plus P/L to a text file you could then
>import to a multiple page spreadsheet, 
>one per company, and put a totals page at the end.. Bit of extra work,
>but then in consolidation you might 
>want to review some things anyway..
>
This is a bit simplistic. At least intercompany must be excluded from 
consolidation... 

Re: Multiple companies and consolidated company reports

[Michael A. S. <msa...@se...>]

hmmm...   How do we set up multiple companies?  Maybe I'm blind, but I don't 
see a link for that.

If the companies are stored in the same database, then I think we can write 
some scripts for consolidated reports.  Right?

Thanks,
Mike Salvucci



On Thursday 21 March 2002 01:43 pm, Dieter Simader wrote:
> Multiple companies, yes, consolidation, no.
>
>
> Dieter Simader    http://www.sql-ledger.org   (780) 472-8161
> DWS Systems Inc.     Accounting Software       Fax: 478-5281
> =========== On a clear disk you can seek forever ===========
>
> On Thu, 21 Mar 2002, Michael A. Salvucci wrote:
> > Does anyone know if sql-ledger handles multiple companies?
> >
> > and
> >
> > Can these multiple companies can be consolidated into one report?
> >
> > Thanks,
> > Mike Salvucci