Lucee does nto seemt o be writing to logs

New to Lucee and am presently transferring some legacy CFML apps to a new
Lucee Server on
WindowServer 2012 with IIS8.

While all apps seem to be working I cannto seem to force an error to show
up or get logged.
Anytime there should be soem kind of error I only see the native IIS 500
error page and nothing
gets sent to /lucee/tomcat/webapps/ROOT/WEB-INF/lucee/logs/exception.log

have been experimenting all day on the admin/server.cfm in both the
settings-error pages
and the logging pages.Any assistance appreciated.

Look in C:\lucee\tomcat\logs.–
Kind regards,
Jordan Michaels
Vivio Technologies

----- Original Message -----
From: “Shinpei Kuga” <@Shinpei_Kuga>
To: “Lucee” lucee@googlegroups.com
Sent: Wednesday, September 14, 2016 2:44:43 PM
Subject: [Lucee] Lucee does nto seemt o be writing to logs

New to Lucee and am presently transferring some legacy CFML apps to a new
Lucee Server on
WindowServer 2012 with IIS8.

While all apps seem to be working I cannto seem to force an error to show
up or get logged.
Anytime there should be soem kind of error I only see the native IIS 500
error page and nothing
gets sent to /lucee/tomcat/webapps/ROOT/WEB-INF/lucee/logs/exception.log

have been experimenting all day on the admin/server.cfm in both the
settings-error pages
and the logging pages.Any assistance appreciated.


Get 10% off of the regular price for this years CFCamp in Munich, Germany (Oct. 20th & 21st) with the Lucee discount code Lucee@cfcamp. 189€ instead of 210€. Visit https://ti.to/cfcamp/cfcamp-2016/discount/Lucee@cfcamp

You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/2e9dad77-9698-44c7-8f80-b8eeb79aea3f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Apologies I mean the logging configuration
(under the the CFADmin UI lefnav in Logging)On Friday, September 16, 2016 at 11:09:18 AM UTC-4, Shinpei Kuga wrote:

Much thanks but these do seem to be a different kind of logs tahn teh oens
that would be in
/lucee/tomcat/webapps/ROOT/WEB-INF/lucee/logs/exception.log

Nor does the logs under tomcat seem to describe ant CFe rrors or be
configurable from the CFAdmin
interface (under error in the left nav)

Much thanks but these do seem to be a different kind of logs tahn teh oens
that would be in
/lucee/tomcat/webapps/ROOT/WEB-INF/lucee/logs/exception.log

Nor does the logs under tomcat seem to describe ant CFe rrors or be
configurable from the CFAdmin
interface (under error in the left nav)

If you’re using IIS in a development/test environment (not public facing
production) then under Settings -> Error you can make the following changes:

Set the 500 and 404 error templates to error.cfm (from the default of
error-public.cfm) and untick the Status Codes checkbox which will always
return 200, bypassing IIS’s handling of errors and returning the infamous
IIS 500 error page.

That will, at the very least, get you visible errors on-screen while
developing. DO NOT do this in production, however, as it’s a big security
risk and will disclose information about your environment that hackers just
don’t need to know :slight_smile:

For logging, go to Settings -> Logging and click the edit link next to any
log (exception, for example) - from there you can change the log level (set
to INFO by default) to DEBUG or, if you really want to punish your server
then set it to TRACE. Levels of logging go from TRACE (the most verbose,
logging everything) to FATAL (the least verbose, logging only fatal
errors).

Much thanks this was for a test staging server for developers so yes I
wanted to see and log errors

Much thanks for al the config info.On Saturday, September 17, 2016 at 2:09:40 PM UTC-4, Denard Springle wrote:

If you’re using IIS in a development/test environment (not public facing
production) then under Settings -> Error you can make the following changes:

Set the 500 and 404 error templates to error.cfm (from the default of
error-public.cfm) and untick the Status Codes checkbox which will always
return 200, bypassing IIS’s handling of errors and returning the infamous
IIS 500 error page.

That will, at the very least, get you visible errors on-screen while
developing. DO NOT do this in production, however, as it’s a big security
risk and will disclose information about your environment that hackers just
don’t need to know :slight_smile:

For logging, go to Settings -> Logging and click the edit link next to any
log (exception, for example) - from there you can change the log level (set
to INFO by default) to DEBUG or, if you really want to punish your server
then set it to TRACE. Levels of logging go from TRACE (the most verbose,
logging everything) to FATAL (the least verbose, logging only fatal
errors).

From here you can also set the location for the logs
({lucee-config}/logs/exception.log by default for the exception log) and
select a logging template if you want. Classic is similar to the ACF log
format, but you can also choose pattern and specify what you want to see
logged, or XML or HTML if you’d rather use them for logging purposes.

They key here is going to be the log level however, you shouldn’t really
need to change anything else unless you have specific requirements you want
to use to override the defaults.

HTH

– Denny

Denard,

How do you get Lucee to display application logs like in the Coldfusion
Administrator? When specific errors and line number references.

Thank you,

DaleOn Saturday, September 17, 2016 at 11:09:40 AM UTC-7, Denard Springle wrote:

If you’re using IIS in a development/test environment (not public facing
production) then under Settings -> Error you can make the following changes:

Set the 500 and 404 error templates to error.cfm (from the default of
error-public.cfm) and untick the Status Codes checkbox which will always
return 200, bypassing IIS’s handling of errors and returning the infamous
IIS 500 error page.

That will, at the very least, get you visible errors on-screen while
developing. DO NOT do this in production, however, as it’s a big security
risk and will disclose information about your environment that hackers just
don’t need to know :slight_smile:

For logging, go to Settings -> Logging and click the edit link next to any
log (exception, for example) - from there you can change the log level (set
to INFO by default) to DEBUG or, if you really want to punish your server
then set it to TRACE. Levels of logging go from TRACE (the most verbose,
logging everything) to FATAL (the least verbose, logging only fatal
errors).

From here you can also set the location for the logs
({lucee-config}/logs/exception.log by default for the exception log) and
select a logging template if you want. Classic is similar to the ACF log
format, but you can also choose pattern and specify what you want to see
logged, or XML or HTML if you’d rather use them for logging purposes.

They key here is going to be the log level however, you shouldn’t really
need to change anything else unless you have specific requirements you want
to use to override the defaults.

HTH

– Denny

Go to the lucee admin and on the left you can see debugging and you can turn that on.

Then under templates you can assign a template to display the debug information.

If you don’t want to show it, you can view the logs under the debugging -> logs section.

HTH

Mark Drew

Denard,

How do you get Lucee to display application logs like in the Coldfusion Administrator? When specific errors and line number references.

Thank you,

Dale

On Saturday, September 17, 2016 at 11:09:40 AM UTC-7, Denard Springle wrote:
If you’re using IIS in a development/test environment (not public facing production) then under Settings -> Error you can make the following changes:

Set the 500 and 404 error templates to error.cfm (from the default of error-public.cfm) and untick the Status Codes checkbox which will always return 200, bypassing IIS’s handling of errors and returning the infamous IIS 500 error page.

That will, at the very least, get you visible errors on-screen while developing. DO NOT do this in production, however, as it’s a big security risk and will disclose information about your environment that hackers just don’t need to know :slight_smile:

For logging, go to Settings -> Logging and click the edit link next to any log (exception, for example) - from there you can change the log level (set to INFO by default) to DEBUG or, if you really want to punish your server then set it to TRACE. Levels of logging go from TRACE (the most verbose, logging everything) to FATAL (the least verbose, logging only fatal errors).

From here you can also set the location for the logs ({lucee-config}/logs/exception.log by default for the exception log) and select a logging template if you want. Classic is similar to the ACF log format, but you can also choose pattern and specify what you want to see logged, or XML or HTML if you’d rather use them for logging purposes.

They key here is going to be the log level however, you shouldn’t really need to change anything else unless you have specific requirements you want to use to override the defaults.

HTH

– Denny


You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/7c7a5a35-c5be-45e3-ba37-e7238e948a17%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.