This list of FAQs contains common questions and problems during installation on various platforms. If something is not working as expected, in most cases the logs tell what is going wrong.

Where can I find detailed logs?

Linux

MongoDB: As provided with the logpath key in the mongodb config
Dashboard: /opt/aom-dashboard/site/apiomat/log/application.log
Tomcat/YAMBAS: /var/log/tomcat/

Windows

MongoDB: As provided with the logpath key in the mongodb config
The locations of the other logfiles are linked in one single place: C:\Program Files\ApiOmat\logs. The links go to:
- C:\tomcat7\logs ("CONSOLE" appender / standard output logs here)
- C:\Users\YourUser\AppData\Local\ApiOmat\logs ("FILE" appender logs here)
- C:\Apache24\logs
- C:\Apache24\htdocs\dashboard\apiomat\log
To read the logs in a continuous way (show new lines automatically), use the PowerShell cmdlet Get-Content with the "-wait" parameter
- For example: gc .\catalina.out -tail 100 -wait

YAMBAS startup setups with error message "license server not available"

This commonly occurs when the installation hosts traffic is blocked to the license server. Please ask support for a offline license key and provide the hardware ID printed out during startup of YAMBAS in tomcat logs.

Dashboard login does not work, no incoming request is logged on YAMBAS

Please check your hostname settings in yambas.conf and try to run a curl command against the hostname, like

curl http://localhost:8080/yambas/rest

Images are not properly displayed in Dashboard

Please see "Dashboard login does not work, no incoming request is logged on YAMBAS"

AH02018: request body exceeds maximum size (xxxxx) for SSL buffer

Go to your SSL configuration and adjust <Location /dashboard>:

SSLRenegBufferSize 10486000

SSL certificate problem: unable to get local issuer certificate' in /opt/aom-dashboard/site/apiomat/protected/extensions/EActiveResource/EActiveResourceRequest.php:542

Please check your certificates. The error "unable to get local issuer certificate" indicates that the CA-certificate (or one of the certs in the chain) couldn't be verified. Try to investigate the error with the command:

openssl s_client -connect host:port

With that you can inspect more in detail where the problem is. The problem should be that the CA-certificate is missing on the server system. Download the correct CA-certificate file (the output of the command should tell you which one you'll need) from the homepage of your CA and add it to /usr/local/share/ca-certificates and then run

sudo update-ca-certificates

error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

Please check your yambas.host configuration in the yambas.conf. Can you reach the specified server with curl on the command line? The error indicates that you're trying to connect to a wrong port (most common: you're trying to establish a HTTPS connection on the HTTP-Port)

curl https://localhost:8443/yambas/rest

403 during yum or apt update

Please check your package manager. Are the packages sources mirrored? Our installation packages have been added? You can ask the admin or the data center.

Internal Server Error SSL received a record that exceeded the maximum permissible length.

Try the following: Disable useSsl in yambas.conf (useSsl=false)

All users can read the data of other users. Is this a security hole?

No. 1) This only applies to the basics.User class with the default module configuration. 2) You can either create a subclass and modify the access rules, or change the configuration of the module "Basics" accordingly (see Basic Module).