Menu
▾
▴
sql-ledger-users
|
From: Dr. R. J. M. <bo...@ho...> - 2001-07-24 04:17:43
|
Accountants,
I am a newbie trying to install sql-ledger. I've successfully used admin.pl,
but login.pl still fails. Any help would be appreciated.
sql-ledger-1.4.12
perlmod-1.0
w3mir-1.0.8
mod_perl-1.21
mysqclnt-3.22.27
mysqldev-3.22.27
DBD-Pg-0.73
At this time, when I get http://localhost/sql-ledger/login.pl
it reports "Internal Server Error".
Do you know why it cannot load Pg?
Do you know what I need to do install DBD-Pg?
Do you know what I can read to learn to install DBD-Pg?
---- /var/log/http.error_log ----
...
install_driver(Pg) failed:
Can't load '/usr/lib/perl5/site_perl/5.005/i586-linux/auto/DBD/Pg/Pg.so'
for module DBD::Pg:
libpq.so.1: cannot open shared object file:
No such file or directory at
/usr/lib/perl5/5.00503/i586-linux/DynaLoader.pm line 169.
at (eval 1) line 3
at SL/User.pm line 110
[Mon Jul 23 23:54:14 2001] [error] [client 127.0.0.1]
Premature end of script headers:
/opt/packages/sql-ledger-1.4.12/sql-ledger/login.pl
---- /var/log/http.error_log ----
---- > ls -l /usr/lib/perl5/site_perl/5.005/i586-linux/auto/DBD/Pg/Pg.so ----
-rwxr-xr-x 1 root root 35666 Oct 31 1998
/usr/lib/perl5/site_perl/5.005/i586-linux/auto/DBD/Pg/Pg.so
---- > ls -l /usr/lib/perl5/site_perl/5.005/i586-linux/auto/DBD/Pg/Pg.so ----
Thanks in advance,
--
Dr. Robert J. Meier
Custom Tools
mailto:rob...@co...
|
|
From: Dr. R. J. M. <bo...@ho...> - 2001-07-25 05:18:01
|
Steve,
Thank you for the install problems flowchart. It arrived too late for me
to run it tonight, but I will try it tomorrow.
How can I complete an upgrade to perl-5.6.1 started by CPAN?
The current status is that I have been trying to install DBD-Pg. Installation
from an rpm package (0.73) was accomplished with apparent success, but only
changed the details of the error. Subsequently, as advised by others, I
tried to use CPAN to install DBD::Pg. CPAN upgraded my installed perl from
5.5.3 to 5.6.1, but any attempts to make, test, or install other bundles
now reports
perl: error in loading shared libraries:
/usr/lib/perl5/site_perl/5.005/i586-linux/auto/Storable/Storable.so:
undefined symbol: cast_iv
/usr/lib/perl5/site_perl/5.6.1/i586-linux/auto is empty.
Attempts to make, test, or install Storable produce the error reported above.
This appears to be catch-22. It can't build Storable.so-5.6.1 with
perl-5.6.1 and 5.5.3 libraries. It can't build 5.6.1 libraries without
Storable.so-5.6.1.
perl -V now reports
Summary of my perl5 (revision 5.0 version 6 subversion 1) configuration:
Platform:
osname=linux, osvers=2.2.13, archname=i586-linux
uname='linux xxxxxx 2.2.13 #1 mon nov 8 15:08:22 cet 1999 i586 unknown ' config_args=''
hint=recommended, useposix=true, d_sigaction=define
usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=unde
f
useperlio=undef d_sfio=undef uselargefiles=define usesocks=undef
use64bitint=undef use64bitall=undef uselongdouble=undef
Compiler:
cc='gcc', ccflags ='-fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_S
OURCE -D_FILE_OFFSET_BITS=64',
optimize='-O2',
cppflags='-fno-strict-aliasing -I/usr/local/include'
ccversion='', gccversion='egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)',
gccosandvers=''
intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize
=8
alignbytes=4, usemymalloc=n, prototype=define
Linker and Libraries:
ld='gcc', ldflags =' -L/usr/local/lib'
libpth=/usr/local/lib /lib /usr/lib
libs=-lnsl -lndbm -lgdbm -ldbm -ldb -ldl -lm -lc -lposix -lcrypt -lutil
perllibs=-lnsl -ldl -lm -lc -lposix -lcrypt -lutil
libc=, so=so, useshrplib=false, libperl=libperl.a
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-rdynamic'
cccdlflags='-fpic', lddlflags='-shared -L/usr/local/lib'
Characteristics of this binary (from libperl):
Compile-time options: USE_LARGE_FILES
Built under linux
/usr/lib/perl5/site_perl/5.6.1/i586-linux
/usr/lib/perl5/site_perl/5.6.1
/usr/lib/perl5/site_perl/5.005/i586-linux
/usr/lib/perl5/site_perl/5.005
/usr/lib/perl5/site_perl
.
Thanks in advance,
--
Dr. Robert J. Meier
Custom Tools
mailto:rob...@co...
|
|
From: Steve D. <sd...@sw...> - 2001-07-25 12:09:12
|
Hi Robert. It seems you're stuck on step 1 :-(.
You don't appear to have the modules (or not in the right place) for the CPAN approach.
"Dr. Robert J. Meier" wrote:
> Steve,
>
> Thank you for the install problems flowchart. It arrived too late for me
> to run it tonight, but I will try it tomorrow.
>
> How can I complete an upgrade to perl-5.6.1 started by CPAN?
>
> The current status is that I have been trying to install DBD-Pg. Installation
> from an rpm package (0.73) was accomplished with apparent success, but only
> changed the details of the error. Subsequently, as advised by others, I
> tried to use CPAN to install DBD::Pg. CPAN upgraded my installed perl from
> 5.5.3 to 5.6.1, but any attempts to make, test, or install other bundles
> now reports
I don't know if rpm's and cpan will play together very well. I know some manual installs don't
work well with Debian packages, but I can't speak for RedHat on this.
Personally, I would try to be consistent and stick with the rpm's.
Everything needed should be available as rpm's. You may want to follow the red hat install notes
per the faq (just the perl steps 2 and 6-13). Note the version dependencies from the rpm's.
It sounds like you were ok on Apache and Postgres.
Try the above and then go through the flow chart and see what happens.
I'll be gone until this evening, but would be curious to hear how this works.
Good luck,
Steve
Redhat 7.0 Installation instructions
Thanks to Jacky Fang who provided the installation instructions.
1.Install apache1.3.12-25.i386.rpm
2.Install perl5.6.0-9.i386.rpm
3.Install postgresql-7.0.2-17.i386.rpm
4.Install postgresql-server-7.0.2-17.i386.rpm
5.Install postgresql-devel-7.0.2-17.i386.rpm (POSTGRES_INCLUDE)
6.tar xvzf DBI-1.14.tar.gz
7.cd DBI-1.14
8.perl Makefile.PL
9.make
10.make install
11.cd ..
12.tar xvzf DBD-Pg-0.95
13.cd DBD-Pg-0.95
14.export POSTGRES_LIB=/usr/lib/pgsql
15.export POSTGRES_INCLUDE=/usr/include/pgsql
16.perl Makefile.PL
17.make
18.make install
19.install SQL-Ledger
Some of the applications have newer version however the installation instructions remain the
same. Just substitute the old version with a newer version.
|
|
From: Steve D. <sd...@sw...> - 2001-07-27 03:34:39
Attachments:
dbi_check.pl
|
Keld J=F8rn Simonsen wrote: > Maybe we should make a script to detect if there are any problems i= n the > installation, and then report ways to remedy them > > keld This is a really good idea, but neither Keld nor I has much time to w= ork on something like this. I hacked this script together (quickly) from th= e zelerate/allcommerce project (http://allcommerce.sourceforge.net/), w= hich will check for valid drivers and available databases. It's based on their= configure.pl, which checks for drivers/dbs, allows db port/document root to be set,= and can write Apache's config for you. Not much on remedies, but it might help you narrow down the problem. = Maybe somebody else can hack zelerate's configuration script more completel= y for sql-ledger. If perl isn't there it won't run. If dbi is missing, you'll get a pa= ckage not available error. If the Pg driver is not available it will tell you.= If Postgres is installed and everything else is ok, you should get at least templ= ate1 as a db available. If you get no database available, postgres isn't installe= d. save the attached script and run it from where it's located like this= : bash-2.03$ perl dbi_check.pl Drivers available - Pg Databases Available: dbi:Pg:dbname=3Ddemo dbi:Pg:dbname=3Dosallcommerce dbi:Pg:dbname=3Dsqltest dbi:Pg:dbname=3Dtemplate1 |
|
From: Andre F. M. A. F. <and...@te...> - 2001-07-24 17:30:05
|
Hello, I am a newbie too. But by your configuration info, you have mySQL rdbms = installed. Currently, sql-ledger only works with PostgreSQL (free open source also)= . DBD-Pg is an "interface" to PostgreSQL. As you try to execute a login into the database also, you fail because=20 PosgreSQL is simply not installed. I guess that if you install www.postgresql.org you will get all up and=20 running. There are rpm and other packages formats around. Good luck. Andre Felipe |
|
From: Dr. R. J. M. <bo...@ho...> - 2001-07-24 19:11:37
|
Andre, Thank you for your response. I hope that with the following and your successful installation as reference you can help me solve my problem. > Currently, sql-ledger only works with PostgreSQL (free open source also). > DBD-Pg is an "interface" to PostgreSQL. I am using PostgreSQL and DBD-Pg. ---- > rpm -qi postgres DBD-Pg | grep Version ---- Version : 6.5.1 Vendor: SuSE GmbH, Nuernberg, Germany Version : 0.73 Vendor: (none) ---- > rpm -qi postgres DBD-Pg | grep Version ---- I created the ledgerdemo database for the sql-ledger installation. ---- > psql -l ---- datname |datdba|encoding|datpath ----------+------+--------+---------- template1 | 26| 0|template1 ledgerdemo| 26| 0|ledgerdemo (2 rows) ---- > psql -l ---- ---- > psql ledgerdemo ---- ... ledgerdemo=> select * from tax; chart_id|rate|number --------+----+------ 10067|0.07| 10056|0.08| (2 rows) ---- > psql ledgerdemo ---- I think that postgreSQL is listening, but I don't know the correct format. ---- > telnet localhost 5432 ---- Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. SELECT * FROM tax; Connection closed by foreign host. ---- > telnet localhost 5432 ---- Unfortunately, my reading of the data at http://www.postgresql.org/ has not helped so far. Thanks again in advance, -- Dr. Robert J. Meier Custom Tools mailto:rob...@co... |
|
From: Steve D. <sd...@sw...> - 2001-07-25 03:40:32
|
I hope this helps those having problems. Fact is, it's not real easy to tell what someone may have done wrong, but I think if all of the below works, you should be set. Installation and configuration is distribution specific and I'll defer some things here to source/distro documentation. If anyone wants to help fill in the blanks or make this prettier, maybe it will make a nice troubleshooting guide that could be distributed with the code. If you don't know you're ok on each of these steps, there is no sense going further, because things won't work. Step 1. Are the following programs installed? 1 - Perl, 5+ (depends on DBI version) 2 - http server (Apache, dnhttpd, NCSA, httpi, ...) 3 - SQL Server with transaction support (PostgreSQL 6.5+, ...) 4 - DBD (DBD-Pg, ...) 5 - DBI 6 - Sql-ledger (unpack at DocumentRoot from Step 4.) If yes, go to step 2., else, install them and proceed. Step 2. Are the required programs running? issue command: ps aux you should see similar lines to the following in with the rest of the output USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND postgres xxx 0.0 0.1 5616 348 ? S Jul15 0:04 /usr/lib/postgres root xxx 0.0 0.7 3720 1384 ? S Jul15 0:05 /usr/sbin/apache If yes, go to step 3., else start them and check your startup scripts if you want them to start on boot and proceed. Step 3. Is postgres configured for tcp/ip connectivity? issue command: psql -h 127.0.0.1 -d template1 if you get the prompt; template1=# you are connected to template1 thru the localhost with tcp/ip - go to step 4. else configure postgres for tcp/ip connectivity (see docs), or check that you haven't removed the localhost from your system (I bellieve all distro's ship with localhost enabled) and proceed. Step 4. Is Apache's httpd.conf configured properly? Adjust for web servers other than Apache as appropriate. Main lines (see http://httpd.apache.org/docs/mod/directives.html for more info on Apache's runtime directives) #Tells Apache the VALID DNS server name for your web server (this could also be "127.0.0.1" or "localhost"). ServerName www.sql-ledger.com #This directive sets the directory from which httpd will serve files. Unless matched by a directive like Alias, the #server appends the path from the requested URL #to the document root to make the path to the document. Example (note NO trailing /). This points requests for #http://www.sql-ledger.com to /usr/local/www DocumentRoot /usr/local/www #tells Apache that perl scripts are executables AND to execute them AddHandler cgi-script .pl #opens document root to public and redirects requests for files in sql-ledger/ to the files #in/usr/local/www/sql-ledger/. The "Directory" should be Apache's DocumentRoot with sql-ledger appended to #the end (Note NO trailing / again). Alias /sql-ledger/ /usr/local/www/sql-ledger/ <Direcory /usr/local/www/sql-ledger> Options ExecCGI Includes FollowSymlinks </Directory> Now type in the server name from above into your browser location like below: http://www.sql-ledger.com and you should see index.html in your browser, or a directory listing of DocumentRoot if index.html doesn't exist in that directory. If that works, go to step 5, else correct Apache (or other web server) config and proceed. Step 5. Are permissions set correctly? Sql-Ledger should unpack with the appropriate permissions except you want to change users as below chmod 777 users templates chmod 666 users/members If you've got everything working here step by step, you should be installed and ready to create the db and visit admin and login per the bottom of the installation instructions (see http://www.sql-ledger.com/source/readme.txt). It seems like most breakdowns are occuring somewhere in these first five steps, so I hope this helps. Please let me know if I've overlooked anything or sql-ledger still doesn't work if you've gone through these steps. Good luck! Steve |
|
From: <ke...@dk...> - 2001-07-25 15:52:18
|
Maybe we should make a script to detect if there are any problems in the installation, and then report ways to remedy them keld On Tue, Jul 24, 2001 at 11:57:25PM -0500, Steve Doerr wrote: > I hope this helps those having problems. Fact is, it's not real easy to tell > what someone may have done wrong, but I think if all of the below works, you > should be set. > > Installation and configuration is distribution specific and I'll defer some > things here to source/distro documentation. > > If anyone wants to help fill in the blanks or make this prettier, maybe it > will make a nice troubleshooting guide that could be distributed with the > code. > > If you don't know you're ok on each of these steps, there is no sense going > further, because things won't work. > > Step 1. Are the following programs installed? > 1 - Perl, 5+ (depends on DBI version) > 2 - http server (Apache, dnhttpd, NCSA, httpi, ...) > 3 - SQL Server with transaction support (PostgreSQL 6.5+, ...) > 4 - DBD (DBD-Pg, ...) > 5 - DBI > 6 - Sql-ledger (unpack at DocumentRoot from Step 4.) > > If yes, go to step 2., else, install them and proceed. > > Step 2. Are the required programs running? > issue command: > ps aux > > you should see similar lines to the following in with the rest of the output > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > postgres xxx 0.0 0.1 5616 348 ? S Jul15 > 0:04 /usr/lib/postgres > root xxx 0.0 0.7 3720 1384 ? S > Jul15 0:05 /usr/sbin/apache > > If yes, go to step 3., else start them and check your startup scripts if you > want them to start on boot and proceed. > > Step 3. Is postgres configured for tcp/ip connectivity? > issue command: > psql -h 127.0.0.1 -d template1 > > if you get the prompt; > template1=# > you are connected to template1 thru the localhost with tcp/ip - go to step 4. > else > configure postgres for tcp/ip connectivity (see docs), or check that you > haven't removed the localhost from your system (I bellieve all distro's ship > with localhost enabled) and proceed. > > Step 4. Is Apache's httpd.conf configured properly? Adjust for web servers > other than Apache as appropriate. > Main lines (see http://httpd.apache.org/docs/mod/directives.html for more info > on Apache's runtime directives) > > #Tells Apache the VALID DNS server name for your web server (this could also > be "127.0.0.1" or "localhost"). > ServerName www.sql-ledger.com > > #This directive sets the directory from which httpd will serve files. Unless > matched by a directive like Alias, the #server appends the path from the > requested URL > #to the document root to make the path to the document. Example (note NO > trailing /). This points requests for #http://www.sql-ledger.com to > /usr/local/www > DocumentRoot /usr/local/www > > #tells Apache that perl scripts are executables AND to execute them > AddHandler cgi-script .pl > > #opens document root to public and redirects requests for files in sql-ledger/ > to the files #in/usr/local/www/sql-ledger/. The "Directory" should be > Apache's DocumentRoot with sql-ledger appended to #the end (Note NO trailing / > again). > Alias /sql-ledger/ /usr/local/www/sql-ledger/ > <Direcory /usr/local/www/sql-ledger> > Options ExecCGI Includes FollowSymlinks > </Directory> > > Now type in the server name from above into your browser location like below: > http://www.sql-ledger.com > and you should see index.html in your browser, or a directory listing of > DocumentRoot if index.html doesn't exist in that directory. > > If that works, go to step 5, > else correct Apache (or other web server) config and proceed. > > Step 5. Are permissions set correctly? > Sql-Ledger should unpack with the appropriate permissions except you want to > change users as below > > chmod 777 users templates > chmod 666 users/members > > If you've got everything working here step by step, you should be installed > and ready to create the db and visit admin and login per the bottom of the > installation instructions (see http://www.sql-ledger.com/source/readme.txt). > > It seems like most breakdowns are occuring somewhere in these first five > steps, so I hope this helps. > > Please let me know if I've overlooked anything or sql-ledger still doesn't > work if you've gone through these steps. > > Good luck! > Steve > > > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X