Menu
▾
▴
sql-ledger-users
|
From: Lenny L. <lle...@ma...> - 2007-01-23 22:26:32
|
Check the permissions on the users directory and make sure the apache user/group has access (rwx). -- Lenny Leblanc =20 628 Leila Avenue Winnipeg, Manitoba R2V 3N7 P: 204.338.0233 =20 -----Original Message----- From: sql...@li... [mailto:sql...@li...] On Behalf Of Rich Shepard Sent: Tuesday, January 23, 2007 4:20 PM To: sql...@li... Subject: [SL] Permissions Error I recently upgraded my system and now get this error when I try to log in: Error! users/rshepard.conf : Permission denied What should be the ownership and permissions on /usr/local/sql-ledger/users? It's owned by nobody.nogroup and had perms of 755. I changed those to 777 but to no avail. Thanks, Rich --=20 Richard B. Shepard, Ph.D. | The Environmental Permitting Applied Ecosystem Services, Inc. | Accelerator(TM) <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863 ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDE V _______________________________________________ sql-ledger-users mailing list sql...@li... https://lists.sourceforge.net/lists/listinfo/sql-ledger-users |
|
From: Rich S. <rsh...@ap...> - 2007-01-23 22:41:30
|
On Tue, 23 Jan 2007, Lenny Leblanc wrote: > Check the permissions on the users directory and make sure the apache > user/group has access (rwx). Lenny, That's what I tried. /usr/local/sql-ledger/users has permissions 777 (rwxrwxrwx). The files in that directory -- specifically rshepard.conf -- is owned by me and has 755 permissions (rwxr-xr-x). /usr/local/sql-ledger is owned by root.root with 755 permissions. This is a new one on me. Thanks, Rich -- Richard B. Shepard, Ph.D. | The Environmental Permitting Applied Ecosystem Services, Inc. | Accelerator(TM) <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863 |
|
From: Rich S. <rsh...@ap...> - 2007-01-23 22:43:30
|
On Tue, 23 Jan 2007, Rich Shepard wrote: > That's what I tried. /usr/local/sql-ledger/users has permissions 777 > (rwxrwxrwx). The files in that directory -- specifically rshepard.conf -- > is owned by me and has 755 permissions (rwxr-xr-x). /usr/local/sql-ledger > is owned by root.root with 755 permissions. I also forgot to write that immediately after upgrading sql-ledger from -2.6.21 to -2.6.22 I logged in to ensure that the application upgrade caused no problems. Rich -- Richard B. Shepard, Ph.D. | The Environmental Permitting Applied Ecosystem Services, Inc. | Accelerator(TM) <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863 |
|
From: Ashley J G. <sql...@pu...> - 2007-01-24 03:43:43
|
Hi Rich, In the doc subdirectory you will find instructions for each version's upgrade. Essentially the bit you need to do is (do this from the root of your sl install, eg /usr/local/sql-ledger/): 2. fix permissions # chown -hR nobody:nogroup * # chmod 711 templates users css spool Note: replace nobody:nogroup with your web server user and group So if apache runs as "apache" then you do chown -hR apache:apache * Ultimately I think your problem is that the config file is owned by yourself, not apache, but you'll have other issues if you don't fix the whole lot by doing to two steps above (note that the first step sets ownership recursively, so will include your conf file etc). -- Regards, Ashley J Gittins web: http://www.purple.dropbear.id.au jabber: agi...@pu... On Wednesday 24 January 2007 08:43, Rich Shepard wrote: > On Tue, 23 Jan 2007, Rich Shepard wrote: > > That's what I tried. /usr/local/sql-ledger/users has permissions 777 > > (rwxrwxrwx). The files in that directory -- specifically rshepard.conf -- > > is owned by me and has 755 permissions (rwxr-xr-x). /usr/local/sql-ledger > > is owned by root.root with 755 permissions. > > I also forgot to write that immediately after upgrading sql-ledger from > -2.6.21 to -2.6.22 I logged in to ensure that the application upgrade > caused no problems. > > Rich |
|
From: Rich S. <rsh...@ap...> - 2007-01-24 04:33:13
|
On Wed, 24 Jan 2007, Ashley J Gittins wrote: > In the doc subdirectory you will find instructions for each version's > upgrade. Essentially the bit you need to do is (do this from the root of your > sl install, eg /usr/local/sql-ledger/): > > 2. fix permissions > # chown -hR nobody:nogroup * > # chmod 711 templates users css spool Ashley, Well, I missed that because permissions were not changed in prior upgrades. > Note: replace nobody:nogroup with your web server user and group According to /etc/apache/httpd.conf, it's nobody.nobody. But, that gave me an internal server error when I tried to log in. So, I changed the group to to nogroup and now I get other access denied errors. > Ultimately I think your problem is that the config file is owned by > yourself, not apache, but you'll have other issues if you don't fix the > whole lot by doing to two steps above (note that the first step sets > ownership recursively, so will include your conf file etc). No, it's more insiduous. When I upgraded my system from Slackware-10.2 to -11.0 a bunch of perl modules went missing for some reason. So, I took a look at /var/log/apache/error_log and saw this: [root@salmo ~]# tail -f /var/log/apache/error_log at SL/User.pm line 117 Compilation failed in require at /usr/local/sql-ledger/login.pl line 99. [Tue Jan 23 20:17:59 2007] [error] [client 127.0.0.1] Premature end of script headers: /usr/local/sql-ledger/login.pl install_driver(Pg) failed: Can't locate DBD/Pg.pm in @INC (@INC contains: /usr/lib/perl5/5.8.8/i486-linux /usr/lib/perl5/5.8.8 /usr/lib/perl5/site_perl/5.8.8/i486-linux /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl .) at (eval 10) line 3. Perhaps the DBD::Pg perl module hasn't been fully installed, or perhaps the capitalisation of 'Pg' isn't right. Available drivers: DBM, ExampleP, File, Proxy, Sponge, mysql. at SL/User.pm line 117 Compilation failed in require at /usr/local/sql-ledger/login.pl line 99. [Tue Jan 23 20:20:42 2007] [error] [client 127.0.0.1] Premature end of script headers: /usr/local/sql-ledger/login.pl Unfortunately, trying to re-install DBD::Pg fails because one or more tests fail. I need to contact a perl expert to learn how to overcome that. >From the log, it appears that when I get the module re-installed I'll be able to log in. If not, I'll be back. :-) Many thanks, Rich -- Richard B. Shepard, Ph.D. | The Environmental Permitting Applied Ecosystem Services, Inc. | Accelerator(TM) <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863 |
|
From: Dieter S. <dsi...@sq...> - 2007-01-24 06:04:16
|
On Tue, 23 Jan 2007 20:32:42 -0800 (PST), Rich Shepard wrote > On Wed, 24 Jan 2007, Ashley J Gittins wrote: > > Unfortunately, trying to re-install DBD::Pg fails because one or more > tests fail. I need to contact a perl expert to learn how to overcome > that. if you compile as root you run into a problem during the test phase because root cannot connect to the postgres server. ignore the error and proceed with 'make install'. It works even though the tests failed. Dieter Simader |
|
From: Rich S. <rsh...@ap...> - 2007-01-24 14:32:01
|
On Tue, 23 Jan 2007, Dieter Simader wrote: > if you compile as root you run into a problem during the test phase > because root cannot connect to the postgres server. ignore the error and > proceed with 'make install'. It works even though the tests failed. Dieter, I tried forcing the installation, but still saw server errors when I tried to log in. Since the .cpan directory is root's I'll grab the module tarball and install it manually. Stay tuned for further reports. :-) Thanks, Rich -- Richard B. Shepard, Ph.D. | The Environmental Permitting Applied Ecosystem Services, Inc. | Accelerator(TM) <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863 |
|
From: Jason R. <jas...@gm...> - 2007-01-23 22:51:41
|
On Tuesday 23 January 2007 17:41, Rich Shepard wrote: > That's what I tried. /usr/local/sql-ledger/users has permissions 777 > (rwxrwxrwx). The files in that directory -- specifically rshepard.conf -- > is owned by me and has 755 permissions (rwxr-xr-x). /usr/local/sql-ledger > is owned by root.root with 755 permissions. Check the permissions of the apache process: ps auxww |grep httpd or ps auxww |grep apache The files in that directory should be writable by that user. |
|
From: Rich S. <rsh...@ap...> - 2007-01-24 18:47:50
|
On Tue, 23 Jan 2007, Jason Rodrigues wrote: > Check the permissions of the apache process: > ps auxww |grep httpd > or > ps auxww |grep apache > The files in that directory should be writable by that user. Hi, Jason! After a lot of hard work, I've turned this into a postgres problem. I had some crufty old libpq.so in /usr/local/lib/ from 2003 and 2004. So I got rid of those, ran 'ldconfig,' retarted httpd and postgresql. Oops! The latter didn't start. That's what /var/log/apache/error_log says, too. I broke something in postgres. While '/etc/rc.d/rc.postgesql start' reports 'OK,' '/etc/rc.d/rc.postgresql status' reports 'pg_ctl: neither postmaster nor postgres running.' I made sym links from /usr/lib/libpq.so* to /usr/local/lib/, but that hasn't helped. Now it's time to ask the fine folks on the postgres mail list for help. Thanks, Rich -- Richard B. Shepard, Ph.D. | The Environmental Permitting Applied Ecosystem Services, Inc. | Accelerator(TM) <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863 |
|
From: Rich S. <rsh...@ap...> - 2007-01-25 02:13:20
|
On Tue, 23 Jan 2007, Jason Rodrigues wrote: > Check the permissions of the apache process: Found and fixed the problem. To summarize where we left off at the last reel, during my distribution upgrade a bunch of perl modules went AWOL. Today I grabbed the source for DBD::Pg-1.49, built, and installed it. Then I started looking at the libpq.so libraries and discovered the old stuff in /usr/local/lib/ I removed them. But, this was after I built DBD::Pg. That's why when 'ldd Pg.pm' reported using libpq.so.3 I thought nothing of it. There's a more recent /usr/lib/libpq.so.3.1. That's not the one to which the perl module pointed. So, a repeat performance of 'perl Makefile.PL, make, make test, and make install' recreated DBD::Pg with the proper library. Now, SQL-Ledger lets me log in. Whew! Two down, two to go. Rich -- Richard B. Shepard, Ph.D. | The Environmental Permitting Applied Ecosystem Services, Inc. | Accelerator(TM) <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863 |
|
From: Rich S. <rsh...@ap...> - 2007-01-24 21:21:36
|
On Wed, 24 Jan 2007, Rich Shepard wrote:
> I tried forcing the installation, but still saw server errors when I
> tried to log in. Since the .cpan directory is root's I'll grab the module
> tarball and install it manually.
> Stay tuned for further reports. :-)
I now have the latest release (1.49) of DBD::Pg installed. Postgres is
idling away in the background. But, when I try to log into SL I get a server
error.
[Wed Jan 24 11:46:58 2007] [error] [client 127.0.0.1] Premature end of
script headers: /usr/local/sql-ledger/login.pl
/usr/local/sql-ledger/login.pl: symbol lookup error:
/usr/lib/perl5/site_perl/5.8.8/i486-linux/auto/DBD/Pg/Pg.so: undefined symbol: PQserverVersion
[Wed Jan 24 13:14:12 2007] [error] [client 127.0.0.1] Premature end of
script headers: /usr/local/sql-ledger/login.pl
The library symbol error is not reported for the latest attempt.
A Google search for 'PQserverVersion' yields 1,830 hits for postgres bug
#2701. But, further checking reveals that the installed libpq.so* are
sufficiently new:
lrwxrwxrwx 1 root root 12 2006-07-06 17:19 /usr/lib/libpq.so ->
libpq.so.4.1*
lrwxrwxrwx 1 root root 12 2006-01-27 10:22 /usr/lib/libpq.so.3 ->
libpq.so.3.1*
-rwxr-xr-x 1 root root 110586 2006-01-26 09:49 /usr/lib/libpq.so.3.1*
lrwxrwxrwx 1 root root 12 2006-07-06 17:19 /usr/lib/libpq.so.4 ->
libpq.so.4.1*
-rwxr-xr-x 1 root root 111532 2006-05-24 15:06 /usr/lib/libpq.so.4.1*
My perl installation and modules appear to be current, appropriate, and
correct. Postgres-8.1.4 has been working with SL before. I'm being pointed
in circles, and I don't know just where the problem really is. But, getting
SL working again is critical for me.
Rich
--
Richard B. Shepard, Ph.D. | The Environmental Permitting
Applied Ecosystem Services, Inc. | Accelerator(TM)
<http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863
|
|
From: Rich S. <rsh...@ap...> - 2007-01-24 23:58:10
|
On Wed, 24 Jan 2007, Rich Shepard wrote:
> I now have the latest release (1.49) of DBD::Pg installed. Postgres is
> idling away in the background. But, when I try to log into SL I get a
> server error.
> lrwxrwxrwx 1 root root 12 2006-07-06 17:19 /usr/lib/libpq.so ->
> libpq.so.4.1*
> lrwxrwxrwx 1 root root 12 2006-01-27 10:22 /usr/lib/libpq.so.3 ->
> libpq.so.3.1*
> -rwxr-xr-x 1 root root 110586 2006-01-26 09:49 /usr/lib/libpq.so.3.1*
> lrwxrwxrwx 1 root root 12 2006-07-06 17:19 /usr/lib/libpq.so.4 ->
> libpq.so.4.1*
> -rwxr-xr-x 1 root root 111532 2006-05-24 15:06 /usr/lib/libpq.so.4.1*
More information that I hope helps someone to point me toward a fix for
this problem:
> Method 1: Find the .so module that perl uses (try locate Pg.so and ldd
> that).
/lib/libsafe.so.2 (0xb7f76000)
linux-gate.so.1 => (0xffffe000)
libpq.so.3 => /usr/lib/libpq.so.3 (0xb7f5f000)
libc.so.6 => /lib/tls/libc.so.6 (0xb7e1a000)
libdl.so.2 => /lib/tls/libdl.so.2 (0xb7e16000)
libcrypt.so.1 => /lib/tls/libcrypt.so.1 (0xb7de8000)
libresolv.so.2 => /lib/tls/libresolv.so.2 (0xb7dd4000)
libnsl.so.1 => /lib/tls/libnsl.so.1 (0xb7dbd000)
/lib/ld-linux.so.2 (0x80000000)
So it's finding all the libraries it wants, and it's using the older
libpq.so. Interesting.
I open a new firefox tab and open http://localhost/sql-ledger/login.pl.
After entering my username and password and pressing [Enter] I get an
internal server error:
"The server encountered an internal error or misconfiguration and was unable
to complete your request.
"Please contact the server administrator, rsh...@ap... and inform
them of the time the error occurred, and anything you might have done that
may have caused the error.
"More information about this error may be available in the server error
log."
The log file (/var/log/apache/error_log) shows:
[Wed Jan 24 15:01:20 2007] [error] [client 127.0.0.1] Premature end of
script headers: /usr/local/sql-ledger/login.pl
Also, I installed 2.6.23 over 2.6.22; VERSION reports 2.6.23. But, when I
load login.pl it's the old version number that displays.
I seem to be going in circles here.
Rich
--
Richard B. Shepard, Ph.D. | The Environmental Permitting
Applied Ecosystem Services, Inc. | Accelerator(TM)
<http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863
|
×
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