Troubleshooting
Both cue-semantic-enrichment-service
and
cue-semantic-feedback-service
service maintain error
logs:
/var/log/escenic/cue-semantic-enrichment-service.log
/var/log/escenic/cue-semantic-feedback-service.log
If one of the services is not running properly, check the appropriate log file for hints.
For the enrichment service, you can control logging levels by changing
the settings in
/etc/escenic/cue-semantic-enrichment-service/cue-semantic-enrichment-service.yaml
:
logging: level: INFO loggers: io.dropwizard: INFO com.escenic.semantic : INFO appenders: - type: file currentLogFilename: /var/log/escenic/cue-semantic-enrichment-service.log archivedLogFilenamePattern: /var/log/escenic/cue-semantic-enrichment-service-%d.log.gz archivedFileCount: 5 timeZone: UTC
For the feedback service, you can configure extra logging by adding a
$log
property to
/etc/escenic/cue-semantic-feedback-service/Agent.properties
:
$log = INFO
The feedback service also maintains a state file,
/var/lib/escenic/cue-semantic-feedback-service.state.properties
.
This state file stores the current position in the change log. If you
want to restart from the beginning, remove this file.
In the case where a service fails completely and doesn't even start,
no log file will be generated. In this case, check the system log
/var/log/syslog
. This can happen, for example, if
there is a typo in the enrichment service configuration file,
cue-semantic-enrichment-service.yaml
.