Gossamer Forum
Home : Products : DBMan : Installation :

Log File = Premature end of script headers

Quote Reply
Log File = Premature end of script headers
This is all my log file gives me. I try and run db.cgi in
a shell using perl and it says :

DBMan encountered an internal error. Please enable debugging to view.

I have it setup as follows

cgi-bin/dbman/files*

-rw-r--r-- 1 jrelectr psacln 20256 Jul 8 2000 README.txt
drwxrwxrwx 2 jrelectr psacln 4096 Jul 8 2000 auth
-rw-r--r-- 1 jrelectr psacln 6800 Jul 8 2000 auth.pl
-rwxr-xr-x 1 jrelectr psacln 46697 Oct 8 19:42 db.cgi
-rw-r--r-- 1 jrelectr psacln 7721 Oct 8 19:30 default.cfg
-rw-rw-rw- 1 jrelectr psacln 2 Apr 3 2000 default.count
-rw-rw-rw- 1 jrelectr psacln 6736 Apr 3 2000 default.db
-rw-rw-rw- 1 jrelectr psacln 655 Jul 8 2000 default.log
-rw-rw-rw- 1 jrelectr psacln 147 Apr 3 2000 default.pass
-rw-r--r-- 1 jrelectr psacln 44424 Jul 8 2000 html.pl

And when i run in the web like this :

http://www.dssmax.org/cgi-bin/dbman/db.cgi?db=default

I get the following:

Internal Server Error


Can you help? I edited the files db.cgi to point to perl and
the file default.cfg to point to my installation dir.

What am i missing?
Quote Reply
Re: [slay] Log File = Premature end of script headers In reply to
hmmmm ....

try:

- turn off debugging
- turn off bold searches
- in db.cgi refer $db_script_path in db.cgi to your full path
- check what your dbman directory permissions are -- it's worth to look here.
- errr ... did you upload in ASCII -- well you never know.
- check for spelling mistakes in links.cfg

are you on UNIX or windows?

try some of the above ... if not please post back here again.

Good luck


openoffice + gimp + sketch ... Smile
Quote Reply
Re: [slay] Log File = Premature end of script headers In reply to
In the FAQ noted below under the section "Troubleshooting" there is a snippet of code you can add
to your script which will give you better error messages.

It's called "Debugging - How To Obtain Useful Error Messages"

There are also modifications you can make to your .cfg file which will catch errors within your .cfg file. See
"Display Debugging within .cfg file" same section of FAQ.

If you are still having problems perhaps you can post a copy of your .cfg file as a text file and provide the url to where it can be viewed.

It's only rare cases where it's necessary to modify the line you may have changed in your db.cgi file:

$db_script_path = ".";

and you should not have to change this line in your db.cgi file:

$in{'db'} ? ($db_setup = $in{'db'}) : ($db_setup = 'default');

Hope this helps


Unoffical DBMan FAQ

http://creativecomputingweb.com/dbman/index.shtml/