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

Re: ledgersmb password problem



Hello Billy,

The file "/etc/apache2/conf.d/ledgersmb-httpd.conf.template" have the basic options for the Apache webserver, in this case:

Alias /ledgersmb WORKING_DIR/

<Directory WORKING_DIR>

You are telling it that when you surf "http://HOST/ledgersmb" it is looking for the files under locally directory $WORKING_DIR.

When you run "sh install.sh", it takes the working directory where ledgersmb is located and it is used to replaceÂWORKING_DIR.

I think that I easy way would be to removeÂ"/etc/apache2/conf.d/ledgersmb-httpd.conf.template", check that there is not another ledgersmb template there and then:

Under ledgersmb directory:

CWD=`pwd`
sed Â"s|WORKING_DIR|$CWD|g" ledgersmb-httpd.conf.template > ledgersmb-httpd.conf
cpÂledgersmb-httpd.confÂ/etc/apache2/conf.d/ledgersmb-httpd.conf

then just restart the apache:

/etc/init.d/apache2 restart

On Fri, Mar 16, 2012 at 10:48 PM, billy akazawa <..hidden..> wrote:

Thanks Andres and Chris,

I tried stepping through Andres procedure (with the exclusion of reinstalling postgres 9.1).

Now when I try to log on using

http://localhost/ledgersmb/setup.pl

I get:

Error!Unable to open script: scripts/setup.pl : No such file or directory

I get the following message in a terminal when I restart apache2.

Restarting web server: apache2[Sat Mar 17 10:13:00 2012] [warn] The Alias directive in /etc/apache2/conf.d/ledgersmb-httpd.conf.template at line 3 will probably never match because it overlaps an earlier Alias.

[Sat Mar 17 10:13:00 2012] [warn] The Alias directive in /usr/local/ledgersmb/ledgersmb-httpd.conf at line 3 will probably never match because it overlaps an earlier Alias.

... waiting [Sat Mar 17 10:13:01 2012] [warn] The Alias directive in /etc/apache2/conf.d/ledgersmb-httpd.conf.template at line 3 will probably never match because it overlaps an earlier Alias.

[Sat Mar 17 10:13:01 2012] [warn] The Alias directive in /usr/local/ledgersmb/ledgersmb-httpd.conf at line 3 will probably never match because it overlaps an earlier Alias.

Lines 2 and 3 of /etc/apache2/conf.d/ledgersmb-httpd.conf.template

Alias /ledgersmb WORKING_DIR/

<Directory WORKING_DIR>

Lines 2 and 3 of / usr/local/ledgersmb/ledgersmb-httpd.conf

Alias /ledgersmb /usr/local/ledgersmb/

<Directory /usr/local/ledgersmb>

The latest apache2 error.log after restart says:

PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/200906$

PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/200906$
PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/200906$
PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/200906$
[Sat Mar 17 10:13:01 2012] [notice] Apache/2.2.16 (Debian) DAV/2 SVN/1.6.12 PHP$
[Sat Mar 17 10:37:51 2012] [error] [client ::1] Directory index forbidden by Op$
[Sat Mar 17 10:38:01 2012] [error] [client ::1] Directory index forbidden by Op$

Thanks in advance. I really want to get this thing up and running.

Billy


On Sat, Mar 17, 2012 at 9:15 AM, Chris Travers <..hidden..> wrote:
On Fri, Mar 16, 2012 at 1:59 PM, billy akazawa <..hidden..> wrote:
> Hi again,
>
> After a lot of frustration with installing ledgersmb, I decided to install
> postgres 9.1, reinstall ledgersmb and do a dist upgrade for Squeeze.
>
> Now I can get to the Data Management Console with
> http://localhost/ledgersmb/setup.pl
>
> but when I type in the Superuser credentials and try to move on by clicking
> on 'login', it brings up the Authentication Required box which says:
>
> A username and password are being requested by http://localhost. The site
> says: "LedgerSMB"
>
> with the User Name ledgersmb and the password filled in (I set it to admin
> using postgres).
>
> Clicking on 'OK' brings up the same screen again. I've tried it with no
> password and the postgres password, but nothing works.
>
> Has anyone experienced this problem before? Any ideas on how to get beyond
> this ledgersmb login password dilemma are really appreciated.

Please check your web server logs for more information on why
authentication was rejected.

There are a number of possible causes here. ÂThese include mod_rewrite
not being enabled, problems with PostgreSQL configuration, and the
like. ÂHowever without the log entries, it is hard to say.

We pass HTTP auth through to the db so this error happens when the
database refuses to allow the user to connect.

Best Wishes,
Chris Travers

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Ledger-smb-users mailing list
..hidden..
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users


------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Ledger-smb-users mailing list
..hidden..
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users


------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Ledger-smb-users mailing list
..hidden..
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users