I managed to install a working version of dbMan which can be seen working at http://www.deadloud.com/cgi/dbman/db.cgi.

I wanted to keep the default intact, so I then went on to create a new version for use on my web site. I uploaded it to my host's server and fixed the permissions. Now, when I try to access this database at http://www.deadloud.com/cgi/dbman/db.cgi?db=bandscfg, I keep getting the internal error message and all attempts to switch on debugging have failed.

The cfg file bandscfg can be viewed at www.deadloud.com/bandscfg.txt and the HTML file I created to use with it can be seen at www.deadloud.com/bandshtml.txt

I'd very much appreciate any help anyone can offer.

Thanks.
Phil.

1) Turn on de-bugging.



in the default.cfg file.

2) Then post the EXACT error messages you receive.

You can also do the following:

1) CHECK your SERVER LOGS (no, not the default.log file in the DBMAN directory, but your SERVER ERROR LOG FILES).

2) Check the syntax of the db.cgi using the following command line via telnet:



Then post the syntax errors.

Regards,

Eliot Lee

Hi Eliot.

I tried turning debug on (again), but to no avail. I still only get a line in the browser indicating internal error and requesting that I switch on debug. Looking through this forum, I see that it's sometimes suggested to switch on debug by adding an additional line in the db.cgi also. Well I tried that as well and that didn't work either. I have posted the new cfg (with debug on) at http://www.deadloud.com/bandscfg.txt.

I syntax checked the db.cgi through telnet at my host's server and it syntax checked ok.

One thing shouldn't $db_dir_url be like this:


# URL of the directory dbman resides in. No Trailing Slash Please.
$db_dir_url = "http://www.jpdeni.com/cgi-bin/relation";


You have uploaded all the dbman files to your dbman directory and given them the correct permissions haven't you?

I suggest you post links to all your database files.

Thanks Philip, but if that's the case, why does the default database work ok without specifying the full URL. I have uploaded all the required files for establishing a 2nd and subsequent database AND given them the correct permissions. The real issue is that I can't get debug to run, so I can't see the exact error that dbman is objecting to.

Ok. I've found with my database that if I have a really serious error it won't display the debug information.

Eliot or someone else will hopefully have a solution for you.

Open up db.cgi and add the line $db_debug = 1; under the line $db_script_path = '.';

That should force the debugging error message.

- Mark


Astro-Boy!!
http://www.zip.com.au/~astroboy/

Thanks Mark.
I had already tried that but it didn't work before. Anyway it did this time and the problem seems to be with loading the libs. I've checked all the permissions of the files and they look ok. You can see the error at http://www.deadloud.com/cgi/dbman/db.cgi?db=bandscfg

It seems to be working fine now...I was able to login to your DBMAN.

To remove the de-bugging info at the bottom of the page, simply set the $db_debug variable to 0 in the default.cfg file:



And BTW, I just gave an explanation of using de-bugging two days ago in this forum. If you want more information, search for db_debug in this forum using All posts for the date range in the forum search form.

Regards,

Eliot Lee

Hi Eliot.
did you use the following link to check this out
http://www.deadloud.com/cgi/dbman/db.cgi?db=bandscfg ....
because it still gives me the CGI Error message when I try it.
Phil.

Cancel that last post. It s working now that I've removed the debug. Many thanks for everyone's help here. Best support forum I've encountered.

Phil.