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