This content has been marked as final. Show 1 reply
you might want to take a look at your process.0.log (Endeca\PlatformServices\Workspace\Logs....)
and if you want to have more logs from your Dgraph to put "-v" arg for your Dgraph Defaults in your appconfig (where you indicate the n° of threads)
Exerpt from Endeca documentation
Tomcat/Catalina logs (e.g. catalina.out, catalina.[date].log, tomcat_stdout.log) -
These logs are useful when errors occur while loading the EAC or Workbench. For example,
if the context configuration for EAC specifies the wrong path for the EAC WAR file, an error
will occur when starting the Endeca HTTP Service and will be logged in these log files.
Alternatively, a "clean" startup of the Endeca HTTP Service will result in no exceptions and a
successful output of a message like "Server startup in [n] ms."
Main log (e.g. main.0.log) - Most EAC logging goes into this log file. For example,
exceptions thrown when invoking a shell or component are logged here. I tried to invoke a
utility on a non-existent host and found an exception logged in this file: "The host 'foo' in
application 'bar' does not exist.“
Invocation log (e.g. invoke.0.log) - This file contains logs associated with EAC Web
service invocations. For example, this file will record the exact XML content of web service
requests and responses.
Logs can also be written into the sub-directories: Shell, Archive, Copy.
Messages previously logged to emgr.log in v5.1.x are now logged to webstudio.log in v6.x.
hope that helps