[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#406935: some problems on install



Antoine,

On Tue, 2012-04-17 at 18:27 -0400, Antoine Beaupré wrote:

> Default postgres configuration problem
> ======================================
> 
> The other problem i am having is it seems the psql user isn't being
> created properly. I can't connect to the postgres database using the
> password i chose or the default password. This requires an extra
> configuration on the postgresql side, where i need the following:
> 
> -local   all         all                               ident
> +#local   all         all                               ident
> +local   all         all                               md5

   IIRC, that's no longer necessary assuming that everything is
configured and the setup.pl cgi script is being used.  I did a test
install on a squeeze system (32 bit LXC) and did not need to do that
after doing the following:
  
1) Installed apache2 postgresql postgresql-contrib
2) Installed ledgersmb package dependencies
3) dpkg -i <lsmb deb pkg>
4) Configured contrib_dir in /etc/ledgersmb/ledgersmb.conf
5) Added my local lan to the Allow section in ledgersmb-httpd.conf

  And I was then able to use the setup.pl cgi to create an initial
database and user.  (I don't think I left out any needed steps...)


> Also, I get the following error when logging in through setup.pl:
> 
> Cannot find Contrib script tablefunc.sql in /usr/share/pgsql/contrib/.
> 
> While there are some instructions in the README.Debian file about this,
> it is rather counter-intuitive. This desserves a bigger warning in the
> README...

   What I'd like to have it do is to have that automatically configured
depending on which version of PostgreSQL is installed <g>;  but without
that, putting more information about it into README.Debian is the next
best thing.


> .... Maybe the ledgersmb user wasn't created properly?

    It's not, yet.  I know what I want it to do, at least initially;
create the 'ledgersmb' database user with the needed permissions.  I've
started attempting to use debconf/dbconfig-common to set that up but
that's not working yet.


>  The README mentions that the package may have done that for you, so I was
> assuming this would work.

    Yes, I need to make it clearer just what is is and is not capable of
doing...


>  At least mentionning how to grant those rights would go a long way.

  Since v1.3 is so dependent on the database superuser, I'm thinking
about adding a separate section for it in README.Debian.




Jame





Reply to: