Support Requests item #486126, was opened at 2001-11-27 11:30
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=203152aid=486126group_id=3152
Category: Configuration: Other
Group: aolserver3_2
Status: Open
Resolution: None
Priority: 5
Submitted By: Danny Lieberman (dannyl50)
Assigned to: Kriston Rehberg (kriston)
Summary: How to debug inside ADP?
Initial Comment:
Hi
I am running aolserver 3.2 with open acs 3/posgres 7.1
For debugging, we open 2 windows: browser in window 1
and tail -f servername.log in window 2
we are doing heavy SQL/tcl development and the errors
get swallowed up in the servername.log file.
isnt there a way JUST to see the errors and not all
the GET commands?
In another installation i had with aolserver 3.1 and
acs 3.5/oracle - we had TWO (2) logs - servername.log
and servername-error.log
thx
danny
--
Comment By: Peter M. Jansson (petej)
Date: 2001-11-27 14:07
Message:
Logged In: YES
user_id=20577
In your database pool definition, set verbose=off and logsqlerrors=on. This will only
show the SQL of a query that failed.
Some folks have had luck with the TclPro debugger, available from scriptics.com, but I
haven't tried it.
There aren't facilities in AOLserver to emit the error logs separately from the rest
of the server log. The location of the server log is set by the servername parameter
of the ns/parameters section, but AOLserver will create a log file called server.log
in the log directory of the server's home before creating the named logfile. Access
logs (is this what you mean by the GET commands?) are defined in the
ns/server/${servername}/module/nslog section, with the file parameter.
--
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=203152aid=486126group_id=3152
