...
| Component | What is affected | Path/File |
|---|---|---|
| TomCat | If the windows service "diagserver" (Displayname: "custo diagnostic server (Apache Tomcat Server) diagserver") does not start. | Path: "C:\Program Files\custo diagnostic server\logs" |
| MariaDB | If the windows service "diagserverdb" (Displayname: "MariaDB for custo diagnostic server") does not start. | Path: "C:\diagserverdata\mariadb" |
| H2 Database | The H2 Database is an Tomcat integrated database. You will find all logged events in the Tomcat log files. | |
| MS SQL Database | Problems with Microsoft SQL Server or of the databases inside of the SQL Server you can find in the logging tool of the SQL Server. | |
custo diagnostic server | If evaluations are not found, if they cannot be saved, if there are problems exporting evaluations. | Path: "C:\diagserverdata\log" File: "diagserver.log" or outdated and compressed: "diagserver-<DATE>-<TIME>.log.gz" |
custo diagnostic client | If the client crashes, there are faults with the device connection or a certain program sequence is disrupted. Activities in the service center are also logged here. Each program (GUI) has his own log file. | Path: "C:\Users\Public\Roaming\customed" File: "<DATE>.<TIME>.customanager.log" File: "<DATE>.<TIME>.servicecenter.log" File: "<DATE>.<TIME>.custodiagnosticclient.log" |
In most support cases custo med will need the client logs, the custo diagnostic server logs, the TomCat logs and the MariaDB logs. Please best grab all of those logs and ZIP them. If the compressed size is below 20 MB you may attach them to an email. If the size is bigger upload them to a cloud service like the custo med NextCloud service and send a link. Please give also a hint when the relevant problems occurred.
Detailed Information
Client
...
custo diagnostic server is based on Apache Tomcat 8.0 . Please rever refer to the Tomcat Logging functionality at "https://tomcat.apache.org/tomcat-89.0-doc/logging.html".
Additionally the "diagserver" Application in the Tomcat creates two Logfiles in the starting pahse phase of the application:
"diagserver-stderr.YYYY-MM-DD.log"
"diagserver-stdout.YYYY-MM-DD.log"
...